In my product archive /wp-admin/admin.php?page=view-archives-editor&view_id=1187
I have the following code:
[wpv-filter-search-box placeholder="[wpml-string context="wpv-views"]Produktsuche[/wpml-string]" output="bootstrap" class="suche"]
It is already marked red in the backend (see screenshot) and causes problems in the frontend ([/wpml-string] exposed in the sidebar)
When I remove the above code or even just the [wpml-string] part, the problem is resolved in the sidebar. ([/wpml-string] not exposed anymore)
There must have been a change in the last update that is causing this behaviour, as I have not changed any of the code.
I was able to reproduce this issue on a clean install. This may confirm that this is a bug. I am escalating it to our 2nd Tier and I'll get back to you as soon as possible.
As a workaround, we can put the placeholder content in a hidden HTML tag, and we can move it to the search box with a custom Javascript code. Let me know if you would need help with that.
I'll keep you updated as soon as I get feedback from our 2nd Tier.
The issue is now escalated to our developers and will be fixed in an upcoming release.
Please let me know if you need help with a Javascript workaround.
Is there a errata page for this bug so that I can track the progress?
I'll let you know about the errata as soon as it is published.
Our developers have produced a fix for this issue and it will be published in the next release. I am changing the status of this post so I can update you when the fix is released.
Thanks for keeping me updated.
Hello,
We have published yesterday a new version of Toolset plugins where we have fixed the issue of the closing shortcode. To update, go to Plugins->Add New->Commercial(tab).
Please note that Toolset Views is not available anymore for automatic updates, you will need to update it manually or to switch to Toolset Blocks(as they are virtually the same plugin).
I'll remain at your disposal.
Hello Jamal,
I have updated toolset and wpml to the latest version.
Now after waiting six weeks for the update nothing has changed or been fixed.
Neither this problem nor the problem with the exposed Closing shortcode [/wpml-string] on website .
https://toolset.com/forums/topic/closing-shortcode-wpml-string-exposed-on-website/page/2/#post-1862451
Please take another look and urge the developers to push a quick update.
I tested it on a clean install and it did not present the issue, you can check it here hidden link
Login with the following link hidden link
So, I wanted to check the local copy of your website and, for some reason, It is not working for me and I can't access the backend. I tried to build it again to no avail.
Then I logged into your website and I found out that Toolset Views was not up-to-date. Because it is not offered anymore on the Toolset Installer, I assume that you did not notice that. So, I updated it manually as you can see on this screenshot hidden link
And it seems to fix the issue, at least that's what I can see in the products categories archives.
Can you check again and let me know where I can see any of the two issues?
Hello Jamal,
I'm very relived that that was the cause of the problem. I have installed the update on my live site and it seems to run fine. Thank you for your help!
Do I still need Toolset Views if my site uses WPBakery next to Gutenberg or can I switch to Toolset Blocks and still use WPBakery?
Also is there a timeframe as to when you will drop support of Toolset views?
Awesome 🙂 I am glad I could be of any help.
Toolset Views and Toolset Blocks are both the same plugin. Built and delivered in two flavors or names. There is only one difference, once Toolset Blocks is installed for the first time, it automatically deactivates the Toolset Views editor, what we call the "Legacy" editor. In fact, if one of these plugins is activated, it deactivates the other plugin automatically.
So, we still offer support for Toolset Views to an undetermined date 😉
With both plugins, you can activate the block editor, the legacy editor, or both editors. In Toolset->Settings->General(tab)->Editing Experience. To continue using WPBakery and Gutenberg, you will need to activate both editing experiences.
So, I'll suggest that you install and activate Toolset Blocks to benefit from the automatic update feature.
I hope this answers your questions. Let me know if you have any doubts about anything.
My issue is resolved now. Thank you!
