EzineArticles Terms of Service
I have a tendency to glaze over when it comes to reading rules and terms of services. They all seem to pretty much be the same across the board.
However, I was doing some research for a plugin of interest. For some reason, I went to EzineArticles.com’s terms of service page. Have you actually read it? Did you pay attention.
Apparently, I didn’t. So when I read their rules, I was taken aback. I own several websites and also sell sites that are autoblogs. If you don’t know what that means, all an autoblog is is a site that automatically posts content on its own by taking said content from sources such as EzineArticles.
I currently use a free autoblog plugin that takes articles from EzineArticles, Isnare, andArticlebase. I am saving up for WP Robot as it is a bad ass plugin that has 17 modules, one of which pulls articles. I had the opportunity to test it out on a client’s site and I love it.
Anyway, I visited EzineArticles’ TOS and realized that it only allows publishers (website owners) the ability to publish 25 articles (MAX) per calendar year per domain. UH. Ooops.
Taken directly from their TOS:
“EZINEARTICLES.COM TERMS OF SERVICE FOR PUBLISHERS:
Attention Publishers & Webmasters; Our Reprint Policies:
If you wish to publish/reprint any article from our site in your ezine, website, blog, forum, RSS feed or print publication, you must:
…Agree to limit the number of articles reprinted to no greater than taking 25 articles from our site per calendar year per unique domain that you own. In addition, for domain owners of many domains, you may not reprint more than 250 articles per year (10 sites x 25 articles reprinted per domain).”
I, for one, hate any sort of limitations. I’m also not big on breaking rules. Soooooo, I decided that I wasn’t going to be pulling articles from EzineArticles any longer. I’m assuming that plugin developers that create the autoblog plugins are aware of this rule and have somehow made it so that when a site reaches it 25 article limit, the plugin will switch to a different article source. Once can hope but I’m not going to depend on it.
I did find out that GoArticles has the same rule as EzineArticles. I’m really not quite sure why they have this rule. But I did find that Articlebase and Isnare don’t have such a rule, which is a plus for me.
It was a minor inconvenience, but one that doesn’t stand in my way. Onward!
Internet Explorer, the Web Developer’s Nemesis
Image via CrunchBase
Well, it’s mine anyway.
I got a big wake up call yesterday morning. I had placed two auctions up on Flippa a couple days back. They are the two that I’m having a helluva hard time selling. Why? I haven’t figured it out yet. Like I said before, I think it’s because of some missing components such as not having necessary software (mostly for backend link building and SEO), the knowledge of knowing how to drive traffic to sites, as well as the reputation needed to soothe the minds of potential buyers.
Anyway, I received an email from a potential buyer who was looking at one of the sites I had up for sale. He told me that he would like for me to fix the header/navigational area so that he could have a better look at the site. I was dumbfounded. I looked at the site in my trusty (or at least I thought) Firefox browser. Nothing seemed out of order. I checked it out on my hubby’s computer to see if it would look differently since I seem to have a problem with clearing the cache on mine. Again – nothing seemed out of place.
So I took a screenshot and placed it on the auction. I also answered the guy’s email and asked if he would kindly send me a screenshot of what he sees on the computer. A few hours later, I received a response.
I gawked and cringed at the screenshot that the person sent me. The site was broken. The navigation was not there except for a near invisible list of links to pages. The background to the articles were not white like it should be. And the footer at the bottom did not exist. I was so embarassed.
Web design 101: Always check to make sure your site is working across all browsers, not just your favorite one. For those of you who would like to avoid my mistake, always check your site at this site Browser Shots for compatibility.
Image via Wikipedia
I wasn’t sure what made the site look horrible in IE. Of course, many web developers know that IE handles websites differently than other browsers like Firefox. I was racking my brain to the point where it hurt.
On a hunch, I checked out all my other sites. I got more and more stressed out and angry when I realized that most of my sites were horribly broken in Internet Explorer. I needed to figure out why they looked like absolute shit.
I ran a mental list to see what they all may have in common. And this is what I came up with.
Most of them:
- Are hosted on Hostgator (it wasn’t the problem)
- Use the WordPress 3.01 platform
- Used most of the same plugins
- Used themes I created in Artisteer
- are owned and run by me (flawed in many ways LOL)
I immediately nixed Hostgator and WordPress as they are heavily supported and backed by their respective companies. That left me, my plugins and Artisteer.
I automatically figured it was Artisteer. I didn’t seem to have a problem with the sites when they were using free WordPress themes. I didn’t want to give it up because Artisteer makes it simple and quick for me to make my own WordPress themes. I did go to the Artisteer forums to look for answers. But to my dismay, Artisteer support was not up to par. A lot of people asking or complaining about Artisteer support. I was cranky that I had paid for another year’s worth of updates when support sucks.
I was ready to give Artisteer the boot so I started the unwanted search for free WordPress themes that fit my criteria. Still, in the back of my mind I felt that Artisteer wasn’t the entire problem.
I couldn’t make any changes to the 2 sites that were up for sale on Flippa so I decided to test a christmas site that used Artisteer and plugins. I kept the theme in tact and instead, turned off all the plugins. Voila! The site was no longer broken! I was tickled pink that I didn’t actually have to do away with Artisteer.
So I painstakingly turned each plugin on, one by one. I kept refreshing the IE browser and things seemed ok… until I turned on Hyper Cache. Then the site was broken once again. “Yes!” I thought. I assumed that was the culprit.
It wasn’t. It was only half of the problem. I deactived the plugin from all the sites and they went back to normal again. However, refreshing the page a few times brought the sites to that ugly stage once more. I grit my teeth and wanted to pound my head on the wall.
I eventually figured out that it was both Hyper Cache and WP Minify that weren’t working well on my sites. They don’t work separately either, meaning that if one was deactivated and the other was not, the site was still broken. So I opted to have them both deactivated.
Lesson learned: always check your site for browser compatibility before selling it or sending traffic to it.
