• Resolved cantoute

    (@cantoute)


    Hi,

    I’ve just noticed that automatic language redirection returns 301 (permanent redirection) witch is an issue and bans the usage of reverse proxy as 301 are cached for 24h as a common behavior… so every body gets redirect to the language of the first visitor!

    I there a way to use temporary redirection? (302)

    Thanks

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Anghel Emanuel

    (@anghelemanuel99)

    Hello there,

    Thank you for letting us know about this!

    There is possible to have an old version of that.

    Sorry, but we are not allowed to speak about the paid versions here. In case you would like to have that conversation please open a support ticket using our site:https://translatepress.com/support/ask-a-presale-question/ and mention this ticket.

    Kind Regards,

    Thread Starter cantoute

    (@cantoute)

    hi,

    How about simply replacing 301 by 302 where it should ?

    Redirecting on a per user case should be 302 in all cases.
    Permanent redirections mean nor browser nor search engine bots should request that url and should not be requested any more/replaced by the new location.
    Simply it asks crawlers to forget about the old url.

    I can’t believe that by now the dev team is not aware of this?!!
    And that should convince us to become client?

    Or is it that the free version is designed to make sure it should not be used in real world?

    I share with you some info to improve your products, sorry to sound a bit rude, but it’s been a long time I hadn’t had such a crap/useless response.

    
    includes/class-language-switcher.php:            wp_redirect( $link_to_redirect, 301 );
    includes/advanced-settings/do-not-translate-certain-paths.php:                wp_redirect( $current_original_url, 301 );
    includes/advanced-settings/do-not-translate-certain-paths.php:            wp_redirect( $current_original_url, 301 );
    includes/compatibility-functions.php:                    wp_redirect( $link_to_redirect, 301 );
    
    • This reply was modified 2 years, 3 months ago by cantoute.
    • This reply was modified 2 years, 3 months ago by cantoute.
    • This reply was modified 2 years, 3 months ago by cantoute.
    Plugin Support Anghel Emanuel

    (@anghelemanuel99)

    Hello there,

    While we don’t have a way to revert to 302 redirect without making changes to the plugin, the reason we use a 301 is for SEO reasons, so search engines know that old URLs were now changed to the new ones that contain the language.

    I’ve asked you about the paid version because I thought you were talking about the automatic user language detection addon that is doing a similar redirect. Not redirects from older url’s to ones containing the language parameter.

    We’ll add a hook so you can change the redirect if you need to. This should happen in the next version hopefully in the locations you mention.

    Kind Regards,

    Thread Starter cantoute

    (@cantoute)

    Hi,

    Thank you very much for this reply.
    Actually my client does have the payed version.

    I think it’s a good thing to have the choice to redirect 301 or 302.
    There are cases where 301 fits better, but I don’t think it’s what we want on landing url.

    Perhaps you want to have 3 options:
    – 301 every where
    – 302 every where
    – 302 on is_front_page() and 301 for the rest

    Just a thought.

    Have a nice day.

    • This reply was modified 2 years, 2 months ago by cantoute.
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Language auto redirect to be 302’ is closed to new replies.