Archive for the 'WordPress' Category

The new WordPress 2.9 Carmen is available from the official download page (click here).
Thanks a lot to all the WordPress Team and to all contributors: you’ve done a great work as always!

The coolest new stuff from a user point of view is:
Read the rest of this entry »

I’m glad to find that WordPress had won the Overall Best Open Source CMS Award (found it in my Dashboard today) and it was also named first runner-up in the Best Open Source PHP CMS Category.

WP is a very powerful and flexible platform and it really deserves both Awards for sure!

I was very excited last week to learn that WordPress has been awarded the Overall Best Open Source CMS Award in the 2009 Open Source CMS Awards. This is a landmark for us, as it is the first time we’ve won this award, and it marks a shift in the public perception of WordPress, from blog software to full-featured CMS. No small contest, the Open Source CMS Awards received over 12,000 nominations and more than 23,000 votes across five categories.
… … …
In addition to winning in the Overall Best Open Source CMS category, WordPress was named first runner-up in the Best Open Source PHP CMS category.

Read the rest of this entry »

The last WordPress versions has introduced the automatic insertion of Generator meta tag in the HTML HEAD.
So what is the problem?
The Generator meta tag reports both the platform name and the software version; an example is “WordPress 2.8.5“. I don’t know why they decided to expose the version number, a so deprecated and potentially harmful information, directly to everybody “eyes” cos this precious information could facilitate a potential hacking tactic based on specific revision problems.

So… is the Generator meta tag bad?
Read the rest of this entry »

Read below for the simple solution!

Example of embedded WordPress standard FLV movie player.

Original clip is 400 x 300 – Displayed here at 500 x 400

Is WordPress able to play FLV movies?
Read the rest of this entry »

The Disable Revisions and Autosave plugins are WordPress 2.8 compatible.

disable-autosave.zip – Disable Autosave function
disable-revisions.zip – Disable Revisions function
disable-revisions-and-autosave.zip – Disable Revisions and Autosave at the same time.

I’ve tested them during the last days and they work flawlessly as expected.

Read the full post here:  Disable Revisions and Autosave plugins

The Disable Revisions and Autosave plugins are WordPress 2.7 compatible.

disable-autosave.zip (Right Click – Save As) – Disable Autosave function
disable-revisions.zip (Right Click – Save As) – Disable Revisions function
disable-revisions-and-autosave.zip (Right Click – Save As) – Disable Revisions and Autosave at the same time.

I’ve tested them during the last week and they work flawlessly as expected.

Edit June 16, 2009 – The plugins are WordPress 2.8 compatible.

---

I’ve already reported about WordPress revisions and autosave problem yesterday.

I was thinking about a quite different solution and then I found that it’s really trivial to prepare three WordPress plugins that can disable Revisions, Autosave or both of them at the same time.

disable-autosave.zip (Right Click – Save As) – Disable Autosave function
disable-revisions.zip (Right Click – Save As) – Disable Revisions function
disable-revisions-and-autosave.zip (Right Click – Save As) – Disable Revisions and Autosave at the same time.

Using a plugin is far faster and easier than editing the wp-config file; plus everyone can Activate or Deactive them whenever is needed.
I’ve got very limited time to test them, but I’m actually using the “disable-revisions-and-autosave” on this blog and as far as I can say it works flawlessly.
Every comment or hint is very welcome!

The disabling Autosave plugin was already online yesterday, but I’ve slightly modify it to report the original code author.

EDIT 11 Sept. 2008
Some comments are not visible (removed) due to DB problems.
During the last weeks an hacking attempt led against the ISP on which Exper Chaotic Flow is currently running forced me to switch to a temporary server which trashed the last automatic DB recovers.
I’ll updated this post’s comments by hand as soon as I’ll have some spare time; some of the vanished ones are still there on my local backup.
Sorry for the setback.

Edit 25 July 2008
I’ve prepared three plugins that can disable Revisions, Autosave or both of them at the same time.
Access here: Disable Revisions and Autosave plugins

---

I’ve recently updated my blog to the last WordPress 2.6 version.
The new version is very bold and I want generally suggest everyone to upgrade to it.

But I’ve also got to say that all the new version goods are mined by a major new introduced feature, a big problem to me and some other users out there: I’m talking about the Revisions and the new AutoSave function.
Revisions simply save the posts many times: WP will add a new row in the DB every time an user change a post; this could be good when the blog is maintained by different editors, cos they can track the various versions/revisions of every post, but it’s actually totally resources wasting to all the single editors ones.
AutoSave now create a second copy of the post that is stored and used to keep the post up-to-date when a subsequent AutoSave is executed on the same one. This is quite annoying too. I never liked much the AutoSave and the new implementation is even worser to me.

I’ve started roaming around the net looking for a solution.
I’ve found a couple of workarounds that can completely solve the problem when used at the same time.

STEP 1 – by me

I’ve found that clearing all the cookies relative to your Wp’s domain installation is always a good start when you make an update.
This is good too on 2.6 especially if you’re going to use the new SSL ones.

STEP 2 – Stop the Revisions scheme – Lester Chan article

To turn off the revisions edit the wp-config file adding this following code after the DB settings lines.

define(‘WP_POST_REVISIONS’, false);

You can also delete all post revisions by running this query in phpMyAdmin:
Be sure to backup your database first before performing any queries in phpMyAdmin.

DELETE FROM wp_posts WHERE post_type = ‘revision’;

STEP 3 – Stop the AutoSave – Untwisted Vortex article

Lester reports that AutoSave doesn’t create a revision.
This is not completely true cos some users (I’m on the same boat) have reported that one revision is created by AutoSave too; it’s actually not clear if this is a behavior resulting from a WP’s bug/problem or a particular provider’s systems configuration.

The solution is to create a plugin that stops the AutoSave function.

<?php
/*
Plugin Name: Disable Autosave
*/
function disable_autosave() {
wp_deregister_script('autosave');
}
add_action( 'wp_print_scripts', 'disable_autosave' );
?>

Select the above reported code, copy it and paste it into a new blank text document.
Save it as “disable-autosave.php”, upload it to the WP’s plugins directory and then activate the plugin.

I’ve also prepared the plugin version here: disable-autosave.zip (Right Click, Save As)

I’ve recently updated my WordPress install form an old unsupported development branch to the new one and found that the Category listing is now printed in Alphabetical order instead of the old ID based old method.

I have to say that I personally prefer the old ID sorting mode, it’s better suited to my own blog needing, so I browsed the codex and the forum to find a solution to put it back to the previous mode.
I found a couple of plugins that can do the trick but they’re not the way I was looking for.
Then I found this a very simple method by MichaelH; it only needs a small change editing one of the WordPress files and it works like a charm on every versions, as far as I can say.

Here it is:
open the “category-template.php” file
change
usort($categories, '_usort_terms_by_name');
to
usort($categories, '_usort_terms_by_ID');

The complete article is available here: the_category sort by ID

You can find that your own Blog is suffering some Feeds problems after updating to a newer WordPress version.
I’ve been able to resolve them, as far as I know, using this simple procedure.

How to fix it

• don’t insert withe/empty lines at the start end of confing and functions files; functions is a Theme specific file; check if you have one in your own Theme folder.
• go to all plugins that have an option-page and update them saving again their own settings.
• go to Settings and save again every section.
• refresh Permalinks.

Hope it helps!