http://www.kriesi.at/support/topic/changes-in-the-backend-only-show-up-after-deactivationreactivation-of-theme Support Forum - Topic: Changes in the backend only show up after deactivation/reactivation of theme en-US Wed, 19 Jun 2013 01:40:05 +0000 http://bbpress.org/?v=1.0.2 q http://www.kriesi.at/support/search.php http://www.kriesi.at/support/topic/changes-in-the-backend-only-show-up-after-deactivationreactivation-of-theme#post-22188 Thu, 07 Jul 2011 07:07:51 +0000 Dude 22188@http://www.kriesi.at/support/ <p>Caches can improve site loading times. However it depends on your content. You can try plugins like: <a href="http://wordpress.org/extend/plugins/w3-total-cache/" rel="nofollow">http://wordpress.org/extend/plugins/w3-total-cache/</a> (I'd use older version like 9.1.9 for now because the newsest version doesn't work for many user - including me). </p> http://www.kriesi.at/support/topic/changes-in-the-backend-only-show-up-after-deactivationreactivation-of-theme#post-22140 Wed, 06 Jul 2011 22:58:54 +0000 hamrockster 22140@http://www.kriesi.at/support/ <p>Ok- Hopefully this will be of some use to others: I thought the above problem was solved until earlier today, when the same thing started to happen to me again on firefox. I originally imported my site from a WP.com blog, so I had several plugins "leftover" from that transition that were still operating: WP Super Cache, Jetpack, and WP Importer. I decided to deactivate all of them, and so far the it seems the problem has been solved on Chrome. </p> <p>Is there any downside to having WP Super Cache not activated? This plugin was not something installed by me, but rather was automatically installed and activated when I made the switch from wp.com to my own host... </p> http://www.kriesi.at/support/topic/changes-in-the-backend-only-show-up-after-deactivationreactivation-of-theme#post-21843 Fri, 01 Jul 2011 05:07:56 +0000 Dude 21843@http://www.kriesi.at/support/ <p>We didn't get any reports about this caching issue yet. </p> http://www.kriesi.at/support/topic/changes-in-the-backend-only-show-up-after-deactivationreactivation-of-theme#post-21819 Thu, 30 Jun 2011 18:30:46 +0000 hamrockster 21819@http://www.kriesi.at/support/ <p>Thanks, I tried to clear Chrome's cache, but to no avail. I switched over to Firefox to rule out anything more serious, and to my relief the changes showed up there without the de/reactivation trick, and more importantly show up instantly when I use Firefox to do my changes from the dashboard. Is Display (or any other custom wp themes for that matter) experiencing problems when people try to use Chrome?</p> <p>Not a huge problem, just more of an inconvenience. Thank you for your quick response, I am sure I will be on here frequently as my site takes shape since I have some rather lofty customization goals. </p> <p>Scott </p> http://www.kriesi.at/support/topic/changes-in-the-backend-only-show-up-after-deactivationreactivation-of-theme#post-21788 Thu, 30 Jun 2011 10:50:13 +0000 Dude 21788@http://www.kriesi.at/support/ <p>Hey,<br /> this sounds like a browser cache problem. Try to clear the cache after each modification to review the sytle changes. </p> http://www.kriesi.at/support/topic/changes-in-the-backend-only-show-up-after-deactivationreactivation-of-theme#post-21766 Wed, 29 Jun 2011 23:51:41 +0000 hamrockster 21766@http://www.kriesi.at/support/ <p>Hello, I apologize if this is something completely obvious, but I am new to the more serious side of wordpress customization through commercial themes and whatnot. Anyways- I just bought the Display theme and have been trying to teach myself around it. For the most part it is pretty intuitive, but it seems that about 75% of the things I try to change (welcome tagline, logo, slider adjustments, custom menus, etc) only show up after I deactivate the theme, activate my old free theme, and then reactivate Display. I am currently still running Wordpress 3.0 and have not upgraded since I do not know if Display will run properly on WP 3.1.4. Chrome is my browser by the way. Any insight you can shed on this would be much appreciated, and I will keep on trying to debug this myself. </p> <p>Thanks, </p> <p>Scott </p>