Makes WordPress function as an editor for tabs you can embed in a Facebook page for your business, campaign, or organization.
Refinements to code for compatibility with standard WordPress theme coding.
Some of the standard checkbox options like "Open Links / Post Forms to New Window" will not function unless you include fbtab_head(); in the head section of your theme/template. Alternatively, you can link between fbtab content and have it displayed within the same frame and template, but if you link to standard pages you'll need to include ?fb=tab as a query string at the end of the link (otherwise, the content will appear within the frame but be displayed in your standard website template).
Updated code for resizing height of page tabs. It's now particularly important to record the App ID assigned by Facebook in the tab manager plugin, as this version of the code will not work without access to that information. Reveal or gate tabs created through the Reveal Tab Setup utility will also need to have an App ID assigned -- if you provided this previously you will have to enter it again for this release because it's handled differently (encoded into the url).
Update for Timeline page layout to support 810px tab width (usable width for images now more like 800 to 805 pixels). Existing tabs will continue to display in 520-pixel width layout until the layout setting is changed. Note that the change to 810 px width must also be implemented in the Facebook developers utility.
Listing of fbtab posts available for editing now displays author login name and an Add to Page link (for adding your tab to one or more Facebook pages) or a Set App ID link if you have yet to record the App ID # set by Facebook for the tabs you have registered.
Modified the roles and capabilities setup, which previously was set to parallel the 'page' rather than 'post' content type. The settings screen now includes checkbox options that let you make creation of Facebook tab content accessible to authors and contributors (contributors can submit posts for approval).
By default, fbtabs are still treated like pages rather than posts, meaning only editors and administrators can edit them, but at least one website owner contacted me to say that's not how he wanted it to work. So now you have a choice. Authoring and editing capabilities can also be such as edit_fbtabs can now also be set for any custom roles you may have created, separately from other types of posts, by other WordPress administration plugins or your own custom code.
Bug fix for settings screen (footer options).
Cleanup of deprecated WordPress functions and minor PHP coding errors.
Continuing to address recent changes in the Facebook platform, which made it necessary for Facebook Tab Manager to supply its own Add to Page function to let you connect your tab to a specific Facebook page.
The new Add to Page Links screen for admins lets you generate an Add to Page link for reveal tabs created with the Reveal Tab Setup utility, or tabs based on existing WordPress pages or posts using the ?fb=tab query string at the end of a URL.
Important update to keep pace with changes in the Facebook platform. Now, after recording the App ID # assigned by Facebook, you can record this in Facebook Tab Manager, and an "Add to Page" link will be displayed in the editor to allow you to add your tab to one or more pages. The previous installation method must be phased out because of Facebook's decision to eliminate application profile pages, which is where the Add to Page link used to be displayed.
Fix for sites that don't have pretty permalinks enabled.
2 new checkboxes.
Renamed function that decodes Facebook signed request to prevent namespace conflicts with other plugins.
Fixes for alternate paths to the includes directory to make jQuery load properly for the preloader effect.
Bug fix in that fancy new theme / template code.
Bug fix. Error in the code for saving customization settings.
Update to Reveal Tab Setup utility. Looks like Facebook has made some platform changes that were preventing this from working properly, and I've made my own changes to compensate. This version also supports using a form plugin such as Contact Form 7 in the fan-only version of the tab, which wasn't working right previously.
Updating template.php code for better handling of wp_head and wp_footer output with filters selectively deactivated.
Session key set for Liked pages so site will "remember" that setting even after following a link or form post. Important for scenarios where you want to embed a form inside an fblike shortcode.
Correcting error in Reveal Tab Setup screen
Thanks to H.P. Logsdon for some fixing some bugs I missed.
Reveal Tab Setup screen added. Includes a utility for constructing a special url pointing to alternate post IDs for fans and non-fans. On-screen documentation explains tradeoffs between this, shortcode methods.
You can now use ?fb=tab&minfilters=1 as a query string parameters to display existing content in the fbtab template with most filters on the_content turned off.
Bug fix. Some checkbox parameters weren't being saved properly.
Added Documentation as a submenu on Facebook Tabs. Pulls in content from the plugin home page on carrcommunications.com
Bug fix for CSS display, particularly in IE9
Fixed bug in CSS code that prevented custom styles from loading properly.
[fblike]shortcode as an alias to
[fbtab decode="1"]. Recommended for situations where you are wrapping a block of text and image content inside a shortcode that indicates whether it should only be shown to people who have not yet liked, or who have liked your page. Example
[fblike like="0"]IMAGE TO SHOW TO NEW VISITORS[/fblike] [fblike like="1"]FAN-ONLY CONTENT[/fblike]
Changed custom post type setup in response to a report of a conflict with a theme that also uses custom post types.
Fix to options screen
Additional shortcode options
Better handling / explanation for checkboxes to turn off filters and actions that aren't appropriate for a Facebook tab.
Fixing template.php display for canvas pages
Correcting tab/canvas setup code.
Refinements to shortcode function
Fixes to default styles handling, directory locations
First public release February 2011
Requires: 3.0 or higher
Compatible up to: 3.8.3
Last Updated: 2014-2-3
0 of 2 support threads in the last two months have been resolved.
Got something to say? Need help?