Updates for CMS Tree Page View brings multi post adding and integration with regular post overview screen

The last updates for my pretty popular page management plugin has brought some pretty cool and useful functions that I thought were worth noticing:

Add multiple pages at once

This is a feature I really like and use a lot myself, especially when setting up the page structure for a new site. It’s easy to add several pages at once: just mouse over a page where you want to add new post after or inside and then click any of the links “after” or “inside” and just start typing – new fields for additional pages are added automatically.


Integration with regular post overview screen

This is a perhaps a small change, but a pretty important one anyway: CMS Tree Page View now let you add an additional icon to the overview page for any post type and clicking that icon takes you to the tree view for that post type. I personally like this feature because it makes CMS Tree Page View so very discrete: all you need to see of this plugin is a tiny icon – no menu items or something like that that may grab attention. But very accessible when you do need it.


That’s it! Two new cool features that I like. Lots of other things have been changed and fixed too lately. Please check out the change log for more information about other recent changes. And as usual, if you happen to like the plugin I don’t say no to a donation, and if you need help then visit the support forum.

Give my WordPress Plugins some Review ♥

A new and nice feature over at the WordPress plugin directory is that you starting from this week finally can give your favorite plugin a review. Since I have a lot of plugins I would reeeeealy like to have some review. So if you use my plugins (and well.. like them!) please head over tot the plugin directory right away and give them a good and honest review.

My plugins are, in case you forgot:

WordPress snippet: Wrap teaser content with a div

This is a nice little snippet of code I wrote today for my domain simple-fields.com.

I wanted to be able to style to content before the “More tag”, using it as a teaser on a page. This solution wraps all content before the more-tag with a div with the class .entry-content-teaser, making it super simple to style it, like adding font-weight: bold to it.

Check out the code and copy, paste, fork, whatever:

Simple Fields users – please help me test the new version

Lately I have been working hard on the next version of Simple Fields – my Custom Fields plugin for WordPress. Some of the new great features are:

  • Support for Custom Field Types/Field Type extensions. This means that you (or anyone else! 🙂 can write your own plugins for Simple Fields that adds new field types. Want a field type that let the user select a date range? Well just write it then! Or hire someone to do it. The main thing is that with this function Simple Fields is endless extendable!
  • New functions for registering field groups and fields and post connectors using plain PHP. Great news for theme developers beacuse now you can add pre-defined sets of fields for your users. No need to add fieldgroups or post connectors manually.
  • Support for slugs: each field you add now have a slug (that you decide) that you can use to access that field. Very useful together with the next feature:
  • New and better/easier functions for getting the saved values for a post: simple_fields_value(“field_slug”) and simple_fields_values(“field_slug_1, field_slug_2”). No more messing with fieldgroup and field IDs.
  • Actions and filters are added at many places so developers can modify parts of Simple Fields behavior.

The above features surely are great, but since I am just one person It’s difficult to spot possible bugs.  So this is what I need you for: please help me find the bugs in the upcoming version of Simple Fields!

You can find the latest version of the plugin at Simple Fields GitHub project page. Please download it from there (or clone the repository, whatever suits you best) and use the plugin on an existing or new site and then report any bugs tot the GitHub project page or directly to me.

Thanks a lot for your help!

Oh – and don’t forget to backup your database first. You know… just in case  🙂