WIKINDX Activity
Virtual Research Environment / On-line Bibliography Manager
Brought to you by:
sirfragalot
Activity for WIKINDX
-
Mark Grimshaw posted a comment on ticket #743
:)
-
Minor amendment to Carambola template.
-
Stéphane Aulery posted a comment on ticket #743
I'm preparing the translations this week. I can release on May 1st.
-
I've been doing this for the last few days—various configurations of sessions and session timeouts—and all seems fine. I'm ready for a release.
-
Are you testing for a few days to make sure the sessions work well? I need to complete the translations, within the limits of my available monthly credit, this week before I can release.
-
Perfect.
-
Update messages catalogs
-
Fix a variable name in translation script
-
Today's SVN, fixing my code, works fine.
-
Display timezone name (not timezone id) on footer
-
Shorter fix for timezone selection
-
CHANGELOG: typos etc.
-
All seems fine now.
-
. . . and it seems the logging out of publication lists is working.
-
Ensuring publications list/logging out to read-only, works with browserTabID.
-
I made a modification ot DATE.php. When viewing the user-timezone adjusted date for resources, CLOSE etc., ensure that formats such as Asia/Hong_Kong are accounted for. That is, if the list of all timezones includes "[Asia/Hong_Kong] => Asia/Hong Kong" (note the difference), and $tzPriorityStack contains the user timezone [1] => Asia/Hong_Kong, then that user timezone is discarded when the array_intersect is applied. No longer. Perhaps there's a more elegant solution, but this works. All seems to...
-
Update a hint message.
-
Ensure only registered users can read news.
-
1. Minor typo causing a crash when viewing user registration details.
-
Add mising files
-
Delete debug code
-
I have finished rewriting the date display to take time zones into account. In the DATE namespace, there are 2 functions for formatting for display, 2 others for converting between values from a form and the database, and still others for determining the user's timezone. Sometimes a date appears in HTTP, RSS, etc. headers. This format uses a full date format where the time zone is specified. Therefore, no special conversion is needed in this case. Incidentally, I also formatted the dates to match...
-
manage date convertion for form display
-
Fix fallback format of dates
-
Add an helper function for datetime inputs
-
Yes. resoutce timestamps are now UTC.
-
Update changelog about Time zones management
-
Remove useless code
-
Delegate datetime insertion to the db for cache, news, and wordprocessor tables
-
Display dates with user's preferred timezone
-
Remove useless code
-
Delegate datetime insertion to the db for cache, news, and wordprocessor tables
-
Browsing a publication list or browsing as a readOnly user randomly bumps back to the login screen
-
Yes. resoutce timestamps are now UTC. Mark On 23 Apr 2026, at 16.12, Stéphane Aulery lkppo@users.sourceforge.net wrote: And do you see the shift of date? [v5bugs:#740] Browsing a publication list or browsing as a readOnly user randomly bumps back to the login screen Status: wip Target: Unknown Found in: Unknown Created: Mon Mar 30, 2026 01:13 AM UTC by Mark Grimshaw Last Updated: Thu Apr 23, 2026 02:08 AM UTC Owner: Stéphane Aulery Hi Stéphane, I've puzzled over this for some time and can't figure...
-
And do you see the shift of date?
-
So far so good. No problems to report this end after upgrading. Mark
-
Hi Mark, I converted the datetimes from the database. Next step is taking care of the display. It will be for tomorrow. Regards,
-
Move date functions in their own namespace
-
Remove dead code
-
Add function \DATE\timezoneOffsetFromUTC()
-
Move date functions in their own namespace
-
Move date functions in their own namespace
-
Update documentation (especially styles help file) for forthcoming 6.13.0.
-
Add an history entry for bib style version 31
-
Hi Mark, Since commit [r6334], UTC is the default for PHP and db engine. Now there are two things left to do: Rewrite all the UTC datetimes in the database with an upgrade step. Rewrite the display code and the code that processes the forms. \LOCALES\determine_timezone() return the user's preferred timezone. I don't yet know if I need to write some helper functions or if PHP's DateTime object is sufficient. Regards,
-
Update all standard bib styles to WIKINDX_COMPONENTS_COMPATIBLE_VERSION['style'] == 31
-
Always set the timezone of PHP/MySQL to UTC
-
Update the default APA style files to WIKINDX_COMPONENTS_COMPATIBLE_VERSION['style'] == 31
-
Update WIKINDX_COMPONENTS_COMPATIBLE_VERSION['style'] to 31 to account for structural changes to bib styles.
-
Fix an issue in MYWIKINDX email notification where the user's preference was not stored.
-
Minor correction to APA format.
-
Minor corrections to CHANGELOG.
-
Ensure users who are members of a group bibliography, can select that bibliography when importing resources or adding/editng a new one.
-
Remove a forgotten file
-
I've shortened the translation history. Let's try to resolve the date issue this week.
-
ReadOnly session not kept throughout lifetime
-
. . . and just to clarify, this is actually an issue with session retention not preference saving. For example, a term put into QUICKSEARCH should be retained and re-presented throughout the session but is not.
-
However . . . perhaps fix the timestamp issue first as (with my time difference in the mysql database) this might affect the retention of session rows.
-
Partly . . . Conditions: PHP sessions and relaunch browser. 1. If logged on as registered user (sessionUserId != 0), switching to readOnly now correctly writes a row to session with sessionUserId == 0. (Previously kept the registered user sessionUserId.) 2. Preferences not set upon change. for a readOnly user Upon Preferences save, a new row is written to the session table (presumably with the defaults). No changes in preferences are saved.
-
Does the last commit fix it?
-
Prevent session resurrection use UserId set
-
. . . but a useful one! ;)
-
You know my opinion. ReadOnly mode is a footgun. :-)
-
Update the CHANGELOG.
-
Seems fine with initial testing.
-
Ah! Thought you had done it. I've discovered a clue pointing to the solution. It is, of course, nothing to do with browsers. I've been testing using standard PHP sessions written to the session table. The issue is to do with one browser previously having used registered user before shifting to readOnly and the other (on opening the browser) starting in readOnly mode. 1. In read only mode, preferences are written and saved when the user had been logged on as a registered user then logs out and enters...
-
Changelog about JSON translation catalogs
-
Malformed strings in message files cause crash
-
Okay, I've recreated all the JSON files. I'll leave this topic for now until I see if Transifex is reliable in future automatic translations.
-
I don't know what to tell you except that I haven't finished yet and it's not worth looking too hard before that.
-
Remove first version of JSON translation catalogs
-
Final version of JSOn translation catalogs
-
A few days later and it's now working on Chrome but not on Safari. Very strange.
-
Complete the process of implementing the new resource_misc.publicationStatus field in the adminstyle plugin and to bibliographic and citation style formatting.
-
Begin the process of implementing the new resource_misc.publicationStatus field in the adminstyle plugin and to bibliographic and citation style formatting.
-
Hi Joachim, Sorry I forgot. At work I use ondemand policy for PHP fpm. Previously I also used dynamic policy but that don't scale as expected. With dynamic max_children is a hard limit, not with ondemand . ; ondemand - no children are created at startup. Children will be forked when ; new requests will connect. The following parameter are used: ; pm.max_children - the maximum number of children that ; can be alive at the same time. ; pm.process_idle_timeout - The number of seconds after which ; an...
-
Thank you, a first step in the right direction. After spending the night on it, I'm hesitant. Even in the newly exported JSON files, there were incorrectly encoded characters. I could only correct them manually, searching for the strings one by one for hours. I simply deleted the erroneous translations. Transifex, once again, exports without properly respecting the encoding of the target format. So, now I have serious doubts about the platform's reliability. Should we redo all the translations or...
-
Sounds like a significant problem. I've done a quick check with the latest SVN and all seems fine. Arabic (multiple versions I think) is listed—I chose one or two of these without the issues previously reported. Mark
-
Hi Mark, The PHP output of Transifex is buggy for two reasons: Transifex PHP input reader is buggy. It read PHP code with custom rules and doesn't parse exactly like PHP interpreter, so illegal escape sequence are loaded in source strings. After that, garbage in, garbage out. For the specific case provided the machine translation is puzzled by the source string for Arabic. For now, I've simply deleted the erroneous string. Since I have no way to control the output of Transifex, I changed the input/output...
-
Remove a wrong Arabic translation
-
Change the format of translations catalogs from PHP to JSON [#742]
-
Typo
-
Hmmm. Interesting. It works on Firefox but neither on Chrome nor Safari (even an old Opera). I tried closing all browsers and restarting. Same thing: Firefox is fine, the others not.
-
ReadOnly user's preferences not saved
-
The code was in reverse order. I've corrected it. Tonight I'll implement the actual fix for time zone management.
-
Restore session GC algo from revision r6208 [#743]
-
For selected resource types (mainly academic, text based), the publication status can now be set (when creating or editing a resource) and it will display for those types when displaying the resource. There are 6 types of status ranging from published to in preparation.
-
Fix auto mode
-
Malformed strings in message files cause crash
-
I'm taking the raw file as it comes out of Transifex. I'm going to see if there's a way in Transifex to protect specific sequences because it's the automatic translation that's doing a poor job.
-
Malformed strings in message files cause crash
-
ReadOnly user's preferences not saved
-
Malformed strings in message files cause crash
-
Add resourcemiscPublicationStatus to resource_misc table. This will (eventually) account for the publication status of the resource to be used in the bibliographic formatting of the resource. Values are TINYINT(1) with 0 (default) == published, 1 == in press, 2 == accepted, 3 == under review, 4 == submitted. I will work on this over the next few days.
-
Write Timezone setting to session for a readOnly user's preferences.
-
Fix default language and timezone in preferences page
-
Fix default value for timezone in preferences
-
Fix default value for timezone in preferences
-
Ensure user's timezone is in the CLOSE footer.
-
Tidy timezone anmes
1 >
