dcbuffalo

This is STILL happening. Had to do a restore of the site because your plugin update broke the site.

PLEASE FIX THIS ISSUE. I can’t believe I’m still asking.

So FYI – I re-did your steps from above, and it works again:

STEP 1:
Go to Plugins > Plugin editor and select Responsive Accordion and Collapse plugin and go to front > style.php on line number 151 replace the below code with another code.

<?php echo esc_attr($custom_css); ?>
to
<?php echo $custom_css; ?>

STEP 2
Go to plugins > plugin editor and select Responsive Accordion and go to lib folder > admin
> data-post > ac-settings-save-data.php file on line number 23 and replace the below code with the new code.

$custom_css = sanitize_textarea_field($_POST[‘custom_css’]);
to
$custom_css = stripslashes($_POST[‘custom_css’]);

Still trying to understand why you don’t just include this in the update.

THIS IS HAPPENING AGAIN IN v.2.3.4.

Please fix.

Or was I still expected to change the other code on my own? Why wouldn’t you just update the code in the plugin?

• This reply was modified 2 years, 9 months ago by dcbuffalo.

You’re welcome.

Right, so it’s affecting other people. My guess is lots of people just delete your plugin and use another one. That wouldn’t be a practical solution in our case. If I have to, I will update and continue to make these two changes to the template files. But obviously, if your solution fixes it AND doesn’t break it for other people, not sure why you wouldn’t put that bug fix into your release cycle.

I don’t want to avoid plugin updates. That can cause other problems.

Does this solution for me cause problems for other people? If not, why not just push these changes to the next update?

If you can’t push these changes to the next version, will these two changes solve the problem in future updates?

I honestly don’t understand why you would not fix an issue that is impacting core functionality like this, even if it’s rare.

That actually appears to have worked! AT LONG LAST!!

Let me know when this pushes to the live version, and I’ll be sure to make sure it updates and still works.

That fixed some of the front-end display CSS, but not all. PLUS, all of the custom CSS still disappears on the back-end when I save an accordion.

The scariest part to me is that my last move with the latest version of the plugin was to save custom CSS to a test accordion, and it was STILL GONE when I used WP Rollback to return to 2.2.8. So if I were to save one of the accordions that was actually in use, I would lose all of my custom CSS for that accordion.

This is a very destructive bug!

Yes, I could move all of the accordion CSS to another CSS location. But I have a lot of accordions, and I only want the individual accordion CSS to load in if that accordion is in use. A lot of the CSS generated by the accordion plugin codes it specifically to shortcode ID numbers, so I have general CSS that affects ALL accordions and specific CSS for each accordion. Plus, that doesn’t solve the problem that saving also wipes out settings.

THERE IS A BUG. IT NEEDS TO BE FIXED.

I don’t believe it’s sending the confirmation email properly, but that’s probably an SMTP issue I’m working on separately.

Also FYI – the error started back up on December 9, pretty much after I cleared out the error log, and it’s logged almost every day since, usually several times.

So the same php error is still occurring. I refreshed the API key, and now the interface doesn’t allow me to set a list for the optin form, which seems problematic. Any thoughts?

Did you ever find this issue and fix it? I am still using version 2.2.8.

Version 4.0.9 works fine, everybody!

Here is a copy of Bold Builder 4.0.6:

https://spaces.hightail.com/space/dQOidVM9gA

Help yourself!

• This reply was modified 3 years, 1 month ago by dcbuffalo.