Skip Navigation

[Résolu] view_template not working with password-protected posts

This support ticket is created Il y a 8 années et 1 mois. 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.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

Marqué : 

This topic contains 2 réponses, has 2 voix.

Last updated by mirkoS Il y a 8 années et 1 mois.

Assisted by: Luo Yang.

Auteur
Publications
#373461
withViewTemplate.png
output.png
directInLoopOutput.png

I'm building an archive site for posts some of wich are password-protected.

Until the last time I updated my toolset plugins everything worked fine - but now with the view using a view_template the protected posts aren't displayed correctly anymore.

When I insert the displaying code directly into Loop-Output everything works as expected.

#373657

Dear mirko,

Thanks for the feedback, I have been able to duplicate same problem, but I don't think it is a bug, and I think it is a improvement, with it you can protect the post content easily:
1) for those content need to be displayed directly, you can put it into the view's section "Loop Output"
2) for those content need to be displayed after user provide the password, you can put it into the content template, and display it with Views shortcode [wpv-post-body]

#373675

Well, I don't think this is an improvement. With "View Template" I have to change the code only in one place if I want to alter it. This worked until recently and it was fine.

Now, I have to search for all the places that have to be changed (in this case three).

Worst of all, it gave me a hell of a time to find the solution for this problem. Maybe this should be documented somewhere.

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.