I updated to views to v 2.5 and now whenever I insert a shortcode, I get `{!{wpv-post-title}!}` instead of [wpv-post-title].
They are no longer highlighted in the editor and it makes it a nightmare moving forward.
I have been using the [] shortcodes and now I'm supposed to either spend another 200 hours redoing everything I have done for my clients in Views, or mix them up and create a s**t soup.
How can I get the old shortcodes back?
We have a new syntax for ShortCodes that uses {{ }} but this is only when you use Page Builders.
This is not happening in any other Text Editor - or at least it should not.
The reason for those new brackets is a compatibility one.
We ensure hereby that our ShortCodes get executed when they should.
Now, this all should not affect your site at all.
Can you please provide me a site's snapshot or access to your Live site where I can see the issue?
Then I will find the solution for you.
Thank you
This is a mess. I have spent over 200 hours working on websites that had page builders. Am I now supposed to go back in there and start re-writing all the shortcodes??
And what happens if I activate a page builder after I create my views?
This is a really horrible way of doing things. Changing things on the fly without any consideration to backward compatibilty. Not everyone is starting out fresh new sites running twenty-seventeen every time you guys decide to push out a new update.
At least update code highlighting to work with the new and "improved" shortcodes. They come up as text and are almost impossible to discern from any other HTML I type.
No, you misunderstood me.
1. There is a new syntax and you do not have to edit, touch or modify that syntax in any way.
2. This syntax is placed by Toolset when you use either the WP Admin Toolbar" > Toolset ShortCodes" or you insert the Fields with a Page Builder.
3. Every other problem that arouse by this is solved here:
https://toolset.com/errata/betheme-options-page-is-not-working-when-views-2-5-0-is-activated/
We have meanwhile found the cause for the issue, fixed it and published an erratum for that.
You should not need to edit anything manually now.
Thank you for your patience.
