Category: WordPress

Plugin developer, Core contributor and support volunteer. Yeah, I’m a WordPress fan!

  • Ironic WPScan Vulnerability Database Website Message

    Ironic WPScan Vulnerability Database Website Message

    The irony of getting this message when attempting to visit the WPScan Vulnerability Database site is not lost on me 😉

    privacy-error
  • How to work out the current state of a plugin

    How to work out the current state of a plugin

    It’s a rare instance where you need to know, from your own code, the state of a plugin but, for instance, this may be something particularly relevant to a theme.

    The usual way is to use the PHP command functions_exists to check whether a specific function is present. Of course, hard-coding this is probably not the best idea as function names change. Instead the WordPress function is_plugin_active is a better solution and you only need to specify the (non-changing) plugin slug for this to work.

    Now, this will tell you if the plugin is active but what if you also want to know if it’s installed or not?

    (more…)
  • Why WordPress developers often get the is_admin function wrong

    Why WordPress developers often get the is_admin function wrong

    Let me first say that I’m guilty. For “performance reasons” I’m always careful to only run functions in their appropriate area of WordPress – so, something only used in the admin area will be checked via the use of is_admin. Only if this is true will I then run that code. It makes sense.

    But for plugins there is no performance improvement.

    (more…)
  • And here’s how NOT to do WordPress Support…

    And here’s how NOT to do WordPress Support…

    Many companies that sell premium WordPress Themes will make “Lite” versions available, free of charge, via WordPress.org. It gets the theme known, gives them a promotional springboard and allows people to try many of the theme’s features. For me too it also gives you an opportunity to see what their support is like.

    (more…)
  • New Domain for WordPress Development

    New Domain for WordPress Development

    Until now I’ve run various test WordPress sites as sub-folders to this domain. However, with potentially insecure sites sitting in the same folder structure as this site this adds an understandable security risk. I’ve therefore purchased a secondary domain (MyWPPlug.in) from which I will now perform all development and testing.

    Heading to any root URL for that domain will get you forwarded to my plugin portfolio page on this site. However, I have sub-folders for my test sites (which I don’t publicise) and bug tracking (I’ve also setup a redirect so my links to the old bug-tracking URL will forward to the new one – in time, I’ll correct these URLs), which now ensures that the only thing installed on this domain is the single WordPress installation.