veggroups

The problem may be that you are now passing the ‘scope’ argument through sanitize_text_field, but it’s an array. Instead you should sanitize each array element of the scope REQUEST.

Some ideas are listed here:
https://wordpress.stackexchange.com/questions/24736/wordpress-sanitize-array

I also have this issue. Happens with 4.3.0 of the plugin, possibly other versions.

In my case, I have a page set to bypass the cache based on a Cloudflare Page Rule. But when I am logged in as an admin and visiting the page Cloudflare is caching it even thought it says it shouldn’t be.

From the response headers:

Logged in, but passing POST data to the page:
cf-cache-status: DYNAMIC
cf-edge-cache: cache,platform=wordpress

Logged in, but not passing POST data to the page:
cache-control: no-cache, must-revalidate, max-age=0
cf-apo-via: origin,page-rules
cf-cache-status: BYPASS
cf-edge-cache: no-cache

Logged out, and passing POST data to the page:
cf-cache-status: DYNAMIC
cf-edge-cache: cache,platform=wordpress

Logged out, and not passing POST data to the page:
cf-apo-via: origin,page-rules
cf-cache-status: BYPASS
cf-edge-cache: cache,platform=wordpress

• This reply was modified 3 years, 8 months ago by veggroups.

Explanation posted by the WordPress team:
https://www.ads-software.com/news/2020/10/wordpress-5-5-3-maintenance-release/

Explanation of what happened has been posted by the WordPress team: https://www.ads-software.com/news/2020/10/wordpress-5-5-3-maintenance-release/

I had this issue also. And it also manifested by not being able to make a DELETE request for clearing the cache. The problem was on my server. My host was blocking those HTTP requests.

Ask your host to modify your server config’s http_methods option to allow PATCH and DELETE.

I don’t want to disable the Events page. I want to disable people being able to go to the root of the Events permalink structure. I have my homepage set up as the Events page, but people can still go to /events/ and get a blank page because all events are structured like /events/page-title.

• This reply was modified 4 years, 1 month ago by veggroups.

Hey Marcus,

I’m not sure if this issue and solution is related or not.

I compared an older version of Events manager with a newer one. And in em-datetime.php, in the il8n function a new else was added to the if statements to call wp_date() in more recent versions of Events Manager. That works okay if an event has a timezone set like Los Angeles, but if it’s set to something like UTC-7 then wp_date() assumes the time is UTC and takes off 5 hours. In the case where an event has something like 5PM set, we want it to stay 5PM and not become 12AM. I’m not sure why it takes off 5 and not 7 hours.

Commenting out that else statement that calls wp_date() solves the problem for me.

if( !function_exists('date_timestamp_get') && $this->timezone_manual_offset !== false ){
			//PHP < 5.3 fallback :/ Messed up, but it works...
			$timestamp = parent::format('U');
			$server_offset = date('Z', $timestamp);
			return date_i18n( $format, $timestamp - ($server_offset * 2) + $this->getOffset() );
		}else{
			return date_i18n( $format, $this->getTimestampWithOffset(true) );
		}

versus

if( !function_exists('date_timestamp_get') && $this->timezone_manual_offset !== false ){
			//PHP < 5.3 fallback :/ Messed up, but it works...
			$timestamp = parent::format('U');
			$server_offset = date('Z', $timestamp);
			return date_i18n( $format, $timestamp - ($server_offset * 2) + $this->getOffset() );
		}elseif( function_exists('wp_date') ){
			return wp_date( $format, $this->getTimestamp(), $this->getTimezone() );
		}else{
			return date_i18n( $format, $this->getTimestampWithOffset(true) );
		}

• This reply was modified 4 years, 3 months ago by veggroups.
• This reply was modified 4 years, 3 months ago by veggroups.

Submit your issue at the github page if it’s not already documented:
https://github.com/cloudflare/Cloudflare-WordPress/issues

Have you seen the github page and submit your issue there if it’s not already documented:
https://github.com/cloudflare/Cloudflare-WordPress/issues

See the github page for help and submit your issue there if it’s not already documented:
https://github.com/cloudflare/Cloudflare-WordPress/issues

See the github page and submit your issue there if it’s not already documented:
https://github.com/cloudflare/Cloudflare-WordPress/issues

See the github page and submit your issue there if it’s not already documented:
https://github.com/cloudflare/Cloudflare-WordPress/issues

See the github page and submit your issue there if it’s not already documented:
https://github.com/cloudflare/Cloudflare-WordPress/issues

What is the error you saw? And what errors do you see now?

Have you tried uninstalling other plugins? What else do you have activated?

Do you have debugging turned on in WordPress to see error messages? Add this to your wp-config.php file:

define(‘WP_DEBUG’, true);