1BJK903

Sorry for my late response, was quite busy.

It probably echos the name of my own content directory, but don’t know how to log it. Can you help me with that?

Goedemorgen, Frank.

I made it like this:

define ( ‘WP_CONTENT_FOLDERNAME’, ‘newfoldernamehere’ );
define ( ‘WP_CONTENT_DIR’, ABSPATH . WP_CONTENT_FOLDERNAME );
define ( ‘WP_SITEURL’, ‘https://’ . $_SERVER[‘HTTP_HOST’] . ‘/’ );
define ( ‘WP_CONTENT_URL’, WP_SITEURL . WP_CONTENT_FOLDERNAME );
require_once(ABSPATH . ‘wp-settings.php’);

Great job, Milan!

Solved it..

It was Autoptimize… haha. I excluded quicktags and the quicktags min JS, but removed jQuery from exclusion and it suddenly worked.

Thank you guys, I appreciate the help.

Weer wat geleerd. Fijne feestdagen!

The JS files that are missing when not logged in, are:
basic-comment-quicktags/quicktags.js?ver=3.1
wp-includes/js/quicktags.min.js?ver=4.4

And the inline JS:
<script type=’text/javascript’>/* */
var quicktagsL10n = {“closeAllOpenTags….. </script>

Hi Frank,

Even when I exclude those, I don’t see the Javascript containing Quicktags, while it appears when logged in. And yes, I tried to disable your plugin, still the same.

Your plugin is a nice btw, I have to say that. Top werk, dank daarvoor.

Haha of course you are.

Anyhow, is there a chance that it might be the Autoptimizer plugin? I am minifying, defering scripts, so maybe it is affected by it?

I will check it tomorrow. Will provide the solution here when I find it.

Thanks for the swift response, Mika.

I enabled all debug scripts, but it doesn’t point me anywhere. It gave a notice of ssl_login being depracated, but that’s it. Nothing with quicktags, whatsoever. I am pretty sure that it has something to do with one of my plugins, but I can’t get what precisely.

Are you running WordPress 4.4 as well?

PS: I disabled Autoptimizer cache plugin, but still the same… I thought that it prevented it or something, but nope.

I don’t get it.

@figu: 3.2.0 was the last stable version I know.

Thanks, Julien.

Thanks, although 3.2.2 has the same problems. Good to know we can downgrade.

Do you have a fix planned for these problems? If so, when?

Not working @ Julien. With 3.2.3, the settings page is resetted to default after saving.

The same problem occurs with 3.2.3

@julien: he says that he has updated to 3.2.3

I have the exact same issues after upgrading to 3.2.3. The “settings” pages are resetted to default after saving… the styling is not correct… the WYSIWYG editor isn’t showing up. Styling is not correct as in: button links aren’t styled, buttons aren’t styled, labels have incorrect link colors…

So have the same problems.

Is there a way to downgrade to a earlier version, somewhere?

Thanks Julien…

Last problem: the “submit ticket” button isn’t working. It gives an error cause the URL isn’t right anymore. Can you check that as well?