-
Posts
-
I’m getting that error from Google for this page: https://takeasmoke.com/wp-content/themes/enfold/framework/avia_framework.php
I am using EnfoldVersion: 4.5.7 and Enfold ChildVersion: 1.0
Any ideas on how to fix it?
Thanks,
LiseHey lisetyrrell,
Please send us a temporary WordPress admin login and login URL so that we can have a closer look. You can post the details in the Private Content section of your reply.
Best regards,
RikardHi,
I just checked and there are a bunch of errors on the error_log. I’ve pasted a few lines from the errors for 6-23-19 below.. It seems like they all have to do with enfold. I use the child theme.
[23-Jun-2019 00:01:27 UTC] PHP Warning: Creating default object from empty value in /home/fwkhlkfw/public_html/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/asset-manager.class.php on line 693
[23-Jun-2019 00:01:27 UTC] PHP Warning: Creating default object from empty value in /home/fwkhlkfw/public_html/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/asset-manager.class.php on line 693
[23-Jun-2019 00:01:27 UTC] PHP Warning: Creating default object from empty value in /home/fwkhlkfw/public_html/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/asset-manager.class.php on line 693
[23-Jun-2019 00:01:27 UTC] PHP Warning: Creating default object from empty value in /home/fwkhlkfw/public_html/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/asset-manager.class.php on line 693Thanks,
LiseHi,
The error you are getting from Google on /wp-content/themes/enfold/framework/avia_framework.php
is because this php file can’t be accessed directly.
This occurs sometimes when Google is indexing a site, the best solution is to add the disallow rule to your robots.txt like this:User-agent: * Disallow: /framework/As for your error /asset-manager.class.php this is typically created by a plugin conflict, please try disabling your plugins one at a time to isolate the problem plugin.
Best regards,
MikeI, too, am getting this error on a few files. I followed Mike’s instructions above regarding the robots.txt file and the number of erroring files went from 46 to 3. Very nice. However, two of the three are the /wp-content/themes/enfold/framework/avia_framework.php files – one HTTP and one HTTPS. The robots.txt edit didn’t fix them. There’s also /wp-includes/sodium_compat/src/Core32/Curve25519/H.php which is generating this error. I spoke with my web host and they said they couldn’t turn on the sodium extension (whatever that is) because I’m on a shared server plan.
Anyone have any other solutions? I’d love to get my error file count down to zero. :-) Thanks in advance.
Hi,
@ashforthmarketing I don’t have any experience with/wp-includes/sodium_compat/and this is the first time I’ve heard of it, but in my research, I found that it could be related to a 32-bit server, here is the WordPress Core Bug Report for WordPress v5.2 and it was marked “fixed” with that version.
Are you still using WordPress v5.2? I don’t fully understand it, but here they say:
The sodium_compat library can be very slow for certain operations on 32-bit architectures, which can lead to web server timeouts while attempting to verify an update.
and the solution is: Upgrade/Install: Don’t run signature verify on slow 32-bit systems.
Perhaps that is what your webhost is referring to when they say they can not do it on your server? I don’t know.
If it was me, I would try a new WordPress install on a testing sub-domain and see if the error continues, my thought is that the error has fixed but upgrading from this version on a 32-bit server will continue the error, where a new install will solve.
This is just a guess, and I can not spend a lot of time on a non-Enfold issue, as our support queue is very far behind right now, but I hope this helps. Thank you for your understanding.Best regards,
MikeThanks for your thoughts, Mike. I’m actually more interested in your help with the Enfold avia_framework file I referenced. Any ideas on how to fix the error related to that?
Hi,
In this thread from 2019 the user had two issues going on, one was the Google search results and the other was their server error log from v4.5.7
So I’m not sure which one you are referring to because the avia_framework.php showing on google is solved by the robots file, only if google chooses to obey the robots file, and the error log error for asset-manager.class.php is typically a plugin conflict for an old version, but it could be something else I guess?
If this is the case then re-opening someone else’s old thread is not the best approach because we would need a lot more info and posting your admin and ftp login here would be a security risk.Best regards,
Mike
- You must be logged in to reply to this topic.