WordPress.org

Ready to get started?Download WordPress

Forums

Monster Widget
[resolved] `searchform` uses id in single instances *and* class in second instance (3 posts)

  1. Edward Caissie
    Theme Review Admin
    Posted 1 year ago #

    Just came across this issue today while testing 3.6-alpha (uncertain if it is directly related).

    Using two instances of the plugin appears to cause the searchform to use different elements?!

    See this site http://wpthemes.edwardcaissie.com/ as an example (I'll leave the current theme active for a while as it makes the visual more obvious). This occurs with every theme I have checked so far.

    The first instance of the plugin uses:

    <li id="monster-widget-placeholder-11" class="widget widget_search">
    <h2 class="widgettitle">Search</h2>
    <form id="searchform" class="searchform" action="http://wpthemes.edwardcaissie.com/" method="get" role="search">
    <div>
    <label class="screen-reader-text" for="s">Search for:</label>
    <input id="s" type="text" name="s" value="">
    <input id="searchsubmit" type="submit" value="Search">
    </div>
    </form>
    </li>

    ... while the second instance of the plugins uses this:

    <li id="monster-widget-placeholder-26" class="widget widget_search">
    <h2 class="widgettitle">Search</h2>
    <form class="searchform" action="http://wpthemes.edwardcaissie.com/" method="get" role="search">
    <div>
    <label class="screen-reader-text" for="s-1">Search for:</label>
    <input id="s-1" type="text" name="s" value="">
    <input type="submit" value="Search">
    </div>
    </form>
    </li>

    I haven't looked into the plugin code, yet, just tested with a few different themes to see if it occurs elsewhere.

    http://wordpress.org/extend/plugins/monster-widget/

  2. Michael Fields
    Themer
    Plugin Author

    Posted 1 year ago #

    I think this has something to do with the following recent change to WordPress core:
    http://core.trac.wordpress.org/changeset/23801

    There's some discussion happening to correct this here:
    http://core.trac.wordpress.org/ticket/16539

    I do not think that this is an issue with the monster widget.

  3. Edward Caissie
    Theme Review Admin
    Posted 1 year ago #

    I agree ... it does appear the current core code is causing this id issue. It's simple enough to fix the style, but obviously the underlying issue is still actively being discussed.

    Thanks for the trac links.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags