Philip Newcomer

Hey Bryan, I’ve just released version 1.1 of Widget Output Filters which now includes the sidebar ID in the parameters it passes to the filter. ??

Bryan,

Regarding your first question, functionally all three examples will give the same result, so here it’s really a matter of personal preference and best practice. If you have more than a couple of if statements you’d definitely want to use the switch, as it will be easier to read and maintain.

Regarding your question on priorities, the only priority that comes into play here is the WordPress filter priority. The filters will be processed in order of weight, so you can change the weight of your callback function when you register each hook in order to change the order in which your filters are run. For any filters that have been registered with the same weight, WordPress will process them in the order in which they were registered.

You could just put all widget filtering in one function and control the order there in your source code, with one filter. Again, functionally all these will give the same result, so it’s a matter of personal preference.

I’ve updated the plugin with version 1.5 of jQuery-rwdImageMaps.

I’m experiencing this issue too.

Actually I hate subscriptions haha, thus I wouldn’t go with subscriptions ??

Haaa, fine, I’ll give you a special code :p

I second this… I don’t like yearly subscriptions either, but I do think it’s best from a developer’s perspective. ??

You have built a great product, and for the long-term health of the project, you should have some sort of income from it to support continued development. It’s not fair for us to get the product for free, and expect one-on-one support for free as well, for the life of the project. So regarding a premium version, I say “go for it, we want to see this project live on for many years!”

With that said, I myself probably wouldn’t buy the premium version if it was more than around $10. I just wouldn’t have that much of a need for additional settings and configuration options. However, I’m not saying that it wouldn’t be worth that. I’m sure there would be corporate users who need to get their WP sites high-res ready, and would be willing to pay much more than that for full configuration options, and a guarantee of support. I’d even be fine with you removing some of the current free version’s features and making them available only in the premium version. I like simple software that “just works”. If users need full configuration options, then they can buy premium. Lots of software works this way. It would probably make a bunch of people mad if you removed features from the current free version, although it’s fine by me. Perhaps if you changed the name, it could be a new product, and you can keep the current state of WP Retina 2x available free as a legacy unsupported version for them, and then create a new simple version for free, and a premium version with full configuration options and support.

Another thing is I am thinking about a new name since we now have 3x devices… what about WP Retina X? Simple ??

I personally think “X” when used in this way is too ambiguous, and provides no useful information. I think a lot of users may think, “WP Retina, I know what that means, but what does X mean?”

May I suggest “WP Retina Plus” as a naming possibility? I think “Retina Plus” is more descriptive than “Retina X”.

On the other hand, I don’t think 2x would be bad to keep. It’s only the really hardcore geeks that even know that a screen is not actually 2x, but 3x instead. The majority of people just want their WordPress to look nice on high-res displays, and don’t know or care that “2x” is not always 100% technically correct.

There is already functionality existing in the WordPress repository which allows users to vote on whether a plugin works with a given WordPress version. Currently there are two “Yes” votes for WordPress 4.0 and no “No” votes. Bumping the version number without making any functional changes could be seen as gaming the system to artificially increase the plugin’s download count.

I am not aware of any issues that the plugin has with WordPress 4.0.

Please open issues for reproducible bugs, feature requests, and contributions on GitHub, and general usage questions here.

I am not aware of any problems the plugin has with WordPress 3.9.

Please keep in mind that the developer of the RWD Image Maps jQuery plugin most likely cannot provide free one-on-one implementation help, so you should restrict the issues you create in the GitHub bug tracker to demonstrable bugs, and reduced testcase scenarios. If you need general implementation help beyond the documentation provided for the WordPress and jQuery plugin, or help with sorting out theme and/or plugin conflicts, you should consider hiring a developer.

From the plugin description:

This plugin provides a filter which will allow developers to modify the complete HTML output of any widget.

The plugin does not “look like” anything on its own. It simply provides a filter which developers can use to modify a widget’s output themselves. The end result will “look like” whatever the developer makes it look like by filtering a widget’s output. Please see the code example for how this is done.

What exactly do you want a picture of? There is already a code example, if that’s what you’re looking for.

Hi, please read the sticky post at the top of this forum “Please Read Before Posting Here”: https://www.ads-software.com/support/topic/please-read-before-posting-here

Here’s the relevant content from the plugin page:

You can use get_author_post_rating( $post_id ) and the_author_post_rating( $post_id ) in your templates. Passing the post ID is optional, if you don’t include it the plugin will use get_the_ID() to try and figure it out for itself. You can pass the current post ID, or the ID of another post if you wish.

get_author_post_rating() will return the numeric post rating, if the post has one. This value does not include the HTML markup or star images which would surround the post rating on a normal post, it just returns the rating value itself.

the_author_post_rating() will echo the post rating along with the label and star images. Optionally, you can set the second parameter to true to return the markup instead of echoing it, like this:
$rating_markup = the_author_post_rating( $post_ID, true );

In your case you’d want to use the the_author_post_rating() function, which will actually display the rating along with the label and stars, instead of just getting the post meta rating value with the get_post_meta() function.