Forum Activity for @ultrajam

Search by _profile_ids, order by profile_id

Jamroom Developers

Thanks Michael, a new smarty function it is

Search by _profile_ids, order by profile_id

Jamroom Developers

_created does work, but lists in the order that the items are created rather than by profile.

Profile 1 creates item 10, profile 2 creates item 11, profile 1 creates item 12.

The order I want is 10, 12, 11

Search by _profile_ids, order by profile_id

Jamroom Developers

Hi, I'm using jrCore_list in a template to search by multiple _profile_ids and order by _profile_id but getting an error in the activity log "you must include the _profile_id field in your search criteria to order_by it".

I'm sure I can sort it out in the template, but should it be working, or am I just missing something obvious?

{jrCore_list module="ujStatement" search="_profile_id in `$_user['user_linked_profile_ids']`" order_by="_profile_id numerical_asc" template="list.tpl" tpl_dir="ujManager"}

From the activity log:

Array
(
[0] => error: you must include the _profile_id field in your search criteria to order_by it
[1] => ujStatement
[2] => Array
(
[jrcore_list_function_call_is_active] => 1
[search] => Array
(
[0] => _profile_id in 3, 5, 6, 7, 8, 9, 10
[1] => _profile_id in (SELECT `_item_id` FROM jr_jrprofile_item_key WHERE `key` = 'profile_quota_id' AND `value` IN(1))
)

[order_by] => Array
(
[_profile_id] => numerical_asc
)

[template] => select_statements_to_zip.tpl
[tpl_dir] => ujManager
[module] => ujStatement
)

[3] => Array
(
[jrcore_list_function_call_is_active] => 1
[search] => Array
(
[0] => _profile_id in 3, 5, 6, 7, 8, 9, 10
)

[order_by] => Array
(
[_profile_id] => numerical_asc
)

[template] => select_statements_to_zip.tpl
[tpl_dir] => ujManager
[module] => ujStatement
)

)
updated by @ultrajam: 10/02/22 11:48:08PM

Accessibility improvements in Jamroom 7

Suggestions

Second thoughts, it might be best to wait a few days before adding your comments to the tracker. I've started to give a few people access to that site, so over the weekend I will make another site and tracker to keep things simple.

Accessibility improvements in Jamroom 7

Suggestions

That's done.

Accessibility improvements in Jamroom 7

Suggestions

This is a good summary to read: https://web.dev/how-to-review/

Accessibility improvements in Jamroom 7

Suggestions

Login sent, thanks Michael

Accessibility improvements in Jamroom 7

Suggestions

I have a tracker set up which lists the issues I've noted at over the past 24 hours (some might not be well explained, and not enough links to further info yet).

If it's ok with you I can add you to the site tomorrow so you can see the type of issues I'm talking about. Happy to add any others in the Team too if that would be helpful. I've added some form designer fields to the tracker, but I'm sure you all know your way around it well enough for it to still make sense.
updated by @ultrajam: 06/02/22 01:12:34PM

Accessibility improvements in Jamroom 7

Suggestions

I think it would be quite a big project, and not necessarily something which has to be done all in one go. Might be better to think of it as a journey towards accessibility.

Jamroom is already very well thought out, clear and easy to use so that's a great place to be starting from! The disadvantage is that its capable of such a wide range of things, and there are so many modules and skins. We could start by looking at the Core with Elastic and see where it's at after that?

There are analyzer tools and services, but automatic checks can only test less than half of the requirements, and most of those still need to be verified as accurate. I like the developer tools in the browsers, especially the way they link to further info, and there are a few plugins which are quite helpful too.

Accessibility improvements in Jamroom 7

Suggestions

I'd be very interested in making Jamroom 7 more accessible for all users.

I work at a university, and because we receive some public finding we are required by law since 2018 to not spend money or work time on anything using a browser which doesn't meet current accessibility regulations. In a nutshell that means WCAG 2.1 AA: https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=pageinfo&currentsidebar=%23col_customize&levels=aaa&technologies=flash
I know there are very similar Section 508 requirements in the US.

Forgetting law and regulations (I do try to), I believe that there is a really good business (and moral) case for making web apps usable by all people. W3C have been advocating for an accessible web since the start. The more people who can use a web platform the better, they will be able to interact/enjoy/feedback/pay/learn/buy things via the platform. Judging by the accessibility conferences I have been to (remotely) over the past 3 years big business is way ahead on this, universities are sadly way, way behind and are now only trying to catch up because they are legally compelled to.

Making Jamroom 7 a more accessible platform is my suggestion. I don't have the skills to make it fully compliant with the guidelines (e.g. I don't even have the patience to learn to use a screen reader properly), but I do have some knowledge in the area. And I'd be more than happy to help with making Jamroom more accessible if the Team have any interest in that.




updated by @ultrajam: 09/07/22 03:03:34PM