403Webshell
Server IP : 81.2.241.106  /  Your IP : 216.73.216.165
Web Server : Apache/2.4.67 (Debian)
System : Linux tranq-f.bakta.org 5.10.0-45-amd64 #1 SMP Debian 5.10.259-1 (2026-07-02) x86_64
User : lisky ( 1002)
PHP Version : 7.4.33
Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare,
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : OFF  |  Sudo : ON  |  Pkexec : OFF
Directory :  /var/www/lisky/wp-content/plugins/events-manager/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ Back ]     

Current File : /var/www/lisky/wp-content/plugins/events-manager//em-pro-compatibility.php
<?php
//in the event the Pro add-on is installed but fails to meet the minimum EM_PRO_MIN_VERSION, this file will be executed in case extra actions are needed
define('EM_COMPAT_MESSAGE_BE_GONE',"Only Administrators see this message. To hide critical messages and prevent this safety measure, you can add <code>define('EMP_DISABLE_CRITICAL_WARNINGS', true);</code> as a new line in your wp-config.php file."); 
if( EMP_VERSION < 2.377 && (!defined('EMP_2376_FIXED') || !EMP_2376_FIXED) ){
	//we changed some function scopes to static, so Pro must be updated or modified to prevent fatal errors and should not be activated
	//we're deactivating Pro until that happens
	global $EM_Pro;
	remove_action( 'plugins_loaded', array(&$EM_Pro, 'init') );
		
	function em_empro_lt_2376_notice(){
		?>
		<div class="error">
			<p>Due to some inevitable changes to some code in Events Manager, it is necessary to use Pro 2.3.7.7 or later. We have disabled the Pro plugin as a safety precaution.</p>
			<p><a href="http://wp-events-plugin.com/blog/2014/04/15/important-changes-to-5-5-3-and-pro-2-3-8-versions/">Click here for detailed information about this change</a>, which includes some simple instructions for fixing older versions of Pro without requiring an update. </p>
			<p><?php echo EM_COMPAT_MESSAGE_BE_GONE; ?></p>
		</div>
		<?php
	}
	if( em_wp_is_super_admin() ){
		add_action ( 'admin_notices', 'em_empro_lt_2376_notice', 100 );
		add_action ( 'network_admin_notices', 'em_empro_lt_2376_notice', 100 );
	}
}
if( version_compare(EMP_VERSION, '3.0', '<') && (!defined('EMP_3_FIXED') || !EMP_3_FIXED) ){
	function em_empro_lt_3_notice(){
		?>
		<div class="error">
			<p>Due to some inevitable changes to some code in Events Manager 6.1, it is necessary to use Pro 3.0 or later, this change affects attendee forms.</p>
			<p><a href="https://wp-events-plugin.com/documentation/v6-migration/">Click here for more information about these changes</a>, which includes a line of code you can use for fixing older versions of Pro without requiring an update. </p>
			<p>You can remove this specific critical message by adding <code>define('EMP_3_FIXED', true);</code> to your wp-config.php file.</p>
			<p><?php echo EM_COMPAT_MESSAGE_BE_GONE; ?></p>
		</div>
		<?php
	}
	if( em_wp_is_super_admin() ){
		add_action ( 'admin_notices', 'em_empro_lt_3_notice', 100 );
		add_action ( 'network_admin_notices', 'em_empro_lt_3_notice', 100 );
	}
}

Youez - 2016 - github.com/yon3zu
LinuXploit