Skip Navigation

[Resolved] Access major bug after update

This support ticket is created 7 years, 5 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Our next available supporter will start replying to tickets in about 5.84 hours from now. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

Author
Posts
#529861

Hello,

I've been using access with the whole toolset suite for a few months. I use access only for its "publication groups" that I assign to some pages. I never used it for "post types", and therefore all post types are set to "not managed by Access". I want it to stay like this.

In backend, admin, editor and author did add and edit new post types, but since last update, and even if the Access settings did not change, only admin may add or edit posts...

What happened ? And how may I solve the problem ?

Thank you.

#530203

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Roman

This change does relate to a bug in Access, but it was the prior behaviour that was a bug and the changed behaviour is the bug fix.

It was listed in the changelog for Access 2.4: "Fixed an issue about post group dialog, in order to exclude post types that are not managed by Access."

I'm afraid you will need to manage the relevant post types with Access to be able to use the post groups.

#530285

I really don't understand this... This new "bug correction" is causing a LOT of new bugs on my website...

If I am forced to manage my posts by Access, why is there a setting called "Not Managed By Access" ?!

#530290

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Roman

I'm sorry if it is causing issues with your site, but the previous implementation contained a bug which the new version fixes.

You are not generally obliged to manage post types with Access, which is why the "Not Managed by Access" setting exists. You are only obliged to manage a post type with Access if you want to control access to individual posts of that type inside a post group.

If you wanted to control the "Hello World!" post using an Access Post Group then 'posts' need to be managed by Access. You can have different settings for the post type and for the post group, so for the post types which you have to bring under Access control you should just be able to use the defaults and then not experience any difference.

#530298

The major bug is that since update, editor users can't access to add/edit a specific custom post type.

If I understand well, deleting the Access Post Groups should solve my problem ?

How may I be sure the Access Post Groups are not used anywhere, and that deleting them will not cause new bugs ?

#530312

It seems it's even worst than I thought...

I have successfully deleted all access post groups. Now, I only use Access for two things :
- the shortcodes ;
- the CRED forms.

But Editors still can't access nor the custom post type, nor the standard posts or pages in backend...

Thank you for your help.

#530331

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Screen Shot 2017-05-30 at 12.47.58.png

Hi Roman

What are the Access settings for standard posts, pages, and your custom post types?

In the screenshot, for example, you can see I am managing the Projects post type with Access and that the Editor role has rights to do everything except "Preview any", which are the default options.

#530342
notmanagedbyaccess.JPG
detail.JPG

Since I don't want to use Access to manage permissions, all are set to "Not Managed by Access".

#530446

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Then it appears there is something wrong with your installation, yes, because that should not happen like that and it is not what I see on my local test site.

The next step will be for me to request a duplicate of your site for testing locally, but before I do can I just ask you to rule out conflicts arising from other plugins or your theme.

Disable all non-Toolset plugins and see if the editor can edit posts, and also try switching theme to twentyseventeen and try again.

Let me know how you get on.

#530466

I've just tried that with no result.
Thank you.

#530472

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

In that case I'll need a copy of your site to do some more testing locally and possibly to pass on to the developers.

Could you please make a duplicate available as described here: https://toolset.com/faq/provide-supporters-copy-site/

I'll mark your next reply as private for you to share the link to the archive files (you can ignore the template asking for FTP credentials).

#531041

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Roman

Thanks for providing access to the site. I was able to observe the problem.

Upon testing further I found that the culprit seems to be a conflict with... WPML. De-activating WPML seems to resolve the problem.

I'm escalating this to second tier so they can investigate further and test whether this is an issue specific to your site and settings or a bug that will affect all users.

I've taken a duplicate of your site to pass on to them.

I'll let you know what they find.

Thanks for your patience.

#531052

WPML... !
Thanks for letting me know.
I'll go ahead and reactivate theme and plugins while waiting for the solution.
Thank you.

#534138

Hello,
Any news on this one ?
Thank you.

#534143

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Roman

I checked the internal tickets for this which show that, yes, the bug is escalated to the developers but, no, it is not resolved yet.

You should be able to work around the problem by bringing your Depeches post type under Access control and granting Editors the permissions required. The bug specifically affects permissions when Access is not managing the post types.

I will update here when there is progress reported by the developers.