[wp-hackers] JavaScript related functionality failure on some admin pages. 3.5.1

[Otto]

The base problem here is that you're getting the 404 error on the
load-scripts.php URL. Using the options you're describing "fix" the
problem because you're not using that load-scripts URL anymore.

So the question you need to focus on is why you're getting that 404 in
the first place. Does the file exist? Do you have some .htaccess rules
interfering? Anything of that sort. This is a problem that you will
find the answer to on the webserver, not within WordPress itself.

-Otto


On Tue, Feb 26, 2013 at 3:41 PM, Haluk Karamete <halukkaramete at gmail.com> wrote:
> Thank you for your reply Aaron. But no, we have not installed that plug in.
>
> As I said in my original post, I went thru the ritual of deactivating all
> my plug ins including reverting to the twentyEleven.
>
> Here is some more insight about this issue..
>
> I do not have to live with the define('SCRIPT_DEBUG', true), I can
> perfectly comment it out and use this instead;
>
> define('CONCATENATE_SCRIPTS', false);
>
> That works too. So I will be keeping that on as of now.
>
> What I've also observed was this, whenever I use SCRIPT_DEBUG(TRUE) or
> CONCATENATE_SCRIPTS(FALSE) solutions, the following takes place on the VIEW
> SOURCE;
>
> With them,  I get this on the source
>
> <script type='text/javascript'
> src='..../wp-includes/js/jquery/jquery.js?ver=1.8.3'></script>
>
> Without, I get the following,
>
> <script type='text/javascript'
> src='....wp-admin/load-scripts.php?c=1&amp;load%5B%5D=jquery,utils,plupload,plupload-html5,plupload-flash,plupload-silverlight,plupload-html4,json2&amp;ver=3.5.1'></script>
>
> which is exactly where the 404 was stemming from.
>
> I read the codex on the  SCRIPT_DEBUG (
> http://codex.wordpress.org/Debugging_in_WordPress#SCRIPT_DEBUG )
> which has the following to say...
>
> SCRIPT_DEBUG is a related constant that will force WordPress to use the
>> "dev" versions of core CSS and Javascript files rather than the minified
>> versions that are normally loaded.
>
>
>
> I rather leave the one-liner *define('CONCATENATE_SCRIPTS', false);* in the
> config, than leaving the other one liner which is* the
> define('SCRIPT_DEBUG', true);*
> *
> *
>
>
>
>
> On Tue, Feb 26, 2013 at 1:09 PM, Aaron Jorbin <aaron at jorb.in> wrote:
>
>> Are you currently, or have you ever used BulletProof Security?
>>
>>
>> http://wordpress.org/support/topic/troubleshooting-wordpress-35-master-list#post-3547427
>>
>> http://aaron.jorb.in
>> twitter: twitter.com/aaronjorbin
>>
>>
>> On Tue, Feb 26, 2013 at 3:59 PM, Haluk Karamete <halukkaramete at gmail.com
>> >wrote:
>>
>> > On 3.5.1 installs, ( and I got two of them ), the admin area JS actions (
>> > such as the "Screen Options" or the "Help" pull downs and a whole bunch
>> of
>> > more functionality that relies on DHTML effects) all fails.
>> >
>> > To troubleshoot the problem, I checked the JavaScript console ( chrome
>> > developer tools ), and I saw a 404 being reported in there.
>> >
>> > GET .../wp-admin/*load-scripts.php*
>> >
>> >
>> ?c=1&load%5B%5D=admin-bar…alog,wpdialogs,wplink,wpdialogs-popup,wp-fullscreen,media-upload&ver=3.5.1
>> > 404 (Not Found) post.php:41
>> >
>> > And this 404 comes up only on some pages at the admin interface.
>> >
>> > For example, when adding a new post ( using the /wp-admin/post-new.php ),
>> > there is no 404 issue and thus no js issues. Everything works like a
>> charm.
>> > But once the post is published and the /wp-admin/post.php responses
>> back, I
>> > get that 404 back again and that's when all the js issues are back.
>> >
>> > I don't know what's causing this, but the following one-liner in the
>> >  wp-config.php totally fixes it.
>> >
>> > *define('SCRIPT_DEBUG', true);  *
>> >
>> > which is not recommended to keep it on a production site.
>> >
>> > So I got this dilemma now. What do I do?
>> >
>> > To eliminate the problem, I not only switched our current theme to
>> > the TwentyEleven( to see if theme is the culprit ),  but no, it wasn't.
>> > Symptoms were the same with TwentyEleven.
>> > I also deactivated all the plugins one by one but no luck... this did not
>> > help neither.
>> >
>> > So to get going, I had to leave the SCRIPT_DEBUG option on...
>> >
>> > But, what's your advise for getting rid of this issue without the
>> > SCRIPT_DEBUG being TRUE?
>> >
>> > And out of curiosity, what is it with define('SCRIPT_DEBUG', true); that
>> it
>> > magically fixes the problem?
>> > _______________________________________________
>> > wp-hackers mailing list
>> > wp-hackers at lists.automattic.com
>> > http://lists.automattic.com/mailman/listinfo/wp-hackers
>> >
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers