Ah no. when I try to see the Custom Field Group, it redirects me to the main site hidden link
So the site was not duplicated correctly, somehow.
Well, the precise slug of the field is wysiwyg, right?
It works perfectly fine in hidden link, hidden link, hidden link
There you can see how I have set this up.
It is a pain when it redirects to the live site, especially when the credentials are working and I start editing the live site thinking its the staging site 😳.
I have now discovered that it has something to do with using Elementor templates. When I checked what you had done, it was exactly what I had done as well, but still it didn't work. So I created a brand new page and did the same thing again. Then it worked. Check: hidden link
So know I will build a new post and a new template and see if I get the same issue again. In that case there is a problem when using templates.
I will test and get back to you with the result.
It seems we are getting closer to it then.
Note, do not use any "global" thigns in the templates. (I am not sure if Elementor has it, but many page builder feature options to make widgets or templates "global"). This will NOT work with Toolset inputs.
Also it's important to make sure, when you design posts with Toolset and Elementor, to assign ONLY Elementor Templates to your posts and in there ONLY use the ShortCodes of Toolset or the widgets provided by Elementor, but not for example trying to display an elementor template inside a Content Template, or similar.
That will always fail (it is not the reason for the issue you see, but I want you to be aware of it not to run into problems later)
Please let me know if the template functions as expected or not, I will have another look respectively.
Now I made a the following test:
1. I created a new post called With Elementor template:
hidden link
2. I created an Elementor template called Toolset test:
hidden link with display condition only for the above mentioned post.
When checkin this in the front end hidden link the slider doesn't display. So there is a problem using this method in combination with a template.
Any ideas on how to get around this, because using your suggestion works perfectly as long as I don't use a template? Problem is that I have to use a template for the custom posts on the live site...
Thanks for hanging on Beda :-). I guess its getting a bit late in your timezone, so perhaps I will not hear from you until tomorrow.
Just letting you know: I have checked the Elementor docs and I don't find anything about global settings for templates apart from that you can make a widget global. So that is probably not the issue here. I am not sure if there are any global widget on the site elsewhere. Do you think that could affect even if the widget isn't used in the template or page/post that we are testing? In that case I should delete all the widgets on the staging site to see what will happen.
I have deactivated the plugins, it takes to long to load the website otherwise. It still seems something is blocking the site from a fast rendering, however. Do you know why this is?
I can see the issue on the template you made applied to the single post.
There are JS errors in the console, which do not seem related to Toolset.
Uncaught TypeError: Cannot read property 'hasClass' of undefined, from /wp-includes/js/wp-auth-check.min.js?ver=5.2.3
Additionally the font errors.
I see that in the template the WYSIWYG Field is inserted as I did in the single post but here it doesn't execute the ShortCodes within it.
That is due to the RAW Attribute when removed the issue is finally solved also on the Elementor Template
Can you confirm this?
I think its slow because of it being a staging site. But I´m not sure, so I will check further.
Great, it looks like the issue is resolved now! I made a test page with Elementor and the Toolset field on the live site to be sure. As far as I can see, there is no error any more. I am at an airport, so a bit messy connection. Maybe you can double check the live site page as well and confirm that you don't see the error? The live site test page is this one:
hidden link
Hi Beda,
I am happy to confirm that by inserting [types field='slug_of_toolset_field_where_the_shortcode_is' suppress_filters='true'][/types] without the RAW attribut in the Elementor text field, the problem is solved.
Thanks for resolving this issue. I am now rid of a large amount of 404 errors on the site.
Best regards,
Jan
You are most welcome, Jan.
Let us know in eventual new tickets if we can help with anything else.
Thanks for confirming the resolution, as well.
