The documentation LIES

  • Author
  • #1155164


    I desperately need a list of the tags created inside the TinyMCE editor. I know a few of them, such as <bold> and <underline> But the documentation I’ve seen so far LIES. THERE IS NO “VISUAL” OR “TEXT” TAB ON MY EDITING BOX. (“Annotum Base”) When I click “Save Draft” all NON-TinyMCE codes disappear. This INCLUDES destroying the invisible codes that are supposed to be retained when you use Shift-Enter to create a Line-Break. If I knew what ALL the codes were for the TinyMCE editor, I could happily format things myself. Obviously the Line-Break codes are NOT the
    codes of ordinary HTML.

    The blog I need help with is



    have you reviewed this:



    Those are NOT the TinyMCE codes, and therefore are useless. They are useless because, as previously stated, THERE IS NO “TEXT” TAB ON MY EDITING BOX. That means it is impossible to enter HTML codes. If I had a choice, I would throw away the duplication-of-effort TinyMCE editor and use HTML text exclusively. Doesn’t anyone around here know how easy it is to do HTML editing in an ordinary word processor, while the file is also open in a browser window? (Just edit file, save file, and refresh browser window to see the result.) But I am not given the choice to use HTML here; I am forced to use TinyMCE. Therefore I need the full list of TinyMCE codes. Very simple—and, apparently, very well hidden!



    Also, please note I’ve asked this question before:

    When is someone going to answer it????



    Here’s what it says on the TinyMCE website:

    TinyMCE is a platform independent web based Javascript HTML WYSIWYG editor

    . That is to say, TinyMCE is the Visual Editor, i.e. a WYSIWYG editor that depends on Javascript.

    As you stated earlier, you turned off Javascript and got some sort of an “alternative editor,” which we can only assume is the basic HTML/Text Editor. Since you are having trouble with the code you are using there, please answer:

    1. What browser and version are you using?
    2. What happens if you turn Javascript back on?

    Because you are using Annotum, which few of us volunteers are familiar with, I am going to tag this for Staff assistance. Please be patient while they get back to you. Meanwhile, perhaps you can find help on the Annotum Support page or the links within it.



    The alternative editor is not actually an HTML editor. It is a text editor that accepts TinyMCE tags that I would personally write, giving me complete control over the final text appearance –EXCEPT for badly-needed linebreaks!

    The Visual Editor (when JavaScript is turned on) automatically inserts TinyMCE tags –even more frustratingly, in the wrong places!!! And it doesn’t support SAVING linebreaks either –the documentation about “Shift-Enter” LIES.

    When I turn JavaScript on, that is when I can clearly see that there is NO TEXT TAB, which would in theory allow me to directly do HTML editing, and bypass TinyMCE altogether. This is true in both Chrome and Internet Explorer browsers.

    Note I’m only using Annotum because that is what was offered when the Google “Knol” system was migrated to WordPress. I could —and did– directly edit Knols with HTML; why am I not allowed to do it here? Especially when it would be a lot easier than learning all-new tag-names for the same old types of output (using <bold></bold> instead of <b></b>, for example).

    P.S. I just spent some time at the TinyMCE website, looking for a special linebreak code, and so far all I’ve found is some sort of “editing of a config file is required” idiocy. As a mere user, I’m not allowed to edit any such config file underlying the TinyMCE editor!



    At this writing I’m using Internet Explorer 8, and like I previously wrote, when I try to edit an article, there is no “Text” tab, which would allow HTML editing, in spite of what the overall WordPress documentation states. I did see a message saying the browser was out of date. However, this computer is a WinXP machine, and IE8 is the latest that Microsoft allows for it. I’m not interested in buying a whole new Operating System just to get a more up-to-date browser.

    Not to mention that other browsers can be up-to-date AND work fine on WinXP. Simultaneous with the writing of this post here, I have currently open Opera, Chrome, FireFox, and SeaMonkey. All of them are up-to-date, and all of them display the Edit Article page the same way –no “Text” tab. Therefore I can only conclude that this is some stupidity associated with the Annotum Base theme.


    Please give me a line-break code that I can enter into the text-editor that is available when JavaScript is turned off. Thank you!



    I’ve been attempting to find a workable alternative to line-breaks.
    One of the things I tried was <list>; the Visual Editor theoretically allows numbered lists and bulleted lists. I can see some text appear at the bottom of the editing window, showing that the edit-cursor is inside a <para> block, and inside a <list>, and even inside a <list-item> –but when I click the Save Draft button, all the “<list-item> tags get removed. The net result is a sequence of <list>(text)</list> <list>(text)</list> <list>(text)</list> blocks which are NOT displayed the same way in a browser that ordinary list-items are displayed, in a single list. TO ME, THAT LOOKS LIKE A BUG you folks should fix!

    The other thing I’ve tried is a table. I found that if you use some style=”border-width:0;” commands not just in the <table> tag, but also in the <td> tags, then you can make the borders disappear, and the result looks very much like you had used line-breaks instead of a table. I can live with that.

    But I’d rather be able to use good old-fashioned line-breaks.



    You have a free hosted blog linked to your username. Please see what Markel (Staff) said here:

    Can you please contact us in Support directly about this and other problems with the Annotum theme?

    Annotum is a partner theme and so we need to pass on this information to the team that is working on it after we test what you’ve reported. The fastest way to do this is to have you contact us directly.

    NOTE: This thread is tagged for Staff attention. Most support Staff are at a meet-up and are monitoring threads here. Please subscribe to it so you are notified when they respond which is no likely to be until after this weekend.



    “list” is not a valid HTML tag. Rather, “ul” (for unordered list) surrounds the list, and “li” (for list item) surrounds each list item. You could also use “ol” for an ordered list (a numbered list).

    At this point, it’s worth noting that Annotum is its own beast, it’s not really a WordPress theme so much so that it’s an entirely separate product-within-a-product. Nowhere else will you find an entirely separate Article system with its own interface (and no “Text” editor tab). It’s entirely unique, and for the most part, functions rather differently than much of the documentation here describes. It’s “special” that way. :)

    What you’re doing with tables is pretty much the best way to go about this in Annotum.

    Looking at what you’re doing with Annotum right now, it may be more than you need. What you’re doing with Articles could easily be done with Posts (essentially Annotum uses Articles like all other themes use Posts), and then everything you experience will match more in line with all of our documentation. If you’re interested, we do have over 200 other themes to choose from:



    The “<list>” stuff that I described were TinyMCE tags, not HTML tags. It remains true that the option to create a list in Annotum doesn’t work right.

    What I’ve done with Annotum almost qualifies as “nothing at all”; the articles were all imported from the Google Knol system. Only one of them have I tried to edit to any significant degree, and as a result had to break it into two parts, and even now I’m not completely satisfied with the way it turned out (mostly because of the lack of a code for linebreaks).

    According to something I saw at the TinyMCE web site, it should be possible to tweak a background function so that when the user presses the Enter/Return key just once, a linebreak code is generated, and when that key is pressed twice, a paragraph break is generated. Who decided that for Annotum no linebreaks would ever be needed –and why can’t that person be overruled?

    This particular thread/discussion began when I started trying to do a brand-new article. That first message above (and the title) was a result of the frustration that accumulated, when preview after preview failed to look anything like I could get my text to look when using pure HTML.

    As for switching away from Annotum, at the moment I simply want consistency. I’m not ready to move all the articles, mostly because I don’t know enough about what “posts” will look like –and who knows what will go wrong and can’t be undone?



    As for switching away from Annotum, at the moment I simply want consistency. I’m not ready to move all the articles, mostly because I don’t know enough about what “posts” will look like –and who knows what will go wrong and can’t be undone?

    You could create a test blog and play with it to your heart’s content, changing to as many different themes as you like, and simply import your current content to see what it will look like (more or less). Just mark it “private” so it won’t be seen by others. I just call mine “mmadfantestblog” — it’s very handy for trying out different ideas.

    I don’t know anything about Annotum, but I know that in ordinary blogs, you can’t use any java script, and I believe that TinyMCE relies on java. You might want to see if that is a problem.



    Definitely create a test blog under your account to play around, you’re welcome to create as many blogs under your account as you want by visiting while you’re still logged in.

    I’m a big fan of testing and trying things out, I just find it more rewarding and more fun. :)

    Try a test blog and import your blog’s content as mmadfan suggested, you might find it to be much simpler, and much more enjoyable. You can always just switch your theme away from Annotum on your main blog if you like it. :)

    As for TinyMCE, it’s a program and we use a lot of it, but not everything. We still filter some code out to keep everything stable and secure around here, so not everything discussed on the TinyMCE site will work on (or even WordPress in general).



    OK, thanks for the feedback. This Thread can probably be closed now.



    You’re welcome!

The topic ‘The documentation LIES’ is closed to new replies.