I’m using bbPress (the new plugin version) for about 2 weeks and I quite like it.
Regarding the comments and emails, I still reply to comments on the ThemeForest commenting system because I think Buyers shouldn’t have to register in all the support forums of the different authors they purchase items from. I do remind them of the support forum though. The emails I redirect to the forum.
Kriesi saidLove that idea.
That sounds great Jason! One question: could you guys write the plugin in a way that we can easily implement it directly into our themes so the user doesn’t have to install a plugin?
This guy never just says +1
Would be nice for a structure like this:
EnvatoUpdater.phpand add a small line of code to functions.php.
Similar to the way Joãos update notifier works:https://github.com/unisphere/unisphere_notifier
By the way guys, feel free to use any of my code or the concept in the new plugin
contempoinc saidDang, wish I heard about that one. Looks awesome!
Here’s the one we’re all using: https://github.com/unisphere/unisphere_notifier
On a side note, I haven’t personally developed a WordPress plugin nor is PHP a language I’m 100% comfortable with so any WP plugin ninja out there fell free to grab my code and apply it to a plugin.
The code is 100% functional but it can be improved in many aspects, mainly:
- using the Transient API instead of manually caching HTTP responses in the database (wp_options);
- a more robust way of mitigating “damage” if the XML file end point in the remote server is inaccessible for some reason.
Sorry guys if this was already posted on the forum, I couldn’t find it.
A potential Buyer of my most recent theme (2 months old) had a pre-purchase concern regarding the validation of the theme in W3C , it was displaying validation errors. You can imagine my surprise since 2 months ago when I submitted the theme the validation errors weren’t there. I decided to search for the validation errors but couldn’t find anything of interest, just this post.
In my theme (and I believe in most theme this is happening), these are the errors:
<meta name="search" content="search..." />
It seems the rel attribute now has limited valid values for a correct validation so lightbox plugins that use the rel attribute, like prettyphoto for example, will have validation problems.
This also happens with the rel=”canonical” markup generated by WordPress.
If you take a look at this post dated from February 2011 you can see the default Tweentyten WordPress theme validates correctly with the HTML5 Doctype. Try and validate it now and you can see the same errors: check errors
Would love to hear your thoughts about this.
Here’s how the badge should look like