Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Reply to: “Rev. Voodoo”

    Personally, I use Chrome now, and I’m completely happy with the editor. If it gets improved, cool. I love improvement!

    Well! Goody for you. I have all my Firefox happy and nice and I should not have to change because THEY want to ignore US!
    THEY are the elite core programmers. I throw the term about because THEY do not show us THEIR faces or names often. You are now a THEY, because (due to the fact that you put your head in the sand over the editor) you (Rev. Voodoo) are just as anonymous as THEM. You even behave like ‘them’.

    Bug reports have been made. YOU are IGNORANT of this. This bug is being plastered all over the WWW, YOU CONVENIENTLY forgot to read that I am not a programmer and do not even play act as one, do you?

    There is us. If you use WP, you are part of us. It’s all volunteers man…. can you fix the editor and make it fabulous? Then do it!! Submit a patch. Get it running all superfly!

    There is no ‘they’. Just us. Whomever feels like stopping by and helping out when they can.

    Submit a Patch? W.T.H. is a patch? I am a mere mortal, only a blacksmith beating on this problem with words… Patches smatches.

    I am one of the loyalist fans that is getting fed up with “they’s and you’s”. You are perpetuating one HUGE dog pile of justifications for a problem that is hurting the awesome WordPress rep.. A simple thing such as this editor behavior in a major browser (Mozilla) used by millions upon millions (except special Mr. You) is a big deal in the competitive world of blogging engines.

    “Bloviating” snobbish opinion spoken in a sneering voice:

    Personally, I use Chrome now, and I’m completely happy with the editor. If it gets improved, cool. I love improvement!

    THE PROBLEM IS NOT WITH MOZILLA -IT IS WITH WORDPRESS!!
    TinyMCE works great in Firefox separately from WORDPRESS.
    ARE YOU -OR DO YOU WANT TO FIX THIS ‘thing’?
    AT LEAST I DID

      SOMETHING

    !!!

    YOU DID NOTHING EXCEPT CONFUSE THE ISSUE AND ATTACK ME!
    AT LEAST

      I narrowed down the problem somewhat

    AND YOU-THEY? -CONTRIBUTED NOTHING EXCEPT EMPTY WORDS -NOTHING! ARE YOU BLOWING REALLY HARD ON YOUR KEYBOARD TO PRESS THE KEYS?
    Do you -Rev. Voodoo- like slow editors WITH NO BACKSPACE KEY??? Then stop complaining about the likes of me and start doing something instead of pawning the problem off, copping out, whining about the doers, and giving in to the shiny CHROME.

    (..not biased here, I use Chrome to do a few chores, and NOW MY EDITING DANG-IT, but still, most of my favorite plugins are still anchored firmly in Mozilla Labs Software. It is a habitual work saving workflow habit developed over time)

    PS1

    “They who must not be named” are not responding to a real turnoff in the WP system.”

    OR did I say this already.
    PS2 I really meant to say two words initially. KISS OFF.
    PS3 MOST of my first post was done “tongue in cheek”, or are you just looking for a fight? I mean come on, everybody knows the generalizing colloquialism “they“.
    PS4

    Foot Stomping RAGE!! I WANT MY TinyMCE EDITOR FIXED NOW NOW NOW -NOW.

    Thats funny Herman!!

    Ran a Test a Ran-t
    1. Went to TinyMCE page and used the demo editor –no probs.
    GOOD on my oldish 4-core win7 64b
    2. YEA Ditto in chrome.
    3. Used the default WP theme. OOPS -no luck
    4. Loaded posts in Chrome -HEY no probs.
    5. Loaded post in three versions of FFox on three different systems using latest WP. I am starting to get annoyed and headstrong.
    -MAJOR PROBLEMA- buffering all puckered -Backspace especially.
    Now I am pissed and determined to bury this annoying problem.
    6. Loaded TinyMCE standalone from TinyMCE website in three versions of FFox on three different systems using latest WP.
    -NO PROBLEMA- Worked Perfectly. Now I am PERPLEXED.

    7. I propose a possible solution: On a lark I copied the TinyMCE code from the TinyMCE website directly and overwrote the TinyMCE code in the wpincludes folder.
    —SPECIFICALLY— I used the improved JQuery plugin model from TinyMCE.
    RESULTS:
    A BIG improvement! My modified editor with all of the whistles and bells ring true. The typematic does not overrun anymore! YEA -a short geeky victory jig damaged my cats psyche.

    BOO PARTIAL SUCCESS!

    SAD FACE Single backspace is still just as bad as ever…

    NOW -I used to blame TinyMCE.
    Then I blamed firefox along with many other misinformed WP posters.
    Then I blamed my theme and the one bizzzillion plugins -until I tried a clean install. and OOPS sameolsameo
    Now I blame word-depress!!!

    To Quote from the above posts,

    I’m afraid the same is happening with the post editor. I didn’t notice me gradually straying away from this core Worpress component, but, yes, I’m straying away from this.

    There is a code/browser conflict that is fixable. You can count on me finding it eventually -god knows how, but I will not share it with the WP big wigs first. I figure it this way. If little-ole me -a non-programmer has to go around fixing this kind of horse $%*% then why am I using WP? hmm? Forum posts go unanswered everywhere. Many are ticked off. The WP muckety-mucks are not responding to a real turnoff in the WP system. Is WP striking out at the plate? If they value the WP fans out there, then they better bust some code open. Personally I think that it is a simple script load order problem.
    If that is the case then I am really mad at all of you programmer types putin us writer types through A BUNCH OF AGGRAVATING *ell for nothing. I HATE SLUGGISH EDITORS AND WANT THIS FIXED.
    Foot Stomping RAGE!! I WANT MY TinyMCE EDITOR FIXED NOW NOW NOW -NOW.

Viewing 2 replies - 1 through 2 (of 2 total)