Viewing 18 posts - 1 through 18 (of 18 total)
  • Author
    Posts
  • August 25, 2016 at 3:34 pm #677565
    Stephenvato

    Hi Enfold team!

    There are 3 URLs detected by Google as triggering a 500 error.
    These files are are:
    /wp-content/themes/enfold/framework/avia_framework.php
    /wp-content/themes/enfold/framework/php/inc-autoconfig.php
    /wp-content/themes/enfold/framework/php/inc-avia-importer.php

    I already called my web hosting provider and they confirmed that everyting is Ok on their side.

    Any idea on what could prevent these scripts from working as they should?
    These are small files with a few lines of code: what are they used for?

    The configuration is Enfold version : 3.7.1 / WordPress 4.6 / PHP 7.0

    Thanks in advance for you advice!

    Steph

    Hereafter the message I can find in my logs:
    “GET /wp-content/themes/enfold/framework/avia_framework.php HTTP/1.1” 500 26 “-” “Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)”
    “GET /wp-content/themes/enfold/framework/php/inc-autoconfig.php HTTP/1.1” 500 26 “-” “Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)”
    “GET /wp-content/themes/enfold/framework/php/inc-avia-importer.php HTTP/1.1” 500 26 “-” “Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)”

    August 30, 2016 at 4:38 am #679249
    Ismael

    Hey Steph,

    Thank you for using Enfold.

    Do you encounter any actual error in the theme options panel or in the advance layout builder? If those files cause errors, the theme will not load properly.

    Best regards,
    Ismael

    August 30, 2016 at 10:05 am #679300
    Stephenvato

    Hi Ismael,
    Thanks for your reply!
    No, from what I can “see”, I don’t encounter any error in the theme option panel or the advanced layout builder.
    These 2 functionalities seem OK from my point of view.

    Since I posted this topic, I can see that Google has detected a new error code 500 on August 28 on the following file:
    /wp-content/themes/enfold/framework/php/auto-updates/auto-updates.php

    Googlebot is scanning/exploring the site partially at each of its new passage, hence this new error appearing only now.
    There might be other ones showing up later until the site has been fully scanned by Google.

    However, with the thousands of php files in WordPress and its plugins, all currently detected errors are only related with Enfold framework (/wp-content/themes/enfold/framework/…). I don’t have any other errors at all detected by Google anywhere on the site.

    So even though, from my point of view, the site works well, there is something to be clarified on why Google would get back an error 500 on running these Enfold framework scripts. Maybe something to check directly with them.
    Such a great theme as Enfold and its developping team cannot satisfy with this kind of situation/statement from Google that customers might conceive as acceptable/OK with a basic free theme.

    Even if it takes a while to find out and get properly solved, I’m quite sure that Kriesi’s team will take up the challenge.

    Best regards,
    Steph.

    September 3, 2016 at 3:14 am #681512
    Ismael

    Hi,

    Thank you for the info. We will ask Kriesi and our developers to check the thread. Please wait for their response.

    Best regards,
    Ismael

    September 4, 2016 at 7:56 am #681742
    Stephenvato

    Thanks for your implication and taking this issue into consideration Ismael.

    Best regards,

    Steph.

    September 4, 2016 at 8:07 am #681748
    Stephenvato

    Below the recently updated Google status on server error code 500:

    Enfold Framework triggering server error code 500

    Thanks

    September 4, 2016 at 8:08 am #681749
    Stephenvato

    ENFOLD Framework

    September 4, 2016 at 9:05 pm #681856
    Basilis

    Hi!

    That is normal.
    Google should not be able to access those files at all, that is why you see that error.
    Nothing you have to worry about – at all.

    Thanks a lot for pointing it out although

    Cheers!
    Basilis

    September 5, 2016 at 7:58 pm #682328
    Stephenvato

    Hi Basilis!

    Thanks for your quick feed-back, I understand.
    Is there a way to make/tell Google bot not access those files ?

    If not, I will contact Google to get this status/issue resolved on their side to avoid having this error status pending on my site and showing up in Google Search Console.
    If indeed, they should not access thoses files, then at least they should not highlight them in GSC and even less expect them to be resolved!

    Please keep the thread open, I’ll get back to you with their information / action.

    Cheers!
    Steph.

    September 10, 2016 at 6:41 pm #684535
    Andy

    Hi,

    alright, we’ll wait for your response here.

    Best regards,
    Andy

    September 11, 2016 at 6:03 pm #684789
    Stephenvato

    Thanks Andy!
    I’ll come back to you as soon as possible.
    Best regards,
    Steph.

    September 12, 2016 at 7:45 am #684920
    Rikard

    Hi Steph,

    Great, we’ll keep the thread open for you :-)

    Thanks,
    Rikard

    December 10, 2018 at 10:30 am #1042976
    rotarex

    Hello, I also keep receiving prompts from Google regarding the theme files (the links are in private content section). I don’t want my website to be affected by the theme’s 5xx errors. What we have to do to stop these errors?

    December 11, 2018 at 2:13 am #1043495
    Ismael

    Hi,

    You can mark those errors as solve. If they resurface again in the console, try to block crawlers or disallow those files from being crawled in your robot.txt file.

    // https://moz.com/learn/seo/robotstxt

    Best regards,
    Ismael

    February 7, 2019 at 7:51 pm #1064283
    canadianllama

    Sorry to Hijack thread, but this is still relevant now.

    *see private content*

    Google search console is still throwing up there errors.

    Any more insight into this issue or things I can try?

    Thanks

    February 8, 2019 at 10:16 am #1064500
    Rikard

    Hi canadianllama,

    Could you try to disallow the whole framework folder instead maybe? There’s no reason for those files to be indexed at all.

    Best regards,
    Rikard

    February 8, 2019 at 7:00 pm #1064738
    canadianllama

    OK i have tried this now

    Disallow: /wp-content/themes/enfold/framework/

    Will let you know either way.

    Thank you!

    • This reply was modified 5 years, 9 months ago by canadianllama.
    February 9, 2019 at 9:00 am #1064896
    Rikard

    Hi,

    Great, please let a few days pass so that everything is updated in Google webmaster tools.

    Best regards,
    Rikard

  • Author
    Posts
Viewing 18 posts - 1 through 18 (of 18 total)
  • You must be logged in to reply to this topic.