Page not found error google webmaster tools crawler

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Chouby

    (@chouby)

    12 years, 5 months ago

    Looking at your website, the first bad link seems to come from a conflict with All in one SEO, which creates a wrong canonical link. You should try to de-activate it and then look a the html source code to check that the canonical link created by WordPress + Polylang only is correct.

    The second bad link was a known limitation of older version of Polylang which did not check for existence of archives in other languages. The feature is implemented since v1.2.

    Thread Starter tasver85

    (@tasver85)

    12 years, 5 months ago

    Hi thanks for the reply ^^

    I looked in the canonical url, first with enabled option and then i looked in italian version from the second page and so on, and it seems that the url were generated right
    <link rel=”next” href=”http://www.bookandnegative.com/page/2/”&gt;
    <link rel=”canonical” href=”http://www.bookandnegative.com/page/2/”&gt;

    If i look in english version i got this,
    <link rel=”next” href=”http://www.bookandnegative.com/en/page/2/”&gt;
    <link rel=”canonical” href=”http://www.bookandnegative.com/en/”&gt;

    I disabled the canonical url
    And i don’t get obviously no canonical url.

    I never had an italian version with
    http://www.bookandnegative.com/it/page/2/
    honestly i don’t know if it is an old sitemap error?
    I don’t know where the error is generated and when, or the error is generated by a cron?

    For the second problem, thanks i’ll upgrade but sorry for the question but polylang is stable now?

    Thanks for your good work! 😉

    Plugin Author Chouby

    (@chouby)

    12 years, 5 months ago

    polylang is stable now?

    I am aware of only a few people who have encountered issues during the upgrade to 1.2 or older, always due to conflicts with other plugins.

    That’s a major upgrade in both program structure and database. So it’s more risky than usual and that’s why I recommended (everywhere I could) to make a database backup before upgrade (to ease revert if needed). And I still recommend it.

    However nobody lost his data because Polylang never removed them (the upgrade process is creating data for 1.2 and newer but does not remove old data from 1.1.6 and older: I will remove them later). That permitted some users to revert temporarily to 1.1.6 using that plugin. But making a DB backup is safer.

    Since 1.2.3 has been released, no more people has complained about broken upgrade.

    I will never claim that Polylang is bug free. And there are always possibilities of a conflict with a theme or another plugin.

    Thread Starter tasver85

    (@tasver85)

    12 years, 5 months ago

    I never had an italian version with
    http://www.bookandnegative.com/it/page/2/
    honestly i don’t know if it is an old sitemap error?
    I don’t know where the error is generated and when, or the error is generated by a cron?

    For the first error what do you think?

    About the upgrade, i do everitime the db backup, but if is it possible could you add a procedure to do a selective backup and a selective revert?
    I see all the code have the comment, but with a clear guide will be more simpler, anyway everyone have to study a little bit the code of the plugin in order to find the database table and location.
    For example my site have a bigger database and a complete restore for a single plugin i think is excessive.

    I’ll do the update from 1.0.4 to 1.3.1, like every plugin update i’ll disable all plugin and back to the default theme and i’ll take fingers crossed XD
    like Arnold Swartzenegger said “I’ll be back” XD

    Thanks for your reply 😉

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Page not found error google webmaster tools crawler’ is closed to new replies.