License renewal and future price

license renewal and price model

Almost a year had passed since we released the first version of the “pro” plugin, and we actually were totally too busy in finalizing and releasing the 4.7.1 to give much thought about license renewal pricing, but our licensing software (If you are interested to know, it’s the Software Licensing extension of EDD) had sent us a reminder that our development license is about to expire and reminded us that this part also needs to be handled.

What is a renewal

When you renew the license you get another year of support which includes support via email, and the ability to use the WordPress built-in plugin upgrade mechanism for upgrades.

How much will it cost

$6,- per license – yes a 50% discount. If you manage several sites give us a call and we will figure out a discount.

What happens if I don’t renew

Apart from not being able to do the upgrades from the WordPress admin, the plugin will continue operating fully.

The current price offer is still available until 02 May

Starting with 02. May 2017 we will raise the price of the widget to $15,- (renewals will cost $7,50), and probably “hide” the 20% coupon on our wordpress.org, Twitter and Facebook pages. So if you feel like saving some money, might be a good idea to get another license now.

4.7.1 version of the Term and Category Based Posts Widget is released

This is a very feature packet release it was tested for compatibility with WordPress 4.3-4.7.

New

New versiton Term and Categorz Based Posts Widget 4.6.1

  • Can have multiple shortcodes at the same post
  • A UI in the editor for the insertion of a shortcode
  • More complex ways to filter by taxonomies and terms
    • Option to match all or any of a selected taxonomy term, or have a negative match (match when terms are not selected).
    • For hierarchical taxonomies it is possible to select whether the “children” of the select terms might match.
    • when two or more taxonomies are used for filtering, it is possible to set matching to require that posts will match the rules of both taxonomies (AND rule) or just one (OR rule).
  • More touch device friendly with the “everything is a link” option, which make the whole screen area of the displayed item to be a link, that includes whatever spaces are there as well.
  • More granular control of default styling with an option to not apply default font styling.

Licensing

You do not need a license to use the plugin on your local machine, enabling you to avoid getting a second license for a development machine, easy to showcase to a client, or whatever other uses there might be (yes we are aware that there are other development settings as well and intend to address them in the following releases).

Technical changes

PageSpeed oriented improvement: We have completed the deprecation of the css file, and started to add only the CSS rules that are actually being used on the page.

Excerpt improvements: New widgets and shortcodes that will be created in the 4.7 release will use our own automatic excerpt generation logic (which mimic 1 to 1 how wordpress generates them) without applying the wordpress filters on the generated results, therefor reducing the chances of bad interactions with other themes and plugins

Never used the plugin before? Download it for free (TACBPW v4.7.1) and give it a test drive on your local machine!

You are welcome to take 4.7.beta2 for a spin

4.7.beta contains all the features we intended to have in 4.7, and as far as our testing goes, it is bug free. We might do some minor UI related changes and obviously fix any reported bugs, but unless a major bug will be discovered we intend to release 4.7 at the weekend of 28th of January.

Get it while its hot 😉 and download the zip  term-and-category-based-posts-widget-4.7.beta2.zip. Reminder you should be able to try it on a local computer without the need of additional license.

What has changed since 4.7 beta1?

  • New filtering options for terms an taxonomies
  • A very slight performance improvement as we eliminated the need to make an extra request to get the additional CSS file on the front-end, by incoperating the rules into the HTML itself

New in 4.7: more post filtering options based on taxonomy and term

In 4.7 we will extend the filtering options to help you narrow the range of possible posts based on their taxonomies and terms.

Customize term shortcode – test 4.7

The first and least important change is how we name the “Anything may match” option. Prior to 4.7 it was named “Any”, and no one every asked if “Any” means that there have to be at least one term of that taxonomy associated with the post, but technically, “Any” meant that there will be no filtering at all done based on that taxonomy and therefor we decided to change its name to “Ignore” which better represent what is actually happening.

