Last modified: 2010-11-16 11:51:09 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 23300 - Nothing appears, whether asking for own window or not
Nothing appears, whether asking for own window or not
Product: MediaWiki extensions
Classification: Unclassified
FCKeditor (Other open bugs)
PC Windows XP
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2010-04-23 16:11 UTC by Even Thorbergsen
Modified: 2010-11-16 11:51 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Even Thorbergsen 2010-04-23 16:11:58 UTC
Using FCKeditor (versjon 1.0.1) with MediaWiki 1.15.1.
Testing both with IE and Chrome.

Nothing appears after pressing edit and then [Rich text editing] or [Open rich editor in new window]. The first changes to [Loading...], but nothing more happens. The other produces a blank window.

I have set

error_reporting( E_ALL );
ini_set( 'display_errors', 1 );

at the start of LocalSettings.php, but no error message is issued.
Comment 1 cgraamans 2010-11-16 11:51:09 UTC
I think I had the same bug. It appears to be an error in the Javascript that loads FCK.

I get the following in my Error Console in FF:
Error: oFCKeditor is undefined
Source File: http://somesiteswiki/index.php?title=Main_Page&action=edit
Line: 319

This points to this bit of code:
oFCKeditor.ready = false;

You may also get an error mentioning wpTextbox1.

The error is quite simple to resolve though: The javascript in the extensions directory is not being loaded (or seen as an actual wiki page) because there're some rewrite rules set in Apache.

Try adding this line in your apache configuration:
RewriteCond %{REQUEST_URI} !^/(stylesheets|images|skins|config|maintenance|extensions)/

[N.B. if you're not sure where to look: /etc/apache2/vhosts.d/vhosts.conf or in your httpd.conf. It's in there somewhere.]

If you already have a line like this in your Apache config just add the |extensions bit to the end of the pipe-separated string or modify the existing rewrite conditions to exclude the extensions directory.

That should solve it.

Note You need to log in before you can comment on or make changes to this bug.