I thought I had done such a great job tightening up things and then seemed to get hit with some repetitive trackback spam notifications.  Since the notifications are coming from one of MY websites, they don’t get marked easily as spam.

A few minutes of googling and a timely post at question-defence.com, published a few days ago pin pointed the problem (Many thanks to google for thier quick search index updating!.. remember the old days?)

Ping status =  ‘open’

Many existing posts still had their ping status set to open.  So to stop trackback spam in it’s tracks (ha! lqtm), take action as follows:

Future posts:

1. Go to WordPress settings > Discussions >
2. untick “Allow Link Notifications From Other Blogs”

Past Posts:

1. Hop into your phpmyadmin
2. Find your posts table, note the name with your sites prefix
3. Goto the SQL view, type in

update  prefix-posts set ping_status = 'closed';

and you are done.  All posts and custom post types now set to NOT accept trackbacks.

Related posts:

1. Getting a list of subscribers Trial, Paid, Expired or Active members For the list of members with their status etc if the list is not...

• a link to the add new page
• preferably with suggested title and content

I wondered???, I googled, I browsed some of the WordPress code and found naught, nought, null, or at least nothing obvious…

and then I just tried it.

‘Content’ was easy I had a few attempts at ‘title’, the found ‘post_title’ worked.

Hooray! A small thing but quite satisfying and of course I felt a need to share….

The Result

Seeing is believing

The php code:

echo '<a title="'
.__('Create a calendar page','amr-ical-events-list')
.'" href="'.admin_url('post-new.php?post_type=page&amp;content=[iCal http://youricsurl.ics]&amp;post_title='
.__('Calendar','amr-ical-events-list')).'">'
__('Add new') // use wp translation
.'</a>';

Link from settings or plugin page

Related posts:

1. Shortcode a widget in a page or post Shortcodize a widget - Use any widget in a shortcode in a page or post...
2. Submenu, Page, slug, attached media confusion I had a really odd one today.  A client had added text to a submenu page that was either empty...
3. Category specific css to achieve a print “cover page” css look For a school’s online newsletter we wanted the “photo of the week” category to present differently from other posts. Ideally...

Faster Phidus, FASTER! - original photo by mauropm

There’s a good post over at webmasterworld with advice on how to speed up WordPress when using it as a cms, plus a few other tips.  Also if you are using a theme that came packaged with timthumb, read this and take action to avoid being hacked.

There was no way to  boomark the individual useful comment  that I could find, so I ‘ve taken the liberty of summarising here, with a link to the original complete conversation – print version here.
1 – Get a dedicated server. The slowdown on a shared or VPS is at the database. {They} used to run the W3 cache plugin, but now only use the “Force GZip” plugin.

1A – Keep your database clean with an optimizer type plugin (or do it yourself) that weekly, backs it up than cleans up scuttle from the database.

2 – Security – Never load more plugins that you need to run the site, and always limit access to your wp-admin directory within the htaccess. We {They} deny all but 3-4 IP addresses from accessing the admin sections.

2A – Delete all unused themes and plugins… Even if they aren’t active!

3 – Using the wp-config.php file, turn off post revision tracking.

4 – If you are using WP as a CMS, use it as a CMS! We {They} use pages for 75-80% of our landing page content, and only use the post features to compliment our pages. Use .html as a file extension on pages and posts… and take GREAT care to make sure the index taxonomy is correct from page to category of post when used.

5 – Tags and Categories are always noindexed for us. The PAGES are our primary landing areas, and the tags and categories ultimately support them.

6 – Clean up your themes to the N’th degree. We use a speed tool that waterfalls the http requests so you can really clean it at the file level.

7 – Always use sitemaps, both xml and reader sitemaps.

8 – Favorite admin plugin, Ozh Horizontal Admin Menu plugin by Ozh. It relocates the admin menu to the top of the site and frees up much needed horizontal space for writing.

Related posts:

1. Why CMS? CMS stands for Content Management System. The good CMS’s now are so good, that in my view no-one should be...
2. Improve your wordpress web’s security – Prevention Easy improvements for the non-technical: are you displaying your username for all the hackers to see? Go to your wordpress...
3. WordPress user training Web Designers sometimes neglect to factor in the training and hand holding required to get website owners comfortable with managing...

The amazing pluggable machine - photo by lukasWP

Pluggable functions are functions that can be overridden by others.  The key is which is defined first.  So to make one your plugin’s functions pluggable one should define it  as late as possible.  So others can get in first of course, but not so late that your plugin tries to use it before it is defined.

Understanding the sequence of wordpress actions is important.

