Can you share the staging environment's basic HTTP authentication credentials? I will log in and take a look.
Again, I need the staging environment's basic HTTP authentication credentials. You provided the production environment's WP and FTP credentials.
I believe you can access staging from the details I provided.
I cannot. A basic HTTP authentication dialog appears and I cannot get past it. I have tried using the production credentials for WP and I have tried using the production credentials for FTP. I have also tried the staging environment's credentials you supplied here: https://toolset.com/forums/topic/permission-denied-text-showing-to-users/#post-1072567.
None of these credentials work for the staging environment's basic HTTP authentication dialog. So again, I am asking you to provide the staging environment's basic http authentication credentials.
Thank you. I am now able to get past the HTTP authentication on staging. Now I need the login credentials for an admin account. The credentials you provided for Daniel Williams and lukem624_staging do not work here: hidden link
Okay I have removed the conditionals from the "Suggest a resource" and "Give feedback" links, and I have also removed the conditionals around the Forms. Now any site visitor can click "Suggest a resource" or "Give feedback" to trigger the modals. I do not see the message "Permission Denied" for any User. Please let me know if this is not what you are expecting.
As a logged in user I still see permission denied. Thats for a standard logged in user, not admin.
A couple of tested this and have the issue. You can see it in the attached screen shot.
Seems the problem still exists.
Dan
The Customer and Subscriber roles are restricted from using the "Create Message : Suggestion" Form in Toolset > Access Controls > Toolset Forms - see the screenshot. This is why the Permission Denied message was displaying. For now, I have added a conditional that prevents the text from being displayed to Subscriber and Customer:
[toolset_access role="Contributor,Subscriber" operator="deny"]
[cred_form form='create-message-feedback' form_name='Create: Message (Suggestion)'][/toolset_access]
Please check and let me know if this is correct now. I created a Subscriber User and logged in, and the Permission Denied text is not appearing for me.
Sorry after clearing the cache we still see permission denied when hitting the resources page.
What User are you testing with? Please provide their login credentials so I can try to replicate the problem.
Here are my test subscriber account credentials. Can you log into staging with these credentials and test again? Please let me know the results.
toolset_test_subscriber
yJ0ra5Nq7x)#YnH3lbhBN2dF
Yes of course, I have made the change in the live site. Please test now to confirm it's working as expected.
That's great, many thanks again for sticking with us on this!
We have cleared the cache and MaxCDN. Looks good.
The only thing I have noticed is that I still get permission denied on user logout, (As per attached).
So the process is, logged in user > logs out > confirms logout > gets shown attached logged out page with permission denied message).
Could we just try and get rid of that and I think we are done!
Thanks
Shane
Supporter
Languages:
English (English )
Timezone:
America/Jamaica (GMT-05:00)
Hi Luke,
Christian is currently on a public holiday today but he will be back tomorrow to continue helping here.
Thanks,
Shane
Okay I edited the View "profile-add-trn" to add inline Access controls around the two Forms shortcodes. Now Guests will not be shown the Forms, which should fix the problem where "Permission Denied" is displayed after logout. I applied this change on staging and on the live site. Please check now.
[toolset_access role="Guest" operator="deny"]
[cred_form form='create-profile-blank-no-trn' form_name='Create: Profile (blank no TRN)']
[cred_form form='create-profile-with-trn' form_name='Create: Profile (with TRN)']
[/toolset_access]
Nice one, looks fine - please can you add to live and then we can close the case.
I applied this change on staging and on the live site.