Skip Navigation

[Resolved] Sanitize not working for wpv-post-title

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

Tagged: 

This topic contains 4 replies, has 2 voices.

Last updated by orlaF 4 years, 11 months ago.

Assisted by: Shane.

Author
Posts
#1503485

Is there any update for when the 'sanitize' option to output slugs will work for wpv-post-title (and other fields)? The last support ticket I can see on this was 2015 and since then the advice has been to use shortcodes instead of fixing the 'sanitize' function so slugs can be output.

#1503593

Shane
Supporter

Languages: English (English )

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

Hi Orla,

Thank you for getting in touch.

Could you provide a bit of clarity on what you mean. Possibly providing a link to the ticket from 2015.

Thanks,
Shane

#1504839
#1505345

Shane
Supporter

Languages: English (English )

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

Hi Orla,

Thank you for the ticket.

Based on this I was able to find the issue on our system. Right now the developers won't be approving this feature request.

This is due to us having a shortcode that you can use to get the slug of the page [wpv-post-slug] . This can be used to get the post title in an essentially sanitized format.

However the custom code that was provided in the link should still function as intended.

Thanks,
Shane

#1506729

Thanks Shane - I'll make note of that. In feedback, it is a poor user experience that the sanitize feature doesn't work - it should be either removed or a note added to say that the shortcode should be used instead. Troubleshooting issues like this wastes time for both the end user and your support team. Thank you again for your help.