Actual additional filtering options are:

  • Exclude child term: By default, when filtering by a hierarchical taxonomies (like categories), the posts being displayed would be of the term being selected and any of it sub/child terms. This option will let you decide if you want those sub/child terms result or not.
  • Content must be associated with: By default, when filtering is done by several terms it is enough for the post to be associated with any of them. This option lets you specify other criteria as well:
    • Any of the terms: An explicit option for the previously default behaviour
    • All the terms: To match, a post must be associated with all of the terms
    • None of the terms: Only posts which are not associated with any of the terms will match. This is useful when you want to exclude posts of specific term (for example one which used to drive a slider)
  • All taxonomies not being ignored, have to match: Before 4.7 it was enough for a post to match any of the taxonomy based filtering. For example if you had filtering rule that involved both categories and tags, it was enough for the post to be associated with the correct categories, but didn’t had to be associated with the correct tag, and vice versa. This option lets you specify a different behaviour in which all taxonomy filters have to match in order for a post to match the filter.

New in 4.7: Exclude child categories

Up to 4.7, when filtering by a specific category the post items displayed included also posts from subcategories of the selected category. In 4.7 we introduce the option to restrict the post items to a specific category without displaying posts from its subcategory.

Customize test 4.6 – Just another WordPress site(4)

Multi selection is available in the premium widget

Is there a need to filter and select category with multi selection? We support such a feature in our premium widget Term and Category Based Posts Widget. We do this differences because we want a light weight widget with Category Posts Widget. In the most cases filtering and show posts from only one category fits all aims. On the other side our premium widget supports also custom post types. So the aim to select two or more categories, terms, what ever, … is more possible. So the filter UI from the premium widget can takes more time for configuration as the free version it does.

New in 4.7: Show all recent post, no category filtering

We think our widget has great features which are no match for the WordPress recent posts widget, and as there was always a possibility to hack the widget into showing all recent posts, we decided to just make it more organized by letting the user just specify an “All categories” in the category filter ti disable the category filtering all together.

Customize test 4.6 – Just another WordPress site(2)

Select more then one category

Is there a need to filter and select category with multi selection? We support such a feature in our premium widget Term and Category Based Posts Widget. We do this differences because we want a light weight widget with Category Posts Widget. In the most cases filtering and show posts from only one category fits all aims. On the other side our premium widget supports also custom post types. So the aim to select two or more categories, terms, what ever, … is more possible. So the filter UI from the premium widget can takes more time for configuration as the free version it does.

New in 4.7: Try before you buy and license migration

We believe strongly that people are willing to pay for value, and that our products are a good value for the price we ask. We have the whole licensing operation merely to prevent honest people from being tempted by the “dark side”, because we are all just human and no matter how wealthy we are we will always be tempted to save that 10$ if possible.

This is why we want the experience of honest people be as smooth as possible and let them do as much as they want with their license.

The upcoming 4.7 release will have two improvements in this regard:

  • Try before you buy – Even with a mere 10$, you are likely to “hate” yourself if you bought something that do not work for you and because of lack of documentation, or whatever other reason, you thought that it will.
    With 4.7 we will let people to download a version which will not require a license as long as it is used on a local development server (in other words, a localhost or if the site domain resolves to the local host ip of 127.0.0.1). This hopefully will let users check the relevant features before buying.
  • License transfer between sites – Sometimes when going from development to production the domain of the site changes, and if you are not going to keep a live development server, it doesn’t make any sense for both the user or us to make the user buy two licenses just for that.
    With 4.7, in this kind of situation you will be able to just deactivate the license on your development site and activate it on production.

We are also looking at doing licensing per domain instead of per wordpress site, but we have no firm idea yet how such an implementation might look, and when will we do it.

New in 4.7: Default thumbnail

Thumbnail are great for the look of the page, but the problem with them is that they require some extra effort when editing the content, an effort for which you might not have time when you rush to publish something, or you just forget.