To make your plugin function pluggable by a theme or another plugin it needs to be defined AFTER the themes and the other plugins. So if your functions are mainly to do with output, you could move them as far back as the ‘wp’ action say.

In your main plugin file:

add_action ('wp','amr_load_pluggables', 10);    //move it later and a low priority

function amr_load_pluggables() {
    require_once('amr-pluggable.php');
}

The Pluggable Functions

Each pluggable function must test that it has not already been defined

if (!function_exists( 'the_pluggable_function')) {
    the_pluggable_function($parameters) {
    // the code
    }
}

The Override Function

The coder doing the overwriting  (ie plugging the pluggable function ) then just defines the function normally in their own plugin, or in their themes functions.php.  All they have to do is not bury it inside an action that executes AFTER the ‘wp’ action (or the action that loads the pluggable files).

Oh and it would be a good idea to fully understand where / when that pluggable function gets called and what it is supposed to do, what values to return etc.  You do not want to cause nasty side effects.  Looking at the code of the pluggable function is a good place to start.

Conditional Override

If they wanted to only override under certain circumstances, EG:  If you want to override ONLY on certain post types and only if certain conditions are met on the single view, then one could do

add_action('wp', 'define_my_override_function', 1) {

// using wp action as well as we need the post query et to have been done already, but a higher priority so will execute before the pluggable function load.

}

function define_my_override_function() {
global $post;

    if (is_single() and ($post->post_type === 'event') and (whatever other criterai)) {
 // then overwrite the pluggable, requires the pluggable loading to be later in the wp action sequence, say on action 'wp' late priority

        function the_pluggable_function($parameters) {

        // your code here

        }
     }
}

Related posts:

1. Plugin does not have valid header.. still activates Wordpress invalid plugin header problems when activating uploaded zip files...
2. Events Plugin The paid version The amr-events plugin is available here (my main site).  Please register or if already a member, please...

Lower case love... by gazeronly

If you have been banging your head against the proverbial brickwall trying to debug a intermittment post_meta bug then this may help.

I googled all aspects, but did not find any post to shed light.  Eventually figured it out….

Put simply:

• get_post_meta() is case sensitive on the meta-key

BUT

• update_post_meta is NOT case sensitive

Thus If there is a pre-existing meta record with a key in UPPERCASE, then one can

1. issue an update for a lowercase key that will
2. update the UPPERCASE key, and not create a lower case record. (Usually update will ‘add’ if no record exists).

Delete_post_meta() has the same behaviour – you can try to delete a lowercase key, but the uppercase version will get deleted (too?)

Then of course when you try to fetch with your same lwoercase key that you did the update with, the fetch will fail as it does not exist – only the uppercase key exists.

That was fun trying to debug……

See trac ticket raised for details or progress.

Mysql db collation

It seems it has a lot to do with the mysql db collation being used.  The default in many db setups is a _ci (case insensitive one) – they are faster and give more ‘natural’ sort orders, although that very much depends on the language you are using.

The get_post_meta behaves differently apparently because wordpress caches the data so one is not necessarily querying the database.

If you are keen to know more, see

• Mysql collation issues, and
• Hakre’s notes on wordpress-database-charset-and-collation-configuration

Related posts:

1. Upgrading to Mysql5 – more strange characters An upgrade of a wordpress site’s Database from Mysql 4 to Mysql 5 gave some surprising results – some strange...
2. Permalinks, custom post types and taxonomies, conflicts How to avoid clash, conflict and 404 problems with permalinks, custom post types and taxonomies....
3. Initial content for a new page or post – wordpress pleasant surprise How to create a link to the add new page or post with default starting content...

• Rules for dealing with a new plugin, or theme or an upgrade
• Debugging the plugin or theme on your site
• Reporting a problem – the rules of engagement
• Debugging for plugin developers

Don't sweat blood over a bug

Rules for dealing with a  new plugin, or theme or an upgrade:

• READ the instructions, okay some plugins can be intuitive, but some may need a crucial step.  Go back and check that you have not missed something
  • Check the readme.txt (or the WordPress.org site – shoudl be the same)
  • Check the plugins own site
  • Check the settings.
    • I like to code my plugin in such a way that you do not have to even look at the settings, it should still work with a default setup, but not everyone does – some people do not even check the settings.  Some developers put their settings in strange places – I found one whose settings were reached off the plugin listing line, but only when you hovered over the plugin line!
    • I also tend to put some explanatory text, or links to explanations in the settings area near the relevant area
