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.

Client-side cropped-, adaptive- and also fluid images for Responsive Layouts

Client-side cropped- and also fluid images

Client-side cropped- and also fluid images

We decided in the past to add a image cropping feature (CPW since 4.1.6, April 13th 2016, as option and TACBPW since 1.0.1, as default), to set your image dimensions in pixel for the feature image or called thumbnail. We called it “CSS cropping for thumbnails“.

This CSS cropping gives your image the possibility to set dimension options for width and height. Our decision till now is to perform this cropping with CSS. CSS is fast and the website admin can use, but it’s not a have to. And our feature don’t neet to generate new images or actually a change for image sizes in the WordPress settings.

We talk much about the feature and implement it to other widgets like Same Category Posts.

We started to solve the max-width problem for our client-side cropped images

Solve "max-width" issue for client-side cropped images with Javascript

Solve “max-width” issue for client-side cropped images with Javascript

The problem we had with our cropped images is we can’t use the CSS property max-width, because the cropping is also made with CSS. No CSS rule solve both features correctly at the same time and we set a fixed width and height. For Responsive Layouts this is very bad to have only one image size and the image can’t be resized, e.g. for many different mobile devices and screen sizes.

For the 4.7 we tried a CSS solution again to solve the aim to have fluid images with CSS attribute max-width. It’s Mark again who mentioned to try it with Javascript. And now it’ll be available with the 4.7 (4.7 beta 1).

The Javascript code works only once at page load or on page resize. Last one is in the normal website usage not performed. The Javascript code is also performance optimized and curse a very less millisecond delay while page load.

Demo page: demo.tiptoppress.com

Advantages with client-side responsive images:

  • No additional (server-side) libraries required.
  • No cookies required.
  • No extra server configuration needed.
  • Does not attempt to perform any client OS detection.
  • Server image storage doesn’t change.
  • Fast server response any time.
  • No image quality loss.
  • No side effects with frequent use on several pages.

Other image features for Responsive Layouts are planed

We’re happy we found a solution and we hope we don’t get problems and can solve the requested Responsive Layout support. What we also want is use the CSS attribute “width” like percentage unit (100%). And either for one dimension and the other as pixels or for both, no size restriction is given and the image fill all the available space. We planed it also for the 4.8 – be patient if all works right.


Related posts:

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:

Terms and Category Based Posts Widget support the Masonry framework

Masonry is a JavaScript UI framework and we decided to support it for “Terms and Category Based Posts Widget” from the version 4.6 and higher. The framework do this “masonry” arrangement for posts and much more – we need some time to understand how the framework works – and now we can proudly say, we know a little part of it. This little part in understanding was enough for support thas UI framework.

Masonry with Thumbnail > Position > Background

Masonry with Thumbnail > Position > Background

The problem(s) which Masonry solve and how is unique

Every time we get to deal with the UI framework we discover and learn something new. Therefore, it is difficult to find one suitable set to describe it. Masonry solve many small and big problems in a simple way. For an entry, following remarks:

“Masonry is used for responsive websites, different screen sizes and all mobile devices and without that media-queries must be defined in the CSS file.”

Especially relevant it’s the second UI framework which is added to the core code beside jQuery which must have a reason. That’s why we want to explain how we use it, which features we start implementing with this Masonry framework and which features we want implement with it further versions of our widget.

Edit the Masonry settings with the customizer

Edit the Masonry settings with the customizer

As a result edit the settings with the WordPress customizer, after Terms and Category Based Posts Widget is added to the widget area or with shortcode. Choose in the Styles panel for Layout: Masonry and our posts should rearrange in a masonry pattern. On the screenshots and at the demo.tiptoppress.com page we use post item width or the thumbnails panel width for position. Thumbnails panel width means “background“, so the text, excerpt and other text content is positioned over the image. So you need to define a width for posts which is enough for the Masonry framework to know to make this posts responsive. Change the Browser width and you can see how the post take place of the page width. Once with three columns, two or one.

Hence for the version 4.6 this should be good to use it. And it will be good, you should try it. Simple to use and solve a lot – for responsive webpages.

