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…)
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…)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.
I use a sequence-based version numbering for my plugins, based on change significance.
Here are further details of my specific methods…
(more…)
It’s been a few months since my site was being constantly hacked over a number of weeks. Enough time, I think, to discuss what happened without compromising my site security to them again (it’s been months since the last attack so I’m assuming they’ve lost interest now).
(more…)