[Solved] 'Publish' button hiden with admin's articles

Pat64 · 2019-10-18 15:28:03

I just noticed a strange behavior with the latest stable TXP version. I write articles as some starting samples, but my client (“Managing Editor” role) can’t see the “Publish” button when he trying to update the corresponding articles.

Is there a kind of security attached to admin’s articles in order to avoid any changes by others autors?

Last edited by Pat64 (2019-10-23 07:40:24)

etc · 2019-10-18 15:55:48

Hi Patrick,

can not reproduce, sorry. The top two user levels can do everything with any article.

gaekwad · 2019-10-19 09:08:17

Pat64 wrote #319775:

[…] my client (“Managing Editor” role) can’t see the “Publish” button when he trying to update the corresponding articles.

Sorry to be pedantic, Patrick – when an article is updated, there is no Publish button, there is a Save button (at least there is on 4.7.3). Are you or is he looking for a button that’s not there?

Pat64 · 2019-10-19 15:23:20

gaekwad wrote #319781:

Sorry to be pedantic, Patrick – when an article is updated, there is no Publish button, there is a Save button (at least there is on 4.7.3). Are you or is he looking for a button that’s not there?

:D Yes, you’re right: no button at all! :(

@Oleg:

Does this button is governed by javascript ? The website is located into a subdomain. Is there a mismach behaviour for this configuration? I’m sorry, I can’t give you more details…

etc · 2019-10-19 16:39:12

Pat64 wrote #319782:

:D Yes, you’re right: no button at all! :(

Does this button is governed by javascript ?

AFAIR, only labels are changed via JS when you change the article status. Are you sure your client is “Managing Editor” and not “Staff Writer”?

Pat64 · 2019-10-23 07:39:57

Sorry for my very late answer, Oleg. But I needed to verify with the client’s computer.

All is fine now. I always create client accounts with “Managing Editor” role but for strangely reasons (the mystery of informatic 😲) it was changed to simple “Straff writer”.

Last edited by Pat64 (2019-10-23 07:41:10)

Pat64 · 2019-10-30 13:20:51

Off topic but for @Devs:

It seems that the “Theme” menu entry isn’t accessible for users with a “Managing Editor” role so they can’t access to a new theme in development.

To be confirmed.

etc · 2019-10-30 15:21:16

Pat64 wrote #319872:

It seems that the “Theme” menu entry isn’t accessible for users with a “Managing Editor” role so they can’t access to a new theme in development.

Yep, among skin, skin.edit and skin.preview privs (all of 1,2,6 levels) only the latter seems to be used at present. Dunno what the other two were designed for. Should we delegate theme manipulations (edit, switch, etc) to skin.edit and extend skin.preview to 1,2,3,6?

Pat64 · 2019-10-30 15:40:52

Maybe attach skin.preview to 1,2,3,6 and skin.edit to 1,2,6 levels with the new links you added for v 4.8 (“Preview” and “Activate”).

etc · 2019-10-30 16:38:06

Wait, not sure to understand: Managing Editors (level 2) can access to all theme features, they just have to check dev preview state in Prefs/Admin. Staff Writers (level 4) can not, exactly like for admins articles publishing ;-)

Should we extend dev theme preview up to level 4?

Pat64 · 2019-10-30 16:50:37

I’m going to visit my client (“Managing editor” role level) next friday and I’ll verify on her computer, then I come back to you.

Textpattern CMS

Textpattern CMS support forum

#1 2019-10-18 15:28:03