Responsive webpages and more

Finally in 4.7 we want to implement two other features for Masonry. We want to add pagination and Ajax scripts which perform infinite page loading effects. If you’re interested in grids and columns for your posts we recommend you should try it out.

In Conclusion the masonry feature is available in the 4.6-beta wich we’ll release in a less days. If you’re already interested in a beta version, please write us: http://tiptoppress.com/contact/

Demo page shows upcoming 4.6 features for the Terms and Category Based Posts Widget

If you’re interested in our new version 4.6 features. We can help you with “start” to expose the final version on demo.tiptoppress.com/.

We release a beta version and use it for our customer sites. Beta means: No more features were added only bugfixes for this version.

Rearrange-our-demo--and-example-page-with-upcoming-4.6-features

All the features announced in further posts are final and we would let you participate with this. Till we decided to release a new version as the same time as WordPress do it. We had a timeline we’ll made a version ready. For the most features it’s good and make a end for coding and coding.

We need your feedback gladly also recognition – as we get it from you in the past. 😉

The demo site shows three main features:

and this demo site will grow in the next days with variations and other good looking and useful features for your website.

With 4.6 we support columns not only rows!

Now it’s possible to arrange your posts not only in rows rather columns are supported. This is possible with the shortcode we had implemented for a while in the free version and now shortcode is also possible with the pro version. (Put shortcode with the pro is: [termposts], with the free widget write [catposts] to the content.) It’s possible use many columns where ever you want, but in the content and not in the widget-area it make much sense and we recomment this layout features to use with shortcode.

Masonry

We had more ideas for all main features and how we improve this. There are a lot of recent topics we are not compleatly doing perfec right now. For the Masonry support we had even delete code we write because we haden’t much time to make it ready and stable.

So we decited to give you a teaser with Masonry and plane next features more sharper. We have to learn to understand this Javascript framework and it can be helpful for responsive websites. When we visit other sites and how to use it so we could be confident to offer it (tympanus.net/codrops or www.elmastudio.de).

New dynamic layout feature “Separate categories”

The feature support the option 'Number of posts per seperated categories'.

The feature support the option ‘Number of posts per seperated categories’.

With the Same Category Posts widget it is possible to get multi category selection with a new dynamic layout feature: “Separate categories”. Here it’s possible to separate all assigned categories for the post which is shown on a WordPress single page. And so we call it layout feature. (Hint: The widget gets all assigned categories if or if not checkt this new option.)

 

With one new number option: “Number of posts per separated categories” you can set the maximum number of post beneath a categorie headline. Which extends the existing parameters “Number of posts to show (overall)”. This option  remains unchanged and gets the overall counted posts.

 

Why it is called dynamic?

Its simple answer: Because it depends on the filter option order by ‘date’, ‘name’, ‘number of comments’, etc. And it goes further, the widget (shows and seperates) posts from this categories which the current post assigned to. If each shown post have other assigned categories, the widget will show for each post other categoies.

 

For example post ‘doostang’ is in the categories CARS and HOUSES and post ‘hipmunk’ is in the categories CARS, TECHNOLOGY and WEBTWO only one shown category is the the same. The other are dynamiclly and different.

 

'Seperate categories' is similar to a order by category.

‘Seperate categories’ is similar to a order by category.

If you want to picture latest news and your post begin date is important for your readers, so it’s better you don’t use ‘Separate categories’. ‘Separate categories’ may cause that not the newes post is on top. But have you many posts to show and you can hide your thumbnail. Order by categories with the feature ‘Separeate categories’ can be very helpful to show a huge number of posts and get a very clearly layout.

 

The idea for this option comes from Aecorn on WordPress.org. He gives the request for this layout because his site and widget area use a lot of post to show. Create idea – thank you Aecorn.

He has given us a 5-star rating on wordpress.org for the implementation of his option.

 

5-star rating on wordpress.org

5-star rating on wordpress.org.

 

 

 

 

 

 

 

 

 

 

 

 

Downlaod link: https://wordpress.org/plugins/same-category-posts


Related posts: