kinggrizzly

Hi Joost,
I’ve been working my way back to this. I don’t like being a 1-star reviewer for you! I’ll get a support ticket going soon to see if we can get this sorted out. Thanks for checking in.
Brian

Thanks Niklas,
I’ve submitted a ticket and am happy to update this rating with some help.
Brian

Thank you @sc0ttkclark and @rainbowgeek!

Sure thing, thanks for the great tool and support!

@rainbowgeek I can confirm commenting out line 837 in SEO Press Pro inc/redirections.php does seem to fix the problem:

//Force WP to display 100 redirects per page
//update_user_meta(get_current_user_id(), ‘edit_seopress_404_per_page’, ‘100’);

Thank you!
Brian

• This reply was modified 2 years, 10 months ago by kinggrizzly.

Excellent, thank you and good luck!

Thanks Scott,
I think I found the conflict: SEOPress Pro 5.3.1.

This host doesn’t have a commit list, but I think 2 or 3 plugins may have had updates: Elementor Pro, SEOPress Pro and WP Rocket. When I disable those three I am able to activate Pods. I can enable WP Rocket and Elementor Pro fine, but SEO Press causes the site to throw a fatal memory error.

Disabling Pods fixes it. I may try to rollback SEOPress temporarily. As an FYI, the error looks like:

`Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 4096 bytes) in site/public_html/wp-includes/class-wp-query.php on line 1073

Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 1052672 bytes) in site/public_html/wp-includes/class-wp-hook.php on line 109′

Is this helpful? Thanks!
Brian

I’m having the same issues on multiple sites with and without this plugin. The issue appears to be with my ACF posts. They set some Rewrite values which make post widget pagination fail for Extras, Ele Skin, and more. If I turn off the rewrites, pagination works but then the urls are hideous.

These are my only clues right now and I’m not sure how to solve. Issue may be with Elementor and ACF?

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

I can confirm the same behavior. The page either reloads with blank content or reloads with the password prompt again.

This worked previously.

We are running an Elementor shortcode widget. Thanks!

Thanks @unixalberto . I’m experimenting with Autoptimize. In the meantime, it looks like WPRocket is working on a way to accommodate Pantheon’s caching: https://github.com/wp-media/wp-rocket/issues/1747#issuecomment-623733800

I successfully created the symlink by removing the source folder and creating the target folder (which is probably what your directions meant!). However, when I configure WP Fastest cache it throws this error when I try to save:

Warning: symlink(): File exists in /srv/bindings/27d55c758f184a5ea4c167e27a4d4be0/code/wp-content/plugins/easy-symlinks/includes/lib/class-easy-symlinks-functions.php on line 128

Warning: mkdir(): File exists in /srv/bindings/27d55c758f184a5ea4c167e27a4d4be0/code/wp-content/plugins/easy-symlinks/includes/lib/class-easy-symlinks-functions.php on line 211

@unixalberto

• This reply was modified 4 years, 7 months ago by kinggrizzly.
• This reply was modified 4 years, 7 months ago by kinggrizzly.

No, was I supposed to create the target folder? I think I did it backwards and created the plugin cache folder instead of the target.

Any idea if this will make WP Fastest Cache or WP Rocket work on LIVE on Pantheon? Thanks!

Hi Carl,
I seem get an error when attempting to add a symlink:

Warning: symlink(): File exists in /srv/bindings/27d55c758f184a5ea4c167e27a4d4be0/code/wp-content/plugins/easy-symlinks/includes/lib/class-easy-symlinks-functions.php on line 128

Warning: mkdir(): File exists in /srv/bindings/27d55c758f184a5ea4c167e27a4d4be0/code/wp-content/plugins/easy-symlinks/includes/lib/class-easy-symlinks-functions.php on line 211

Any idea what this means?

Secondly, should I expect WP Fastest Cache or WP Rocket to work on Pantheon if I use this plugin? I’m under the impression most caching plugins don’t work on Pantheon because they fight against Pantheon’s caching.

Thanks for any help!

+1 I got this after updating WooCommerce PayPal Checkout.

constant WC_VERSION - assumed 'WC_VERSION' (this will throw an Error in a future version of PHP) in .../wp-content/plugins/woocommerce-gateway-paypal-express-checkout/includes/class-wc-gateway-ppec-plugin.php on line 138