Download ABT Featured Heroes  Download from WordPress

As taken from the readme file:

Description

Provides a new content type “Heroes” to manage your featured slides. You can then add a slideshow to any page using the shortcode abt_slider_hero. The slideshow is automatically configured using jQuery Cycle and the options you specify in the shortcode.

One of the options postType allows you to use other content than the provided “Heroes”, effectively allowing a slideshow of almost anything in WordPress.

Installation

1. Unzip, upload plugin folder to your plugins directory (/wp-content/plugins/)
2. Activate plugin
3. Add slideshow shortcode anywhere you need it.
4. If you want to put the widget (shortcode) in a Widget, you’ll need to allow shortcodes in widgets
5. You can call the slideshow in code using abt_featured_heroes::embed( array $atts )

Frequently Asked Questions

What is the shortcode?

Use the following format (defaults indicated here):

[abt_slider_hero fx="fade" width="100%" height="400px" order="asc" orderby="menu_order" speed="600" timeout="7000" classes="" postType="heroes" style="photo"] 

where

• fx = the cycle transition effect (fade, scrollUp, shuffle, etc) – see jQuery Cycle homepage for more information
• width = width of the slide
• height = height of the slide
• order = sorting order (asc/desc) for the fetched items
• orderby = how to sort the fetched items
• speed = transition speed from one slide to the next
• timeout = delay between slide changes
• classes = optional classes to apply to the slideshow
• postType = you can retrieve other content types than “heroes” if desired
• style = normally the thumbnail navigation just reuses the full-size image, but if you want to “control” the quality of the shrunken thumb specify an alternate image size (like “thumbnail”)

Pretty much all of the attributes are optional, so all you need is:

[abt_slider_hero] 

How do I put a slideshow in code?

You can call the slideshow in code using abt_featured_heroes::embed( array $atts ), where $atts is an array matching the shortcode attribute list.

Can I change the defaults?

Only one simple hook available:

• add_filter('abt_featured_heroes_localize', YOURFN);change the base javascript variables used by the flipwall init script:
  • stylesheet: replace the default stylesheet with your own to change the default appearance of slides
  • speed: change the transition speed (from 600 ms)
  • timeout: change the slide delay (from 7000 ms)
  • fx: change the slide transition (from ‘fade’)
  • style: optionally use actual thumbnail photos for navigation, instead of reusing full-size images (default ‘photo’, alt ‘thumbnail’)
  • width: default width (from 100%)
  • height: default height (from 400px)

How to put shortcode in widget?

Use a filter to apply shortcode processing to widgets.

Filter: <?php add_filter('widget_text', 'do_shortcode'); ?>

Download Sponsor Flipwall Shortcode  Download from WordPress

As taken from the readme file:

Description

Creates a cool sponsor wall with flip effect; instead of complicated post management, embed tiles anywhere with shortcodes!

Creates a two-sided square with a “logo side” and a “detail side”. Logo side will display a scaled image, while the detail side will show a name, description, and website link.

Based on awesome script Sponsor Flip Wall with jQuery & CSS by Martin Angelov. Not related to plugin WP Sponsor Flip Wall, which creates a content type in order to display tiles.

Installation

1. Unzip, upload plugin folder to your plugins directory (/wp-content/plugins/)
2. Activate plugin
3. Add flipwall tile shortcode anywhere you need it.

Frequently Asked Questions

How do I make a flipwall tile?

Use the shortcode!

What is the shortcode?

Use the following format:

[flipwall id="image-name" title="Sponsor Name" url="http://whatever.com" linktext="Instead of whatever.com" image="url to image" text="description if singleline" ] Description with <em>HTML</em> [/flipwall] 

where

• id = a unique identifier; if not provided just increments flipwall-#
• title = the name to display at the top of the “detail side”
• url = external link on “detail side”
• linktext = if provided, the text of the external link (instead of just showing the URL)
• image = url of the image for the “logo side”; if not provided will just display text “More about $title”
• text = optional – you can use this for a simpler shortcode if the description is just one line
• class = optional class to apply to the tile

Pretty much all of the attributes are optional:

[flipwall]This tile has no attributes, just a description[/flipwall] [flipwall text="This is just a one-liner"] 

