LiteSpeed Problem

[rrg92]

Description

Hello! I'm not sure if the issue is with Pods or the LiteSpeed Cache plugin.

However, I decided to open this issue because it may affect other users as well.
My WordPress was auto-installed by Hostinger, which included the LiteSpeed Cache plugin.

I never encountered any problems with Pods and LiteSpeed until I updated both plugins to their latest versions.

After the update, strange things began to happen: Pods did not list the correct entries, and editing or creating any pod resulted in too many redirect errors.

Disabling LiteSpeed resolved the issue, and Pods worked again.

The LiteSpeed versions where I noticed the problem are 6.5.1 and 6.5.2.

If you are experiencing these errors, try disabling LiteSpeed.

Version

3.2.7.1

Testing Instructions

1. Install new wordpress 6.6.2 from hostinger
2. Add pods plugin
3. try create or edit some pod

Screenshots / Screencast

No response

Possible Workaround

Disable LiteSpeed Cache

Site Health Information

No response

Pods Package

No response

[Webfronten]

I've had the same issues like you describe. For me the solution right now is to just disable object cache inside the litespeed cache plugin but I don't understand why it doesn't work with OC enabled

[ctotech-pl]

I'm on Hostinger WordPress and just came across this issue too. On a fresh WordPress install, when creating a Custom Post Type, it is stuck in an endless redirect loop.

I've had the same issues like you describe. For me the solution right now is to just disable object cache inside the litespeed cache plugin but I don't understand why it doesn't work with OC enabled.

You're right, it is the Object Cache. With LiteSpeed enabled but OC disabled, Pods works fine.

I found a solution.

Leave LiteSpeed and Object Cache ENABLED.

But on the Cache > Object Cache page, find "Cache WP-Admin" and set to OFF.

Note: I tried clearing cache, even tried this code suggested by ChatGPT which should run whenever Pod is Created/Edited, which is supposed to clear wp cache, but it doesn't work; looks like the Object Cache doesn't get cleared.

// Hook into Pods post-save action
add_action('pods_api_post_save_pod_item', 'clear_litespeed_object_cache', 10, 3);

// Clear the object cache for both new and edited Pods
function clear_litespeed_object_cache($pod, $is_new, $data) {
    wp_cache_flush();
}