You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue first reported via the user forum 2024-05-09; reproduced in the public demo site
Steps to reproduce the behavior
Make sure you are using the BS5 Dominion theme
Navigate to Admin > Plugins and enable the arRestApiPlugin
Navigate to an admin user's view page, via Admin > Users, and selecting a user
Enter edit mode
In the Access control area, select "(Re)generate API key" from the drop-down, and save
Observe the resulting key on the view page
Error encountered
Key is incorrectly labeled as the OAI-PMH key
If you use the old BS2 template, you can confirm that the same key value is shown properly labeled as the REST API key there
Expected Behavior
REST API key is properly labeled in the User details View page
Possible Solution
No response
Context and Notes
No response
Version used
2.7.3 - 182 in public demo; user reported issue in 2.8.1
Operating System and version
Ubuntu 20.04
Default installation culture
en
PHP version
PHP 7.4
Contact details
No response
The text was updated successfully, but these errors were encountered:
fiver-watson
added
the
Type: bug
A flaw in the code that causes the software to produce an incorrect or unexpected result.
label
May 9, 2024
Current Behavior
Issue first reported via the user forum 2024-05-09; reproduced in the public demo site
Steps to reproduce the behavior
Error encountered
Key is incorrectly labeled as the OAI-PMH key
If you use the old BS2 template, you can confirm that the same key value is shown properly labeled as the REST API key there
Expected Behavior
REST API key is properly labeled in the User details View page
Possible Solution
No response
Context and Notes
No response
Version used
2.7.3 - 182 in public demo; user reported issue in 2.8.1
Operating System and version
Ubuntu 20.04
Default installation culture
en
PHP version
PHP 7.4
Contact details
No response
The text was updated successfully, but these errors were encountered: