• Resolved ian_spare

    (@ian_spare)


    First, I’ve got to say the responses that have been posted when people have tried to report this have been poor. The responses have just been a simple repetition of the same “solutions” which have been nothing of the sort.

    Second, there’s clearly a whole class of problems here and I’m focussed on the one I have for obvious reasons.

    So, how to verify you’ve the same problem. Use some sort of debugger tool like firebug etc, Peter Hengl gives a nice description here : https://www.ads-software.com/support/topic/164990

    The first thing to establish is that it’s not a cache problem, at least not in the way that keeps getting posted. For a start, browser and network caches don’t work like that. What I did find was that different files were returned using different clients, any browser (opera, safari, firefox) over three OS’es (Mac OSX, XP, Linux) returned a “cached” file that didn’t reflect debugging changes I made on the server, it was instantly obvious from a network trace that this wasn’t held in any browser cache. However, curl and wget instantly reflected the debug code, someone should have tried that before blaming caching as it’s obvious when you look at the code in tiny_mce_config.php why that’s going to be different. In fact, looking at the code I’d guess this would also work correctly (this far) in IE5.

    To fix this, remove the files from wp-content/uploads/js_cache and you’ll start getting an up to date copy of the mce code. NOTE, not everyone will have this issue as such, the cache code is broken in a way I’ve not fully analysed so this is a nuisance rather than the root cause.

    Next, to the source of the real problem. The debugger instantly spots this, it’s related to some I18n code and follows back to the get_locale function. The function is weak and used weakly in places which is why there’s a problem. This problem will most likely effect people not using 100% English language environments like Peter who’s German or me with Swiss/French locale, in fact, Peter’s nationality already made me guess the I18n code was broken.

    The simple fix is to go to your wp-config file and set the WPLANG variable to something suitable. For me, “en” is fine.

Viewing 8 replies - 31 through 38 (of 38 total)
  • timclark

    (@timclark)

    I would not worry if you could not find your cache as I have deleted mine and all works fine still no wysiwyg tools though.

    With your wp-config file I put en.js in there and it works so it will read like this, define (‘WPLANG’, ‘en.js’); but still no tools I think that sugestion might work for some issues but not for me.

    I am starting to have the assumption that there is either no one really has a clue about this issue or they are all at a coding convention some where in Iceland for the winter.

    HELP PLEASE……

    noeticvirtuoso

    (@noeticvirtuoso)

    I had the same problem, thankfully i got the answer from this thread.

    my /wp-includes/js/tinymce/tiny_mce_config.php had a file attribution 664 i changed it to 755, worked for me.

    thanx

    _cornelius_

    (@_cornelius_)

    It’s possible to get the visual editor working with GoDaddy’s free hosting. The fix involves a slight alteration to WordPress’s script-loader.php.

    I’ve outlined the steps to do it here:

    https://www.teknolio.com/blog/how-to/fix-wordpress-editor-on-a-free-godaddy-hosted-site/

    nicadmin75

    (@nicadmin75)

    i did the 755 instead of 644
    i did the ‘en’ instead of WLANG = ‘ ‘
    i did the clear cache stuff
    nothing!

    it shows visual, html is now clickable.. but when i click ‘html’ the textbox where you write your post disappears… i have 0 plugins installed (installed 2.6.5 from stratch, made a fresh new database, deleted the old wp folder, fresh install) and i still get this error!

    tried everything possible and still can’t make it work! why aren’t the wp creators looking into this? seems like a serious problem!

    please, somebody, help me! i’m very frustrated now knowing what to do and not being able to find the answer.

    Finally got my visual editor to appear and thus unsticking the html mode !!

    After trying everything suggested in this thread and numerous others, I was about to give up when I was looking for the /wp-includes/js/tinymce/tiny_mce_config.php file and like bergie812 mentioned as I think someone else also mention,,I noticed I did not have a tinymce folder !!!! When I opened wp_includes/js there were only a few files there and NO folders and this is after deleting the wp_admin AND wp_includes folders and uploading fresh twice !

    I uploaded the missing folders, (logged out of WP, cleared cache just in case) and then presto chango the visual editor appeared !!! However despite installing the tinymce advanced plug in, it does not seem to work as I see the regular visual editor instead, but I am so happy to see it that I will not complain !!

    I will most likely uninstall that. If any issues arise I will post them.

    Thanks to all for working on this issue.

    RAT

    Hi, my solution lied within the wp-config file, in case you want to know more, check https://www.csnotes.net/?p=15

    sorry, the correct link is https://www.csnotes.net/?p=31

    does not open the page (
    https://www.csnotes.net/?p=31
    Server Not Found,

Viewing 8 replies - 31 through 38 (of 38 total)
  • The topic ‘2.5 and TinyMCE not working in visual mode’ is closed to new replies.