Shortcode Custom CSS Still Not Saving

Hi @dcbuffalo,

Which custom CSS you are implementing in additional CSS also you can implement custom CSS in the customizer section.

Thanks

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.

Hi @dcbuffalo,

Please 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; ?>

If it works let us know

Thanks

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!

Hi @dcbuffalo,

The above solution is for the front end now we give you a back end solution. So please 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']);

If it works let us know

Thanks

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.

Hi @dcbuffalo,

Glad that your issue has been resolved if you like our plugin please rate us. This issue comes only in rare cases so try to avoid updates if you keep your custom CSS.

Thanks

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.

hi,

we will update it if this issue occurs with other users as well.

thanks

It does affect me and I’m sure it affects many others who use CSS to style the accordion content.

I’m not sure I understand the reluctance to fix a known issue with an update.

Hi @yukitopia,

Please provide the custom CSS code you are using so we can check it.

Thanks

The problem is that the custom CSS won’t save. It would also erase all the front end settings if you put anything in the custom CSS box and try to save. It doesn’t matter what custom CSS I put in there.

But here is the custom CSS I tried to add:

.pullquote {
margin: 1em 0;
line-height: 1.4;
color: #999;
padding-left: 10%;
padding-right: 10%;
}

p {
font-family: ‘Lato’;
color:#666;
font-weight:400;
line-height:1.6;
margin: 0 0 28px 0;
}

p a {
color:#00828c;
text-decoration:none;
}

p a:hover {
color:#00828c;
text-decoration:underline;
}

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.

Hi @yukitopia,

We have applied the CSS code you shared and it is saved in our custom CSS.

Thanks

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, 6 months ago by dcbuffalo.