krmarshall87

Awesome, as I had noticed this as well!

Unfortunately the answer to this questions I have no control over, but 5.4.45. Reading your requirements page, I do see you recommend 5.6. I have requested my host to upgrade, but they are a small company and have a hundred other sites that they host and are hesitant to upgrade- somewhat understandably, but that what a test environment is for..

I have re-enabled Wordfence. I have noticed just toggling it resolved another issue I had with the redirect after admin login (had 500’d rather than 302). Since it is a FATAL error, I guess I will see if it crashes the site in the next month or so. That is about the frequency- only recently got access to the PHP log to troubleshoot.

Is file_exists() a newer WordPress function? I know some plugins have had to make backward compatibility changes for 5.4 about a month ago.

Or a better question, since I don’t have access to the root dir of the site install, what is the case that the plugin would enter this section of code so that I can attempt to prevent it.

Thank you for your help!

Thanks @richardgabriel! It looks like that has probably done the trick! No errors since the upgrade. Really appreciate this!

Wanted to see if this problem was re-addressed as it is not resolved. With multiple entries dozens an hour, it clusters the log for any real problems. Thank you!

I think this issue still exists:

PHP Warning: Invalid argument supplied for foreach() in ...\wp-content\plugins\staff-directory-pro\gold-framework\staff-directory-plugin.settings.page.class.php on line 930

The line number has changed since version changes, but you can tell that it is still the end of the file. To be specific:

	function add_extra_classes_to_admin_menu() 										
	{										
		global $menu;									
		foreach( $menu as $key => $value ) {			<-- HERE						
			$extra_classes = 'company_directory_admin_menu';								
			$extra_classes .= $this->root->is_pro()								
							  ? ' company_directory_pro_admin_menu'				
							  : ' company_directory_free_admin_menu';				
			if( 'Company Directory Settings' == $value[0] ) {								
				$menu[$key][4] .= ' ' . $extra_classes;							
			}								
		}									
	}										

I still have bots smart enough to try /login as well. Is it possible to make that value variable? Without yours checked, I confirmed that my wp-login.php is already disabled.

Let me reword or at least account for my experience with the bug.

If a plugin is already assigned a group and then a user goes back to unassign it, while at the same time assigning a new group, then in some cases, rather than unassigning the old group, it will double-assign it to the plugin, along with assigning the other group that was checked. Sorry for the long conditional sentence.