Are you on multisite with domain mapping? If so, editing a domain that’s not the primary parent domain is usually blocked by mod_security on the server.
It’s also possible your server has its security reacting to a false positive, meaning it’s mistaking your editing for something bad. That you would have to ask your hosts about.
It could also be a plugin or theme conflict. Deactivate all plugins except microthemer and see if it works. If so, reactivate one by one until you identify the culprit.
If it still fails with all plugins disabled, try the default wordpress theme to see if that works.
@Abland, many thanks for your suggestions, as always.
@jallen148 If you can send me login details for your site via this secure contact form I will troubleshoot the issue for you. Unless you would prefer to try out Ablands suggestions yourself first.
I took on this project for a university, and I knew they had some crazy tight security restrictions going in – such as, I can only get FTP access to the site through VPN.
I hadn’t done a lot with wordpress so I was looking forward to trying Microthemer to help smooth out layout tasks.
But, Abland hit it on the head – security is too tight for the plugin to do it’s job. I can’t even edit .php and stylesheets using the built in WordPress editor. On top of everything, turns out they’re using IIS servers so, even though I have FTP access, I can’t change permissions on files. Looks like I’ll have to slog along doing things the hard way on this one. I’m sure I’ll get a chance to try Microthemer on another project.
Ah that’s a shame you can’t use Microthemer on the University server. But thanks for sharing your experience.
If tight permissions cause you a headache when working with WordPress in general, you might prefer to work on a copy of the website locally. Have you used WAMP or XAMPP for Windows/Mac?
Besides not liking to work on things “live”, I got a call today while I was out and about asking about one of the social media feeds not updating. Tried to login to the admin console with my phone and remembered: they only allow me to access the admin console from my home IP.
Working on it locally sounds like just the ticket. Is there anything to look out for when uploading the site from a local copy? Any good WAMP related resources you can recommend? (I know that’s well beyond the scope of Microthemer support, but hey… you brought it up!)
Sorry for the slow reply. I went looking for WAMP resources yesterday and then got distracted. I find WAMP to be the easiest of the bunch to install first time without problems, but they can arise. Unfortunately there isn’t a great repository of WAMP learning resources I can point you in the direction of beyond the WAMP forum. I recommend reading the ‘sticky’ posts at the top.
WAMP is a quick install of (Windows) Apache, MySQL, and PHP (WAMP). These technologies are updated frequently. So try to find recent tutorials if you can, otherwise you may get incorrect information.
With regards to FTP uploading, you will need to have a separate wp-config.php file, as the database connection details will be different on the live site compared to your local install. I normally put it into a sub folder called ‘live’ and then copy it to the root directory only on the live version of the site.
Also, unless you set up a virtual host with exactly the same domain name as the live site, you will need to do a find and replace of URLs in the database. I use this tool for that.
Of course you can use the same domain name as the live site when setting up your virtual host. In which case you will need to update your windows .hosts file when switching between the live and local site (which is covered in the WAMP sticky post about virtual hosts). And to ensure this has an immediate effect, you will want to flush your DNS cache.
Not to butt in or anything, but my setup contains DesktopServer with a custom blueprint so I have everything installed in one go. WordPress, Microthemer, Yoast SEO, BackupBuddy and so on.
Might that be helpfull for you?
DS has no real learningcurve. So that saves time :-).
.
.