- This topic has 1 reply, 2 voices, and was last updated 11 years, 7 months ago by
.
-
Posts
-
-
Hi there,
I havent updated to Mikmag 2 because we have customized our version (V1.3.2) so much that it would probably take 2 weeks time to sync to your changes with v2 (I have noticed that there is not one file you haven’t touched!).
Thus, related to above, my question comes: should i upgrade to today’s new WP release of 3.5.2? If i do, would it break anything?
What about WP 3.6?
I am testing on xampp and can’t notice anything but still do not want to gamble as we have more than 100K of posts.
thanks,
Jim
-
Hi Jim,
Mikmag 2.0 was released as a version to be compatible with 3.5.1+ (as the previous version was not compatible) and woocommerce 2.0. Other than this compatibility, a lot of work has been done on cleaning up the theme and bringing it back to the top with a completely overhauled framework. A lot of bugs have been fixed and functionalities updated. I can imagine pretty much all files have been touched as the work on the update has been quite massive.
I wouldn’t suggest to bring mikmag 1.3.2 to wordpress 3.5. I don’t know what wordpress version you are using now, I would guess 3.4.2?
Mikmag 2.0 has been made compatible with the WP3.6 beta so if wordpress doesn’t stray too much from their beta with the official release it shouldn’t be much of a problem.
What might be interesting for you to know is that one of the new functionalities that came with mikmag2.0 is the ability to create child themes. That means updating the theme versions on customized sites has become a bit easier and safer than it is in 1.3.2.
Whatever you decide to do, I very much advise you to make a backup of your current theme version (or even 2 backups, may you accidentally mess with one). I agree you can never be safe enough with things like this so a backup to fall back on is always important.
Kevin
-
-
- You must be logged in to reply to this topic.