This topic has 14 replies, 2 voices, and was last updated 2 years, 10 months ago ago by webmakers2011
Hi, we had a beautiful website and have made the purchase buttons green and the sale with our default color, however after the theme update all of the colors have disappeared… Now the theme has it’s default black color for the buy now button and the color I have set is not the default theme color.
Is this going to be fixed in the next update and when should we expect it?
Thanks
It seems like the whole Styling/Colors tab of Theme Customization is not working for us anymore and the theme is using the default values for these… The other one that is not working is the Sale & Out of Stock customization.
Now I have updated the theme on our localhost environment and the same thing happened after 7.2.11 update. Is it possible for me to download the 7.2.10 version of the theme and the core plugin for it and rollback until you fix the colors issue with my layout?
I have also tried disabling all plugins. After I downloaded the 7.0 version of the theme and replaced in my localhost the colors are back as they should be.
Thanks
Hello,
Go to Theme Options > resave settings. Check the frontend after that. Let me know if it helps?
Regards
P.S. Provide us with WP Dashboard access to your site if it does not help.
Provide screenshot of the buttons, elements that lost colors and tell us what colors should be there.
Regards
Hi the save button does not do the trick. Can you just send me the 7.2.10 version and the xstore Core plugin to replace it, since it was working fine before the update…
Hello,
We have sent archives to your registration email. But downgrade is not the solution. We need to find out why the issue appeared and help you to avoid issues with the updates. So, once you downgrade the theme and plugin then reply back, provide us with WP Dashboard access to your site and provide screenshots of the elements that were affected after the update. We’ll check and help you.
Regards
Hi Olga,
you have send me the latest version – 7.2.11 and core 3.2.11 , not 7.2.10 and 3.2.10, please send me these.
Yes, I know that this is not the perfect solution but this website is our main website with lots of visitors and I cannot grant dashboard access to it… I will however try to move it on a demo environment and grant you access there, if possible?
For now the 7.2.10 version will be OK for us. Also, I think that your programmers know the changes in 7.2.11 and will be able to pinpoint the issue if they try to find it.
Best Regards,
I also can send you the Xstore child export file for you to check it out. It is with our options…
The file is in private area
Hello,
Oh, our bad. Take my apologies. We sent you the correct files this time, check again, please.
If you can’t provide us with the production site access then create a staging site (copy of the production site, you can use Duplicator plugin for these purposes) and provide us with the staging site access. We’ll check the issue.
Regards
Hi Olga, it seems like the theme issue has started with the version 7.2.10, not 7.2.11, since I have just replaced it on our local environment and it does not fixed the issue… Can you send me the 7.2 version to try it out? Since we don’t update every version of the theme…
Thanks and sorry for the inconvenience
It is very strange since I had a backup of my website with 7.2.6 and I have tried it and it does not fix the issue… However I am sure that it was working fine back then…. When I try with the 7.0 version the colors are fine, but there are other problems…
It seems like the theme default values overwrite theme options and custom CSS since I have tried adding:
div.sale-wrapper{
border-radius: 50% !important;
}
and no change to the border-radius of the sale badge… 🙁 I don’t know why is that.
This is with all other plugins disabled!
Hi Olga! I have managed to fix the problem! 🙂
It was because I was using the files generator, when I deleted the generated file it all came to normal!!! 🙂
The issue related to '‘Colors problems after theme update…’' has been successfully resolved, and the topic is now closed for further responses