Archive for January 17th, 2007

Fatal error: class jsmfFrontend not found after Joomla Patch to 1.1.12

Wednesday, January 17th, 2007

Recently I upgraded one of my clients from Joomla 1.1.1 to 1.1.2.

After installation, I found I was suddenly receiving the following error:-

Fatal error: Class ‘jsmfFrontend’ not found in /modules/mod_smf_login.php on line 107

after installing a patch to upgrade from Joomla 1.1.11 to 1.1.12

I was able to temporarily abolish it by going into my admin and turning off the SMF-Login module (from Modules Menu). It’s obviously an incompatibility between the Joomlahacks SMF bridge login module and the Joomla 1.1.12 upgrade.

The joomla upgrade reinstalls the index.php file in root - so it removes the patch that the joomlahacks smf bridge applies to that file during installation.

You need to go to your admin panel, components, select JoomlaHacks SMF-Bridge, and install, and then ‘click to patch’ the index file..

You might need to chmod your index file to 777 to allow the patch to be applied.

This removes the Fatal error: Class ‘jsmfFrontend’ not found in /modules/mod_smf_login.php on line 107
message

Optimizing wordpress (or any CMS) to stop duplicate content penalty and supplemental results

Wednesday, January 17th, 2007

This blog entry follows up on my previous blog about supplemental nightmares ‘Gone Supplemental’, and you’d be well advised to read that one first.

Some of my clients recently pointed out to me that their wordpress blogs were showing huge numbers of supplemental results in Google. A supplemental result occurs when google, for some reason or another, deems that information in a page is not important enough to include in its’ main index. This can be the kiss of death for sites like this one, which rely upon unique information to generate traffic and adsense revenue.

So, how do you stop supplementals with wordpress? Well, after a bit of hunting around, I discovered that the most likely reason for the problem was the structure of wordpress itself - Content is replicated all over the place. For instance, this blog entry will appear under the ‘wordpress’ and ’seo’ categories to the right, in the archive for January, and in the blog entry itself. In most cases, it will also appear on the main page of your site, but I get around that problem by using the ‘Optional Excerpt’ field in the wordpress editing box to serve a small summary of each of my wordpress blog entries on the front page rather than the whole article.

If you don’t watch yourself, Google will see this replicated content as ‘duplicate content’, meaning, as far as Google is concerned, you are spamming them. This is a quick and easy way to get relegated to supplemental status, and once you are there, it is hard to come back. This is a real problem with CMS systems in general, and I’ve experienced it using Joomla also.

So, what’s the solution?

Well, there are a few, but for ease of use, I reckon you can’t beat a good robots.txt file. This will help prevent duplicate content.

In my particular setup, I’ve used the following robots.txt rules to ban google from crawling the archives, categories and RSS. Note that banning crawls of your RSS directory can be a bit of a hairy banana - many search engines, like yahoo, deliberately look for RSS feeds, and they can improve your popularity amongst other blogs. I’m still not quite sure where I stand there - perhaps I’ll wait for some of your views on that issue.

Check out my modified robots.txt to avoid supplemental results in wordpress here. Also, a decent wordpress plugin that I use on my site to reduce supplementals is DupPrevent, which you can download here

If you don’t understand regular expressions and robots.txt files, google provides a good guide to robots.txt files here.

Doc


Update - I’ve had some clarification on whether RSS is considered duplicate content - see RSS and Duplicate Content if you like, otherwise, just be advised that having an RSS feed shouldn’t be a problem. I’ve updated my robots.txt file to reflect that, and include RSS content.Doc

Subdomains, SEO and getting crawled

Wednesday, January 17th, 2007

Hi Everyone -

This blog was previously hosted on a subdomain - http://blog.utheguru.com. That subdomain was submitted using google webmaster tools, at the same time as the top level domain, www.utheguru.com .

The top level domain was crawled, cached and searchable within approximately two days, whereas the subdomain, four months later, is still waiting to be indexed, even though my logs tell me it is being crawled.

I’ve seen this same reticence from Google to index subdomains before on my other sites. As far as I can glean from my research, google doesn’t have a problem with subdomains - see here for another site that talks about it - but, really, in all honesty it’s really hard to find an OFFICIAL policy about subdomains on google.

I know in the past, there have been examples of people trying to manipulate PR by registering hundreds or millions of subdomains, and carefully interlinking the pages so as to impart an artificially high number of backlinks to the TLD. I’m pretty sure that google has cracked down on it now, as Matt Cutts talks about the problem of subdomain spamming in his online blog.

I’ve tried asking about subdomains, SEO and indexing on the Google Groups Webmaster Help Forum - in my first post, I asked the question:-

I’m considering starting a new site with a bit of a revolutionary
business model.

But let’s forget about that for now..

What I’m interested in is whether seperating a site into subdomains is
beneficial in terms of a site’s page rank and overall ability of users
to find information relevant and helpful to them.

There were a few interesting responses, but the general feeling I got was that I had entered a no-go zone and people were a bit reluctant to give any real answers. A few weeks later, I asked directly whether google indexes top level domains in preference to subdomains. Again, no real authoritative answers.

I’m thinking that this problem is worth asking about. At the end of the day, I have just 301 redirected blog.utheguru.com to www.utheguru.com, while I try and get answers.

I’d love to hear from you all about your experiences with subdomains.

Cheers,

D


Ok - so I think I’ve got the solution. I did eventually get ONE of my pages indexed, and that was by backlinking to that page a great deal (ironically, it’s this one) from other sites. Subsequently I got the poo’s with waiting for google, and transferred all pages over to the TLD (as you can see above). This ‘Solution’ has quickly paid dividends, as the site was indexed within a few days after the change over.So, my ideas -

  1. Google is reticent and reluctant to quickly index subdomains.
  2. If you want to get subdomains indexed quickly, you’d better have a strong backlinking program.
  3. I think google has a ‘delay’ between crawling and indexing a sub-domain - I saw my subdomains regularly crawled, but indexing hadn’t occured up until two months after they were first crawled. The equivalent wait for a top level domain was only about a week.

If you want to use subdomains -

  1. Initially add your new site to a subdirectory of the TLD of your existing website.
  2. Get it indexed.
  3. 301 redirect that directory to your subdomain.

Cheers and all the best!

Duck