Tagged: editing window, Error, preview URL
- This topic has 4 replies, 2 voices, and was last updated 10 years, 1 month ago by
Sebastian.
Author | Posts |
---|---|
husterk
March 12, 2015 at 3:05 pm
|
Heads up! this post was created when Microthemer was at version 3. The current version is 7. Some references to the interface may be out of date. I just installed Microthemer on a local copy of my site hosted by WAMP Server. The site loads fine and I can access the WP Admin dashboard. However, every time that I attempt to navigate to the Microthemer dashboard I am simply shown a “The server refused the connection.” error message. I can get to the Microthemer preferences page but not the Microthemer dashboard view so I am not able to edit my site layout. Please help! |
Sebastian
March 13, 2015 at 5:10 am
|
Hi there, It’s possible that this is caused by lack of support for gzip compression on your wamp server. Could you try going to the Microthemer > Preferences page and setting the Gzip option to ‘No’. If that works, we know what is causing the issue. But a preferable option is to enable gzip compression in wamp: http://www.zigpress.com/2009/04/09/enabling-gzip-on-wamp/ Please let me know if that solves your problem. Thanks, |
husterk
March 13, 2015 at 12:02 pm
|
Thanks for the quick response. I enabled the deflate_module and headers_module per your instructions and updated the httpd.conf file to allow for GZip compression. Unfortunately this did not resolve the issue. I then disabled GZip on the Microthemer preferences page but that did not help either. Any other suggestions? Are there any log files generated by the Microthemer plugin that I could examine? |
husterk
March 13, 2015 at 12:08 pm
|
I figured it out! I had to add a trailing “/” to the Frontend preview URL on the Microthemer preferences page. It looks like this may be an issue with Chrome / Microthemer. When I copy and paste the URL from the Frontend Preview URL form input into the Chrome address bar the navigation attempts to append a port number (i.e. :8081) for some reason (maybe something stuck in my cache). By appending the trailing slash it no longer attempts to append the port number and everything works fine. |
Sebastian
March 14, 2015 at 5:21 am
|
Brilliant! I’m really glad you managed to sort this. I’m sorry I wasn’t quicker to respond. I was thinking the iframe might have something to do with it, but I wouldn’t have guessed the port number issue. Good work. Sebastian |