Title: Custom styles bug Last modified: August 21, 2016 --- # Custom styles bug * Resolved [gbell12](https://wordpress.org/support/users/gbell12/) * (@gbell12) * [11 years, 10 months ago](https://wordpress.org/support/topic/custom-styles-bug/) * Hi, * Using 2.2.21, I’m seeing the “Customise Styles” is very buggy: * 1) Sometimes after a “customize” and a “save changes”, there’s no new theme. * 2) Sometimes, changes are not saved at all. * 3) Sometimes, changed lines in the file are deleted altogether after a Save and reload. * 4) Once a custom theme DOES show up in the list, I cannot delete it. * I’m a developer, so I don’t think this is a “you’re doing it wrong” question 🙂 * [https://wordpress.org/plugins/slideshow-jquery-image-gallery/](https://wordpress.org/plugins/slideshow-jquery-image-gallery/) Viewing 14 replies - 1 through 14 (of 14 total) * [mbrsolution](https://wordpress.org/support/users/mbrsolution/) * (@mbrsolution) * [11 years, 9 months ago](https://wordpress.org/support/topic/custom-styles-bug/#post-5126234) * Hi gbell12 are you still experiencing this issue? * Thread Starter [gbell12](https://wordpress.org/support/users/gbell12/) * (@gbell12) * [11 years, 9 months ago](https://wordpress.org/support/topic/custom-styles-bug/#post-5126235) * It was consistent at the time. I have not been using the plugin recently. What would you like me to test? * [mbrsolution](https://wordpress.org/support/users/mbrsolution/) * (@mbrsolution) * [11 years, 9 months ago](https://wordpress.org/support/topic/custom-styles-bug/#post-5126236) * Can you try to install the plugin again and add some custom style. Make sure that if you have a cache plugin that you clear the cache both in the plugin and the browser. Also if it does not work with your current theme can you test a default WordPress theme like Twenty Fourteen? * If none of the above work can you disable all plugins except this one and carry out a test. * Let me know how you go. * Regards * Thread Starter [gbell12](https://wordpress.org/support/users/gbell12/) * (@gbell12) * [11 years, 9 months ago](https://wordpress.org/support/topic/custom-styles-bug/#post-5126237) * Hi Stefan, * I accompanied my last bug report with a financial donation (please, everybody who gets some value out of this, please follow suit!). * This one, I’ll accompany with a demo video 🙂 * [video src="https://dl.dropboxusercontent.com/u/17914213/slideshow_demo_for_stefan. ogv" /] * [mbrsolution](https://wordpress.org/support/users/mbrsolution/) * (@mbrsolution) * [11 years, 9 months ago](https://wordpress.org/support/topic/custom-styles-bug/#post-5126238) * Hi I have watched your video, great information. * This is what I have done on my test environment. I go to custom styles tab, I click on Dark Customize link which produces a copy of the style. The name given to the new style is **New – Dark** as you mentioned in your video. * I don’t make any changes, I simply click on Save Changes button. So now I have a **“new Custom stylesheets added New – Dark”** * Next I click on Delete to delete the new custom style added. A pop up window is displayed with the following message **Are you sure you want to delete this custom style?**… I click on OK and the custom style is deleted I then click again on Save Changes button so that the deletion is completed. I refresh the window and in my website it is deleted. So I was not able to produce your error. This was carried out in Firefox 31.0 version. * Which browser did you use? * Thread Starter [gbell12](https://wordpress.org/support/users/gbell12/) * (@gbell12) * [11 years, 9 months ago](https://wordpress.org/support/topic/custom-styles-bug/#post-5126239) * Firefox 30, under Ubuntu. * Trying it with an empty Firefox profile in safe mode… same thing! * Well, now we have a mystery. Want me to send me a test version with some alerts and var_dumps sprinkled around? * Even blowing away the WordPress codebase – same thing. * [mbrsolution](https://wordpress.org/support/users/mbrsolution/) * (@mbrsolution) * [11 years, 9 months ago](https://wordpress.org/support/topic/custom-styles-bug/#post-5126240) * Hi gbell12 make sure that you allow pop ups. Please see this [URL](http://mbrsolution.com/tutorial/wordpress-slideshow-plugin-custom-styles.php) I did some testing and added some screen dumps. * Regards * Thread Starter [gbell12](https://wordpress.org/support/users/gbell12/) * (@gbell12) * [11 years, 9 months ago](https://wordpress.org/support/topic/custom-styles-bug/#post-5126241) * Ah, you’re “Manuel”! Sorry for calling you “Stefan” in the video. Stefan’s the original creator and you help with with maintenance and support now? * I get the pop-up… but wasn’t hitting “Save Changes” as you must have seen in the video. * I hope you’ll agree it’s not exactly obvious that must be done since “delete” makes it look like the deletion already happened. Perhaps a checkbox instead? The way deleting posts or pages works. Check mark it for deletion, then hit “ Save changes”. Much more obvious, especially if “Save changes” is called “Apply”. * Thread Starter [gbell12](https://wordpress.org/support/users/gbell12/) * (@gbell12) * [11 years, 9 months ago](https://wordpress.org/support/topic/custom-styles-bug/#post-5126242) * And there’s still the issue shown in the video of a duplicated style becoming empty… * [mbrsolution](https://wordpress.org/support/users/mbrsolution/) * (@mbrsolution) * [11 years, 9 months ago](https://wordpress.org/support/topic/custom-styles-bug/#post-5126243) * Hi gbell12, [@stefan](https://wordpress.org/support/users/stefan/) is the plugin’s developer I am just simply helping when ever I can ;). * I will test the duplicate style becoming empty. I will keep you inform. * [mbrsolution](https://wordpress.org/support/users/mbrsolution/) * (@mbrsolution) * [11 years, 9 months ago](https://wordpress.org/support/topic/custom-styles-bug/#post-5126244) * Hi I just carried out a test. * I can confirm that when I click on custom styles tab, then I click on Dark Customize link which produces a copy of the style. The name given to the new style is New– Dark. I click on **Save Changes** button the style is not empty even if I refresh the browser as per your instructions above in the video. * Regards * Thread Starter [gbell12](https://wordpress.org/support/users/gbell12/) * (@gbell12) * [11 years, 9 months ago](https://wordpress.org/support/topic/custom-styles-bug/#post-5126245) * But you saw it happen to me in the video, right? So you tell me 🙂 * [mbrsolution](https://wordpress.org/support/users/mbrsolution/) * (@mbrsolution) * [11 years, 9 months ago](https://wordpress.org/support/topic/custom-styles-bug/#post-5126246) * Yes I saw your video and it did happen as you mentioned however I carried out the same task on my production server locally in running Xampp and Windows 7 sp1 and it works. Also running Firefox 31.0. * Have you tried to use a different browser? * Thread Starter [gbell12](https://wordpress.org/support/users/gbell12/) * (@gbell12) * [11 years, 9 months ago](https://wordpress.org/support/topic/custom-styles-bug/#post-5126247) * Can’t get it to go on Chrome. I guess you can just wait to see if other users have the same error. * Cheers for the support. Viewing 14 replies - 1 through 14 (of 14 total) The topic ‘Custom styles bug’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/slideshow-jquery-image-gallery_d3d2de. svg) * [Slideshow](https://wordpress.org/plugins/slideshow-jquery-image-gallery/) * [Frequently Asked Questions](https://wordpress.org/plugins/slideshow-jquery-image-gallery/#faq) * [Support Threads](https://wordpress.org/support/plugin/slideshow-jquery-image-gallery/) * [Active Topics](https://wordpress.org/support/plugin/slideshow-jquery-image-gallery/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/slideshow-jquery-image-gallery/unresolved/) * [Reviews](https://wordpress.org/support/plugin/slideshow-jquery-image-gallery/reviews/) * 14 replies * 2 participants * Last reply from: [gbell12](https://wordpress.org/support/users/gbell12/) * Last activity: [11 years, 9 months ago](https://wordpress.org/support/topic/custom-styles-bug/#post-5126247) * Status: resolved