Take the 2-minute tour ×
WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. It's 100% free, no registration required.

I've found other posts related to this, but none had a answer to my issue.

After updating to WP 3.4 my visual editor is broken.

Firebug reports this error

Failed to load: http://xxxxxx.com/wp-includes/js/tinymce/langs/pt.js

wp-tin...9-20805 (linha 1)

I've tried setting the theme to a default theme and it WORKS.

So, is there any way I can determine what's causing this in order to fix it?

share|improve this question

2 Answers 2

There shouldn't be a pt.js file in that directory. There wasn't in 3.3.2 nor in 3.4. There's several possible issues that could be taking place, but my guess is that your WordPress install has been compromised and your theme files are corrupted. They are then trying to access that js file which is no longer there and it's no longer there because it's within the WordPress core which gets erased during an update.

Download your theme file and do a search for pt.js. Also do a search for eval(base64_decode and see if anything comes up.

share|improve this answer
    
There's no pt.js at the original theme files nor there's any instance of 'eval(base64_decode' at any of the files. –  Souljacker Jun 15 '12 at 21:17
    
If the file is only being requested by that one theme, then there has to be a reference to it within the theme files. You search the code of the files for a reference to that file, correct? (Not just searching the theme for that file.) –  user1337 Jun 15 '12 at 22:30
    
I did search within all the files. No reference at all. It might be that it's being referenced through a variable, since it's a lang file (pt stands for Portuguese). I really don't have any clue of what is happening here. –  Souljacker Jun 15 '12 at 23:03

I resolve this problem when I create a blank pt.js file into wp-includes/js/tinymce/langs/pt.js and another one into wp-includes/js/tinymce/themes/advanced/langs/pt.js

share|improve this answer
1  
-1, Modifying WordPress Core is not right choice. –  amit Oct 17 '12 at 14:39
    
Is not a right choice when the core of Wordpress run as well! I have the same code in two machines and one have this problem and another not. The same code!! This is a Wordpress core bug! It's not a bug of my theme, because this problem happened in all my themes. –  Brunno Dos Santos Oct 17 '12 at 18:10
1  
If the same code is on two machines an one has the problem and the other doesn't, then it sounds like a server config issue. Even if it was a core issue, then a bug should be filed with WordPress. An update to WP will likely erase that change. The core files should never be modified. –  user1337 Oct 17 '12 at 20:13
1  
Editing the core file is never the answer. It just messes up future installations. –  Nicole Oct 17 '12 at 20:45

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.