With WordPress version 3.3 comes with the Feature Pointer a well-known idea from other tools. We know this for example from Gmail or Google Doc where they notice you of new features, in which they point with bubbles to these new features. In WordPress 3.3, the Admin Bar has been redesigned successfully – I think – and this is the first time the feature pointer points to it.
add_filter( 'show_wp_pointer_admin_bar', '__return_false' );
If you don’t have the admin bar not active, then it won’t show a feature pointer to it.
Also you can use the hooks to create your own feature pointer. Without adjustment in the design and position is the following simple example conceivable. If the position is changed, it is sufficient to adapt the script section JS-function
pointer() in the PHP function
get_content_in_wp_pointer(). The function
pointer() can be controlled by various parameters (
content, position, arrow) .
Please note: The implementation is based on a nightly build of WordPress, not the final Release 3.3 and thus might have some changes or other solutions are possible in a later version. Therefore, please validate according to the version of WordPress the solution. As a tip this should be enough – anything else is creativity and your skills.
8 responses to “How to Add and Deactivate the new Feature Pointer in WordPress 3.3”
Here’s an example admin pointers implementation in a child theme for Twenty Eleven: http://theme.fm/2011/09/introducing-pointers-in-wordpress-3-3-2407/ 🙂
Phew, thanks for this! The pointers are totally incompatible with IE7. You can’t close ’em! I mean, that’s totally cool, WP no longer supports IE7 with this release. But, unfortunately at work, I have no options. I can’t upgrade my browser, I’m stuck with what they give me.
That’s not right.
If you think it’s broken then please add a comment on http://core.trac.wordpress.org/ticket/18693.
wp_localize_script()to access the pointer content.
Looks like it’s an issue in IE8 as well, Ipstenu and I reported the same problem, at the exact same time….
The “Please note” at the bottom is nice, but it never ends up being enough. This API is absolutely guaranteed to change.
I’d be nice if new features aren’t written about at least until beta or something.
@Andrew: hmm, i see this as an chance to get little peeks for WordPress, news are very interest, especial if it a news, waht also see the Users outside the source 😉 If an developer will use this, then he can see the source on the current version. Also, maybe so it is possible you get more feedback to this topic, more people read this and can give constructive feedback; install the nightly build, see this new feature, see the ticket and give feedback.
I like the idea of people writing about upcoming features, but I can understand why getting into the technical details may not be such a good idea. Certainly any changes to the API should be reflected in the post to avoid incorrect information getting a high search position?