[Plugin: Polylang] Attempted access of home page gives 500 Internal Error

  • CKatzman

    (@ckatzman)


    11 years, 6 months ago

    I am still having a problem accessing the home page of my website (Google gives a 500 internal error). When in my wordpress dashboard’s page-edit, I have no trouble viewing uploaded pages. Once on the page, I could navigate through the sidebar menu to other pages, although I did eventually get a 310 error: TOO MANY REDIRECTS.

    My brother-in-law is trying to help me with this. We both tried what you suggested to him, classifying a page in the other language as a translation of the home page, but this did not solve the problem. The problem is definitely caused by Polylang because it appears only when Polylang is activated. My brother-in-law suspects that there may be a problem in using Polylang with one’s own custom home page rather than a wordpress generated menu for the home page.

    I have the latest versions of WordPress, PHP, and Polylang. I don’t have any other plug-in activated.

    I found that the error message when attempting to access the home page via the website URL occurs only when the home page most recently set was classified as English. This makes it appear that Polylang recognizes only one home page. This puzzles me because the documentation said a home page must be set for each language, and that setting a page translation is optional (categorically, without exception for the home page).

    When I checked the option to select the language of the home page via the browser preference, no matter how I set the language of my browser, the language of the home page the plug-in apparently attempted to return was the one I last assigned to be a home page. When I do not check the option to select the language of the home page via the browser preference, the front page access problem remains as before.

    The problem occurs whether or not the page assigned to be the front page and classified as English is included in the English menu.
    I went through Polylang’s documentation thoroughly and saw that the only requirement I had not yet taken care of completely, is localization of the theme to any desired language which isn’t English.

    My theme is a child theme of Bouquet. Bouquet is translation-ready, and it includes the exact same line of code mentioned in Polylang’s documentation as necessary for theme localization, just where it’s supposed to be, in the file header.php after the DOCTYPE line and above the <head> line. I have also tried using the 2011 theme, but this does not solve the problem. This means that the problem is not caused by incompatability between Polylang and the theme.

    However, I understand from the documentation that, in addition to being translation-ready and including the aforementioned code, the theme (not just the plug-in) must be equipped with language-specific files. Polylang’s documentation suggests asking the theme author to do this, so I posted a request for this, but got no response. I also tried contacting the person who equipped Polylang to use Hebrew, also no response. I took a look at the links referred to in the documentation that suggest using Poedit to generate the required files; I have not yet tried doing this.

    I very much doubt that my not yet having provided language-specific files for Hebrew could possibly explain the problems I’m having accessing the English front page, because:
    • Wordpress comes already equipped for English.
    • Polylang does manage to display a front page when it is classified as Hebrew. Whether the page is actually Hebrew or English doesn’t matter, it is the classification that determines whether the page will be displayed successfully or an error message returned. Trying to access my website URL when the home page most recently set was classified as English always causes an error message.
    • I wrote the Hebrew pages in Word in Israel on a computer equipped for Hebrew, and uploaded them to my website. Amazingly, these web pages are readable on my brother-in-law’s computer in America, although his computer is not equipped for reading or writing Word files in right-to-left languages, nor is his computer equipped to recognize Hebrew charcters.

    ⇒ Any ideas how to fix my English front page access problem?
    ⇒ What is the purpose of the language-specific files the documentation mentions? What function (if any) am I missing by not yet having provided the Hebrew-language files? If these are essential, please provide a link to Poedit.

    http://wordpress.org/extend/plugins/polylang/

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

    (@chouby)

    11 years, 6 months ago

    Could you please precise:

    • your Polylang settings
    • your permalink structure
    • the option chosen in settings->reading->Front page displays
    Thread Starter CKatzman

    (@ckatzman)

    11 years, 6 months ago

    A few weeks ago, I already tried changing all the various Polylang settings, including permalink structure and front page settings, one at a time, checking after each change if this solved the problem. Unfortunately, the front page remained inaccessible whatever settings I choose.

    I have also tried testing with a theme which claims to be equipped for French. I deleted Hebrew, designated a French page, menu, and translation of the English front page, but couldn’t get rid of the 500 error. Since I didn’t know how to find the .po and .mo files in this theme, I don’t know if they are there. When I contacted my webhost, they reported a pot file in that theme, but I couldn’t find it.

    A 500 error message can be caused by a file permission error. I have not yet having provided the .po and .mo files that Polylang’s documentation said must be provided by the website master to the theme, and I suspect that this is the cause of the problem.

    I have a few questions:
    1) Can I simply copy the files I need from Polylang into my theme, including .po and .mo files for Hebrew and the .pot file?
    3) Once I have these files, how do I get into the theme to put these files into it?
    • through my website control panel: file control/wordpress/wp-content/themes (All that I found there was the child theme my brother-in-law wrote for me, with no hint of my current theme.)
    • through my website control panel: file control/wordpress/wp-content/languages
    • through a different way?
    4) Once I get into the theme, where do I place the files? Is this in a folder called lang? If there is no such folder, where do I put it?
    6) When a new version of the theme will be released, will upgrading to the new version wipe out these files? If so, can I put them in a child theme instead?
    7) The documentation says, “Create one front page per language”. I find that only the most recently created front page is recognized. How does one create more than one front page? The documentation says that each page must have a language classification, and that establishing a translation is optional. Is it necessary to establish a translation for the front page in order to create a front page in another language?

    Thread Starter CKatzman

    (@ckatzman)

    11 years, 6 months ago

    P.S. Sorry I messed the numbering of the questions when I deleted two of them on the post form, I’m used to Word’s automatic renumbering.

    Thread Starter CKatzman

    (@ckatzman)

    11 years, 6 months ago

    In the meantime I deactivated Polylang,so my site birthdoulajerusalem.com is now accessible.

    Thread Starter CKatzman

    (@ckatzman)

    11 years, 6 months ago

    I copied the .po and .mo files from Polylang, and uploaded them to my theme. The 500 error remained.

    Then my brother-in-law installed and activated the Roots theme which definitely comes already localized for French, complete with .po and .mo files for French. He deleted Hebrew,designated French,made two pages with one as the translation of the other, deleted menus, made new ones for each language,made them front pages – still got a 500 error.

    Even when he made a subdirectory, with nothing extraneous in it,the 500 error remained. We are stumpted.

    Plugin Author Chouby

    (@chouby)

    11 years, 6 months ago

    Definitely, if you use a static front page, then you have to translate it. The same, in that case, for the posts page. These are the only two exceptions. For all the other contents, the translation is optional.

    Does the error 500 occur only when you have a static front page?

    Could you give me your PHP version?

    Thread Starter CKatzman

    (@ckatzman)

    11 years, 5 months ago

    The PHP version I’m using is 5.2. (I have an option either upgrade to 5.3 or downgrade to 4.)

    The 500 error occurs only with a static front page. Although my site has only static pages, no posts, I tried setting the front page as the latest post. This resulted in the display of a nonfunctional search box in lieu of the nonexistent post. I tried making a test post with a translation. When the front page was set to a post front page, the test post displayed, and the language switcher brought me to its translation. When I switched to a static front page, there was a 500 error.

    Because I had some difficulty trying to use Poedit, I copied the .po and .mo files for Hebrew from Polylang and uploaded them to my theme, although I’m not sure if these are appropriate. Translation of the front page apparently succeeded: in All Pages, a pencil icon replaced the plus icon that all untranslated pages have to the right of the page name, and when the cursor hovers over the pencil, the name of the translated page appears.

    A few weeks ago, before I managed to make a translation that appeared in All Pages, the 500 error appeared only when the page most recently entered as the front page was classified as English. When the page most recently entered as the front page was classified as Hebrew, there was no 500 error, but the English menu appeared alongside the Hebrew page. The classification determined whether the error occurred; the actual contents did not matter. Now that the Hebrew page has an English translation, there is a 500 error even when the last page entered as the front page is Hebrew.
    Is this because the translation of the front page automatically becomes the front page for the second language?

    When I check “When using static front page, redirect the language page to the front page in the right language”, I get a 500 error. When I uncheck this, I get a 310 error. This happens no matter how “Forces link to front page” is set. What is the language page? How do I eliminate these errors?

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘[Plugin: Polylang] Attempted access of home page gives 500 Internal Error’ is closed to new replies.

Tags