Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Bumping this post. I need to be able to do this too. I installed the plugin with one API key and realized that I want to use a different API key. I am able to change it for Akismet very easily. But there is not interface to managing the API key for Stats.

    Thread Starter everah

    (@everah)

    That is some oddness. The login just worked for me in Opera. It failed consistently yesterday.

    Weird. I guess this one is maybe a gremlin as opposed to a bug.

    Thread Starter everah

    (@everah)

    Something to add:
    I forgot that this problem did happen to me on my Linux machine as well. I ended up having to FTP the images to my server elsewhere and link to them from the post I had made. Opera 9.27 on Ubuntu.

    FYI Both of these Opera installations are using the most recent flash viewer. Not sure that it is relevant, but I did see mention of that in other areas. Also, this is only happening in Opera. All other browsers are handling the media gallery without issue.

    Thread Starter everah

    (@everah)

    I think I found the problem…

    The balanceTags filtering function in wp-includes/formatting.php is called as a filter from wp_insert_post (wp-includes/post.php). This filtering functions attempts to balnace and straighten the markup that is posted in the content. The regular expression used in the balanceTags function is looking for all words within < and > symbols. As it does this, anything between the opening and closing tag is treated as a single HTML tag and filtered like a non-closing HTML tag (like a BR or HR)

    I changed the regular expression used in the balanceTags function from:
    "/<(\/?\w*)\s*([^>]*)>/"

    to:
    "/<(\/?[^?]\w*)\s*([^>]*)>/"

    And it seems to do what I want it to. Tests are still available at the link I posted previously.

    Something to note… the text strings “<?php” and “?>” seem to not be run through an entity-izer of any sort, so if you use them in plain text, the browser interprets the opening tag as an HTML tag and will not show anything that is on that line.

    Thread Starter everah

    (@everah)

    The entry in the database contains the space. Here is the entry taken straight from the DB:

    < ?php
    // this is code
    ?>

    <pre lang=”php”>
    < ?php
    // this is in the hightlighter
    ?>

    A sample of the output san be seen here: http://www.robert-gonzalez.com/2007/08/14/test-post/

    I removed the spaces in the DB to test what would happen if I removed them at the data level, and in the highlighter (wp-syntax) everything works fine, but in straight context the opening tag gets buggered because the greater than sign (tag opener) is interpreted by the browser as an HTML tag (naturally).

    After removing the spaces, I opened the post in the editor (I don’t use the tinyMCE editor) and the spaces were not there on fresh load. But as soon as I posted the post (using save or publish) the spaces reappeared, so I suspect that the spaces are being added somewhere in the save routine.

    Does anyone know if there is any new information on this users issue? I am experiencing the same thing and it is driving me nuts. I cannot post a new thread because the forums are closing and killing my threads as soon as they are posted. Any help with this problem would certainly be appreciated.

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