Howto avoid using the AJAX search in add-users-to-session screen

In Dokeos 1.8.5, in the admin screen that allows to add users to a session, we have implemented an AJAX search, or in human words, a search box that dynamically generates a short list of the users which contain the search string.

This feature is only enabled when you have more than 100 users, because the users list would otherwise be very long to load.

If you don’t like this feature, and would like to keep to a straight, classical, 5000 users list, just change the main/admin/add_users_to_session.php, line 232, change “100” to “5000” to put the limit at 5000, or just remove the option by setting $ajax_search = false; directly.

Related Posts

No security flaw so far…

It might seem kind of weird to mention it, but I had somewhat...

What’s left before 1.8.5 stable…

Not that I’ve been too busy on Dokeos lately (I tend to take...


  • Ajax makes us with non UTF-8 Dokeos sad.

    Look at the “template” menu on this picture..

    .. it is generated with Ajax from Windows-1250 charset text and the non-western characters are incorrect.

    I also reported a similar problem: “Documents have no charset” on Dokeos forum.

    I think the best solution would be to make UTF-8 the only option available. That would of course mean conversion of all language files and creation of a script which would convert the text in the DB & change the charset setting of DB fields.

  • Why is it using Windows-1250? That’s a Windows-only charset and is probably the most frequent cause of broken display of strings on the web…
    Are you using Windows-1250 as a character set for your Dokeos install?

    We are currently planning on having UTF-8 by default *before* the move to Dokeos 2.0. I was slightly touching the topic here but it is not official so far, it’s just a plan that I have and that no company is directly requesting.

  • Yes, my installation of Dokeos uses Windows-1250 charset, because the translation files for Slovenian language were created using that charset (it supports our local characters – čšž).

    I guess I’ll have to convert my Dokeos to UTF-8 somehow.. I just wanted to warn you about the possible problems users face when you add more Ajax to Dokeos.

  • Yes, I understand, but I wouldn’t like people to think that we just don’t cope with character sets in AJAX (Dokeos has a lot of flaws, but I’d like not to add more that are not real flaws, or not due to our careful work). We do deal with character sets as much as we possibly can, but some translation files (contributed by the community) are just wrong or not portable, which breaks things for the final user, sadly.
    There is a new set of translations appearing in the Dokeos Language Translation Tool at the moment, suffixed by “_unicode”, which are made in UTF-8. I think there is one in Slovenian, maybe you could try it out (as you mentioned before, the courses contents should be converted as well, otherwise t will all be broken at once, but maybe you can already see if that language pack would be alright by trying it out on a test portal).

Comments are closed.