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
Describe the bug
In a multi-tenant preprints server instance of Janeway (seriously, what's a better way to describe this? multi-preprints-tenants press?), Server B displays Subjects from Server A on the Subjects setup page. This is confusing, as none of these subjects may be added; it gives the impression that there's no way to add a new set of subjects.
Janeway version
Preprints 1.4.1.1
To Reproduce
On a Janeway install which hosts at least 2 preprints servers:
Log into Preprints Server A on any account
Access Server A's repository wizard, view the Subjects setup page, and open "Parent" drop-list
Log into Preprints Server B on superuser account
Access Server B's repository wizard, view the Subjects setup page, and open "Parent" drop-lis t
Compare Server B "Parent" list with Server A's
Expected behavior
Subjects are server-specific; Server B displays only Server B subjects.
Screenshots
Additional context
Much like #2934 , not sure whether this is intentional or not.
The text was updated successfully, but these errors were encountered:
Describe the bug
In a multi-tenant preprints server instance of Janeway (seriously, what's a better way to describe this? multi-preprints-tenants press?), Server B displays Subjects from Server A on the Subjects setup page. This is confusing, as none of these subjects may be added; it gives the impression that there's no way to add a new set of subjects.
Janeway version
Preprints 1.4.1.1
To Reproduce
On a Janeway install which hosts at least 2 preprints servers:
Expected behavior
Subjects are server-specific; Server B displays only Server B subjects.
Screenshots

Additional context
Much like #2934 , not sure whether this is intentional or not.
The text was updated successfully, but these errors were encountered: