= Version 2.1 =
* Released May 2013
* Added plugin version data dynamically to enqueue calls
* Added (enqueued) ‘BNS Login Form Style’ to style the form
* Added `bns_login_form` (`wp_login_form` wrapper) for use as the shortcode output
* Updated for version compatibility and minor code formatting
BNS Login Changelog

© 2013, Edward Caissie. All rights reserved.

= Version 1.0 Changelog =
* Released <:3()~~~ 2013
* Added code block termination comments
* Added ‘hat.png’ image for “Hat Tip” type
* Added missing `bnsia` class to theme elements other than default
* Added style definitions for “Hat Tip” type
* Minor documentation improvements
* Moved stylesheet into its own directory
* Moved images into their own directory
* Moved JavaScript into its own directory
* Refactored $bnsia_element to simply $element
* Removed direct jQuery enqueue (called as a dependency of ‘bnsia-script.js’)
* Removed unused style definitions
* Use an array of elements rather than a convoluted if statement to sort out if an accepted container is being used
BNS Inline Asides changelog

Enjoy!

© 2013, Edward Caissie. All rights reserved.

= 0.6.1 =
* Released April 2013
* Fixed conditional logic used to display plugin
* Refactored where $ea_display Boolean value is set
BNS Early Adopter Changelog

© 2013, Edward Caissie. All rights reserved.

= 0.5.1 =
* Released April 2013
* Fixed wrong function being called by action hook

= 0.5 =
* Released April 2013
* Added additional related tags to header block
* Added Christian Calendars for the years 2013 and 2014
* Added Jewish Calendars for the years 2013 and 2014
* Code formatting and code block termination comments
BNS Body Classes Changelog

© 2013, Edward Caissie. All rights reserved.

Currently the comment-template.php file uses an asterisk (*) as the default glyph for required fields used in the comment_form() function. This glyph is not easily manipulated without having to essentially over-write the entire comment_form() function.

I suggest the glyph be filtered. Therefore if one wants to change it, for example, to a hash (#) symbol then they can simply filter the output; or, if for any other reason one might want to enhance the glyph visibility or utility the filter would then allow for this while minimizing the impact on the default comment form.

A response was made to the ticket providing an example snippet to accomplish the basics of the ticket description but not the entire idea as I envisioned it. Here is Sergey’s snippet:

function change_required_fields_glyph_23870( $defaults ) {
	$defaults['fields']['author']     = str_replace( '*', '#', $defaults['fields']['author'] );
	$defaults['fields']['email']      = str_replace( '*', '#', $defaults['fields']['email'] );
	$defaults['comment_notes_before'] = str_replace( '*', '#', $defaults['comment_notes_before'] );
	return $defaults;
}
add_filter( 'comment_form_defaults', 'change_required_fields_glyph_23870' );

I replied (twice) with the second response providing some modifications to Sergey’s snippet that does complete the idea if the patch I submitted does not get included. Here is what I would suggest to make the Comment Required Field symbol, or glyph, filterable:

function required_fields_glyph_23870() {
	$glyph = apply_filters( 'comment_required_glyph_23870', '*' );
	return $glyph;
}
function change_required_fields_glyph_23870( $defaults ) {
	$defaults['fields']['author']     = str_replace( '*', required_fields_glyph_23870(), $defaults['fields']['author'] );
	$defaults['fields']['email']      = str_replace( '*', required_fields_glyph_23870(), $defaults['fields']['email'] );
	$defaults['comment_notes_before'] = str_replace( '*', required_fields_glyph_23870(), $defaults['comment_notes_before'] );
	return $defaults;
}
add_filter( 'comment_form_defaults', 'change_required_fields_glyph_23870' );

You will find a version of this code being used by Opus Primus version 1.2 and later …

… and here’s a plugin idea for this code: link the comment required field glyph, via the filter, to a privacy policy.

The latest improvement (at least in the current development version) is the ability to add a definition to the wp-config.php file allowing developers to work with Jetpack in their local test/development environments.

To develop with Jetpack in a local environment is now easy to do.

1. Add define('JETPACK_DEV_DEBUG', true); to wp-config.php (I like to add it right underneath the define('WP_DEBUG', true); definition for consistency.
2. Download the Jetpack Development Version from WordPress Extend Plugins and install via the Plugins > Add New > Upload method.
3. Activate the module(s) you want to work with.

Open the httpd.conf file with a text editor and search for rewrite. You will be looking for the following line:

#LoadModule rewrite_module modules/mod_rewrite.so

Just remove the leading # and save the file. (The # makes the line read as a comment.) You may need to restart your WAMP services, I suggest simply exiting the program and re-starting it no matter the case if configuration files are modified.

The development version also has a number of warnings fixed in it. The required WP version has been updated to 3.1. The development version above has had no feature changes.

© Ron for WordPress "Must-Use" Tutorials, 2013. | Permalink | 2 comments | Add to del.icio.us
Post tags: domain mapping, multisite, network plugins

Check out WPeBooks.com for multisite plugins & ebooks.

Feed enhanced by Better Feed from Ozh

© 2013, Edward Caissie. All rights reserved.

Here is the code:

jQuery( document ).ready( function( $ ) {
    /** Note: $() will work as an alias for jQuery() inside of this function */

    var video_selector = $('.format-video embed, .format-video iframe');

    /** Get the initial width and height values */
    var embed_width = video_selector.attr('width');
    var embed_height = video_selector.attr('height');

    /**
     * Find the ratio between the height and the width to recalculate the height
     * of the embedded video
     */
    var embed_ratio = embed_height / embed_width;

    /**
     * Change the embed / iframe video to use the full width of the post content
     */
    video_selector.attr('width','100%');

    /** Get the new width value as a number and replace the 100% value */
    var new_width = video_selector.width();
    video_selector.attr('width', new_width );

    /**
     * Calculate the new height by multiplying the new width times the original
     * ratio. Then change the embed / iframe video height to the new height.
     */
    var new_height =  new_width * embed_ratio;
    video_selector.attr('height', new_height);

} );

The comments fairly explain the ideas being applied. Simply stated:

• Get the width and height of the original video
• Calculate the aspect ratio based on those values
• Find the HTML class container width and apply it to the video
• Apply the calculated aspect ratio to the video height

In general this will work under most any circumstance, although the sample above is specifically used for WordPress Post-Format: Video posts; the key is the value(s) used in the video_selector variable.

Huge credit goes to Frederick Townes and the W3 Edge team for being proactive and diligent in correcting the issues that several hosts encountered. W3 Total Cache is a great plugin, which is why we recommend it to every site we host as well as providing Synthesis-specific settings in your welcome email.

Update and deploy with confidence!

First – let me say we love W3 Total Cache and will continue to recommend it as the most robust and flexible caching plugin out there. And secure. Did we say secure?

But for now – leave your W3 Total Cache UN-upgraded.  There have been some issues with upgrades that are wide spread enough to warrant a bit of caution. Check back to this post for updates and when we think its safe to upgrade, we will let you know. This information comes from the smart people at Synthesis, who I trust with my hosting needs, and recommend exclusively for anyone who gets more than 1,200 unique visitors a day to their WordPress site.

Huge credit goes to Frederick Townes and the W3 Edge team for being proactive and diligent in correcting the issues that several hosts encountered. W3 Total Cache is a great plugin, which is why we recommend it to every site we host as well as providing Synthesis-specific settings in your welcome email.

Update and deploy with confidence!

First – let me say we love W3 Total Cache and will continue to recommend it as the most robust and flexible caching plugin out there. And secure. Did we say secure?

But for now – leave your W3 Total Cache UN-upgraded.  There have been some issues with upgrades that are wide spread enough to warrant a bit of caution. Check back to this post for updates and when we think its safe to upgrade, we will let you know. This information comes from the smart people at Synthesis, who I trust with my hosting needs, and recommend exclusively for anyone who gets more than 1,200 unique visitors a day to their WordPress site.

The post Important Message regarding W3 Total Cache appeared first on Website Services for Small Businesses.

Please note this is more for intermediate site admins.

© andrea for WordPress "Must-Use" Tutorials, 2013. | Permalink | No comment | Add to del.icio.us
Post tags: comments, spam

Check out WPeBooks.com for multisite plugins & ebooks.

Feed enhanced by Better Feed from Ozh

= Version 2.0.1 =
* Released February 2013
* Documentation updates (copyright year, compatibility version)
* Added code block termination comments
* Changed MultiSite conditional to use `is_multisite`
BNS Login changelog

© 2013, Edward Caissie. All rights reserved.

= Version 2.4 =
* Assigned the string from `get_the_excerpt` to be used as the basis of the custom excerpt string
* Added conditional to only append link if there are words to be used in the excerpt
* Added termination comments to code blocks
* Added dynamic version to enqueue parameters used in Options
* Refactored code into a more OOP style
BNS Featured Category changelog

© 2013, Edward Caissie. All rights reserved.

When I released it there were quite a few people hoping that it added/output a new menu on the sub sites. I’ve written a bit of code that allows you to do that. What needs to be done to use the NWM for a new menu is

1. Register a new menu across the network
2. Make sure that menu is registered before the regular menus are registered on the sites. This ensures that the new global menu is the first menu slot on all sites.
3. Hide the global menu admin on the sub sites so users do not attempt to populate it with items that will never be shown
4. Add the menu to the themes across the network

You can accomplish the first 3 items with the following:

The best place to have that code is in a small plugin in the mu-plugins folder. The earlier this code executes the better.

Now all you need to do is add the menu output to your theme and style it appropriately in each theme:

© Ron for WordPress "Must-Use" Tutorials, 2013. | Permalink | 9 comments | Add to del.icio.us
Post tags: global menu, network menu

Check out WPeBooks.com for multisite plugins & ebooks.

Feed enhanced by Better Feed from Ozh

Warning: Missing argument 2 for wpdb::prepare(), called in /var/www/techwork.dk/public_html/wp-content/plugins/sharebar/sharebar.php on line 112 and defined in/var/www/techwork.dk/public_html/wp-includes/wp-db.php on line 990

Warning: Missing argument 2 for wpdb::prepare(), called in /var/www/techwork.dk/public_html/wp-content/plugins/sharebar/sharebar.php on line 124 and defined in/var/www/techwork.dk/public_html/wp-includes/wp-db.php on line 990

(Emphasis mine.)

And then a quick google search turned up the perfect solution by Techwork.dk.

You’ll need to use FTP to be sure that you can fix any errors if they occur. Copy the file and edit it offline. Then upload it back to your server.

Warning: You need to use FTP. See above!

Find the plugin Sharebar under wp-content/plugins/sharebar.php.

Download a copy. Make the edits described below.

Line 112 looks something like this:

$results =$wpdb->get_results($wpdb->prepare(“SELECT * FROM “.$wpdb->prefix.”sharebar WHERE enabled=1 ORDER BY position, id ASC”)); $str .= “n”; 

Correct line 112 to look like this instead:

$results =$wpdb->get_results($wpdb->prepare(“SELECT * FROM “.$wpdb->prefix.”sharebar WHERE enabled=1 ORDER BY position, id ASC”, null)); $str .= “n”; 

Line 124 looks something like this:

$results = $wpdb->get_results($wpdb->prepare(“SELECT * FROM “.$wpdb->prefix.”sharebar WHERE enabled=1 ORDER BY position, id ASC”)); $str .= “n”; 

Correct line 124 to loo like this instead:

$results = $wpdb->get_results($wpdb->prepare(“SELECT * FROM “.$wpdb->prefix.”sharebar WHERE enabled=1 ORDER BY position, id ASC”, null)); $str .= “n”; 

Upload it back.

You’re done!  If you have any questions leave them below and I’ll do my best to answer!

Warning: Missing argument 2 for wpdb::prepare(), called in /var/www/techwork.dk/public_html/wp-content/plugins/sharebar/sharebar.php on line 112 and defined in/var/www/techwork.dk/public_html/wp-includes/wp-db.php on line 990

Warning: Missing argument 2 for wpdb::prepare(), called in /var/www/techwork.dk/public_html/wp-content/plugins/sharebar/sharebar.php on line 124 and defined in/var/www/techwork.dk/public_html/wp-includes/wp-db.php on line 990

(Emphasis mine.)

And then a quick google search turned up the perfect solution by Techwork.dk.

You’ll need to use FTP to be sure that you can fix any errors if they occur. Copy the file and edit it offline. Then upload it back to your server.

Warning: You need to use FTP. See above!

Find the plugin Sharebar under wp-content/plugins/sharebar.php.

Download a copy. Make the edits described below.

Line 112 looks something like this:

$results =$wpdb->get_results($wpdb->prepare(“SELECT * FROM “.$wpdb->prefix.”sharebar WHERE enabled=1 ORDER BY position, id ASC”)); $str .= “n”; 

Correct line 112 to look like this instead:

$results =$wpdb->get_results($wpdb->prepare(“SELECT * FROM “.$wpdb->prefix.”sharebar WHERE enabled=1 ORDER BY position, id ASC”, null)); $str .= “n”; 

Line 124 looks something like this:

$results = $wpdb->get_results($wpdb->prepare(“SELECT * FROM “.$wpdb->prefix.”sharebar WHERE enabled=1 ORDER BY position, id ASC”)); $str .= “n”; 

Correct line 124 to loo like this instead:

$results = $wpdb->get_results($wpdb->prepare(“SELECT * FROM “.$wpdb->prefix.”sharebar WHERE enabled=1 ORDER BY position, id ASC”, null)); $str .= “n”; 

Upload it back.

You’re done!  If you have any questions leave them below and I’ll do my best to answer!

The post Simple fix Sharebar Plugin error with WordPress 3.5 appeared first on Website Services for Small Businesses.

Here is the theme’s screenshot … you be the judge.

The Pinup Meets Grunge screenshot image.

A larger version of the screenshot is available on the theme’s home page.

© 2013, Edward Caissie. All rights reserved.

/**
 * Makes our wp_nav_menu() fallback -- wp_page_menu() -- show a home link.
 *
 * @since Twenty Twelve 1.0
 */
function twentytwelve_page_menu_args( $args ) {
	if ( ! isset( $args['show_home'] ) )
		$args['show_home'] = true;
	return $args;
}
add_filter( 'wp_page_menu_args', 'twentytwelve_page_menu_args' );

Note line 194 is turning on the show_home option. If you have a look at the WordPress codex article for the wp_page_menu function you can read more about other menu options. To change the default “Home” text to something else, simply replace the word true with a word or phrase of your own choice (remember to place this new “Home” name in quotes).

Now, the best way to actually do this would be via a Child-Theme. All you need to do is create a simple Child-Theme and add a functions.php template file with a similar function as the one used in Twenty Twelve itself. Something like this would work:

/**
 * Makes our wp_nav_menu() fallback -- wp_page_menu() -- show a home link named "Bacon".
 */
function twentytwelve_child_theme_page_menu_args( $args ) {
	if ( ! isset( $args['show_home'] ) )
		$args['show_home'] = "Bacon";
	return $args;
}
add_filter( 'wp_page_menu_args', 'twentytwelve_child_theme_page_menu_args' );

Note the two differences: the function name; and, on line 6 the show_home option now reads "Bacon" instead of true.

This method will work with any theme that has turned on the show_home option in this fashion. The Twenty Twelve theme was used as an example as this post was inspired by this WordPress Support forum thread.

You might want to read this article as a reference for creating a Child-Theme as starting point, or a refresher if you are familiar with how to create a Child-Theme.