• READ the changelog.  If the author is diligent, there should be detailed description of the changes.  If there is no detailed description, assume anything could have changed.  If it says ANYTHING about a database change, you definitely need to
  • switch maintenance mode on – a number of plugins can do this for you
  • do a backup that includes the database, and know how to restore it!
• If the plugin is crucial, check the forums BEFORE you upgrade. If you are really unlucky you may be the first to flush out a bug or clash, but the odds are someone will have got there before you.
• Test the new plugin, theme or upgrade on a test server first, with other crucial plugins active. NEVER ever apply it to your live site straight off, even if you trust the developer.  There are infinite combinations of circumstances and your site may just find one that breaks the plugin.
• Have a backup that YOU know how to restore.   Yes it seems it is  not obvious to all, but it is  no good having a backup if you have no idea how to use it.  Hopefully your host has a simple option for you – be aware of lead times if you need their input.
• Do not start late at night.  If you hit a problem at past 10pm at night, stop, reverse, go to bed. (Yes I’m a mother, but I also know when I am not  being effective.  I do not like to waste my time.)

Only break these rules if…

you are able to cope with the consequences of  a problem

1. simple actions you may need to do could be  to get the prior version of the code and ftp that over the ‘new’ version
2. worst may be having to reverse an updated database (and no backup),
3. or have the plugin deactivated for a while.

Debugging the plugin or theme on your site

If it is a simple, obvious problem or visible error, a “fatal error”, “warning” or “notice”, then an internet search, or forum search both at wp and at a plugin own site,  using the words but removing anything that relates to your site can be very useful and give you a quick sense of what may be wrong. It may educate about the WordPress functionality is use.

Common things are :

• permalinks needing flushing with custom post types and taxonomies,
• missing a wp function  due to an old wp install,
• function or class naming clash with a theme or another plugin
• etc

Not a simple, obvious problem, or plugin developer cannot recreate the problem?

If it is not a simple, obvious problem or a visible error, then you may need to do one of the following. Both  are looking for a clash or trying to isolate the circumstances that cause the problem

1. Go backwards – Either start with your test server and switch off  plugins, one by one,  testing the plugin in question after each step, or
2. Start at the beginning and go forwards – start with a clean install and add in the plugins and themes one by one

This may seem cumbersome, but sometimes it is the only way.  It can also be highly informative about the plugins you are using and/or the theme.  before you all of this, though check first:

• Is it an old WordPress? If yes, try on a new clean install with latest
• Did you just upgrade to latest WordPress and was it just released ?  the plugin may not yet be compatible with something that changed in WordPress.
• It is the php version?  the plugin should work on the ‘most’ common php version, which at time of writing is 5.2  See http://wordpress.org/about/stats/.  If your php is old or very new, this may be it. You need to be able to tell the developer what php you are using.

Be methodical

Be careful that you are doing the necessary steps to adequately test at each step, so you do not waste your time. Do you need

• refresh the browser and /or clear the cache’
• logout / login (depends on the functionality of the plugin)

The objective

You want to be able to honestly tell the developer that you have tested the plugin on a

• clean (non customised) WordPress install, preferably with the latest WordPress version
  
• with the current default theme (eg: twentyten) and
• no other plugins active (or maybe only standard plugins active)

It is highly unlikely that you will get  to this point without  finding some thing out. Examples:

• a clash with a theme or other plugin
• if it worked on a clean new wp install, it may be that your database or your WordPress is corrupted. Scary, does happen.  Sometimes even a clean WordPress install gets corrupted and one has to “install” it twice.  I’ve seen people describe this.

Reporting a problem – the rules of engagement

• Do NOT struggle for multiple hours, getting more frustrated.  Take a tea break, go for a walk, get a nights sleep.  Check for environment changes… i’ve seen people curse WordPress and a developer only to shamefacedly report back after a day or so to report why it was actually something that had happened on their side.
• Report early to the plugin forum – you may be highlighting something new, the sooner the developer knows, the quicker they can address it.  Use some good judgement about how early to flag an error, but do continue with the debug steps.
• BUT DO not report without doing some of your own debugging.  Your situation may be unique.
• Be specific – report  with as much information as possible .   “It does not work” is not helpful to anyone.  Clearly it will have worked for some people or most likely many. The more info you can provide, the more likely you will get quick resolution.
• Unless you have a support contract with a guaranteed response time, do not realistically expect better than a 48 hour to 1 week turnaround, or even one at all in the case of free plugins or ones that explicitly exclude guaranteed support. It doesn’t mean that they do not support it, it just means they are unable to guarantee it – this is quite reasonable – particularly if the the developers are a small organisation or an individual. For example most of you know that  I usually get to a question within hours, but cannot guarantee that, so I explicitly exclude guaranteed support in my terms.
• When reporting, have good manners and remember timezones.  You never know what is happening in someone else world (births, deaths, tsunamis, earthquakes, snake bites, sick children, broken fibre optic undersea cables, loss of power, loss of internet…) .

