- This topic has 14 replies, 3 voices, and was last updated 1 year, 6 months ago by Canek.
January 12, 2021 at 10:28 am #1616125Canek
I get 500 errors in 170 files in the wp-includes directory (although not all) and one in the gp-premium plugin directory.
I already contacted my host (WPX) and they tell me that the errors are caused by the gp-premium plugin. They tell me that the plugin is conflicting with some other part of the site configuration.
They shared the errors from the error log with me. I share them in the private information section along with some of the urls with the errors
Could you guide me and help me with this?January 13, 2021 at 5:33 am #1616868Canek
I just checked another website that I have with another hosting (Dreamhost) in which I also have Generatepress installed.
I checked the equivalent urls. The same files on the other site that have the 500 error, also have it on this one. So it is not a server problem.
If it is of any help, I can share the settings and plugins of the two sites, or add the 171 urls that show the error.January 13, 2021 at 5:41 am #1616878DavidStaffCustomer SupportJanuary 13, 2021 at 5:49 am #1616895Canek
Already did. It was the first thing the host asked me, but the problem continues. Also in the two sites I have different configurations and plugins.
The only plugins that are installed on both sites are:
WPForms LiteJanuary 13, 2021 at 5:54 am #1616904DavidStaffCustomer SupportJanuary 13, 2021 at 6:08 am #1616921Canek
Hello and thanks for the support.
In one it is “The optional module, imagick, is not installed, or has been disabled.” (normal notification in WPX) and on the other site there is no notification.
Among others, the same errors on the two sites are:
It strikes me that the problem is in the two sites that are very different.January 13, 2021 at 6:28 am #1616957DavidStaffCustomer Support
How old are the two sites ? As i believe that issue is related to the Old image resizer that GP used to use for the Featured Image resizing.
Can you share a screen short of the Customizer > Layout > Blog –> Featured Image settings ?January 13, 2021 at 6:35 am #1616971Canek
One is 2 years old and the other about 7 months.
I’ll send you the screen shot in a moment (let me find out how, I don’t know how to do it)
By the way, I think you also have a similar problem:
https://generatepress.com/wp-content/plugins/gp-premium/library/batch-processing/wp-background-process.phpJanuary 13, 2021 at 9:02 am #1617393CanekJanuary 13, 2021 at 9:43 am #1617438TomLead DeveloperLead Developer
If you go directly to that URL (as you linked to above), you’re going to get an error like that.
That file is used by our Site Library to run some background processes, but it’s not intended to be navigated to directly.
Are you seeing any errors on your actual website as you use it, or is this error only happening when navigating to that file?January 13, 2021 at 9:58 am #1617453Canek
It only appears when I open the url. Actually there are no problems on my sites.
I had an indexing problem in google (a lot of files were indexed from the wp-includes and wp-content/plugins/ directories).
When I made Google to crawl them again to de-index them, 171 new files in those directories appeared in Google Search Console with the error 500. When checking them directly, the error did appear.January 13, 2021 at 10:00 am #1617457TomLead DeveloperLead Developer
Individual PHP files like this should not be indexed, as they don’t have any content – they’re purely functional files.
We can add a check in that file to make sure it can’t be directly accessed, but if you have search engines indexing individual PHP files like this, you’ll want to remove them from the index and make sure there are no links to them for search engines to follow.January 13, 2021 at 10:29 am #1617496Canek
The question I have is if having 170 files in the wp-includes directory with error 500 will not cause problems for my sites later?
Or even if the following files appear with error 500, will they not cause problems and will they work well?
Some of the files are:
In case they do not give me a problem with this error later, I would be interested in adding a check in the files to make sure it can’t be directly accessed. Would they appear as 404?January 13, 2021 at 1:03 pm #1617657TomLead DeveloperLead Developer
These are all files you shouldn’t be accessing directly – there’s no reason to, and linking to them (when the links are set to follow) will index them in Google.
Your host may be able to block direct access to the files, but I’m not 100% sure.
I don’t know if it will cause issues, but it would certainly be nice to keep your error_log empty so actual errors are easier to find.January 13, 2021 at 1:40 pm #1617687Canek
Thank you very much for your support and patience.
- You must be logged in to reply to this topic.