Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].
After upgrading to Page Builder 2.0.7 my site’s CSS toggle function no longer works. When you now press on a + icon on my page, the content no longer opens up.
My css code is as follows:
/* Toggle
================================================== */
/* .symple-toggle .symple-toggle-trigger { display: block; color: #C4690E; display: block; padding: 10px 10px 10px 37px; border: 1px solid #ddd; background: #F9F9F9 url("/images/shortcodes/plus.png") no-repeat 15px center; outline: 0; text-transform: none; letter-spacing: normal; font-weight: normal; font-size: 1em; line-height: 1.5em; margin: 0; margin-top: 10px; cursor: pointer; } */
.symple-toggle .symple-toggle-trigger { display: block; color: #000; display: block; padding: 12px 12px 12px 37px; border: 1px solid #ddd; background: #F9F9F9 url("/images/shortcodes/plus.png") no-repeat 15px center; outline: 0; text-transform: none; letter-spacing: normal; font-weight: normal; font-size: 1em; line-height: 1.5em; margin: 0; margin-top: 10px; cursor: pointer; }
.symple-toggle .symple-toggle-trigger:hover { background-color: #FFFDF3; text-decoration: none; }
.symple-toggle .symple-toggle-trigger.active, .symple-toggle .symple-toggle-trigger.active:hover { color: #000; background: #FFFDF3 url("/images/shortcodes/minus.png") no-repeat 15px center !important; text-decoration: none; }
.symple-toggle .symple-toggle-container { display: none; overflow: hidden; padding: 15px; border: 1px solid #DDD; border-top: 0px; }
Hi bbloqx,
Can you check if rolling back to 2.0.5 fixes the issue? You can download it here:
https://wordpress.org/plugins/siteorigin-panels/developers/
The last version of the plugin that did not break my site was version 1.5.3.
Can you roll back to that version then and check if that fixes it? That'll rule out any other plugin updates you might have done causing the issue.
From there, we can look into this a little deeper to figure out the issue.
I have rolled back the plugin to version 1.5.3 and everything is working again. So it does in fact look like its the upgrade that breaks it. Thanks
Hello Greg, I you ever figure out the issue?
I remember something in the changelog in the version AFTER 1.5.3 something about css on the home page, but never figured out what it was.