ProxxiM

Hi wfalaa,

I’ve increased the available memory via the wp-config.php file.

At the moment I’ve configured the ‘How much memory should Wordfence request when scanning’ at 128MB, WP_MEMORY_LIMIT in diognostics is at 1024MB. If I decrease WP_MEMORY_LIMIT to 728MB, the test fails.

This is what the memory test says:

Wordfence Memory benchmarking utility version 6.3.21.
This utility tests if your WordPress host respects the maximum memory configured
in their php.ini file, or if they are using other methods to limit your access to memory.

--Starting test--
Current maximum memory configured in php.ini: 1024M
Current memory usage: 23.00M
Attempting to set max memory to 128M.
Starting memory benchmark. Seeing an error after this line is not unusual. Read the error carefully
to determine how much memory your host allows. We have requested 128 megabytes.
Tested up to 30.25 megabytes.
Tested up to 35.25 megabytes.
Tested up to 40.25 megabytes.
Tested up to 45.25 megabytes.
Tested up to 50.25 megabytes.
Tested up to 55.25 megabytes.
Tested up to 60.25 megabytes.
Tested up to 65.25 megabytes.
Tested up to 70.25 megabytes.
Tested up to 75.25 megabytes.
Tested up to 80.25 megabytes.
Tested up to 85.25 megabytes.
Tested up to 90.25 megabytes.
Tested up to 95.25 megabytes.
Tested up to 100.25 megabytes.
Tested up to 105.25 megabytes.
Tested up to 110.25 megabytes.
Tested up to 115.25 megabytes.
Tested up to 120.25 megabytes.
Tested up to 125.25 megabytes.
Tested up to 128.25 megabytes.
--Test complete.--

Your web host allows you to use at least 128.25 megabytes of memory for each PHP process hosting your WordPress site.

Harish, thank you for taking the time to answer my question, this seems to solve my problem. Thanks!

Hi Averta,

Thanks for your message. This sounds good, I’m really looking forward to this! Do you have any indication for when this update will be released?

A little update, I’ve got the verification working with this:

function upcoming_events_validation( $result, $tag) {
    //$tag = new WPCF7_Shortcode($tag);
    $name = $tag['name'];

	if (empty($_POST[$name])) {
    	$result->invalidate( $tag, "Selecteer een locatie");
	} else {
    	$result['valid'] = true;
	}
 
    return $result;
}
add_filter( 'wpcf7_validate_upcoming_events*', 'upcoming_events_validation', 20, 2);

I’m not sure what’s wrong with “new WPCF7_Shortcode($tag);”, but when it’s active I get the server error again.

The only thing missing is an explicit warning message for the input field. Can someone give me pointers on how to achieve that?

Hi gplsaver,

Hope you had a good weekend. I’ve updated to the latest version of Woo-RFQ.
The plugin suits my needs perfectly now, I’m very grateful for your hard work!

Hi gplsaver,

I’m sorry that it didn’t occur to me to enable the debug mode right away, this is what I get:

‘Warning: include_once(/cart-prices/cart-prices.php): failed to open stream: No such file or directory in /var/www/vhosts/qombine.nl/subdomains/vanelse/wp-content/plugins/woo-rfq-for-woocommerce/woocommerce/cart/cart.php on line 19

Warning: include_once(): Failed opening ‘/cart-prices/cart-prices.php’ for inclusion (include_path=’.:/usr/share/php’) in /var/www/vhosts/qombine.nl/subdomains/vanelse/wp-content/plugins/woo-rfq-for-woocommerce/woocommerce/cart/cart.php on line 19′

Update:

Things started working again after changing this line in admin.php:
‘require_once(‘/settings/gpls_woo_rfq_settings.php’);’

to:
‘require_once(‘settings/gpls_woo_rfq_settings.php’);’