This topic has 19 replies, 4 voices, and was last updated 8 years, 10 months ago ago by Eva Kemp
Curious to when the new update for the Classico theme will be available? It seems that there are a lot of out of date woocommerce files that throw a flag when doing a System Status check. If I just merely grab the latest woocommerce files (fron their plug in) and overwrite the files in the Classico theme woocommerce folder, it breaks certain elements of the theme.
Thanks.
Hello,
We recommend to use old Woocommerce version until we release theme update.
It will be produced approximately in a week.
Sorry for inconvenience.
Regards,
Robert Hall.
Thank You Robert! No problem at all. Will I be notified through the Dashboard of the update availability?
You can monitor for a new theme update at this link:
http://themeforest.net/item/classico-responsive-woocommerce-wordpress-theme/11024192
Regards,
Robert Hall.
Thanks. So no flags are thrown at my Dashboard of availability of the new version? I just have to check checking themeforest?
Do you think this version will fix the bug of my fonts not changing at the front end? I already have a topic started on this.Eva confirmed that it is indeed a big and devs were notified.
Hello,
Unfortunately there is no update message for the theme in dashboard.
The bug with fonts should be fixed in the theme update as we’ve forwarded this issue to our developers and they are aware of it.
Thank you.
Regards,
Eva Kemp.
Alright. Just FYI…I can’t change font color as well. that whole interface is completely dead. I tried all browsers…all the same.
Which incidentally, Chrome doesn’t display my font colors correctly. In fact, any change I made to test it out for that browser resulted in zero changes…everything is white.
Odd. This Typography thing is killing me.
Hello,
We’ll fix it in the next theme update.
Please take our apologies for inconveniences.
Regards,
Eva Kemp.
No problem. Now let’s hope that a new release will actually be in a week. 🙂
Thanks again.
Hello,
You’re welcome and have a good day!
Regards,
Robert Hall.
I’m impressed! The update is here within a week just as you said! Incidentally, tell me the best way to update my current 1.4 theme. I sure hope it also fixes the issues I have when viewing the theme in Chrome as well.
Thanks!
Hello,
How to update the theme you can watch here:
(it’s for Legenda theme but the process is the same).
Don’t forget to create back up of your files and database before starting update process!
Regards,
Eva Kemp.
Thanks Eva. Most of my trouble was aimed at *where* to actually get the update. Makes it easier because I just got an email notification from themeforest that there is a DL available.
BTW…what is the best method of backing up the entire site as you suggested to do before updating?
I usually would download everything to my local environment with a ftp client and download the database and then set it up locally to make sure everything looks and works as expected, then I make the update… But its not very time efficient.
I know there’s plugins to back up your site too.
Hello,
Please read here how to back up site:
https://codex.wordpress.org/WordPress_Backups
Regards,
Eva Kemp.
Hello. Changing google fonts still does not work. I can’t change color of the font either. It works for breadcrumbs and Top Bar…but not the page body and “custom heading” element chosen in VC. It might not work in other areas as far as I know. Who knows?
Please check entire Typography in all areas. Please advise.
Hello,
I’ve commented the code you added in Theme Options > Styling > Custom CSS > Global Custom CSS:
body, h1, h2, h3, h4, h5, h6 {
font-family: Verdana !important;
}
Now font is changed:
http://storage2.static.itmages.com/i/16/0130/h_1454141240_7705594_9210018864.png
Clear browser cache and check.
Regards,
Eva Kemp.
Ahhh yes! I forgot about that little override! You had actually added that code yourself as a workaround when this issue first arose. 🙂
Thanks! All good now.
Hello,
You’re welcome.
Regards,
Eva Kemp.
The issue related to '‘Classico Update When?’' has been successfully resolved, and the topic is now closed for further responses