Maintenance mode doesn't work anymore in .50.1

require(C:\wamp\www\oekofaktumhttp://localhost/oekofaktum/_oeko_wp/bps-maintenance.php)

First try something simple: Resave your MMode options and generate/create new MMode template files. If the issue/problem is still occurring read on…

This is not a valid path above. You should not be seeing the folder path and URL path. I believe the only valid path would be this path for your WAMP site: C:\wamp\www\oekofaktum/bps-maintenance.php. Not exactly sure what would cause this on your particular WAMP setup/server. My best guess is this could be some sort of Symlink configuration issue/problem in one of your .conf files. If you made any changes to any of your .conf files then check them for configuration mistakes.

There were no changes in MMode in .50.1 that had anything related to includes, requires or file paths so either something changed on your WAMP setup or the index.php MMode template file write did not happen correctly for whatever reason on your WAMP setup.

Changes to MMode in .50.1
Maintenance Mode Accordion: Maintenance Mode Accordion created for better functionality/usability (visual display only). Code correction (affects the Login link displayed only): Maintenance Mode website name not displayed in the reminder email. Code correction (affects the visual text area only): Maintenance Mode Apostrophes/single quote code character displayed with an escape backslash.

index.php uses the __FILE__ Magic constant for the require path

if ( in_array( $_SERVER['REMOTE_ADDR'], $bps_maintenance_ip ) || in_array( $matches_three[0], $bps_maintenance_ip ) || in_array( $matches_two[0], $bps_maintenance_ip ) || in_array( $matches_one[0], $bps_maintenance_ip )) {
require( dirname( __FILE__ ) . '/wp-blog-header.php' );
} else {
require( dirname( __FILE__ ) . '/bps-maintenance.php' );
}

bps-maintenance.php uses the __FILE__ Magic constant for the include path

if ( file_exists( dirname( __FILE__ ) . '/bps-maintenance-values.php' ) ) {
include( dirname( __FILE__ ) . '/bps-maintenance-values.php' );
}

And it appears that you are doing some sort of vhost thing since this portion of the URL shows a different structure than your folder path: /oekofaktum/_oeko_wp/

.50
Bugfix/Code Correction: Maintenance Mode str_replace has been changed to dirname for GWIOD site types to get the site root index.php file path

In .50 a change/code correction was made to get the correct site path for the GWIOD root site index.php file, but after checking the code again it looks like one of the variable names was not changed to the new variable name. I will need to double check this, do some testing and confirm that this is the problem even though it looks like problem. I will post the code modification that needs to be done after testing confirmation and we will release a new BPS version with that change made permanently.

or for some strange reason the string replace is not stripping out the URL: https://localhost/oekofaktum

The code should look like this for the site root index.php file. The URL should be stripped out of the require and only the folder name/path should be in the URL/code.

if ( in_array( $_SERVER['REMOTE_ADDR'], $bps_maintenance_ip ) || in_array( $matches_three[0], $bps_maintenance_ip ) || in_array( $matches_two[0], $bps_maintenance_ip ) || in_array( $matches_one[0], $bps_maintenance_ip )) {
# BEGIN BPS MAINTENANCE MODE GWIOD
require( dirname( __FILE__ ) . '/_oeko_wp/wp-blog-header.php' );
} else {
require( dirname( __FILE__ ) . '/_oeko_wp/bps-maintenance.php' );
}
# END BPS MAINTENANCE MODE GWIOD

The format looks correct so something else is causing the problem on your local WAMP installation. str_replace is a simple PHP function that should work on every type of site so the problem is probably not with that function itself. I guess you are back to looking at your Server configuration files or something going on in your database. If it was me I would install another local test site and only install BPS and see what happens to determine if it is a site specific problem or a Server configuration problem.

I guess it could be something in your Browser too. Some sort of Add-on or extension?