Support
Sebastian.| Author | Posts |
|---|---|
 Sebastian
August 7, 2013 at 7:42 pm
|
Heads up! this post was created when Microthemer was at version 2. The current version is 7. Some references to the interface may be out of date. When upgrading to Microthemer 2.3.2 or 2.3.5 WordPress may deactivate the plugin and return an error message on the Plugins page saying Microthemer was deactivated because the plugin file doesn’t exist. The solution is simple – ignore the message and reactivate Microthemer. This happened because under some circumstances the plugin extracted to a folder called “crothemer” instead of “microthemer” (and so WordPress had the wrong file path saved in the database). Version 2.3.5 fixes this issue, but if you’re upgrading from 2.3.2 to 2.3.5 you’re going to get the same problem (as the folder has changed again from “crothemer” back to the normal “microthemer”). Just ignore the message and reactivate Microthemer. This won’t happen with future updates. Apologies if this causes any inconvenience! Sebastian |
|
Sebastian
August 7, 2013 at 7:42 pm
|
ps I haven’t released version 2.3.5 yet, but I will very shortly. |