But your resulting tiles wouldn’t be very useful.

Please note: if using the single-line version with text, you must either list all of them as such or list them at the end (due to the way shortcodes are closed in WP)

Also, if you want to use the default container, just wrap everything inside

[flipwall-group] ... [/flipwall-group] 

which will automatically clearfix the tiles.

Can I change the defaults?

Only one simple hook available:

• add_filter('abtSponsorFlipwall_localize', YOURFN);change the base javascript variables used by the flipwall init script:
  • stylesheet: replace the default stylesheet with your own to change the default appearance of tiles
  • speed: change the flip speed (from 350 ms)
  • direction: change the flip direction (from ‘lr’)

Download Contact-Form-7: 3rd-Party Integration  Download from WordPress

As taken from the readme file:

Description

Send Contact Form 7 Submissions to a 3rd-party Service, like a CRM. Multiple configurable services, custom field mapping. Provides hooks and filters for pre/post processing of results. Allows you to send separate emails, or attach additional results to existing emails. Comes with a couple examples of hooks for common CRMs (listrak, mailchimp, salesforce).

The plugin essentially makes a remote request (POST) to a service URL, passing along remapped form submission values.

Includes hidden field plugin from Contact Form 7 Modules: Hidden Fields. Based on idea by Alex Hager “How to Integrate Salesforce in Contact Form 7”

Installation

1. Unzip, upload plugin folder to your plugins directory (/wp-content/plugins/)
2. Make sure Contact Form 7 is installed
3. Activate plugin
4. Go to new admin subpage “3rdparty Services” under the CF7 “Contact” menu and configure services + field mapping.

Please note that this includes an instance of hidden.php, which is part of the “Contact Form 7 Modules” plugin — this will show up on the Plugin administration page, but is included automatically, so you don’t need to enable it. This file will only be included if you don’t already have the module installed.

Frequently Asked Questions

How do I add / configure a service?

See Screenshots for visual examples.

Essentially,

