Hey there, we’re using your plugin for such a while. Unfortunately Avada shortcodes in ctl-description are no longer working in CTL versions after v2.7.1. (How) Can I fix that with the current version of CTL? Thanks in advance. Lars
Sry, I’m late. We’re using Avada (https://avada.com). This theme comes with a visual page builder, the Fusion Builder, which is working with shortcodes. As described above your plugin can’t interprete this shortcodes properly in versions later than 2.7.1. so we had to rollback CTL. See screenshots attached. Thank you.
(backend)
(frontend)
This reply was modified 1 year, 12 months ago by orp7.
I have checked the same scenario with the latest version of our plugin (2.9.2), I have added the shortcode inside Timeline Stories and it is working and rendering on the frontend. Can you please share a screenshot of your Timeline shortcode so I can figure out the issue.
thank you for your help. This makes the shortcode work but causes a whole series of other problems. The large circles with year numbers are no longer displayed. Custom styles are messed up (certainly due to structural changes). Preview images for the lightbox are displayed in the wrong size (thumbnails before, now thumbnails but scaled up to the available space) and so on.
I rolled back to version 2.6.1 which solved all problems for now but this is not a permanent solution. I have to think about to spent more time to fix all the issues (at the risk that problems will occur again with the next update) or not.
Can you share some screenshots of the issue you faced after adding story-content=”full” inside the shortcode attribute? We changed some classes and HTML structure in version 2.8.0, which is why your previous custom CSS is not working in the latest version. If you can share your previous CSS it would help to share the updated CSS to be compatible with the latest version. I have tested the migration of the plugin with 2.6.1 to 2.9.2 and I am not facing any styling issues on my end.
unfortunately I can’t share more screenshots here because it’s a customer’s project. It’s not a problem to change the css to fit the new structure, I can handle this.
But one thing is left to know: How the larger year marker (see screenshot) can be reactivated?
