Skip Navigation

[Resolved] Permission denied text showing to users

This support ticket is created 6 years, 4 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.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 38 replies, has 3 voices.

Last updated by Christian Cox 6 years, 2 months ago.

Assisted by: Christian Cox.

Author
Posts
#1100819

Sorry, we may have just spotted an issue linked to this.

hidden link

Is not displaying correctly and we wonder if its linked to the symptom of the permissions denied issue.

When logged in as admin this is'nt a problem, only when logged in as a user does the page look incorrect.

Its pretty urgent as its impacting our live site.

Could you validate for us please?

#1101701

Hi, sorry can we get an urgent response to this please?

New threads created by Christian Cox and linked to this one are listed below:

https://toolset.com/forums/topic/wordpress-archive-title-is-repeating-several-times-when-logged-in-as-non-admin-user/

#1101708

I edited the Layout applied to Resource Category archives and removed the conditionals and Forms shortcodes completely from the Content Template cell so you can see that this has nothing to do with the code we just added. Not sure what's going on here, so I have split this problem into another ticket. Once you have examined the Layout and you confirm that the problem still exists without the changes we made, you can re-add this code or I will re-add it for you. Let me know which you prefer.

[toolset_access role="Contributor,Subscriber" operator="deny"]
  [cred_form form='create-message-feedback' form_name='Create: Message (Suggestion)'][/toolset_access]
[cred_form form='create-message-feedback-2' form_name='Create: Message (Feedback)']
#1103660

Hi, in the last post I presume you undid the changes on staging?
If so the issue has cleared in staging, please could you apply the same to live asap? This will give us the issue on permission denied but will fix the phonics page which we need working asap. We will then have to understand why the change has broken the Phonics page and hopefully get a fix for both but Phonics need to be working on live asap.
Ta
Luke

#1103723

The permission denied change has been backed out of production but as I said multiple times already it has nothing to do with the repeating archive title. The staging environment is not identical to the production environment, and that must be resolved by someone on your team.

#1103724

Hi, Ok thanks I will create a new staging copy now and provide the details as soon as it's up. Sorry but please can you re apply the permissions denied fix again to live if as you say, it's unrelated.

Thanks
Luke

#1103725

Hi Christian,

I have just created hidden link

The initial login is the same as staging1 and it should have copied over all your admin accounts. If you could look to understand why the Phonics page is broken so we can seek a fix for live.

Regards
Luke

#1104317

Hi Christian, I have been over the setup for staging1 which is working vs staging4 which is not working and I can't identify the issue. There were some differences in woocommerce views and views in Toolset relating to Phonics but even though I have these now aligned we still have the issue on the Phonics page. Happy if you want to run this as a new case and close the permissions denied case, so long as the code fix is back on live. We really need to try to fix the Phonics page so any help would be appreciated. I also compared plugins and versions between staging1 and 4 and disable CDN and WP_Rocket on both so I am confident the issue is not related to a plugin version or conflict.

#1104802

Okay I will continue investigating the other issue in the other ticket.