WYSIWYG Editor suddenly stopped working

[dan325ci]

Our WYSIWYG Editor stopped working. I actually don't know when this happened but our users have been complaining so I am guessing recently. Ive tried disabling all mods and that didn't fix it. Tried clearing cache, and still broken.

Any other suggestions to fix this?

[dan325ci]

I used the fix outlined here: http://tracker.vbulletin.com/browse/VBIV-15721 and that fixed it up.

So what is the issue here? I am guessing that above fix is not the best solution otherwise it would be fixed already in the latest stable release.

[Mark.B]

This shouldn't be happening. I have converted multiple vB 4 sites to HTTPS without any effect on the editor.
However, I have seen several reports of this behaviour, so it would be interesting to find out what is really going on, since I just can't replicate it.

What version of vBulletin are you running?

[dan325ci]

This shouldn't be happening. I have converted multiple vB 4 sites to HTTPS without any effect on the editor.
However, I have seen several reports of this behaviour, so it would be interesting to find out what is really going on, since I just can't replicate it.

What version of vBulletin are you running?

Right now we are running the latest stable version of 4.2.4.

I am not 100% sure if the move to https is the cause or not. I just recently noticed that the WYSIWYG editor was even missing although we converted to HTTPS a couple months ago. Having said that, I didn't make any changes lately so it may have been like this for a while.

[Paul M]

You are probably using off-loaded https (Cloudflare Flexible ?)

Turning on the "Always use Forum URL as Base Path" option will likely fix it.

(and undo whatever "fix" you made).

[dan325ci]

You are probably using off-loaded https (Cloudflare Flexible ?)

Turning on the "Always use Forum URL as Base Path" option will likely fix it.

(and undo whatever "fix" you made).

Yes we have a Cloudflare SSL certificate we purchased from them. (but that was many months ago, well before this issue started)

The "Always use Forum URL as Base Path" was already set to YES

Any ideas now what?

[dan325ci]

Just updated to 4.2.5 and still getting the WYSIWYG editor problem unless i implement the fix here: http://tracker.vbulletin.com/browse/VBIV-15721

Any ideas what next?

[Mark.B]

Go to Settings > Options > Server Settings & Optimization Options > Use Remote YUI
Make sure this is set to Google.

[dan325ci]

Go to Settings > Options > Server Settings & Optimization Options > Use Remote YUI
Make sure this is set to Google.

From what i can tell, that fixed it up. We had it set to NONE before. Thank you.

[Wayne Luke]

From what i can tell, that fixed it up. We had it set to NONE before. Thank you.

Interesting, as the problem shouldn't occur with NONE if you have updated your forum URL in the settings to reflect HTTPS.

[dan325ci]

Interesting, as the problem shouldn't occur with NONE if you have updated your forum URL in the settings to reflect HTTPS.

Ok i was completely mistaken. Turns out I never reverted the class_bootstrap.php file back to original. Changing REMOTE YUI to Google does not help at all. It turns out that the only way to get the WYSIWYG editor to work is to replace the following in class_bootstrap.php:

$templater->register('ajaxbaseurl', VB_URL_BASE_PATH);

with

$templater->register('ajaxbaseurl', $vbulletin->input->fetch_basepath());

Remote YUI actually does not help at all. Sorry for all the confusion. I am still back to square one now with no resolution except editing the above file.

[Paul M]

That's an unnecessary (and wrong) change.

Set the correct option in the 4.2.5 config file, and revert the change.

[dan325ci]

That's an unnecessary (and wrong) change.

Set the correct option in the 4.2.5 config file, and revert the change.

Paul,

You are referring to this in the config file right?

/* #### FORCE URL SCHEME ####
By default, vBulletin will try and work out what URL scheme to use (http or https) by checking the incoming page request.
However, in some circumstances, this can fail. You can force the scheme to 'http://' or 'https://' using the below setting. */
//$config['Misc']['vb_url_scheme'] = 'https://';

I have always just changed my path in the admin panel, i never knew about this setting. So just uncomment that $config line out?



UPDATE: uncommented the above but it still did not work after reverting my changes.

[Mark.B]

Yes, uncomment it.

[Paul M]

Paul,

You are referring to this in the config file right?

/* #### FORCE URL SCHEME ####
By default, vBulletin will try and work out what URL scheme to use (http or https) by checking the incoming page request.
However, in some circumstances, this can fail. You can force the scheme to 'http://' or 'https://' using the below setting. */
//$config['Misc']['vb_url_scheme'] = 'https://';

I have always just changed my path in the admin panel, i never knew about this setting. So just uncomment that $config line out?



UPDATE: uncommented the above but it still did not work after reverting my changes.

Yes, that option.

Make sure you have added it to your actual config file (copy it from the example). It was only added in 4.2.5.

Given how the code works, it find it hard to believe it doesnt fix the basepath. Since it does on every test forum I have.