This kind of situation could have been handled in 3 different ways before 4,7

  • Do nothing and just don’t display a thumbnail. If the thumbnail setting produce a small thumbnail, it might be ok, but when the thumbnail is big and dominant, an item without it will ruin the balance of the design and might be harder to spot.
  • Just don’t display posts without a thumbnail. This keeps the visual balance but it means that the post is going to be more hidden than other posts.
  • Use a plugin that lets you specify a fallback thumbnail.

In 4.7 we are going to add an additional option, to set a fallback thumbnail for a specific widget. This will let you keep the visual balance without having to install additional plugins, and even have different fallbacks in different widgets.

default-thumbnail

And something that might have looked like

Customize test 4.6 – Just another WordPress site(2)

easily transformed to (notice the first item)

Customize test 4.6 – Just another WordPress site(3)

This feature will go into the 4.7 version of both the “free” and “pro” plugins due to be released right after WordPress version 4.7 will have its first RC release which is scheduled right now to november the 15th.

You can try the feature by downloading and installing the beta from https://github.com/tiptoppress/category-posts-widget/releases/tag/4.7.beta1, and report bugs or just get an impression of what is planned from our bug repository at https://github.com/tiptoppress/category-posts-widget/issues

New in 4.7: Skip first few items with the offset parameter

Some times you just don’t want to show the most recent posts, maybe because you have two widgets and the two most recent posts you want to display in the sidebar while another 8 are displayed at the footer.

To get this possible in 4.7 we have add an “start offset” parameter (not the greatest name, suggestions welcome) to indicate how recent (or whatever sort criteria is used) the post displayed should be, with a value of 1 indicates that the posts should stat with the most recent, 2 indicates they will starts if one item after the most recent and so forth (we preferred a 1 based system as it seems to be easier to understand than zero based one).

Technically the feature is implemented by requesting the DB to return items starting from position N and does not retrieve the first “ignored” items at all.

Widgets ‹ test 4.6 — WordPress(1)

This feature will go into the 4.7 version of both the “free” and “pro” plugins due to be released right after WordPress version 4.7 will have its first RC release which is scheduled right now to november the 15th.

You can try the feature by downloading and installing the beta from https://github.com/tiptoppress/category-posts-widget/releases/tag/4.7.beta1, and report bugs or just get an impression of what is planned from our bug repository at https://github.com/tiptoppress/category-posts-widget/issues


Related posts:

New in 4.7: Multiple shortcodes

When we added the shortcode to 4.6 we were not very sure about the way the feature was implemented. Due to the large number of option it was obvious that doing it the “normal” way works and users know it and accept it, but making users cram them on one line hoping that they got the syntax correctly is a bad user experience.
Instead we decided to try a different approch, use the shortcode itself as a pure place holder, and configure the settings via the customizer, with the settings being stored as a custom field in the relevant post DB instead of being part of the shortcode itself.

Wanting to reduce the risk of developing something that people will hate, we implemented in 4.6 only one shortcode per post, but in general it seems like the feature got a good reception, we had a very good experience with it while testing the code and setting our own demo pages, and seems like the only problem where with some obscure page builders (Pippin Williams’s review of them is a must read) and therefor we are enhancing the feature in 4.7 and enabling to have as many shortcodes as you like.

The only change from 4.6, is that if you want to have more then one shortdcode, in order to differentiate between the short codes you need to assign a value which will identify them in the attribute “name”. The value can be anything you like, no special formatting is required. If the name attribute is not explicitly assigned it default to be a “” (empty string).

Here is an example of how it looks in the editor:

Edit Post ‹ test 4.6 — WordPress(1)

And the possible front end output.

4.7 test – test 4.6

This feature will go into the 4.7 version of both the “free” and “pro” plugins due to be released right after WordPress version 4.7 will have its first RC release which is scheduled right now to november the 15th.

You can try the feature by downloading and installing the beta from https://github.com/tiptoppress/category-posts-widget/releases/tag/4.7.beta1, and report bugs or just get an impression of what is planned from our bug repository at https://github.com/tiptoppress/category-posts-widget/issues


Related posts: