This support ticket is created 4 years, 3 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.
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.
I am trying to:
I'm trying to set a CPT posts carousel with View CSS and JS, and using Divi Builder in Content Template.
Link to a page where the issue can be seen: hidden link
I expected to see: The carousel that uses the CSS code I have added on it, but in the frontend, the View doesn't read it, and in the frontend has displayed the carousel, with JS automatic scroll, but without the CSS stylization...
This, after the last View and Type update.
This happens like in other sites of my customer and I don't have updated Toolset to the last version, and if I have do the update after I have done the downgrade.
I'm not able to identify any immediate reason for the css not loading. The javascript editor loads fine and the items are being loaded.
As a part of the debug step, can you re-create this view and re-add it to this exact page and check again to see if the problem still remains?
It could be that the view is corrupt and not loading the css settings for it. If this does not work then I would need to grab a copy of the site so that I can make further checks in a safe environment without disturbing your live site.
Hi Shane,
I have recreated the two carousel Views using the following name "carousel-clienti-2" and "carousel-clienti-web-2".
I have changed the two shortcode name on homepage.
But, the display issue remains... The CSS code is not read from the CSS box in the Views. So, a speed solution is to move the CSS code into the WordPress CSS code Editor or in the style.css file but, I think that the View bug need to be solved!!!