Pro Editor not loading on multisites

Support
#1

I have Pro installed on a wordpress multisite installation, but it is exhibiting strange behavior outside of the main domain.

To start, for each multisite I had to re-validate the theme, which from what I have been gathering through searching various topics should not be the case. It seems like I should have only had to validate on the main site in order to validate through all our sites. I used the same key (the one key I have) for all three and each time it went through without error.

Now I am facing the issue of the Pro editor not loading. It launches correctly, but selecting any of the options (Header, Footer, Content, etc) results in a loading bar across the top of the window and then nothing. Trying to click on Headers results in this error in the console: cs.js?ver=2.0.6:42610 Unhandled AJAX error. Expecting valid JSON from response. Object {readyState: 4, getResponseHeader: function, getAllResponseHeaders: function, setRequestHeader: function, overrideMimeType: function…} failOver @ cs.js?ver=2.0.6:42610 normalizejqXHR @ cs.js?ver=2.0.6:42629 run @ cs-vendor.js?ver=2.0.6:635 run @ cs-vendor.js?ver=2.0.6:24064 (anonymous) @ cs.js?ver=2.0.6:42635 (anonymous) @ jquery.js?ver=1.12.4:2 i @ jquery.js?ver=1.12.4:2 fireWith @ jquery.js?ver=1.12.4:2 y @ jquery.js?ver=1.12.4:4 c @ jquery.js?ver=1.12.4:4 cs.js?ver=2.0.6:330 Transition Error Object {} Transition {state: TransitionState, intent: C, router: Router, data: Object, resolvedModels: Object…}

similar errors result when clicking the other options.

Trying to launch Pro directly from an edit page on one of my sites results in the following error: jquery.js?ver=1.12.4:4 Mixed Content: The page at 'https://esports.eae.utah.edu/x/#/content/4' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://esports.eae.utah.edu/'. This request has been blocked; the content must be served over HTTPS.

But on another one of my sites, doing the same thing results in a series of errors similar to the first cs.js?ver=2.0.6:42610 Unhandled AJAX error. Expecting valid JSON from response. Object {readyState: 4, getResponseHeader: function, getAllResponseHeaders: function, setRequestHeader: function, overrideMimeType: function…} failOver @ cs.js?ver=2.0.6:42610 normalizejqXHR @ cs.js?ver=2.0.6:42629 run @ cs-vendor.js?ver=2.0.6:635 run @ cs-vendor.js?ver=2.0.6:24064 (anonymous) @ cs.js?ver=2.0.6:42635 (anonymous) @ jquery.js?ver=1.12.4:2 i @ jquery.js?ver=1.12.4:2 fireWith @ jquery.js?ver=1.12.4:2 y @ jquery.js?ver=1.12.4:4 c @ jquery.js?ver=1.12.4:4 cs.js?ver=2.0.6:330 Transition Error Object {} Transition {state: TransitionState, intent: C, router: Router, data: Object, resolvedModels: Object…}

I recognize that one of my sites clearly has an ssl issue to sort out, but the other sites do not and still refuse to load the front-end editors. The main site loads all the editors just fine.

I believe the error might stem from the fact that during a recent overhaul of the site (when we switched to the Pro theme), I created a new site under the multisite and once it was ready used a domain mapper to redirect the main site to that one. At that point I think I had my license just attached to the one site and had to re-assign it to the whole multisite. Which I think may be the reason why Pro asks for re-validation every time I make a new subsite but I’m not sure.

Any help in sorting this matter is appreciated. More information can be provided as necessary.

#2

Hey,

if you could post some logins details in a secure note and we`d be happy to take a look.

P.S: You can search by “secure note” on this article if you don`t know about this: https://theme.co/apex/forum/t/themeco-support-overview/288

#3

See attached.

#4

Hello There,

Thanks for writing in! Please keep in mind that one license can only be used with two domains at the same time. One for the staging and for the live site. Even if you set up multisite, since each of the sites were using sub domain names the validation and the use of the license will still apply. Pro editor should still work even if it is not yet validated.

Based on the information above, it is not working because of mixed content issue.

jquery.js?ver=1.12.4:4 Mixed Content: The page at 'https://esports.eae.utah.edu/x/#/content/4' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://esports.eae.utah.edu/'. This request has been blocked; the content must be served over HTTPS.

To resolve this issue, please go to your network admin > sites and make sure that the site url and wordpress url is using https.

Please let us know how it goes.

#5

I checked this setting and confirmed that the site url (one we have been testing) is not running https:
However the site address is:

Attempting to change the siteurl from the settings page results in no change.

I have talked extensively with our IT department in an attempt to force our site to use SSL. They informed me that everything should be running through SSL now, but I am still getting mixed content errors. Are there any other methods to change this setting?

typing https manually into the address bar with the editor allows editing of headers and footers but the content editor still gives the “A conflict on the front end of your site has prevented the preview from loading” error.

#6

Hello There,

Thanks for writing in! You should be able to change it in the Network Admin > Sites and click on the site and then Settings tab. If possible, can you please make the given user credentials as SuperAdmin so that we can take a closer look at your sites?

Thank you in advance.

#7

Having the same issue! Can’t edit content in any language.

#8

Hi @Mr.alriksson,

Would you mind starting a new thread and provide your site’s URL and login credentials there? And don’t forget to add them in a secure note.

Your issue might be related to translation plugin or feature which is different from this thread.

Thanks!

#9

Thanks, posted over here: https://theme.co/apex/forum/t/pro-editor-not-loading-on-multisites-polylang/13756

#10

Thanks! Let’s discuss it there.