Tips that save time.
Let’s start a new series on this blog. Today, Jan 31th is the B-day of the “WordPress Advice of the Month” series. Now some rules.
This sounds like it’s going to be a monthly series. But it’s not. Good WordPress advice is not that easy to find. I mean, there are loads of stuff out there, but not everything is really that interesting or valuable.
WordPress has been around for quite some time now. Many people are familiar with it. The level of so-called common knowledge is rather high. This results in a situation when 90% of new posts keep explaining the same ol’ stuff over and over again (just rehashing it slightly). New ideas are in the minority.
It’s somewhat similar to the situation in the “blogging about blogging” world. It seems like every day I see a post saying that the number one most important thing is to produce “good, valuable content”. Come on, if I had a nickel for every time someone wrote that… But it’s just a side note/rant.
Ok, let’s just get on with it
This month’s WordPress advice of the month touches upon the situation with free WordPress themes, and comes from the WPMU team. Here’s the post I’m talking about:
Why You Should Never Search For Free WordPress Themes in Google or Anywhere Else
The biggest problem with free WordPress themes is that they are not really free.
If you’re using one you are paying with your link juice (I love that phrase – “link juice” – sounds delicious, anyway). Most of the free themes force you to link back to something. And most of the time it’s not even the website of the creators themselves. What you usually end up with is a bunch of links to places like dating sites, affiliate offers, even link farms. Not cool. But you can always remove the links by hand, right?
Wrong. In most cases you can’t because they are not placed in a manner you were taught by the programming gods. Theme creators are using encrypted code. It prevents you from removing it because if you try the theme just stops working.
Here’s an example of such a code:
<?php eval( base64_decode( ‘JF9YPWJhc2U2NF9kZWNvZGUoJF9YKTskX1g9c3RydHIoJF
This particular code comes from one of the themes I’ve been using. The most important part of this fragment is the usage of eval() and base64_decode() PHP functions.
Let me tell you something about the eval() function. What it basically does is it evaluates a given string as PHP code. In plain English it means that it can be used to perform almost ANY operation on your web server! PHP is a easy to use yet very powerful programming language. You shouldn’t give anybody the power of performing eval() function on your server. Especially if you never met the guy, and all you know about him is that he created a nice looking WordPress theme.
What you can do
First of all, read the post by the WPMU team, you will find a much more complete explanation there. Then use three little plugins and check your theme for any malicious behavior. These plugins are:
Then come back and share your results here. Is your theme safe?
Head image from: https://icons8.com/illustrations/illustration/arabica-1028
[…] This post was mentioned on Twitter by Karol K, Åukasz Chojnowski. Åukasz Chojnowski said: RT @carlosinho: Just posted: WordPress Advice of the Month: Why Free Themes are EVIL – http://bit.ly/edBe5S […]
I quite understand you. Measure thrice and cut once 😐
[…] thereâ€™s more! If youâ€™re just starting your blogging adventure donâ€™t forget to check out my WordPress advice of the month, and the WordPress […]
[…] Today itâ€™s time for another edition of the â€œWordPress Advice of the Monthâ€ monthly series, which isnâ€™t really monthly, by the way. (Hereâ€™s the previous episode, in case you missed it: Why Free Themes are EVIL) […]
When something comes in free, there is always a catch. And that’s the catch when you use ‘free’ WP themes. It’s smart to buy one if you’re planning to monetize your blog.
Good one I had to get rid of some code previously. Btw is “there’re” even a word. Never seen the apostrophe being used like this before. Perhaps it was a tactic to get someone to comment 🙂
Comments are closed.