Last modified: 2011-09-23 18:44:52 UTC
WikiEditor doesn't load in debug mode on 1.17 and 1.18 Works fine on trunk though seemingly
This makes it hard to debug wikiEditor or extensions thereto.
Works for me on test2wiki, both on secure (logged in) and non-secure (logged out).
Works for me on trunk, 1.18, 1.17, and the live sites test2.wikipedia.org and mediawiki.org
Created attachment 9088 [details] debug=false debug=false Not shown
Created attachment 9089 [details] debug=true
There's obviously something a miss somewhere... :/
Well since it's just you, you might need to dive into your debugger and see what's going on...
(In reply to comment #7) > Well since it's just you, you might need to dive into your debugger and see > what's going on... It's not just me. It was reported on IRC, and I was able to verify it. The only main difference in my configs is memcached setup for my trunk wiki, setting it for the others makes no difference reedy@ubuntu64-esxi:~$ apache2 -v Server version: Apache/2.2.17 (Ubuntu) Server built: Sep 1 2011 09:31:14 reedy@ubuntu64-esxi:~$ php -v PHP 5.3.5-1ubuntu7.2 with Suhosin-Patch (cli) (built: May 2 2011 23:00:17) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies with Xdebug v2.1.0, Copyright (c) 2002-2010, by Derick Rethans reedy@ubuntu64-esxi:~$ mysql --version mysql Ver 14.14 Distrib 5.1.54, for debian-linux-gnu (x86_64) using readline 6.2 Right, fixed for me by setting $wgExtensionAssetsPath = '/w/extensions/extensions'; As my extensions are in branch/extensions/extensions NOT branch/extensions So it's a config issue, WFM is still true
I reported this issue to Reedy on IRC. So, setting $wgExtensionAssetsPath is a workaround?
(In reply to comment #9) > I reported this issue to Reedy on IRC. > > So, setting $wgExtensionAssetsPath is a workaround? Setting $wgExtensionAssetsPath correctly is *necessary* for any extension to work correctly in debug mode.
Documented: http://www.mediawiki.org/wiki/Manual:$wgResourceLoaderDebug
The default value for me should suffice - I've moved nothing around. Same issue. How can I debug this?
You have in fact moved things (or rather set up from the beginning in a non-default place, namely the fact that your extensions are not in scriptpath/extensions but somewhere else). You should always set wgExtensionAssetsPath, just like one sets wgScriptPath, wgArticelPath in LocalSettings etc.
I figured out what my problem was - it was a conflict between JavaScript libraries. Running in debug mode changed the order in which they load, which in turn caused issues. Leaving $wgExtensionAssetsPath undefined works for me.
