Repository navigation
Releases
Vocab Sync 1.39.0
- Recorded in Revision History. Vocab Sync writes values with its own SQL (one statement for a whole vocabulary). When the Revision History module is installed, every such write — import, revert, recheck, assign, freeze and their undos — is handed to it, under the person who pressed the button and one run per press. With Revision History 1.2.2 or later each write is one entry for all the records it changed (each record's page shows it with only its own values), which keeps a rewrite of a whole vocabulary to a few seconds; with 1.2.1, one entry per record; with 1.2.0, record by record up to 200 records.
- Renaming a term notes the new wording on every record that uses it (one automatic entry, folded away on the record's page).
- Without Revision History every write is made exactly as before.
Vocab Sync 1.38.3
Renaming a term now says which wording the form was opened on. When somebody else renamed the term in between, the rename is refused and the page says what the term is called now, instead of silently putting the old wording back over theirs. A page opened before this version still works as before. No database change.
Vocab Sync 1.38.2
A value is read by its word first, so two terms with the same word came back as the lower id every time the edit form was saved, and an id sent in @value could be read as a term whose word is that number. When vocabsync:term_id is sent (the edit form sends it, the API hands it back) and it is a term of the list whose word is @value, or @value is that same id, the id is now taken. Anything else is read as before. No database change.
Vocab Sync 1.38.1
Ready for PHP 8.4: the data type factory declares ?array $options, and the CSV exports pass fputcsv's escape argument explicitly. No change in behaviour, no database change.
Vocab Sync 1.38.0
Every POST of the module now needs Editor, Supervisor or Global Administrator. Freeze, Revert, undoing an import and switching templates now need Global Administrator. Every role can still open every page and choose terms on the edit form. No database change.