WordPress.org

Ready to get started?Download WordPress

Forums

Some Problems with WP 2.1 (5 posts)

  1. xfai
    Member
    Posted 7 years ago #

    After upgrading my WP blog to version 2.1 I found some problems:

    1. In WP Admin -> Options -> Writing, the option: "Users should use the visual rich editor by default" is missing. I am not able to enable / disable the tinymce editor.

    2. The parse of blogpost content has some problem,

    2.1 <b r /> tages inserted between the table html tags. for example:

      <table border="0" width="98%"><b r />
      <tr><b r />
      <td valign="top"></td><b r />
      <td>: </td><b r />
      <td>td><b r />
      </tr><b r />
      <tr><b r />
      <td valign="top"></td><b r />
      <td>: </td><b r />
      <td>Yeah.</td><b r />
      </tr><b r />
      </table><b r />

    2.2 the text "!!!" is parsed to <img src="http://blog-home-domain/!">

  2. subiectiv
    Member
    Posted 7 years ago #

    actually, that exists. i don't know how you can't see it. still, i found some problems in the text editor - rich version. the insert link/image ajaxy pop-up sucks big time. you cannot close it, clicking the X, insert or Cancel being disabled or something. i believe it's smth wrong in the code.
    more, the autosave is not working properly.
    and there would be a few more...

  3. todmaffin
    Member
    Posted 7 years ago #

    Try looking at "Your Profile" tab in Users, not the "Users" list. The checkbox should be there.

  4. subiectiv
    Member
    Posted 7 years ago #

    yes, tod, but that doesn't explain why some features in the Rich Editor aren't working properly

  5. matriphe
    Member
    Posted 7 years ago #

    Hi, i found error when i was trying typing "XML-RPC" in post section in code mode (not in rich text editor, i don't like use rich text editor)..

    It results error 403 Forbidden.. Here the complete message:

    Forbidden
    You don't have permission to access /wp-admin/post.php on this server.

    Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags