Skip Navigation

[Resolved] Access doesn’t deny access to same page in other languages

This thread is resolved. Here is a description of the problem and solution.

Problem:

The issue here is that the user is using Polylang to translate their site, however they used the Access plugin to deny access to guests on their page. When the guests views the translated version of the page then the page is no longer being blocked.

Solution:

I have the perfect workaround for this. Instead of blocking the page itself. I would suggest blocking the content inside the page.

So the reason why its not working is because of the language parameter in the URL which changes the url structure.

What you can do is to use our access shortcode to block the contents of the page based on the user as well as to show the login form.

https://toolset.com/documentation/user-guides/access-control-texts-inside-page-content/

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
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

This topic contains 4 replies, has 2 voices.

Last updated by Marcel 6 years, 4 months ago.

Assisted by: Shane.

Author
Posts
#1079752

I am trying to:
Get access to deny access to a certain page

Link to a page where the issue can be seen:
hidden link
hidden link

I expected to see:
In the default language, I get a login form like I want. However, when I select another language, I can see the content which should be protected by access.

#1079813

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Marcel,

Thank you for contacting our support forum.

What I believe is happening here is that I suspect is that the translation is a separate page in itself so you will need to restrict it with access as well.

Thanks,
Shane

#1079815

That doesn't seem to be the case with this plugin (WPGlobus). It seems to be a fork of qtranslate so it works with tabs and shortcodes like {:fr}French{:} and {:es}Spanish{:}. Can you login to check?

#1081328

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Marcel,

I have the perfect workaround for this. Instead of blocking the page itself. I would suggest blocking the content inside the page.

So the reason why its not working is because of the language parameter in the URL which changes the url structure.

What you can do is to use our access shortcode to block the contents of the page based on the user as well as to show the login form.

https://toolset.com/documentation/user-guides/access-control-texts-inside-page-content/

Please try this and let me know if it helps.
Thanks,
Shane

#1081343

Hi Shane,

Thanks, this workaround seems to work fine 🙂

Marcel