As you might already know, Movable Type beats WordPress when it comes to integrated plugins, that means those plugins get better support than 3rd party plugins.

Moving further with the story Movable Type 4.0 provided (as they claim “for the first time”) framework for developers, so they could

define their own custom asset types as illustrated through the Media Manager and Podcasting plugins for Movable Type.

Well in Movable Type 4.1 (which is still in BETA) administrators and authors can more easly edit, tag and orginize the assets within their Movable Type install. From now on, you can:

• Filter Assets by Type - you can simply filter your assets by Flickr images, YouTube videos… well you got the point.
• One Click Previews - provides small and zoom-able thumbnails for all the assets in a list.
• Asset Auditing - from the details screen you can view which and where assets are used, so you can for example: update them sitewide.
• Edit Assets - tag it, rename it, change description… you know - edit them

It will really make our life easier when it comes out of BETA.

Well, Magento might not be as popular as oscommerce and zen-cart, but it really worths trying, Magento got Web 2.0 look, packed with features (such as Tags and product comparison) and develops rapidly, did I mentioned it’s also free?

They reached 100 000 downloads today, which really is something… and they are very thankfull indeed:

This is an incredible achievement that could not have happened without the support of the community. We are very grateful and look forward to what’s shaping out to be an exciting 2008 for eCommerce.

Happy New Year everyone!

What to say? Good luck Magento.

WordPress-ians are calling for immediate attention, today they fixed bugs that could:

• Show bad guys your draft posts
• give away information about your database table structure and limits (to the same bad guys)
• give away some information in the XML-RPC and APP implementations

I do not know who can ever use those bugs to do some bad things with our blogs, but well - it’s better to update your blog up to 2.3.2.

There is some bonus as well, now we can set a custom DB error page, for that we should place our custom template at wp-content/db-error.php and if WordPress has a problem connecting to blog’s database, this page will displayed rather than the default error message - neat ha?

This is actually first post on newborn blog, let me quickly round-up what we are going to WRC (write-read-comment) here and move on to actuall blogging.

I am deploying, developing, reviewing, installing and doing other things with php+mysql scripts since 1998, that means I got about 10 years of experience in this field.

So, what I will try on this blog is to deploy all new releases, bug fixes, updates, etc. and test it, so you can read results and decide what to do. Provide reviews so you can choose wisely which web-software solution better suits your needs.

I am always more than happy to ITR (install-test-review) any new web-script start-up, so if you would like to read in-depth review on any script just contact me.

Best wishes - Gio.