building my archive page for Ranger directory and the view is not visible from the WordPress editor but is visible via front end view. tried clearing all caches and logging in and out again.
Hello. Thank you for contacting the Toolset support.
First of all, based on the debug information you shared I find that you are using the outdated Toolset plugins. We always recommend running your site with the latest stable release plugin version.
*** Please make a FULL BACKUP of your database and website.***
Could you please update ALL Toolset plugins to it's latest officially released version. You can download the latest plugin release from your accounts page:
=> https://toolset.com/account/downloads/
Alternatively, You can install/update Toolset pluigins using the installer plugin:
-https://toolset.com/faq/how-to-install-and-register-toolset/#automatic-installation-once-you-have-otgs-installer-plugin-installed
Please check after you update ALL Toolset plugins to latest release, Do you see the isssue? If yes:
I try to login with the admin access details you shared but I get the following error:
The username or password you entered is incorrect. Lost your password?
Can you please send me working admin access details and problem URL where I can see the issue.
Hi, I have check your archive for the rangers CTP, thank you for that. I can see what you have done both back end and front end.
Did you manage to uncover why the Toolset CTP for Rangers ( Alan Yan is the example) is showing even when its published but password protected?, users are able to see this post without putting in the password. I have checked it in incognito windows.
So, what if instead of a post title with link, if the post is password protected we can display only post title (not the link) or alternatively just do not display the post if post is password protected.
Thank you for sending me the links. The article was very helpful, but I’d like to clarify the issue I’m facing in more detail.
I’ve created a Custom Post Type (CPT) called “Rangers” using Toolset. Each post in this CPT includes private contact information, none of these posts are assigned to any default WordPress categories.
Here’s how I’ve set things up:
I’ve created a custom archive page using Elementor and Toolset to display all Ranger posts.
The archive page is password protected, and I’ve verified that the protection works in an incognito window. - hidden link password - rangers
I’ve published one test post (Alan Yap) and set that individual post to “Password Protected.” password - test
However, when I visit the archive page (in an incognito window on a different device, not logged into WordPress), I can see the full content of the Alan Yap post without being prompted to enter a password.
This differs from the expected WordPress behavior—normally, when a post is set to “Password Protected,” visitors are prompted to enter a password before viewing the content. That’s not happening here, which means private information is being displayed publicly, despite the post-level protection.
Could you advise if this is a known limitation when using Toolset with CPTs and Elementor, or suggest a way to properly enforce post-level password protection? - could this be achieved using Access Control rather than snippet code?
Well - offering password protected promps is where the theme involves. If theme is not supported such thing then there is no solution.
Toolset does not offer any feature to offer input/prompt to input the password when post is set as password protected.
I can offer you workaround if the post is set to password protected and if you want to exclude it from the view results but there is no workaround I've to offer you to prompt the password input box if post is set to password protected.
Well - if there is no such feature availavble even I'm helpless. You can quote such things when you do not get the solution you wanted but the fact is that I do not have solution to offer.
Well - I try to setup a demo for you but then I realize that it should be better if you can do it on your own and maybe pro version of plugin required.