Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thanks again scribu! Much appreciated.

    Hello again. It seems that the bug with added slashes that I described here has resurfaced.
    Unfortunately, editing a text-widget with front end editor is just too much of a hassle when situations like these occur. :/

    Make it plus one for nicedit on text widgets.
    I was surprised to find it gone after upgrading to fee 1.9 today. πŸ™

    ashaman

    (@ashaman)

    Hi, I followed the instructions mentioned above and the links work perfectly on the frontpage. Although, when you visit a category or click on a tag, the same double links appear.
    Is there something I can do that affects that behaviour as well?
    Thanks.

    I’ve run into yet another issue:
    Editing a text-widget opens up a veeery small textbox to show the text, around 2 lines. It’s quite hard to edit using that, plus this was introduced with the recent updates; it wasn’t like this before.
    Actually, trying that again for another time, a quite large textbox appeared, but with no slider to scroll to the bottom. :/

    Indeed! Cheers for the quick update! πŸ™‚

    Hi again!
    I’ve run into a new problem:
    It seems that the front-end editor is messing with the html code in my text widget.

    For example, editing the widget and pressing apply (with or without changes being made), produces this for links:

    <a href=\"url\">

    The \ inserted appear only after editing with f-e.e., changing the text through the dashboard works fine.

    Scribu to the rescue? πŸ˜›

    Thank you ver much scribu, it works now. πŸ™‚

    On a sidenote, does having two classes, or rather a different classname, interact in any other way with the blog/theme?
    Just curious, is all…

    if ( function_exists('register_sidebar') )
        register_sidebar(array(
    	'name'=>'sidebar_full',
            'before_widget' => '<li id="%1$s" class="sidebaritem %2$s"><div class="sidebarbox">',
            'after_widget' => '</div></li>',
            'before_title' => '<h2 class="widgettitle">',
            'after_title' => '</h2>',
        ));
        register_sidebar(array(
    	'name'=>'sidebar_left',
            'before_widget' => '<li id="%1$s" class="sidebaritem %2$s"><div class="sidebarbox">',
            'after_widget' => '</div></li>',
            'before_title' => '<h2 class="widgettitle">',
            'after_title' => '</h2>',
        ));
        register_sidebar(array(
    	'name'=>'sidebar_right',
            'before_widget' => '<li id="%1$s" class="sidebaritem %2$s"><div class="sidebarbox">',
            'after_widget' => '</div></li>',
            'before_title' => '<h2 class="widgettitle">',
            'after_title' => '</h2>',
        ));
        register_sidebar(array(
    	'name'=>'footer_left',
            'before_widget' => '<div id="%1$s" class="widget %2$s">',
            'after_widget' => '</div>',
            'before_title' => '<h3>',
            'after_title' => '</h3>',
        ));
        register_sidebar(array(
    	'name'=>'footer_middle',
            'before_widget' => '<div id="%1$s" class="widget %2$s">',
            'after_widget' => '</div>',
            'before_title' => '<h3>',
            'after_title' => '</h3>',
        ));
        register_sidebar(array(
    	'name'=>'footer_right',
            'before_widget' => '<div id="%1$s" class="widget %2$s">',
            'after_widget' => '</div>',
            'before_title' => '<h3>',
            'after_title' => '</h3>',
        ));

    Only the sidebar_full is in use though.

    What else would you like to know apart from WP version [2.9]?

    I’d rather not give out the link publicly, call me paranoid…

    I verified that with the previously installed version it works as fine as ever; pulled it out of a recent backup.
    Installing the 1.6 has definately caused the error as far as I can figure out.

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