Swapnil V. Patil

Insert separate widgets or a entire widget area (sidebar) into a page using a shortcode.
Customize the widget setting in “widgets for shortcodely” widget area.No extra efforts. Exactly as you would do it for any other widget.
do_widget shortcode,will do its magic and display the widget or the even a chosen sidebar from the do_widget_area shortcode.
The plugins default action is that it will magically find the settings for your themes first sidebar and use them to control the widget’s output. In most cases this would mean that the widget will be styled as per the rest of your theme. In case, yout need to change the styling, there are parameters to override it.
Whenever you need to change your theme, the plugin automagically saves and restores the widgets and its settings. It will then select the sidebar setting from the currect theme you are using.
Instructions:
<ol>
<li>Make sure you test the widget in the regualr widget area, or any exisitng sidebar.</li>
<li>Then Activate shortcodely. (Ignore id already done.)</li>
<li>Go to Appearance > Widgets and find the ” widgets for shortcodely” sidebar or widget area</li>
<li>Add your desired widgets to the Shortcodely side bar. Save.</li>
<li>Go the Shortcodely settings. Click on one of the create page links to help you setup the shortcode.</li>
<li>
OR go to an existing page and enter a shortcode:
[do_widget widgetname] eg: [do_widget calendar] 
[do_widget “widget name”]. eg: [do_widget “tag cloud”] 
[do_widget id=widgetid]
[do_widget_area] (will use the “widgets in shortcodes” widget area / sidebar 
[do_widget_area sidebarname] for another sidebar or widget area – eg: to maximise likelihood of getting your theme’s widget css to apply.
</li>
<li>
If the plugin cannot work out what you want and you are logged in as an administrator, it will show a debug prompt to you, the logged in admin only. 
Click on the link ‘Try debug’. It will produce a bunch of info. Look for the id of your widget in the shortcodes sidebar (you may have to scroll through a lot of debug info). Try using the widget id. Sometimes the widget name that wordpress calls it internally is not the same as what you see on the screen and you will need the ‘debug’ to find the id.
</li>
</ol>
[do_widget …] Parameters:
<ul>
<li>nameofwidget or name=”nameofwidget” This is NOT the title of the widget. THis is the name that you see in the widgets menu page even when unassigned to a sidebar. For existing users , you can also use just the name of the widget without name=. It must bethe first parameter then.</li>
<li>id=wordpress assigned id of widget</li>
<li>title=false to hide the widgets title OR to override your themes first sidebar html settings for widget titles, use title=htmltag where htmltag is one of h1,h2,h3,h4,h5,header,strong,em. If not entered plugin will use the same title html that your themes first sidebar uses – yes even if you change themes, it will switch to the new themes html.</li>
<li>wrap=htmltag where htmltag is one of div,p,main,aside,section. This will override your themes first sidebar html settings for widget wrapping html.</li>
<li>widget_classes=none This will remove the class “widget” from the wrapping html and the class “widget_title” from the title html. This may be enough to remove any unwanted css styling from your theme.</li>
<li>class=yourclassname By default the plugin will add a class of amr-widget tto the wrapping html. You can use this to add any special css. Add css either by editing your themes stylesheet if it is a custom theme, or using something like the wordpress custom css plugin.</li>
<li>sidebar=”sidebarname” will default to widgets_for_shortcode sidebar. Only use if you want to re-use a widget already beingused in another sidebar. THis is theme dependent and WILL break if you change themes.</li>
</ul>
[do_widget_area …] Parameters:
<ul>
<li>widget_area=yourwidgetarea defaults to ‘widgets_for_shortcodes’ if nothing entered</li>
<li>widget_area_class=none /* option to remove theme styling by removing the widget_area class from the sidebar html */</li>
<li>widget_classes=none /* option to remove the widget class from the widget wrappinghtml</li>
<li>class=yourclassname default is amr_widget_area’</li>
</ul>
See the settings page for links to help your create the shortcodes in a page.
To ‘remove debug mode’ 
remove ?do_widget_debug=1 from the url you are looking at (NOTE it only debugs if you are logged in and an administrator, so this is really NOT a problem.)
The plugin has been tested with most standard widgets (rss feeds, tag cloud, pages, meta, search, and of course my own plugins widgets – upcoming events list, calendar and user lists.
If you use a widget more than once for different reasons, you may need to use the widget id to isolate which widget instance and it’s settings to use. ie: [do_widget id=categories-6] . If you just use the name, it will display all widgets in the shortcode sidebar with that name (all instances).
If you liked this plugin, you might also like my other plugins:
<a href="https://wordpress.org/plugins/login-and-logout-redirect/" rel="ugc">Login and Logout redirect</a> – Redirects users to specified url on logging in, logging out OR both.
<a href="https://wordpress.org/plugins/gravity-pre-submission-confirmation/" rel="ugc">Gravity Pre-submission Confirmation</a> – adds a pre-submission confirmation page to your Graviy forms where users can preview their entered data before they submit it.

Shortcodely

Enable the usage of shortcodes almost any where on your website

LorenW

In WordPress each page must be intentionally assigned a template (or have a template file intentionally named for it) or WordPress applies the default page.php template. Child pages do not inherit parent page templates. On a large website with many child pages within a hierarchy of pages this does not make for an easy or error free way to use page templates to create a sectioned CMS. A user can assign a template to a top level page (or a “beginning of section” page) but its descendants (child pages) will not follow with their ancestor’s template. Each page’s template must be individually assigned. For small sites with few pages and few users this is not a significant matter. On a site with hundreds or thousands of pages and multiple editors and multiple “sections” this makes WordPress less than ideal as a CMS platform
This plugin solves that problem. It investigates each page and assigns hierarchical templates to pages and their children giving precedence to page-[id].php templates. If no page-[id].php templates are found all the way up the ancestory tree then it will check for page-[slug].php templates back up the ancestory tree. If those are not found then it will look for a meta assigned custom.php template – first for the currently selected page and then if the page does not have a custom.php template assigned the function will look back up the ancestory tree to see if an ancestor page has been assigned a custom.php template. If all of these fail it will fall back to WP’s default page.php template.
There is more description at http://www.warkensoft.net/wordpress-plugins/wordpress-hierarchical-page-template-redirect-plugin/

Hierarchical Page Template Redirect

Assigns hierarchical templates to pages and their children giving precedence to the page-[id].php templates.

Shortcodely vs Hierarchical Page Template Redirect