Title: Bug with 1.7. Page Reloading Script
Last modified: August 22, 2016

---

# Bug with 1.7. Page Reloading Script

 *  Resolved [Raptor2771](https://wordpress.org/support/users/raptor2771/)
 * (@raptor2771)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/bug-with-17-page-reloading-script/)
 * Hello!
 * There is a current bug on 1.7. If you have the “The front page url contains the
   language code instead of the page name or page id” Selected, the home page breaks.
   Google gives you a message saying that there is a reloaping happeing. But if 
   you unselect that option, the site works fine.
 * That option is what makes the home page cleaners, from yourdomain.com/en/home
   to yourdomain/en
 * Hope this makes sense 🙂
 * [https://wordpress.org/plugins/polylang/](https://wordpress.org/plugins/polylang/)

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

 *  [Sigor](https://wordpress.org/support/users/sigor/)
 * (@sigor)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/bug-with-17-page-reloading-script/#post-5919971)
 * Hi Chouby.
    I have the same issue than Raptor (thanks Raptor for your tip). So
   I’ve unchecked this naughty check box and it works fine. But… now the home’s 
   url is ‘awful’. Instead of [http://www.mywebsite.com/en/](http://www.mywebsite.com/en/),
   [http://www.mywebsite.com/anotherurl/](http://www.mywebsite.com/anotherurl/) 
   seems not pretty to me. I don’t think I’m finicky but with this amazing plugin,
   I know Chouby that you are finicky. Do you plan to fix that bug? Warm regards
 *  Plugin Author [Chouby](https://wordpress.org/support/users/chouby/)
 * (@chouby)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/bug-with-17-page-reloading-script/#post-5919974)
 * Hi!
 * I will work on this. Waiting for this I have disabled the 1.7.
    You can revert
   to 1.6.5 with FTP. It is available here. [https://downloads.wordpress.org/plugin/polylang.1.6.5.zip](https://downloads.wordpress.org/plugin/polylang.1.6.5.zip)
 *  Plugin Author [Chouby](https://wordpress.org/support/users/chouby/)
 * (@chouby)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/bug-with-17-page-reloading-script/#post-5919983)
 * I am tracking the bug. Are you setting the language from the content in Polylang
   settings?
 *  Plugin Author [Chouby](https://wordpress.org/support/users/chouby/)
 * (@chouby)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/bug-with-17-page-reloading-script/#post-5919984)
 * I have uploaded a new development version (1.7.0.1).
    Could you confirm if the
   problem is fixed for you? [https://downloads.wordpress.org/plugin/polylang.zip](https://downloads.wordpress.org/plugin/polylang.zip)
 *  [Kjetil](https://wordpress.org/support/users/kjetilgf/)
 * (@kjetilgf)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/bug-with-17-page-reloading-script/#post-5919987)
 * I wrote the post below before I saw the thread – just for your info.
    Things 
   seem to work fine now. Thanks!
 * One question though, since I’m new to Polylang: The widget language switcher,
   shouldn’t it point to eg. a twin post, or should it always point to the other
   language’s front page (as it does on our site now)?
    Thanks See [http://www.toscanatailormade.com](http://www.toscanatailormade.com)(
   might be down due to upgrading) ———- After upgrading from 1.6.5 to 1.7 the site(
   [http://www.toscanatailormade.com](http://www.toscanatailormade.com)) won’t load
   anymore. Instead I get the error (my translation): “The site does not forward
   correctly. Firefox ha discovered that the server forwards the request for this
   address in a way that will never end.» A possible factor might be a setting under
   General where I’ve set the wp address to wp.toscanatailormade.com while the site
   url is [http://www.toscanatailormade.com](http://www.toscanatailormade.com). 
   This has worked for several years, though. Things work if I replace www with 
   wp in the address bar. Also the Norwegian links don’t work, even with wp. instead
   of www. Downgrading to Polylang 1.6.5 solves the problem. WP 4.1.1
 *  [Sigor](https://wordpress.org/support/users/sigor/)
 * (@sigor)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/bug-with-17-page-reloading-script/#post-5919991)
 * Hi Chouby,
    Thank you for your work. I’ve installed and tested your 1.7.0.1 version
   and Polylang seems now fixed with WP4.1.1. I’ve tried with the Home page and 
   also with another page inside the website. All seems fixed.
 * Your previous question:
    Are you setting the language from the content in Polylang
   settings? > Yes I am.
 * Thanks you very much Chouby.
    Very Good Job. I’m fond of Polylang.
 *  Thread Starter [Raptor2771](https://wordpress.org/support/users/raptor2771/)
 * (@raptor2771)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/bug-with-17-page-reloading-script/#post-5920081)
 * I updated to 1.7.1 but now the site is broken. I got this message:
 * Fatal error: PLL_Model::_languages_list(): The script tried to execute a method
   or access a property of an incomplete object. Please ensure that the class definition"
   PLL_Language" of the object you are trying to operate on was loaded _before_ 
   unserialize() gets called or provide a __autoload() function to load the class
   definition in /home/content/p3pnexwpnas03_data01/69/2414569/html/wp-content/plugins/
   polylang/include/model.php on line 209
 *  Thread Starter [Raptor2771](https://wordpress.org/support/users/raptor2771/)
 * (@raptor2771)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/bug-with-17-page-reloading-script/#post-5920083)
 * Sorry I had to move all of my websites that use Polylang to 1.6.5. Major erros
   happening right now 🙁
 *  Plugin Author [Chouby](https://wordpress.org/support/users/chouby/)
 * (@chouby)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/bug-with-17-page-reloading-script/#post-5920086)
 * [@raptor2771](https://wordpress.org/support/users/raptor2771/)
 * You should have opened a new topic rather than posting on a resolved one. Your
   problem is not linked to the Polylang update but to a conflict between your host(
   I guess it is godaddy) and Polylang.
 * This is an old problem for which I got no help to solve it properly.
    See [https://wordpress.org/support/topic/fatal-error-pll_model_languages_list](https://wordpress.org/support/topic/fatal-error-pll_model_languages_list)
   [https://wordpress.org/support/topic/fatal-error-1178](https://wordpress.org/support/topic/fatal-error-1178)
   [https://polylang.wordpress.com/2014/07/12/polylang-1-5-3/](https://polylang.wordpress.com/2014/07/12/polylang-1-5-3/)
 *  Thread Starter [Raptor2771](https://wordpress.org/support/users/raptor2771/)
 * (@raptor2771)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/bug-with-17-page-reloading-script/#post-5920105)
 * aah!
 * Sorry, I didn’t know the topic was solved.
 * Yet you are right. The client is using Godaddy. Everytime I deal with them, they
   have something they don’t support. One time I couldn’t use a Theme because of
   the same issue. The I installed the theme on Hostgator and no issues what so 
   ever.
 * I hate GoDaddy!
 * thanks so much for all you do 🙂

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

The topic ‘Bug with 1.7. Page Reloading Script’ is closed to new replies.

 * ![](https://ps.w.org/polylang/assets/icon-256x256.png?rev=3433336)
 * [Polylang](https://wordpress.org/plugins/polylang/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/polylang/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/polylang/)
 * [Active Topics](https://wordpress.org/support/plugin/polylang/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/polylang/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/polylang/reviews/)

 * 10 replies
 * 4 participants
 * Last reply from: [Raptor2771](https://wordpress.org/support/users/raptor2771/)
 * Last activity: [11 years, 4 months ago](https://wordpress.org/support/topic/bug-with-17-page-reloading-script/#post-5920105)
 * Status: resolved