Topic on Project:Support desk

Hello,

I just set up my first MediaWiki site and I can't get the WidkiEditor toolbar to show up. I have scoured the internet, tried many things but with no success. Here is my current config:

IIS - 7

MediaWiki - 1.26.0

PHP - 5.6.16 (cgi-fcgi)

MySQL 5.7.9-log

I have these included in my config:

wfLoadExtension( 'WikiEditor' );

$wgDefaultUserOptions['usebetatoolbar'] = 1;

$wgDefaultUserOptions['usebetatoolbar-cgd'] = 1;

$wgDefaultUserOptions['wikieditor-preview'] = 1;

$wgDefaultUserOptions['wikieditor-publish'] = 1;

I'm not sure what else to try. Some direction would be very helpful.

Thanks,

-Gabe

Just to be sure: When you say that you have added the settings to your configuration, then you mean the file LocalSettings.php, right? This is where you should put these lines.

According to Extension:WikiEditor this configuration should work.

When, in your wiki, you visit the wiki page Special:Version, does it then list WikiEditor as being installed?

Thanks for the reply. I did add the lines the the LocalSettings.php. I even commented out all the other extensions just to make sure only the WikiEditor was installed.

The WikiEditor also shows up on the Special:Version page.

I agree that my configuration should work! I just can't figure out why it isn't...

Does the wiki have a public URL so that I can take a look?

I am guessing that you have some kind of JavaScript problem:

The problem is not that the wiki also is completely unstyled, right? Styling of the whole page, of the headline, the logo, tabs and so on all display fine, right?

In your LocalSettings.php file, is the variable $wgServer set correctly?

Edited from //localhost/ to

$wgServer="http://knxdfewsmc1:3037/"

Still, no luck.

It could be Manual:Errors and symptoms#Missing edit toolbar, JavaScript not working, or Manual:Errors and symptoms#The wiki appears without styles applied and images are missing

We are behind a firewall, so no public URL. The wiki is styled, so no problem there. Everything is displaying fine.

There doesn't appear to by any problems with the $wgServer varible. Tried several differnt configuration options.

I looked at the suggestions regarding JavaScript and I am not seeing any Java errors. However I am getting this from the web console:

Internal error

Problematic modules: {"startup:"errror"}

Not sure exactly what that means. Did a quick web search but didn't find much usefull. Any more thoughts?

Thanks!

Problematic modules: {"startup:"error"}

This may well be the reason for your problem. Please add

$wgResourceLoaderDebug = true;

to your LocalSettings.php file and see, if you afterwards get more information about the startup error you are having. This kind of error can e.g. be caused by an extension.

Added $wgResourceLoaderDebug = true;

Same error message, without anymore info.

I was hoping that would show some more info...

Me either.

Can you please again uncomment all extensions, clear all caches and try again?

We recently had someone, who had the same problem.

He also had all extensions deactivated, but the error remained. After some more testing - without extensions - he could nail it down to a faulty extension.

After trying all the suggestions and everything I could think of my last ditch effor was to downgrade to 1.25.3.

I see that the toolbar wikieditor works fine in verison 1.25.3.

Looks like it is a problem with 1.26. Not sure how to fix it so I guess we will have to stick with 1.26 for now.

I am not so sure about that. As with the other user, which Joerg mentioned, the problem in fact was an extension, although he had all extensions uninstalled - just like you had.

He most likely had a caching issue, which made him see the error, although it in fact was no longer present. And that is the problem, which you most likely have as well.

Or maybe an error in one of the JavaScript files, if it wasn't copied correctly. $wgResourceLoaderDebug only makes JavaScript to not be minified and also each module is split on its own request. The useful configuration here is $wgShowExceptionDetails. It won't show you a more meaningful error in JavaScript console, but opening the URL that loads that module on a new window should display the error details inside a JavaScript comment.