thefuxia / wp-magic-widgets Goto Github PK

Seen in plugin version 2013.05.28

The generated markup looks like

<ul><li>
                <label for="widget-unfiltered_text-2-visibility">
                <input name="widget-unfiltered_text[2][visibility]" id="widget-unfiltered_text-2-visibility" value="all" type="radio"> All
                </label>
                </li><li>
                <label for="widget-unfiltered_text-2-visibility">
                <input name="widget-unfiltered_text[2][visibility]" id="widget-unfiltered_text-2-visibility" value="members" checked="checked" type="radio"> Members only
                </label>
                </li><li>
                <label for="widget-unfiltered_text-2-visibility">
                <input name="widget-unfiltered_text[2][visibility]" id="widget-unfiltered_text-2-visibility" value="anonymous" type="radio"> Anonymous visitors only
                </label>
</li></ul>

Apply a text input to alter the widgets title which will be displayed in the admin widget list. In the widgets front-end the title should be simply ignored, of cause.

There is currently no option to add the widget to the log-in screen. We could do two things:

1. add a checkbox to the front- or backend widget to include log-in
2. add extra widgets for the log-in page

Not sure what might be better.

Code is usually the content, so a monospaced font would fit better.

If you add a widget to the admin footer, its controls will be rendered instead of its content. The reason is that WordPress changes the parameters for dynamic_sidebar() per filter in wp-admin/includes/widgets.php::wp_list_widget_controls(). The filter has be removed before we call the footer widget.

This part in Unfiltered_Text_Widget::widget() returns too early:

if ( empty ( $instance[ 'visibility' ] ) ) {
    print $instance[ 'text' ];
    return;
}

The action tmw_after_show_widget is not called because of this.

The current readme.txt is formatted for wordpress.org. This is not compatible with GitHub’s markdown detection, and some parts should be separated out, the changelog for example and the tags.

We should add a readme.md.

Do we need a composer.json? What should be the content?

Hello my dear Tom, I am sorry for using the issue as I couldn't figure out how to suggest something without using this form so if its in the wrong place, my apologies.

As you know, recently on StackExchange, I used your plugin to bypass a problem with Amazon code not running core text widget and your unfiltered text widget helped.

Currently it provides "Front End Header/Footer" and "Back End Header/Footer" for a total of 4 other places to add widgets. I love and have found use for the FEH/FEF ones and not quite sure about the BEH/BEF ones. I was hoping if there can be a way to add an alternative to FEH so that it doesn't go above the header of the page (such as the twenty-thirteen theme's header) but rather go just below it (more specifically under the MAIN_WIDGET_AREA that includes the searchbox but before the posts start to appear) would this be possible? Say we call it Front End Sub Header or Below Header.

Also another super useful one would be adding one that automatically goes between the posts on the page. Meaning whatever you place in it will appear between all the posts on the page as they are iterated by the theme to display. It would streamline the need to manually hack the posts.php file which is how I am getting it done now.

Take a look at MajorMike.us to see what I mean as an example. Thank you.