Anyone getting "Aw, Snap!" screen using microthemer?

Author Posts

cjseven April 27, 2015 at 11:42 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.

Hello,

I have installed MT on one site, and I’m getting the “Aw Snap!” chrome screen after a few seconds inside MT panel.

I already deactivate all plugins and changed the theme to verify any conflict, but the issue remains.

I also checked my other MT powered sites and everything seems ok. So it is something with this website but I can find what it is…

Any ideas?

Sebastian April 28, 2015 at 3:15 am

Hi Antonio,

Yes it sounds like something is conflicting with Microthemer on that particular install. Could you email me login details for that site via our contact form so that I can troubleshoot?

https://themeover.com/support/contact/

Thanks!
Sebastian

cjseven April 28, 2015 at 2:32 pm

Hi Sebastian,

Email sent.

Thank you.

Sebastian April 30, 2015 at 4:11 am

Thanks for the details Anotonio.

I was getting the same Aw snap error as you. I set the preview URL in the Microthemer preferences to: http://eivissa.in/wp-content/plugins/microthemer/includes/place-holder2.html to rule out any scripts in the frontend – the error still happens. I think the problem could relate to a conflict between your MainWP Child plugin and Microthemer. Specifically this section of code which it adds to the left WordPress menu for creating a dashicon menu item:

<a href='admin.php?page=mainwp_child_tab' class="wp-has-submenu wp-not-current-submenu menu-top toplevel_page_mainwp_child_tab" aria-haspopup="true"><div class="wp-menu-arrow"><div></div></div><div class='wp-menu-image dashicons-before'><img src="data:image/png+xml;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAA2RpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADw/eHBhY2tldCBiZWdpbj0i77u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlkIj8+IDx4OnhtcG1ldGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhNUCBDb3JlIDUuMC1jMDYwIDYxLjEzNDc3NywgMjAxMC8wMi8xMi0xNzozMjowMCAgICAgICAgIj4gPHJkZjpSREYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjIj4gPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIgeG1sbnM6eG1wTU09Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC9tbS8iIHhtbG5zOnN0UmVmPSJodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvc1R5cGUvUmVzb3VyY2VSZWYjIiB4bWxuczp4bXA9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC8iIHhtcE1NOk9yaWdpbmFsRG9jdW1lbnRJRD0ieG1wLmRpZDpFMjE1RkEwNjU5RjhFMjExQURFMkZGNjRFNThEMDA2OSIgeG1wTU06RG9jdW1lbnRJRD0ieG1wLmRpZDoxMjM3M0VFRkZBMTgxMUUyQTY0Mjg1RUEwQUYzQUEwRiIgeG1wTU06SW5zdGFuY2VJRD0ieG1wLmlpZDoxMjM3M0VFRUZBMTgxMUUyQTY0Mjg1RUEwQUYzQUEwRiIgeG1wOkNyZWF0b3JUb29sPSJBZG9iZSBQaG90b3Nob3AgQ1M1IFdpbmRvd3MiPiA8eG1wTU06RGVyaXZlZEZyb20gc3RSZWY6aW5zdGFuY2VJRD0ieG1wLmlpZDozODBGMzQyMjIzRjlFMjExOUZCRDgzMjVFM0I5NTM5QyIgc3RSZWY6ZG9jdW1lbnRJRD0ieG1wLmRpZDpFMjE1RkEwNjU5RjhFMjExQURFMkZGNjRFNThEMDA2OSIvPiA8L3JkZjpEZXNjcmlwdGlvbj4gPC9yZGY6UkRGPiA8L3g6eG1wbWV0YT4gPD94cGFja2V0IGVuZD0iciI/Pj1o4GcAAAIkSURBVHjaZJNPaBNREMa/3Wy6blppY0JtWmOtKPYgLUixt6ao4F8QTwUP3iQIimihV/HiSU8qiB6q4Ek8qBcFaxVr1UMRxYp4UWhUqilRYzVNk934zXOTvk0GfvD2zez35s2bMc7cRb0NkrRXwQ7XQxfXhmnia8jAY66vkmk92NLWNjlHjlUAp9VJoMXuUI6/y9nkz8LnIwYwws9rZIwUxGdqP98mp4lTcoEN8RTSqVeKLR0HsVyuxR0n90hEF5CTD1RTCXE3k3sBt1JU33O5KbWn2S5yoXqFAXJC9/K++FWYw8N3YwhbESwsfqgXEEuTm5afUlj3uCxCrLkbw71nYZk2PmYn8GlhBk2hgIAh/5p+OgErswY9sRRWWW0UcNCbOIRWJ66EDSMQOiwCnfW6ErSpfU9tq7NtAP3Jw4hGkih7gei1DTer8JQWuxndsaGVqNV9zKqI/X0XWR87EC8C84H0PTlxG0VWEpN+KJRycMIx+raqq/iWFYFJXcCjwOb2fQ0l3xjfifHpvfien1Wv5NtTEbgkhdd7oCu6vUFgXXSQ2S2i5BX17csi8JJcqdWQ6vffjiK/lKlFldw/eDA7Wns738bJk2oRpbcnVGdJF/54jRvPd+P30hflvDUzgvfzk8rn2zNyUglq0yi9fZ4cZRZWkb2/fk0/n64HbzJ30PR/7OQRr5NTJF8vUDV5vzRFhjhUCY61dOA37k35k/hID/4nwACMf5SQmUsK8gAAAABJRU5ErkJggg==" alt="" /></div><div class='wp-menu-name'>MainWP Child</div></a>

I’m not sure why this code might be causing an issue on the Microthemer UI page but no other. I didn’t want to disable that plugin to confirm my hypothesis either as it looks like the site is live and active. I’ve emailed MainWP in case they can shed any light on this.

I’ll update you when I know more.

Cheers,
Sebastian

cjseven April 30, 2015 at 11:02 am

Hi Sebastian,

You can deactivate that plugin if you think it could help. In fact, you can do whatever you like with that WordPress install because I’m just beginning the project.

I didn’t deactivate before because all my other sites have mainwp installed and I didn’t think it could be the problem.

However, that code is strange. It seems like the site was hacked. I will check that also.

Thank you,
Antonio

You must login or register to reply to this topic.