1. Name your service
2. Enter the submission URL — if your “service” provides an HTML form, you would use the form action here
3. Choose which forms will submit to this service (“Attach to Forms”)
4. Set the default “success condition”, or leave blank to ignore (or if using post processing, see Hooks – this just looks for the provided text in the service response, and if present assumes “success”
5. Allow hooks for further processing – unchecking it just saves minimal processing power, as it won’t try to execute filters
6. Map your form submission values (from the CF7 field tags) to expected fields for your service. 1:1 mapping given as the name of the CF7 field and the name of the 3rdparty field; you can also provide static values by checking the “Is Value?” checkbox and providing the value in the “CF7 Field” column.
7. Add, remove, and rearrange mapping – basically just for visual clarity.
8. Use the provided hooks (as given in the bottom of the service block)
9. Add new services as needed

How can I pre/post process the request/results?

See section Hooks. See plugin folder /3rd-parties for example code for some common CRMs, which you can either directly include or copy to your code.

Screenshots

1. Admin page – create multiple services, set up debugging/notice emails, example code
2. Sample service – mailchimp integration, with static and mapped values
3. Customized thank-you page

Hooks

1. add_action('Cf73rdPartyIntegration_service_a#',...
   • hook for each service, indicated by the # – this is given in the ‘Hooks’ section of each service
   • provide a function which takes $response, &$results as arguments
   • allows you to perform further processing on the service response, and directly alter the processing results, provided as array('success'=>false, 'errors'=>false, 'attach'=>'', 'message' => '');, where
     • success = true or false – change whether the service request is treated as “correct” or not
     • errors = an array of error messages to return to the form
     • attach = text to attach to the end of the email body
     • message = the message notification shown (from CF7 ajax response) below the form
   • note that the basic “success condition” may be augmented here by post processing
2. add_filter('Cf73rdPartyIntegration_service_filter_post_#, ...
   • hook for each service, indicated by the # – this is given in the ‘Hooks’ section of each service
   • allows you to programmatically alter the request parameters sent to the service

Basic examples provided directly on plugin Admin page (collapsed box “Examples of callback hooks”). Code samples for common CRMS included in the /3rd-parties plugin folder.

Download Promoted Posts Widget v0.2  Download from WordPress

As taken from the readme file:

Description

Simple widget to display (promote) a specific post/page. Provides a list of from all public post types to choose an entry to promote until a specified date. When this “promotion” expires, you can either display a static message or use another post/page instead.

Installation

1. Upload the plugin folder to your plugins directory /wp-content/plugins/ directory
2. Activate the plugin through the ‘Plugins’ menu in WordPress
3. Add the Widget “Promoted Content” to a sidebar

Frequently Asked Questions

What are the options?

• Title: The displayed widget title – leaving it blank will use the post title (if you override the default, see Hooks)
• Feature Expires: until what date (YYYY-MM-DD) to show the promoted post; after which fall back to the default
• Feature Post: choose from the dropdown of public post types to promote
• Default: display this entry instead after the expiration
• Trim summary to: if no excerpt is provided, shorten the post content to this number of words

Note that you can select the most recent post from the dropdown options.

How can I change the defaults?

If you don’t specify certain options, the widget will use builtin defaults. Override these with the following hook:

add_filter('abt_promo_post_defaults', 'YOUR_HOOK');

where YOUR_HOOK is a function that takes an array and returns the following settings:

function promo_widget_defaults($settings){
    return array(
            #'title'        => 'Latest From MY SITE',    // disable to use post title
            'display'   => 'Check out our new video! Credit goes to ... <p><a class="archive" href="/category/news">News Archive</a></p>',
            'url'       => '#',
            'image'     => '<img src="' . get_stylesheet_directory_uri() . '/images/g_video.jpg" alt="Latest from MY SITE">',
    );
}

What else can I use?

Two static methods are available for “embedding” the widget in code – basically just the internal processing used by the widget function.

abtcore_feature_widget::display_promo($args, $before_title, $after_title) 

which uses the following

abtcore_feature_widget::get_promo($args) 

to get either the promoted post or the default. $args will contain an array of the widget options (title, expire, promo, default, trim).

Function get_promo will return an array of (title, display, url, and image) to display_promo where it gets combined with the defaults from the hook to output the widget HTML.

It will look like this:

1. Go to http://yoursite.com/admin/modules
2. Run the following javascript in your Console (Firebug, Developer Tools, etc – F12)

(function($, D, boxid){ /*--start--*/var $checkboxes = $(':checkbox')
    , $checked = $checkboxes.filter(':checked')
	, $dom_render_to_div = false
	;
    console.log($checked.length, 'enabled modules');

// clear old version
$('#'+boxid).remove();

var render = function(o, renderfn){
	renderfn(o);
};
var render_to_console = function(o){
	console.log(o.i, 'Section:' + o.s, 'Module:' + o.l, o.v);
};
var render_to_div = function(r){
	if( false === $dom_render_to_div ){
		var $container = $('<div id="' + boxid + '" class="debug"><h3>Active Modules</h3></div>');
		$container.append('<table></table>').append('<div class="clearfix">Copy Above</div>');
		$container.css({
			'background-color': '#FFFFFF'
			, 'left': '20%'
			, 'padding': '5%'
			, 'position': 'absolute'
			, 'top': '20%'
		});

		$('body').append($container);
		$dom_render_to_div = $container.find('table');
		$dom_render_to_div.append('<tr><th>i</th><th>Section</th><th>Label</th><th>Version</th></tr>');
	}
	$dom_render_to_div.append('<tr><td>' + r.i + '</td><td>' + r.s + '</td><td><a href="http://drupal.org/project/' + r.id + '">' + r.l + '</a></td><td>' + r.v + '</td></tr>');
};

$checked.each(function(i,o){
	var $o = $(o);
	var $row = $o.parents('tr');
	var section = $o.parents('fieldset').find('legend').text();
		if( 7 == D ) section = section.replace(/Hide /i, '');
	var label = "" + $row.find('td:nth(1) label').text();
	var version = $row.find( 7 == D ?'td:nth(2)' : 'td.version' ).text();
	var iden = $row.find(':checkbox').attr('name').match(/\]\[([^\]]+)\]/)[1];

	var row = {"i": i, "s": section, "l": label, "v": version, "id": iden};

	render(row, render_to_div);
});
/*--end--*/ })(jQuery, 7, 'module-list-debug');

The following steps are the mostly-complete guide to setting up XAMPP: set alternate folders/domains/subdirectories, enable “missing” extensions, and let it play nicely with VisualStudio’s local IIS.

1. Download zip version
2. run setup_xampp.bat to fix directories
3. to access your local dev like `http://ALIAS.localhost:81/whatever.php`, in \apache\conf\extra\httpd-vhosts.conf add your custom directories like: (note port 81 from step 7)

   
   <VirtualHost *:81>
    ServerAdmin YOUR@EMAIL.COM
    DocumentRoot "/Relative/Path/To/LocalFiles"
    ServerName ALIAS.localhost
    ServerAlias www.ALIAS.localhost
    ErrorLog "logs/ALIAS.localhost-error.log"
    CustomLog "logs/ALIAS.localhost-access.log" combined
   
    <Directory "/Relative/Path/To/LocalFiles">
    Options Indexes FollowSymLinks
    AllowOverride All
    Order allow,deny
    Allow from all
    </Directory>
   </VirtualHost>
   

    

4. Update your hosts file (C:\Windows\System32\drivers\etc\hosts) accordingly: 127.0.0.1 ALIAS.localhost
   (added bonus: wildcards in hosts file (untested))
5. OR, instead of #3 and #4, configure subdirectory aliases in \xampp\apache\conf\extra\httpd-userdir.conf, which will let you access your local dev like `http://localhost/ALIAS/whatever.php`
   

   <IfModule alias_module>
    # ===== Description of the following
    Alias /ALIAS "/Relative/Path/To/LocalFiles"
    # Access control, etc
    <Directory "/Relative/Path/To/LocalFiles">
    AllowOverride All
    Options Indexes FollowSymLinks
    Order allow,deny
    Allow from all
    </Directory>
   </IfModule>
   

6. Allow “missing” extensions by uncommenting dll line in \xampp\php\php.ini
7. If also have IIS (VisualStudio) on same computer, you’ll need to change the ports (you can use other numbers)
   1. in \xampp\apache\conf\httpd.conf – change `Listen *:80` to `Listen: *.81`, `ServerName localhost:80` to `ServerName localhost:81`
   2. in \xampp\apache\conf\extra\httpd-ssl.conf – change `Listen 443` to `Listen 442`
   3. ignore the message in xampp-control that says it started on port 80 (that’s hardcoded)

Download Custom User Registration plugin Download from WordPress

As taken from the readme file:

Description

Customize the user registration page with additional validated fields.   Hooks right into existing parts of the registration process.

Provides a number of hooks to allow further customization: fields, validation, email header/message/template, custom signup url (if used with other plugins like BuddyPress).

Works with anything using the regular WP register hooks, like BuddyPress and Prospress.

Installation

1. Upload plugin folder custom-user-access to your plugins directory (/wp-content/plugins/)
2. Activate plugin
3. Go to new admin page User Login – ABT and change the registration url, if needed.

Please note that this includes an instance of Singleton and WP_Options_page, both taken from the WP-Dev-Library plugin, so if you are also using that plugin please be aware of potential conflicts. This plugin checks for the existance of those classes before including files, so if you experience any issues you can remove those lines.

Frequently Asked Questions

How do I add extra fields?

• Use the hook abt_custom_register_fields. Append or replace items in the $fields array with an array of attributes.
• Specify validation with data-validation. See plugin file for examples of password and name fields.
• Make sure that, if you’re providing default WP fields, that the field names are correct.

function YOUR_register_fields($fields){
    $fields []= array('name'=>'user_url', 'type'=>'text', 'class'=>'input url', 'size'=>20, 'label'=>'Your Website', 'data-validation'=>'url');
    $fields []= array('name'=>'aim', 'type'=>'text', 'class'=>'input social-client', 'size'=>20, 'label'=>'AIM', 'data-validation'=>'alphanumeric');

    // set name required
    $fields[3]['data-validation'] = array('required', 'string');

    return $fields;
}
add_filter('abt_custom_register_fields', 'YOUR_register_fields');

How do I change the email?

** Headers **:

function YOUR_register_email_headers($headers){
    $headers []= 'Bcc:youremail@domain.com';
    return $headers;
}
add_filter('abt_custom_register_email_headers', 'YOUR_register_email_headers');

** Template **: Just copy email-signup.tpl.php from the plugin folder to your theme folder. Or use the hook abt_custom_login_email_templates.

How do I customize my thank-you message?

On your custom thank-you page, add something like the following:

    // check if we had a successful signup - indicated by a notification in session
        $referer = isset($_SERVER['HTTP_REFERER']) ? $_SERVER['HTTP_REFERER'] : NULL;
        if( false !== strpos($referer, 'action=register')
            || (
                true === ABT_Custom_User_Access::flash_var('notification')
            )){
                ?>
                <p>Thank you for registering!  Please check your email for a confirmation message.</p>
                <?php
                // clear the flash message
                ABT_Custom_User_Access::flash_var(false);
        }

Hooks

1. abt_custom_login_nometa determine which fields are not treated as usermeta, but instead directly on user table format: pipe-separated, default = '|user_url|display_name|'
2. abt_custom_login_fields add or remove additional login fields
3. abt_custom_login_extra_validation apply extra validation, return whether it has errors or not – uses $has_errors, $key, $attr, $post
4. abt_custom_login_has_errors do something with the errors instead of saving the field
5. abt_custom_login_email_templates adjust default template names
6. abt_custom_login_email_headers change default email headers
7. abt_custom_login_email_message change email message before it’s sent to user
8. abt_custom_register_url change where the form redirects to on error; not completely working, so please rely on the admin option instead.
9. abt_custom_register_admin_settings add more admin settings (using WP_Options_Page class)

However, even though it appears they tell you where things went wrong (via trigger_error), it actually just points you to the _doing_it_wrong function.

Fortunately, those hook-crazy developers threw us a bone in that function:

do_action( 'doing_it_wrong_run', $function, $message, $version );
//

Now we can figure out the offender ourselves with a hook:

/**
 * Because new WP 3.3 "doing it wrong" warnings don't really tell you where you screwed up...
 * @param string $function The function that was called.
 * @param string $message A message explaining what has been done incorrectly.
 * @param string $version The version of WordPress where the message was added.
 */
function abt_doing_it_wrong_helper($function, $message, $version){
	$before = <<<EOD
<strong>$function:</strong> v$version
EOD;
	debug_whereat(3, 5, $before);
}
add_action( 'doing_it_wrong_run', 'abt_doing_it_wrong_helper', 10, 3 );
//

And the helper function for printing debug_backtrace (use your own flavor):

/**
 * Pretty-print debug_backtrace()
 * @param int $limit {optional} when to stop printing - how many recursions up/down
 * @param int $skip {optional} when to start printing - how many calls to skip over
 * @param string $before {optional} extra html to print before the table, inside debug container
 * @param string $after {optional} extra html to print before the table, inside debug container
 *  */
function debug_whereat($limit = false, $skip = false, $before = '', $after = ''){
	static $debug_whereat_counter; if( !$debug_whereat_counter) $debug_whereat_counter = 0;
	$uid = $debug_whereat_counter++;
	?>
	<div class="debug trace">
		<?php echo $before; ?>
	<table>
		<thead><tr>
			<th id="th-index-<?=$uid?>"><i>nth</i></th>
			<th id="th-line-<?=$uid?>">Line</th>
			<th id="th-file-<?=$uid?>">File</th>
			<th id="th-method-<?=$uid?>">Method</th>
		</tr></thead>
		<tbody>
	<?php

	$backtrace = debug_backtrace();
	if( $skip ) $backtrace = array_slice($backtrace, $skip);

	foreach($backtrace as $index => $trace){
		//force quit
		if($limit !== false && $index == $limit){
			?>
			<tr><td colspan="4"><em>----- FORCE STOP RECURSION -----</em></td></tr>
			<?php
			break;
		}

		?>
		<tr class="trace-item">
			<th headers="th-index-<?=$uid?>"><?=$index?></th>
			<td headers="th-line-<?=$uid?>" class="line"><?=$trace['line']?></td>
			<td headers="th-file-<?=$uid?>" class="file"><?=$trace['file']?></td>
			<td headers="th-method-<?=$uid?>" class="method">
				<code><?=$trace['function']?></code>
				<?php
				if(!empty($trace['args'])){
					echo '<br />';
					while(!empty($trace['args'])){
						?>	{<i><?php print_r(array_shift($trace['args']) ); ?></i>}	<?php
					}//	while !empty $trace['args']
				}
				?>
			</td>
		</tr>
		<?php
	}
	?>
	</tbody></table><?php echo $after; ?></div>
	<?php

}//	function debug_whereat

The lazy method we got away with before:

function abtcore_shortcode_button( $atts, $content = null ) {
	extract( shortcode_atts( array(
		'color' => 'blue'
	), $atts ) );
	return '<p>' . $content . '</p>';
}

add_shortcode( 'button', 'abtcore_shortcode_button' );

The better way that is now required by WordPress 3.3:

function abtcore_shortcode_button( $atts, $content = null ) {
	extract( shortcode_atts( array(
		'color' => 'blue'
	), $atts ) );
	return '<p>' . $content . '</p>';
}
add_action('init', 'abtcore_register_my_shortcodes', 100);
function abtcore_register_my_shortcodes() {
	add_shortcode( 'button', 'abtcore_shortcode_button' );
}

Notice the add_action() call on the ‘init’ on line 7. This will properly register your shortcode function when WordPress initiates.

I hope this helps.

1. Create a custom field on a node
2. Optionally use that field (if populated) instead of the menu title in the breadcrumb list

So, add the following to your template.php file after creating a node field field_breadcrumb. If you have a better idea, let me know in the comments!

Based on digging through hook_menu_breadcrumb_alter and menu_get_active_breadcrumb.

/**
 * Reconfigure the breadcrumb trail to use each parent's custom field
 * @see hook_menu_breadcrumb_alter
 * @see menu_get_active_breadcrumb
 *
 * @param array $active_trail the current page active trail
 * @param whatever $item the current trail item
 */
function YOURTHEME_menu_breadcrumb_alter(&$active_trail, $item) {

	// must step through each menu item, check to see if it has the 'custom breadcrumb' field
	foreach( $active_trail as &$crumb ) :
		$node_id = str_replace('node/', '', $crumb['link_path']);
		if( $node_id ) :
			// get the node to find the field
			$node = node_load($node_id);
			// best...function...ever
			$crumb_text = field_get_items('node', $node, 'field_breadcrumb');

			// replace existing text if we should
			if( $crumb_text ) :
				$crumb['link_title'] = $crumb_text[0]['safe_value'];
				$crumb['title'] = $crumb_text[0]['safe_value'];
			endif;

		endif;
	endforeach;

	// add a sacrificial final item, since that gets removed later on
	$active_trail []= $crumb;

}//--	fn	YOURTHEME_menu_breadcrumb_alter

/**
 * Return a themed breadcrumb trail.
 *
 * Implements Zen theme `zen_breadcrumb`.  Paired with XYZ_menu_breadcrumb_alter, which appended a sacrificial duplicate
 *
 *
 * @param $variables
 *   - title: An optional string to be used as a navigational heading to give
 *	 context for breadcrumb links to screen-reader users.
 *   - title_attributes_array: Array of HTML attributes for the title. It is
 *	 flattened into a string within the theme function.
 *   - breadcrumb: An array containing the breadcrumb links.
 * @return
 *   A string containing the breadcrumb output.
 */
function YOURTHEME_breadcrumb($variables) {
	if( isset( $variables['breadcrumb']) && !empty( $variables['breadcrumb'] )) :
		// Don't show a link to the current page in the breadcrumb trail.
		// this should automatically take into account theme settings...
		$last_key = end( array_keys( $variables['breadcrumb'] ) );
		$end = end( $variables['breadcrumb'] );
		$current_path = url(request_path(), array('absolute' => false));
		if ( false !== strpos($end, $current_path) ) {
			$variables['breadcrumb'][$last_key] = strip_tags( $end );
		}
	endif;
	// business as usual
	return zen_breadcrumb($variables);
}//--	fn	YOURTHEME_breadcrumb

Todo: make this a module…