• Starting yet another thread on the Visual Editor not working in 3.5 because the mods insist on it.
    ____
    For the record – I’m am REALLY tiring of the many trolls calling themselves mods closing legitimate threads that are a few days old because they don’t like people resounding that they are having the “exact same” problem. I’m fed up of them spending more time harassing people than resolving issues. The level on stupidity is getting very frustrating. But I suppose this topic will be closed too, since I am not bowing at their feet.
    ____

    OK rant over – Same problem as most others here. Visual editor not working in 3.5. Normal checks. Turned off plugins, set to default theme, no fix. Cleared cache, tried different browser, so change. Removed and re-uploaded core files, no change.

    What’s odd is a literally have another 3.5 install with the same plugins, settings etc and the VE works.

    I keep thinking Java issue but clearing cache did not change a thing and neither did another browser. I also tried come if the changes suggested on various threads to wp-config with no luck.

    Nothing really new here. Just a few FYI’s on an ongoing issue. Please share if you find anything else or are having the same problem.

    Gav

Viewing 11 replies - 1 through 11 (of 11 total)
  • Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    As I stated to you before, despite the fact that you think it’s “the exact same problem”, it is not. The problem in the thread you were replying to was solved by the user clearing their browser cache. You state that you did this, and it didn’t work. Therefore, not the same problem at all.

    The problem you’re describing is one of javascript not loading or not working properly for some reason. So, what debugging steps have you taken?

    Did you read the master list? I know we hate to keep pointing it out, but if you actually had read it, then you’d be presenting the results of your debugging efforts in a thread instead of ranting about our issue-handling policies.

    For example, one thing it points to is this article:

    http://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors

    This article tells you how to debug a javascript problem (which you are clearly having), step by step, and how to present the results on this forum in a meaningful manner. And by “meaningful”, I mean by presenting information in a way that would actually let somebody assist you and perhaps guide you to finding a solution.

    Telling us that you have a problem, that you disabled plugins and themes, and that that didn’t solve it… really isn’t telling us a lot. You’re basically saying that you’re taking the shotgun approach of trying everything you can find, but not doing anything to actually diagnose the problem and find the root cause. We don’t have access to your site, and we cannot magically wave our hands and fix things. We need you to figure out the cause, so that we can tell you the solution.

    Thread Starter ventrilqstman

    (@ventrilqstman)

    Samuel Wood you pretty much make my point. I have NOT yet done everything possible. I am still trying to pin it down and as such had NO need for a fresh thread that said the same thing as everyone else. That’s WHY I was following up on some other threads in that I was experiencing a near identical issue and sharing what I knew.

    This issue is common right now and no one seems to have the solid answer. Perhaps instead of trying be be top mall cop you could work on actually resolving the problem.

    I am aware of the links you mentioned. If I find something “new” I will report. In the meantime “I appreciate” other people sharing what they are dealing with/have learned about the issue. That’s the whole point of posting.

    It’s odd that in your furor to force order, you mods are actually causing more chaos then good. Irony?

    Thread Starter ventrilqstman

    (@ventrilqstman)

    PS: I also did try adding script debug in wp-config. Is did not effect the issue.

    define('SCRIPT_DEBUG', true);

    Thread Starter ventrilqstman

    (@ventrilqstman)

    PSS:

    I did run debugger and there are loads of items. Probably hundreds, mostly warnings emanating from the post window or editor.css. These don’t seem to fall in the “errors” tad.

    Here’s just a few…

    Timestamp: 1/2/13 11:15:08 PM
    Error: TypeError: DOM.events is undefined
    Source File: …/wp-admin/post.php?post=7138&action=edit
    Line: 1899

    Timestamp: 1/2/13 11:15:07 PM
    Warning: Error in parsing value for ‘background-repeat’. Declaration dropped.
    Source File: …/wp-admin/post.php?post=7138&action=edit
    Line: 1

    Timestamp: 1/2/13 11:15:07 PM
    Warning: Error in parsing value for ‘background-image’. Declaration dropped.
    Source File: …/wp-includes/css/editor.css?ver=3.5
    Line: 1

    Timestamp: 1/2/13 11:15:07 PM
    Warning: Expected color but found ‘bottom’. Error in parsing value for ‘background-image’. Declaration dropped.
    Source File: …/wp-includes/css/editor.css?ver=3.5
    Line: 1

    I’ll probably get banned for posting this, but since no one has responded to my thread that I was asked to post I went digging further. πŸ™‚ I thought you may want to read it too and then you can decide if you want to try it.

    I tried what is in the last comment here (the plugin) and it worked. I am not satisfied on this being a long term solution, but for now I will go get get some sleep.

    http://wordpress.org/support/topic/visual-editor-not-working-in-wordpress-35?replies=6

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    That’s WHY I was following up on some other threads in that I was experiencing a near identical issue and sharing what I knew.

    Except that you were not doing that. You were posting “me too” posts. Posts that state you have the same problem, state that a bunch of solutions didn’t work for you, and then not furthering the solution in any way.

    – Saying that you have the same problem when you don’t know that you actually do have the same problem is not helpful.
    – Stating a bunch of shotgun approach stuff that does not work for you is also not helpful.

    If you post in somebody else’s thread, then you should be trying to actively help them, not to commiserate or say a bunch of stuff that relates to your problem and potentially not to theirs. Most people don’t have the same problem, because problems are caused by other factors than just the immediately visible symptoms.

    It’s odd that in your furor to force order, you mods are actually causing more chaos then good. Irony?

    You’re free to have your own opinions, but here are the facts:
    – your posts are not helping people
    – they are actively hurting other people’s attempts to help people
    – if you continue to interfere with other people’s efforts at support, then you will be removed from this forum.

    Those are the rules. If you want help, then I’m glad to help you. But having it in your own thread makes things easier all around, without distractions from posting in many places.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    Now, that out of the way:

    What’s the URL of your site? If I knew the URL, I could look to see if you’re having the bracket problem. The bracket problem stems from bad .htaccess “security” rules, and can prevent your javascript in the admin section from loading properly.

    Thread Starter ventrilqstman

    (@ventrilqstman)

    RE my site: The domain is seimeffects.com, but unless you mod your local hosts file to the server “204.197.244.21” for seimeffects.com, it won’t work as this is a new move for the site that I’m setting up based on the one you will currently get redirected to by default, for seimeffects.com.Interestingly the site I’m migrating from with all the same settings and WP 3.5 works fine. So I will try to look at my .htaccess again files and see what I can find.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    Your site does not have the bracket problem. I changed my hosts file and checked.

    Basically, try to diagnose what Javascript files aren’t loading, or where the source of the errors is coming from.

    To do this, first, turn off the Use Google Libraries plugin. It will interfere.

    Next, load up Chrome, and start the Inspector. Put it on the Network tab, then visit a page in the admin which is having problems. You want to find any files that aren’t loading properly and are getting 404 errors or anything other than 200’s basically. Somehow, some part of your javascript either isn’t loading or isn’t compatible. Without seeing the wp-admin in my browser myself, I can’t see exactly what script is causing the issue.

    If I had login information, then I could see it and tell you what the problem is, if you want to email it to me.

    Thread Starter ventrilqstman

    (@ventrilqstman)

    Naa, I’ll find help from others. You have deleted the posts of others trying to help on this thread. You have edited my posts where I was critical of your behavior.

    Your actions are completely inappropriate. You can’t even handle the moderation of a polite thread where people are trying to help each other. Do you really expect people to trust you with login information?

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    Do you really expect people to trust you with login information?

    Many people do, all the time. Having an email address on wordpress.org helps, I admit.

    And since you want to continue ranting instead of participating in the forum properly, as I’ve already asked you to do on multiple occassions, then you’re free to go do your ranting somewhere else.

    Goodbye.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Another Failure of the Visual Editor in 3.5’ is closed to new replies.