Debugging for plugin developers

Most of the above applies to you too! however there is more. Mostly I recommend

• always working with php and mysql  ALL errors, warnings, notices etc switched on.
• test on multiple platforms and browsers
• before releasing an upgrade, test on existing (upgrade) and one new clean install

For more details, see

• http://andrewnacin.com/2010/04/23/5-ways-to-debug-wordpress/ (a key wp developer)
• http://fuelyourcoding.com/simple-debugging-with-wordpress/
• http://wordpress.org/extend/plugins/search.php?q=debug – some plugins that may help. Personally I sue my own little dummy debug plugin that switched all errors one and off as I activate and deactivate it.

It's tempting.. but should you?

Judge the risk/benefit tradeoff before you click that one step upgrade all – you are the one responsible!

Related posts:

1. Looks good, dived in with a developers license A record or informal guide of the installation process of the Your Members wordpress membership plugin....
2. wordpress user reporting plugin has a new site The amr wordpress users plugin for flexible user reporting now has it’s own site:...

Unique permalink URLS

However you setup your permalinks, custom post types and taxonomies, you need to ensure that the resulting permalink urls will be unique so that the system can identify the post or custom post content correctly and the url’s generated do not conflict.  Else the first rule to fire will determine what is returned.

I first encountered this problem way before post types and taxonomies when a client had an image named the same as a post, with some weird results in certain situations – took me a while to figure that out!

To demonstrate the problem, I

1. defined my permalink structure using /%category%/%postname%/
2. created a category called event and
3. activated my event plugin that has a ‘event’ custom post type.
4. I then created two posts called the same “CPT 99999″

A standard post in a category called event

When I click down from the standard post category archive instead of getting the standard post, I get the custom post type event with the same name.  There are two rules leading to/from the same url.  The first will win.

Clicking down on the standard post takes me to the custom post type event

Solutions

1. for new systems, or where you can still change the permalink structure:

Make sure that you have something that will guarantee uniqueness in your permalink structure.  Since I usually do not feel the need to have the category name in my permalinks, I use /%post_id%/%postname%/ which will always give me a unique url ! – and since my audience is mostly technical, I am not concerned about the post id in the url.

2. for existing systems with many posts

Essentially you must ensure that each url somehow generates a unique url – this may mean changing some slugs somewhere (posts, custom, taxonomies or categories)

Consider also reversed words

I had the sense in my taxonomy code for the amr-events plugin to check for wordpress “reserved” words and prevent prevent creation of a taxonomy that uses them.  This sort of  checking may need to go further, although as pointed out  here in response to this question, it is not much different from the risk of plugin function names or input form names overlapping with reserved words.  Plugin, theme authors and web developers need  to bear these risks in mind.

More information:

• http://codex.wordpress.org/Using_Permalinks#Choosing_your_permalink_structure and
• http://ottopress.com/2010/category-in-permalinks-considered-harmful/
• http://lists.automattic.com/pipermail/wp-testers/2010-May/013010.html
• http://shibashake.com/wordpress-theme/custom-post-type-permalinks-part-2#conflict

Key points extracted from above:

• Custom Post Types have a URL of /slug/postname.   The “with_front” option lets you make that into /something/slug/postname, if you happen to have a post permalink structure with a prefix on it (like /text/%postname% or something)
• Don’t setup a permalink structure that will clash with the archive structure. e.g. say you only had one post a day and wanted to use: %year%%monthnum%%day%, links so generated will be interpreted as the archive of all posts for that day.
• Add taxonomies slowly, one by one – verify that permalinks continue to work each step of the way.
• For performance reasons, it is not a good idea to start your permalink structure with the category, tag, author, or postname fields
• Google looks at the words in the URLs of your posts and uses them as factor in determining relevance, and therefore he (Matt) advises using %postname% in your WordPress permalinks. He doesn’t advise using ONLY %postname%.   There’s nothing wrong with using postname. Just use something else at the beginning of the string.
• There is a LOT of benefit of having postname in url if you are using adsense. Try this: Take any new domain timbuktu.com and if you have a post for which the url is timbuktu.com?p=7 you will get junk ads.   Now try timbuktu.com/car-insurance-save-on-car-insurance – You will get beautiful insurance ads.

