On the Toptal.com site author Donald Mudenge has written up a post that wants to help debunk the top 5 WordPress myths that are still floating around about this popular and common tool.

In the early days, people used WordPress only as a blogging tool. However, today WordPress covers more than 50 percent of the market share for CMSs, supporting nearly 60 million websites worldwide.

As a commonly used platform for building websites and other online applications, misconceptions have spread like a forest fire, keeping people away from WordPress. In this article, I outline and explain the five most common WordPress taboos and myths, clarify them and offer solutions on how to overcome them.

The five myths he tries to dispel are:

• WordPress is significantly more likely to be hacked.
• WordPress is just blogging software.
• WordPress professionals are designers.
• WordPress isn’t an enterprise solution.
• One WordPress requires one database.

For each item on the list he includes a brief summary of what's usually said about the myth and corrects it with his own description and links to other resources helping to prove his point.

In a new post to his blog today Hannes Magnusson talks about the benefits of doing a code review and getting your eyes on as much other people's code as possible (and a bit about a pleasant side effect of it).

Reading code is not only fun, its also a great way to exercise your brain - not to mention a fantastic way to discover new ways to solve problems. At work (we are hiring btw!), for example, I read pretty much every single commit (and merge requests, for that matter) - and I'm subscribed to several different OSS commit lists. I can't say I read every commit to PHP, I focus on the areas I care about, but I do skim over the rest - if only just to see when new features are added.

He talks about the various mailing lists that are around the PHP project (like the documentation, PEAR and PECL ones) and how many of the subscribers are cross-list, following along with multiple parts of the project.

Just the simple fact that I know people will be reading through my commits makes me think about what I am doing a bit more; "Is this really needed?", "Is there be a better way solving this?", "Could it potentially break other things?", "Is this actually correct?".. The people who review the commits often don't seem like the friendliest people in the world.. If there are issues with the commit; You will be told. No doubt about it.

What's the side effect I mentioned? Hannes' account credentials were hacked but, because of the code review process, a random commit from another developer was caught.

As a testament to why you should keep your copy of PHP-Nuke up to date, the KenRadio.com site has been hacked to show a large image on its main page from the infiltrator (hosted from imageshack.us).

You can check out the result of the hack on the main page of the site, or, if they've corrected the problem, the image that's displayed is here (while it lasts).

For anyone out there using PHP-Nuke, be sure that you're running the latest version - PHP-Nuke 7.9 Final - so that you and your site don't suffer the same fate.

As a testament to why you should keep your copy of PHP-Nuke up to date, the KenRadio.com site has been hacked to show a large image on its main page from the infiltrator (hosted from imageshack.us).

You can check out the result of the hack on the main page of the site, or, if they've corrected the problem, the image that's displayed is here (while it lasts).

For anyone out there using PHP-Nuke, be sure that you're running the latest version - PHP-Nuke 7.9 Final - so that you and your site don't suffer the same fate.