- This topic has 3 replies, 2 voices, and was last updated 6 years, 4 months ago by
Sebastian.
Author | Posts |
---|---|
adkoen
November 27, 2018 at 8:10 am
|
Heads up! this post was created when Microthemer was at version 5. The current version is 7. Some references to the interface may be out of date. Hi Sebastian, When working/updating a website on a local install, do I need to copy over the database to move over the CSS and selectors generated by Microthemer? Or is it enough to copy over the folder where all the css/scss is written to files? Reason for asking, just want to know the inners when pulling such a website locally and make some edits. Maybe it’s not necessary to pull the database too. I would be a bit easier for websites that have a lot going on. I do understand the Microthemer settings are stored in the database. That’s no problem. And one more thing, any idea if I could call a function from my own plugin and have Microthemer save and compile the scss file to css? The same actually as when you hit save when working with Microthemer. Thanks!!! |
Sebastian
November 27, 2018 at 9:54 am
|
Hey Koen, Microthemer’s style settings and workspace settings are stored in the wp_options table. Look for the following option_name keys: microthemer_ui_settings (style settings) Revision history is stored in a dedicated table: wp_micro_revisions I recommend copying the database as well to avoid surprising behaviour. MT expects settings to exist in the DB, and so I foresee potential problems. Although I can’t predict exactly what would happen right now. Micorthemer uses the following SCSSPHP library to compile SCSS to SCSS: http://leafo.github.io/scssphp/docs/ So you could just install that yourself somewhere and then include the library where you need it. Here is some sample code to help you get started:
I hope that helps! Cheers, |
adkoen
November 27, 2018 at 10:03 am
|
Yep, it sure helps 🙂 |
Sebastian
November 27, 2018 at 10:30 am
|
No, I just change the name of the library folder to signal when it was last updated. This isn’t strictly necessary. I could flag this some other way if you want to tap into MTs version of SCSSPHP? The import path will always be /wp-content/micro-themes/ |