micsu

Hi!

Yeah, thanks!
Got rid of the problem with the beta version.

Just to clarify, I meant that while the executed script file is responsive-menu.php in script root directory, that includes ‘app/bootstrap.php’, the current working directory is still the plugin root dir, right?
Then through the inclusion of boostrap.php, it tries including ‘autoload.php’.

Sorry bout keeping talking about this, I’m still just trying to make sense why I get the error and other people don’t (and based on my current inclusion logic thoughts, more confused about why it works for the others).

Thanks for the fix to be and sorry about the trouble.

Yeah, I do realise that I’m the only one having this problem.
I just don’t understand why.

I have seen no documentation that PHP inclusion paths would work in WordPress relatively to the file it’s included from.
Inclusion happens relatively to the executed script file and directories defined in include_path.

It doesn’t really matter that autoload.php and bootstrap.php are in the same directory while bootstrap is included from parent directorys responsive-menu.php script with ‘app/bootstrap.php’.

The inclusion for autoload.php is checking the parent directory (plugin root directory) and include_path.

Should the <plugin dir>/app be defined especially in the include_path or do you have some config magic that follows the relative includes through files (without escpecially usign: include(dirname(__FILE__)./included_file.php’)) ?

I’m not that familiar about how WordPress works but just a thought:
In DOCROOT/wp-content/plugins/responsive-menu/responsive-menu.php file bootstrap is required by line:
require_once ‘app/bootstrap.php’;
Then, in DOCROOT/wp-content/plugins/responsive-menu/app/bootstrap.php the autoload is loaded with:
require_once ‘autoload.php’;

Now, these both are the first lines of actual code in both files, so it should start with this plugin by running:
require_once ‘app/bootstrap.php’; -> require_once ‘autoload.php’;
Due to inclusions, the cwd for both cases is DOCROOT/wp-content/plugins/responsive-menu/ and that’s why autoload.php won’t load and that results the fatal errors.

Unfortunately I can’t give you access to the site, while it’s the companys WP and I’m just the guy maintaining it. It’s located at https://blog.appelsiini.fi/ but I’m thinking that doesn’t give you a lot.

The WP is a network installation with just one site using this plugin.
The theme used is a custom made child template for Responsive Theme.
I’ve also included TGM Plugin Activitation to this child theme and it requires Responsive menu plugin as well as 6 others (7 if you count one custom made author detail expansion plugin).

I also think this is very weird issue as it appeard so suddenly, without updates in this plugin or wordpress.

Thanks for the response!
I actually had the configuration correctly in <Directory …> but it was redefined inside <VirtualHost ..> and it was missing Options MultiViews there.

Got rid of that whole redefinition and it doesn’t seem to be giving this log anymore.

Nope, this ain’t resolved on plugins side.
Got the same 500 fatal error and same custom fix saved me

Yeah, I’ll inform about that after next update.
Currently running with that fix of mine

Thanks for the response.
This is indeed quite odd issue, while it appeared at the time described above and no updates for this plugin or WP core seems to be made then.

I’ve currently disabled automatic plugin updates but I’ll have to check whether the next update for the plugin will fix this issue or not.

Not sure what could’ve caused this but my custom fix is as described above. Maybe you’ll add something similar if can’t find the reason for the require path there to be invalid?

I changed the line:
require_once ‘autoload.php’;
to:
require_once plugin_dir_path( __FILE__ ).’autoload.php’;
from /var/www/html/wp-content/plugins/responsive-menu/app/bootstrap.php (that’s what should be in the topic) and it seems to be working.

First time this error’s in log is at Tue Dec 29 06:55:02 2015 (UTC+2)

Yeah, I have automatic updates for plugins enabled.
Sometimes it seems to not have readme.txt files updated so I restore to original file manually. But the problem is when the file is up-to-date and Wordfence’s saying it’s not.

If I understood correctly, the problem’s with the “Immediately block the IP of specific usernames” feature. I’m having the same issue.
I have e.g. “admin” username as such specific username but still I see from the live feed that the same IP’s been trying with that username for something between 20 and 100 times within a minute or such.
Not sure if this is due to some delay in blocking that IP but that’s a bit confusing while the IP should be blocked the first time. I’ve the “How long is an IP address blocked when it breaks a rule” set to 30 minutes.

Thanks for your reply. The commenting layout should always include captcha while I’m using custom created theme. I tried with false captcha answer on the blog and it got blocked successfully. I have both numbers and words checked in the captcha complexity settings. Now I also unchecked the box “Hide CAPTCHA in Comments form for registered users” but don’t think that should matter in this case. I’ll try the Limit Attempts plugin but I already have Wordfence for brute-force login attempts so I’ll hope they work together.

I have the same problem as LChief. Been getting a lot of spam comments last month or two. Maybe the encryption for result could be made more complex or changed somehow to prevent these ?