• Skip to main content
  • Skip to primary sidebar
  • Skip to footer
  • Web
  • Creative
  • Mobile
  • IT
  • Code
  • CMS
  • Podcast
  • Memes
  • Resources
  • Newsletter
  • About

ChurchMag

The #1 Resource for Church Technology Creativity & New Thinking

Web Hosting

ChurchMag / CMS / 15 WordPress User Errors That Make You Look Silly [Infographic]

15 WordPress User Errors That Make You Look Silly [Infographic]

15 WordPress User Errors That Make You Look Silly [Infographic]

July 30, 2013
by Eric Dye

In light of our recent Tech Wreck Tuesday series, this infographic from Copyblogger seemed fitting.

Just because you’ve installed WordPress ump-teen times (I think “ump-teen” may be a technical term) and set up billions (just because it isn’t literally a billion times, doesn’t mean it feels less) of websites before, doesn’t mean you are immune to these somewhat common WordPress user errors.

This might actually make a decent checklist! 😀

How many of these errors have you made in the past?

wordpress errors

[Subscribe to Copyblogger’s Newsletter Here!]

There are some good times for WordPress n00bs and veterans alike!

Have you made any of these mistakes before?

[via Copyblogger]

Eric Dye

Support Lead at Valet, and Proprietor of DYECASTING. Human by day, gamer at night, lover of coffee, and all things spicy.

Category: CMS, WordPress

Level up your inbox.

Free resources, top posts, and more!

Reader Interactions

There are 4 comments already... Come join us!

  1. Raoul Snyman says

    July 31, 2013

    One of WordPress’s problems is that it still hasn’t migrated away from the idea that a URL needs to point to a real file on a server. Go to any WordPress site and type in “http://example.com/wp-admin/”. You’ll get the login page, which just is a subdirectory in the WordPress installation. Most modern systems don’t have a correlation between files and URLs.

    If you look at other systems, like Drupal (which I’m most familiar with), there is zero correlation between URL and filenames. This doesn’t necessarily make your site any more secure, but it does mean that potential crackers have a higher barrier to entry.

    Of course this is rooted in the fact that WP is written in PHP, which also is deeply rooted in the “URLs == files” mindset. And I’ll stop there before I venture into the “why PHP is bad” rant.

    Reply
    • Eric Dye says

      August 1, 2013

      LOL!

      Reply
  2. Jason T. Wiser says

    August 4, 2013

    Great list and info graphic. Some very practical check list items.

    I am not sure though about #7 how do you see hackers getting into deactivated plugins?

    Reply
    • Eric Dye says

      August 5, 2013

      That’s a good question… :-/

      Reply

Speak your mind... Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar



‹ Previous

10 Year Old Beats International Chess Master [Video]

Next ›

Tall Chess

Tall Chess: A Beautiful iOS App [Free]

Footer

Web Hosting

About

About
Contact
Advertise
Write for Us!
ChurchMag Minecraft Server

We #HEART

Powered by

Member of the ChurchMag Family

ChurchMag Podcast

Tired of Video Conference Calls

Are You Tired of Video Conference Calls? [Podcast #321]

Pick your favorite ways to connect.

Comment Policy / Privacy Policy / Archive / Log in

© 2021 ChurchMag