Related posts:

1. wp_dropdown_categories with taxonomies Fix - custom drop down categories with taxonomy...
2. WordPress Installation Checklist Installation Cheatsheet for wp 3.0 up.  WordPress has improved so much, many of the checklists on the web include unnecessary...
3. Shortcode a widget in a page or post Shortcodize a widget - Use any widget in a shortcode in a page or post...

Google The+plugin+does+not+have+a+valid+header and you will find a lot, most of them will tell you that

1. Mostly it is the folder structure which suits ftp’ers but does not suit zip installers
2. sometimes  there is a minor problem in the plugin header
3. sometimes  it is a bug in the way that the zip installer works and you will find that even though you have that invalid header message, the plugin will have activated or you will be able to activate it from the inactive plugins list

Use FTP if you can

The wordpress zip install is finicky – it does not cope with certain situations that I expect it to.  If you can at all use ftp instead, please do.  Not only will you have a better view of what is going on and your websites folder structure, you will also avoid some problems.

Handling a zip file – Zipped at folder or file level?

• If the plugin zip file has a version number (which is a good practise so one knows which file is which, the zip installer will install it into a version folder… and NOT upgrade – you will end up with two versions.
• Unzip or explore the zip file first – if it is all neatly in a folder, you can ftp that folder up sweetly.  Nice!
• If you insist on using the zip install, you will have to unzip, and then rezip at the lower level, without the top folder in order to use the zip installer

Still getting an invalid header message (even in 3.0.1)?

• Somehow once you have mucked around trying the zip  install with folders etc, WordPress has stored the fact that it does not like the plugin, and even if you have now ftp’ed a copy up it remembers that it had a problem.  I was getting really frustrated and had double checked my header endlessly.  Then I found this little comment about ignoring the message, heading back, back, back to the plugin list.
• Go to inactive plugins, refresh if you have to, activate.
• In one instance, after being told there was an invalid header and not being to see it in the inactive list, I found that it had activated after all.

I have had an attempt at describing what seems to be the cause possible corrective action.  See

http://core.trac.wordpress.org/ticket/15191

Hope that helps!

Related posts:

1. Debug a wordpress plugin or theme – for non-developers For non-developers - how to debug a plugin or theme, or at least provide some better information about why it...
2. Moving wordpress Step by Step Guide to Moving the wordpress admin code and optionally relocating your content directory. This facilitates sharing of...
3. How to give your plugin pluggable functions How to give your plugin pluggable functions and how to override a pluggable function by defining your own....

If you’d like it to show times in your wordpress site timezone, here is a modified version.    Oh – just realised – if you are still using the old gmt offset, please change to timezone string to use this (or add code to use offset).  Remember offset do NOT cope with daylight saving changes, so I standardise on setting the city timezone in all the webs I do.

Update: the zip file now also includes modificiation which checks to see if an action of the same name has been added (for developers working too late!). Remember: Cron Jobs scheduled but not executing??? You need to add the action for the cron job:

add_action(‘my_action’,'my_function’);

Wokamoto, you are welcome to take changes and add to your plugin – It’s only a few lines of code, but scattered through the plugin.

Screenshot of modified wordpress cron dashboard with action check

Related posts:

1. Timezones and offsets in wordpress Writing a plugin that requires a correct timezone object ?  Not sure how to deal with wordpress installations that may...
2. Timezones, WordPress, Ical, Php…. What a lot of fun this can be (not!) Your Ical file may have a timezone specified, the event may...
3. WordPress Installation Checklist Installation Cheatsheet for wp 3.0 up.  WordPress has improved so much, many of the checklists on the web include unnecessary...

Attached is a sample file.  The code is based on code from somewhere else, but I forget where.  I had to do even more funky things like swop the default url out for an “events” url so that the query would deliver event posts ordered by event instance date rather than published date.  See that in action at icalevents test site

I have stripped that back, so I think the attached file is all you need now.  I am using it for another private plugin which is adding filtering to the manage posts admin page and it seems to work ok.

Zipped file: amr-custom-dropdown-taxonomy

Note: the taxonomy being used here is called “plugin_categories” – it NOT using categories.

Custom filter

The filtered result

the url

Related posts:

1. Permalinks, custom post types and taxonomies, conflicts How to avoid clash, conflict and 404 problems with permalinks, custom post types and taxonomies....
2. How to give your plugin pluggable functions How to give your plugin pluggable functions and how to override a pluggable function by defining your own....
3. Why I code without javascript if i can Developing without javascript - why?...