Hi Polyfade,
Please can you let me know which line of admin.js is that error happening on?
Also, how did you install the plugin – do you happen to be using the development version somehow? I’m asking because there’s something in the development version which might be causing that error, but it hasn’t been officially released yet.
Regards,
Tom
Tom,
I updated from 1.8.1 to 1.8.2 again. The JS error went away, so let me tell you what’s going on from this point.
When trying to turn a regular link into a megamenu, I get the progress wheel and all options (select boxes) seem disabled. It won’t allow me to do anything but click ‘X’ icon to close the modal.
Sometimes it allows me to create a megamenu so long as the link has children links, but not always. And sometimes when it does, it won’t allow me to edit it again. Meaning, I get the progress wheel with seemingly disabled select boxes.
I see this plugin stores info to the database. Could it be my charset is set to utfmb4 rather than utf8 general? That’s the difference between the 2 sites I tested on.
FYI, if that’s the case, new/updated WP installs install with the utfmb4 charset. I’m not going to pretend I know anything about MySQL. https://goo.gl/n6QKyP
Hi polyfade,
I doubt it is anything to do with the database so you can rule that out, it sounds like a JavaScript error.
Please can you try a different browser and ensure you’re on a totally clean installation of WordPress, with just MMM and Twenty Twelve enabled? I would expect to see lots (loads!) of support items if this was a problem that’s happening for everyone, so I think it will be a conflict with a theme or plugin, or maybe a problem with your browser.
Regards,
Tom
Hello,
I have a kind of similar problem with myself developed child theme. With the parent premium theme and standard themes everything works fine.
When I click the “mega menu” button only the modal window itself appears with only [x] button on the side and a spinning wheel while ajax request is being fired. It never loads any other menu items of this modal window:
I’ve started debugging the case and found out that instead of getting json markup I get only “broken” symbols in response, something like:
� ��k�䶕���� �w���]�����b0�����ȇm���XUڑD�DuO’�_^t�D��%c�
The number of these “broken” symbols is exact the same as the number of symbols in the correct json response object from the server for other proper themes as twentythree or the premium one that I am inheriting on.
So I suggested there was some trouble with encoding and found out that in my child theme I don’t get two headers in the response object: Content-Encoding: gzip and Vary: Accept-Encoding that are sent in the responses to other themes. Here is the diff between request/response for my child theme (on the left) and other themes. The only difference is in these two response headers.
I can’t imagine why this might happen. I am not also sure that those headers are the reason of broken symbols.
Again this trouble takes place only in my child-theme, so I guess it is the real reason, but I don’t know what could I do the wrong way to break it down and the child-theme overrides several files.
Of course the encoding of the html document itself is UTF-8, DB collation is utf8_unicode_ci, plugin and WP are updated to the latest version, ajax request is sent in UTF-8 by default as I know.
It would be great to get any help! Thanks in advance!
Hi Fallah,
Apologies for the delay getting back to you. I haven’t come across that error before.
Do you still get the same error if you empty the contents of your themes functions.php file?
Regards,
Tom
