I’ve noticed an error message on an WordPress install which is using custom paths for the location of WordPress core. In this case the site is using the composer template project Bedrock by Roots.
The error is a 500 internal server error while requesting the following file:
I think the reason behind the fault is line 4 in the file, but it just a guess.
require_once( explode( "wp-content", __FILE__) . "wp-load.php" );
In Bedrock wp-load is located on another location:
This seems to be a common issue when using WordPress with custom paths, since it’s noted in Bedrocks documentation about compability. https://roots.io/docs/bedrock/master/compatibility/
Would it be possible to create a bugfix for this?
- You must be logged in to reply to this topic.