My WordPress plugin, Gravatar Signup Encouragement, got an update. This version adds to new things under the hood and in some situations it may cause some issues, so here is what’s changed.
Previously, plugin depended on
allow_url_fopen to be enabled so that it can check if gravatar exists. Thanks to report by wp.org user jlencion, plugin will now check if
allow_url_fopen is enabled and if not, it’ll fall back to WordPress HTTP API.
After another report on wp.org forum by user Parakoos, plugin now checks for existence of gravatar of the same rating as chosen in site’s settings.
Please report if there are any issues with this new changes.
This version improves existing and adds new features. You can check full changelog here but below I’ll highlight most important ones.
Now you can show message to registered user in admin bar so it will follow them through whole site.
If you use new bbPress plugin, you can show message in a reply form.
One issue that was preventing inserting correct e-mail address in field on Gravatar’s signup page was fixed too.
Other issues are under the hood. Everything now has documentation for developers, functions are reordered in a more logical way, plugin uses less resources since settings are moved to a separate file.
Finally, I prepared a video tutorial that shows plugin in use. Don’t forget to turn on captions (subtitles) since this is where you’ll get text.
If you like this plugin, promote it through tools below or donate.
Do you like new Gravatar Hovercards? Why don’t you prepare your visitors without Gravatar for the upcoming plugin with this feature for self-hosted WordPress installation by encouraging them to signup to Gravatar?
This version improves existing and adds new features. You can check full changelog here but below I’ll highlight most important.
Now message is also shown to users who already left comment before. Also, it is much easier to show message on comment form that doesn’t follow standard WordPress markup (I added support Carrington Blog and Mystique themes though users can add support for any other too).
If you was limited with way of selecting page elements for showing of message there are good news: now you can add a message to literally any element by using any jQuery selector! Note that old custom IDs are automatically updated to new form on plugin’s upgrade.
You thought that message shown when comment is written was not visible enough? Welcome the new way to show message: in a dialog box after user posted comment as in picture below.
This dialog will be shown only if user doesn’t have Gravatar, not to all users who left comment. It is not popup window, it is simply a Thickbox iframe showed on top of your page that will be easily hidden after user clicks close button or click on a link to Gravatar’s signup page.
You thought that message shown on profile page was not visible enough? Welcome the new way to show message in administration area for registered users: in an administration notices as in picture below.
Since WordPress MU was merged to main WordPress branch, I added support to multisite installations so you can show a message to users who signup on your network. Also, you can setup Gravatar Signup Encouragement on per site basis.
If you had problems with Gravatar Signup Encouragement settings, now you can simply click link “example of how this looks” to see screenshot of example of usage of that feature. Also, by clicking “Help” menu in top right corner, you’ll get links to Gravatar Signup Encouragement documentation and support forums.
If you thought that message was not descriptive enough, there is a new, more descriptive one which is shown by default.
For developers, there are many new hooks and functions that can be used in themes and plugins. Post that describes this features will be posted in the future.
You can easily upgrade to new version via automatic upgrade tool in WordPress or by downloading zip archive.
Send your thoughts about Gravatar Signup Encouragement in comments of this blog, or via official support forum.
I have tried for some time to make following: having WordPress installed in a root of host (like example.com) and having content below root (like example.com/page, or example.com/custom-post-type/entry), while having blog posts in special directory (like example.com/blog). This is needed when blog is not main type of content on WordPress powered website, but instead is just one part of a site. Example of usage is having a company website where pages are used for usual static content while there is blog or news section where updates are posted.
At first, this seems easy to achieve. Just change permalink structure on Settings → Permalinks page to something that starts with /blog/ (or whatever subfolder we want to use) as some people (and Codex entry) already suggested.
But there is a problem with this approach: your blog posts will be in your chosen subdirectory but blog’s index and paged pages won’t. This means that you wouldn’t see latest posts by going to blog’s subdirectory (example.com/blog), but instead only by going to front page (example.com).
Solution for this is very easy and I couldn’t believe how I didn’t remember it. I found it on WarriorForum, posted by user Dan Sherman. You simply need to create two empty pages and go to Settings → Reading page and choose those two pages as “Front page” and “Posts page”. Then you go to Settings → Permalinks and choose your new permalink structure.
What is important to remember is to give a name to page that should be chosen for “Posts page” with the same name as you want to name your subdirectory. Also note that for front page you need to either create content as you would for any page, or to use special page template.
Below is a video from WordPress.tv on how to create and setup “Front page” and “Posts page”.