Closed cessda-bitbucket-importer closed 1 year ago
Original comment by Stefan Dlugolinsky (GitHub: Stifo).
@TainaFSD Please, can you explain what exactly is content admin and SL admin? What are the differences?
Looking into the user management I see following roles:
ROLE_ADMIN
, ROLE_ADMIN_CONTENT
, …Agency roles (role per agency and language): ADMIN
, ADMIN_SL
, ADMIN_TL
, …
ADMIN
= ADMIN_SL
+ ADMIN_TL
Currently, deprecation button is restricted to show only for agency roles ADMIN
and ADMIN_SL
+ (major version >= 1 and minor version > 0 → bug; e.g.: it won’t show for version 2.0)
Original comment by Stefan Dlugolinsky (GitHub: Stifo).
I’ve looked at the “kung pao” dictionary in staging and I think that the cause of this error is in checking the version constrains. In staging, the vocabulary version is 3.0. Code deprecation button is not shown for versions x.0 (minor version is 0). I’ve fixed this to not show code deprecation button just to very first versions; i.e., version == 1.0.
Original comment by Taina Jääskeläinen.
Your fix is correct: only the very first versions (i.e. where the first two digits are 1.0) should not have code deprecation. I’ll check it in staging.
If it helps, here is a short explanation of the roles
I’m not quite sure what ROLE_ADMIN does.
ADMIN_CONTENT which I called ‘content admin’ and which in the user roles table is ‘Administrator_content’ has rights to:
ADMIN_AGENCY which is currently not yet implemented but Martin B is working on the roles
SL_Admin
TL_Admin
Original comment by Taina Jääskeläinen.
Still no deprecation button for SL Admin. I created new version of KunPao (DRAFT 3.1) as SL Admin but do not yet have the code deprecation button.
Tested in Chrome on Friday 14th as well.
Original comment by Taina Jääskeläinen.
I seem to have lost the deprecation button as content admin as well (both in Firefox and Chrome).
Original comment by Stefan Dlugolinsky (GitHub: Stifo).
Hm, I can see it with iisas_guest account in staging:
I’ve changed your roles in staging; i.e., deleted the Agency roles:
To the following:
They’re now the same as for iisas_guest. @TainaFSD Can you see the deprecation button now?
Original comment by Taina Jääskeläinen.
Yes, I now have the deprecation button in my ROLE_Admin role as [email address removed](mailto:email address removed) in staging.
Still do not have the button in my other staging role [email address removed](mailto:email address removed) where I have SL_ADMIN role for CESSDA and DDI Alliance
Original comment by Stefan Dlugolinsky (GitHub: Stifo).
There must be a problem with agency roles. It seems that agency roles do not work. This problem is related to #395.
Original comment by Taina Jääskeläinen.
I’m reopening this issue so that I remember to check that SL Admin has ‘deprecate code' button when #395 is resolved.
Original comment by Martin Bobak.
The deprecation button is accessible for Admin SL.
Original comment by Taina Jääskeläinen.
Thanks, Martin. Tested in staging and the deprecation is there for Admin SL.
Original report on BitBucket by Taina Jääskeläinen.
When creating a new SL, content admin has the ‘Deprecate code’ button. Add this button for SL Admin.
Current SL Admin buttons for creating new SL (deprecation missing):
Current content admin buttons (deprecation is there):