Support » Plugin: Sublanguage » Problem with Pods: 500 – Internal Server Error

  • If I have Sublanguage and Pods plugins activated I receive this error when translating posts/pages or entering my web. Please help!

    500 – Internal Server Error
    This is a temporary server error.
    Please try to reload the webpage later.

    If you are the webmaster of this site please log in to Cpanel and check the Error Logs. You will find the exact reason for this error there.

    Common reasons for this error are:

    Incorrect file/directory permissions: Above 755.

    In order files to be processed by the webserver, their permissions have to be equal or below 755. You can update file permissions with a FTP client or through cPanel’s File Manager.
    Incorrect Apache directives inside .htaccess file.

    Make sure you have not specified unsupported directives inside the local .htaccess file. Such include PHP settings and Apache module settings.

Viewing 15 replies - 1 through 15 (of 18 total)
  • mlibbey

    (@mlibbey)

    I have a similar problem with 500 errors showing. My site uses the Disable Gutenberg plugin, and when I’m in the backend editing a page and tab to the language I want to edit, I get this a Server 500 error.

    If I disable Gutenberg, I can switch between the two tabs. I tried changing the content on the language tab (in this case it’s Hebrew) but when I go to look at it I see a blank page after the closing <body> tag. I get a prompt from my browser about translating the page though.

    Is there some setting I need to tweak? I’m using ACF on most pages, but this particular page is just calling a standard template, which is a Genesis theme.

    Thanks!

    Jim True

    (@jimtrue)

    @manoleixon The error message is telling you exactly what you need to do. Reach out to your server host with the error messages and have them help you rectify that.

    500 Server Errors will almost always present themselves somewhere in the Server Logs on your host. They usually refer to permissions, .htaccess file corruption or memory limits, but they will always give some hint of what is wrong in the Server Logs at your host.

    If they don’t and your host doesn’t cooperate with you in investigating them, you need to move to a new server host.

    manoleixon

    (@manoleixon)

    Thanks both!
    @jimtrue in my server host they checked the web and everything’s okay: permissions, .htaccess and also memory. They’re telling me to contact developers of Sublanguage plugin…

    Jim True

    (@jimtrue)

    Nothing in the logs that explains those 500 errors? Duplicate the site locally or somewhere else and see if you have the same issues

    Plugin Author maximeschoeni

    (@maximeschoeni)

    Hello manoleixon,
    Sorry I really don’t know what can cause this problem. I checked but I can’t see any conflict with Pods plugin. Isn’t there any other plugin causing this problem, especially cache plugins?

    manoleixon

    (@manoleixon)

    @jimtrue @maximeschoeni thanks both! The plugins which are causing the problem are Pods and Sublanguage, as another person in my host server has checked out.
    This is the error that appears in the Apache register

    [Mon Apr 15 23:06:14.972397 2019] [core:error] [pid 8901] [client 87.118.135.66:37546] End of script output before headers: index.php
    [Mon Apr 15 23:06:15.194969 2019] [core:error] [pid 20282] [client 87.118.135.66:37624] End of script output before headers: index.php, referer: (my web url)

    I could also send you privately the core dump files and the strace.txt file.

    Are there any PHP error logs that go along with this issue? You would be looking for “Fatal” errors most likely.

    manoleixon

    (@manoleixon)

    @sc0ttkclark how could I look for that?

    https://codex.wordpress.org/Debugging_in_WordPress

    Specifically the debug logging.

    manoleixon

    (@manoleixon)

    @sc0ttkclark thanks!

    [14-Apr-2019 22:26:41 UTC] PHP Catchable fatal error:  Object of class WP_Error could not be converted to string in /home/.../public_html/.../wp-includes/pluggable.php on line 1282
    [14-Apr-2019 22:44:38 UTC] PHP Fatal error:  Allowed memory size of 805306368 bytes exhausted (tried to allocate 262144 bytes) in /home/.../public_html/.../wp-includes/cache.php on line 123
    [14-Apr-2019 22:44:38 UTC] PHP Fatal error:  Allowed memory size of 805306368 bytes exhausted (tried to allocate 81920 bytes) in Unknown on line 0
    [15-Apr-2019 03:26:45 UTC] PHP Warning:  date() expects parameter 2 to be integer, string given in /home/.../public_html/.../wp-includes/functions.php on line 114
    [15-Apr-2019 03:26:45 UTC] PHP Warning:  date() expects parameter 2 to be integer, string given in /home/.../public_html/.../wp-includes/functions.php on line 116
    [15-Apr-2019 03:26:45 UTC] PHP Warning:  date() expects parameter 2 to be integer, string given in /home/.../public_html/.../wp-includes/functions.php on line 119
    [15-Apr-2019 08:09:48 UTC] PHP Warning:  date() expects parameter 2 to be integer, string given in /home/.../public_html/.../wp-includes/functions.php on line 114
    [15-Apr-2019 08:09:48 UTC] PHP Warning:  date() expects parameter 2 to be integer, string given in /home/.../public_html/.../wp-includes/functions.php on line 116
    [15-Apr-2019 08:09:48 UTC] PHP Warning:  date() expects parameter 2 to be integer, string given in /home/.../public_html/.../wp-includes/functions.php on line 119
    [15-Apr-2019 14:33:27 UTC] PHP Warning:  date() expects parameter 2 to be integer, string given in /home/.../public_html/.../wp-includes/functions.php on line 114
    [15-Apr-2019 14:33:27 UTC] PHP Warning:  date() expects parameter 2 to be integer, string given in /home/.../public_html/.../wp-includes/functions.php on line 116
    [15-Apr-2019 14:33:27 UTC] PHP Warning:  date() expects parameter 2 to be integer, string given in /home/.../public_html/.../wp-includes/functions.php on line 119
    [15-Apr-2019 14:43:59 UTC] PHP Warning:  date() expects parameter 2 to be integer, string given in /home/.../public_html/.../wp-includes/functions.php on line 114
    [15-Apr-2019 14:43:59 UTC] PHP Warning:  date() expects parameter 2 to be integer, string given in /home/.../public_html/.../wp-includes/functions.php on line 116
    [15-Apr-2019 14:43:59 UTC] PHP Warning:  date() expects parameter 2 to be integer, string given in /home/.../public_html/.../wp-includes/functions.php on line 119
    [15-Apr-2019 19:49:43 UTC] PHP Warning:  date() expects parameter 2 to be integer, string given in /home/.../public_html/.../wp-includes/functions.php on line 114
    [15-Apr-2019 19:49:43 UTC] PHP Warning:  date() expects parameter 2 to be integer, string given in /home/.../public_html/.../wp-includes/functions.php on line 116
    [15-Apr-2019 19:49:43 UTC] PHP Warning:  date() expects parameter 2 to be integer, string given in /home/.../public_html/.../wp-includes/functions.php on line 119
    [15-Apr-2019 20:35:08 UTC] PHP Fatal error:  Call to undefined function apply_filters() in /home/.../public_html/.../wp-includes/load.php on line 332
    [15-Apr-2019 20:36:08 UTC] PHP Parse error:  syntax error, unexpected '[' in /home/.../public_html/.../wp-content/plugins/autodescription/inc/functions/api.php on line 120
    [16-Apr-2019 13:21:51 UTC] PHP Warning:  date() expects parameter 2 to be long, string given in /home/.../public_html/.../wp-includes/functions.php on line 114
    [16-Apr-2019 13:21:51 UTC] PHP Warning:  date() expects parameter 2 to be long, string given in /home/.../public_html/.../wp-includes/functions.php on line 116
    [16-Apr-2019 13:21:51 UTC] PHP Warning:  date() expects parameter 2 to be long, string given in /home/.../public_html/.../wp-includes/functions.php on line 119
    [16-Apr-2019 22:01:04 UTC] PHP Fatal error:  Uncaught exception 'wfWAFStorageFileException' with message 'Unable to verify temporary file contents for atomic writing.' in /home/.../public_html/.../wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:47
    Stack trace:
    #0 /home/.../public_html/.../wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(650): wfWAFStorageFile::atomicFilePutContents('/home/.../...', '<?php exit('Acc...')
    #1 [internal function]: wfWAFStorageFile->saveConfig('synced')
    #2 {main}
      thrown in /home/.../public_html/.../wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php on line 47
    [16-Apr-2019 22:41:59 UTC] PHP Fatal error:  Uncaught exception 'wfWAFStorageFileException' with message 'Unable to verify temporary file contents for atomic writing.' in /home/.../public_html/.../wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:47
    Stack trace:
    #0 /home/.../public_html/.../wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(650): wfWAFStorageFile::atomicFilePutContents('/home/.../...', '<?php exit('Acc...')
    #1 [internal function]: wfWAFStorageFile->saveConfig('synced')
    #2 {main}
      thrown in /home/.../public_html/.../wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php on line 47
    [16-Apr-2

    Hello?

    Sorry, there is multiple fatal errors caused by different things, including Autodescription and Wordfence plugins. Nothing looks directly related to Sublangauge. I can’t help you more with this.

    @maximeschoeni @max345 well, thank you…
    However, none of those Fatal errors are shown now, as I was trying to solve some things. Now I only receive this, and I guess is related to Sublanguage:

    [29-Apr-2019 11:30:34 UTC] PHP Warning:  Missing argument 2 for Sublanguage_current::translate_post_title(), called in /home/.../public_html/.../wp-includes/class-wp-hook.php on line 286 and defined in /home/.../public_html/.../wp-content/plugins/sublanguage/class-current.php on line 887
    [29-Apr-2019 11:31:05 UTC] PHP Warning:  Missing argument 2 for Sublanguage_current::translate_post_title(), called in /home/.../public_html/.../wp-includes/class-wp-hook.php on line 286 and defined in /home/.../public_html/.../wp-content/plugins/sublanguage/class-current.php on line 887
    [29-Apr-2019 11:33:21 UTC] PHP Warning:  Missing argument 2 for Sublanguage_current::translate_post_title(), called in /home/.../public_html/.../wp-includes/class-wp-hook.php on line 286 and defined in /home/.../public_html/.../wp-content/plugins/sublanguage/class-current.php on line 887
    [29-Apr-2019 11:39:15 UTC] PHP Warning:  Missing argument 2 for Sublanguage_current::translate_post_title(), called in /home/.../public_html/.../wp-includes/class-wp-hook.php on line 286 and defined in /home/.../public_html/.../wp-content/plugins/sublanguage/class-current.php on line 887
    [29-Apr-2019 11:44:08 UTC] PHP Warning:  Missing argument 2 for Sublanguage_current::translate_post_title(), called in /home/.../public_html/.../wp-includes/class-wp-hook.php on line 286 and defined in /home/.../public_html/.../wp-content/plugins/sublanguage/class-current.php on line 887
    [29-Apr-2019 11:47:05 UTC] PHP Warning:  Missing argument 2 for Sublanguage_current::translate_post_title(), called in /home/.../public_html/.../wp-includes/class-wp-hook.php on line 286 and defined in /home/.../public_html/.../wp-content/plugins/sublanguage/class-current.php on line 887
    [29-Apr-2019 11:49:36 UTC] PHP Warning:  Missing argument 2 for Sublanguage_current::translate_post_title(), called in /home/.../public_html/.../wp-includes/class-wp-hook.php on line 286 and defined in /home/.../public_html/.../wp-content/plugins/sublanguage/class-current.php on line 887
    • This reply was modified 6 months, 2 weeks ago by  manoleixon.

    This warning is thrown in Sublanguage because it filters a function that is called (from somewhere else) with an incorrect number of arguments: as you can see there is actually 2 arguments for this functions, so it can’t be fixed in Sublanguage.

    apply_filters( 'the_title', string $title, int $id )
    (https://developer.wordpress.org/reference/hooks/the_title/).

    Also this problem is probably not the reason why you got a 500 code error.

    @max345 thank you! So, what do you recommend me to do, knowing that the problem is caused by plugin Pods? (@jimtrue)
    I suppose this because when I deactivate Pods, Sublanguage works properly.

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘Problem with Pods: 500 – Internal Server Error’ is closed to new replies.