Yahoo indexing issues since RC ?

Started by riker, March 03, 2009, 12:55:08 PM

Previous topic - Next topic

riker

Noticed a problem with yahoo indexing my site and wondered if anyone else had issues since RC ?

karlbenson

What sort of a problem?
Not spidering? Spidering too much?

There is a known bug with Yahoo spiders all getting misdetected as Yahoo (Publisher) spider.
But that shouldn't impact yahoo from spidering, only a stats issue.

riker

#2
Quote from: regularexpression on March 03, 2009, 01:07:00 PM
What sort of a problem?
Not spidering? Spidering too much?

There is a known bug with Yahoo spiders all getting misdetected as Yahoo (Publisher) spider.
But that shouldn't impact yahoo from spidering, only a stats issue.

Either blank yahoo cache pages or post but no post text

karlbenson

Can you link me to the forum/page its happening on your forum
(not the yahoo cached page).

I'll check with my useragent switcher what yahoo sees


karlbenson

#5
semantic html/css
  +
search engine adding code in an xhtml invalid place (before the <html> tag)
  +
IE (it looks ok in chrome, opera, firefox)

(Note it affects Google Cache in the same way).
It won't affect your search engine/ranking, only how ie mis-renders it.

I think it might be possible to fix it, since it doesn't affect Beta 4.
http://209.85.229.132/search?q=cache:k5zeyPdppcQJ:galleryproject.oldiesmann.us/index.php%3Ftopic%3D632.0+Powered+by+SMF+2.0+Beta+4&hl=en&ct=clnk&cd=3&gl=uk

karlbenson


riker

Quote from: regularexpression on March 03, 2009, 02:13:52 PM
semantic html/css
  +
search engine adding code in an xhtml invalid place (before the <html> tag)
  +
IE (it looks ok in chrome, opera, firefox)

(Note it affects Google Cache in the same way).
It won't affect your search engine/ranking, only how ie mis-renders it.

I think it might be possible to fix it, since it doesn't affect Beta 4.
http://209.85.229.132/search?q=cache:k5zeyPdppcQJ:galleryproject.oldiesmann.us/index.php%3Ftopic%3D632.0+Powered+by+SMF+2.0+Beta+4&hl=en&ct=clnk&cd=3&gl=uk

What with the PM's, Membergroups and now this their does seem to be a lot of problems to fix in this RC :(

riker

#8
Quote from: AäronThat's because Google caches only the page, not the CSS. Since the CSS in RC1 differs from the CSS in beta 4, we simply cannot 'fix' this.

omg, can someone please come up with a way of downgrading to smf1.1.x because 2.0 is going backward not forward.

Ps I'm very hesitant in calling it a downgrade

greyknight17

There is no simple way to downgrade which is why we ask all users to make a complete backup of their forum before proceeding with any major upgrade.

H

Quote from: riker on March 04, 2009, 03:19:32 AM
Quote from: AäronThat's because Google caches only the page, not the CSS. Since the CSS in RC1 differs from the CSS in beta 4, we simply cannot 'fix' this.

omg, can someone please come up with a way of downgrading to smf1.1.x because 2.0 is going backward not forward.

Ps I'm very hesitant in calling it a downgrade

There is a reason 2.0 is still in testing. If you choose to upgrade before we deem it stable, you'll have to live with the consequences
-H
Former Support Team Lead
                              I recommend:
Namecheap (domains)
Fastmail (e-mail)
Linode (VPS)
                             

riker

Quote from: H on March 17, 2009, 04:18:06 PM
Quote from: riker on March 04, 2009, 03:19:32 AM
Quote from: AäronThat's because Google caches only the page, not the CSS. Since the CSS in RC1 differs from the CSS in beta 4, we simply cannot 'fix' this.

omg, can someone please come up with a way of downgrading to smf1.1.x because 2.0 is going backward not forward.

Ps I'm very hesitant in calling it a downgrade

There is a reason 2.0 is still in testing. If you choose to upgrade before we deem it stable, you'll have to live with the consequences

Thanks H but it's no longer a beta it's RC

H

RC is still part of the testing stage :)
-H
Former Support Team Lead
                              I recommend:
Namecheap (domains)
Fastmail (e-mail)
Linode (VPS)
                             

karlbenson

I think I've fixed it in the SVN.
A single line was responsible. However in changing that line, it caused half a dozen issues in other browsers.

So fingers crossed that once our beta testers test it, we don't discover I broke any other browsers.

So should be in RC2 (whenever that is released)

Advertisement: