Nate Reist

After reading the next support thread here, I believe I may have a solution:

add_filter( 'relevanssi_live_search_add_result_div', '__return_false' );

I’ll give that a shot and mark this resolved for now, sorry to bother you.

Confirmed it works in local testing for me as well! When do you anticipate a public release of this patch?

For what its worth, it fails out in the shortpixel Replacer class (method replaceContent) while looping over the post meta from beaver builder (meta_keys _fl_builder_data and _fl_builder_draft) which is serialized. It ends up passing back corrupted serialization like this: https://www.dropbox.com/scl/fi/mjwlmq0zz1lt5msh4izec/Screenshot-2023-09-20-at-1.40.34-PM.png?rlkey=ruijp5fytc1pz5n46r123ct5i&dl=0

Since this is could lead to a significant amount of data loss is it possible to exclude those meta_keys from this process with a filter or anything until this issue is resolved?

Also @sky4est, I found that in beaver builder you are able to restore previous versions of the page and it will restore the modules for normal editing

• This reply was modified 1 year, 6 months ago by Nate Reist. Reason: Spelling correction and more data

@sky4est @sixaxis I’m also experiencing this issue when replacing a file. Beaver Builder is installed on this site as well:

https://www.dropbox.com/scl/fi/m16zcl97eumnvaryxp47f/replace-bug.png?rlkey=cj2t83h9r88we1gpd5ciwfew2&dl=0

@chetan0987 It’s possible the other plugin removes the button as it is added with a filter.

Did you try using the shortcode or just leaving the filter activated?

It is also possible that these plugins are not compatible at all, since the Password Protect WordPress Lite plugin rewrites the password functionality from WordPress.

Looks like the latest update fixed this bug! I’m closing this thread.

Thanks YIKES, Inc.!

I would think most likely this has to do with the servers’ expires and caching setting for HTML files.

The server has an expires header on the response for the page to expire 1 hour in the future:

Date: Mon, 04 Nov 2019 15:19:26 GMT
Expires: Mon, 04 Nov 2019 16:19:26 GMT

What that means is visitors will not get a new version of the HTML unless they do a hard refresh, or have caching disabled on their browser, like I said with developer tools.

Hi @ve7gct,

Sorry to hear you are having an issue with this plugin. I tested your page and I see what you mean. If you refresh the page you are now logged out, so the plugin is working but not forcing the page to reload. I tested this with google developer tools on and the refresh of the page then happens automatically. This leads me to believe plugin is working as it should, but the caching of the HTML from your server’s caching/expire headers is keeping the web browser from downloading a new, logged out, version of the page. Developer tools can disable the cache so the browser always must download the assets (html/images/css/js) on each request.

Are you using a caching plugin or any .htaccess caching rules? If so, I would suggest disabling those and testing again to see if the issue is resolved.

I’m going to close this topic since it has been a month with no reply, please re open if you need more help.

Hi @chrisev,

Sorry to hear you are having issues with the plugin. To help me troubleshoot the issue, can you answer a couple things? Have you recently change themes, plugins, or anything else about your site? I’ll need to actually test the logout functionality and see what is occurring. Can you provide a password protected page as well as the password to access it? If you don’t want to share that private page above, I recommend create a new page for testing purposes and just send me that information.

@robertofvg18 I’m going to close this topic.

Feel free to open another one if you experience more issues.

@robertofvg18 it could also be the settings on your server for HTML page caching. The expires for the page when I load it is 7 days from now, so your browser wants to keep a local copy of the page for 7 days before loading it again. Your server could have expires headers set like this in an .htaccess or configuration file:

<IfModule mod_expires.c>
ExpiresActive on
ExpiresDefault "access plus 1 month"
<strong>ExpiresByType text/html "access plus 7 day"</strong>
</IfModule>

It is also possible that your browser is caching the page even though you’ve disabled ( since thee browser already cached the header ).

I would recommend making sure your server does not set expires headers to cache text/html.

hi @robertofvg18 it appears your server is showing a cached HTML file likely because of a caching plugin. It appears the expires header for the page HTML is 7 days, so you either need to clear your cache or use a browser tool to disable caching to see the logout screen again.

I think you would fix this by excluding the password protected page from your caching plugin ( LiteSpeed Cache ) on the setting page pictured here: https://ps.w.org/litespeed-cache/assets/screenshot-4.png?rev=1851289.

When you say members do you mean actual WordPress users? or users with a protected post password? The logout button should show on individual pages which are password protected, are all of your pages password protected or just the main page?

To share, can you create a sample page with a fake protected password and post it here?

Hi Agnes,

I’d love to try to help you out. Couple things come to mind. The sidebar needs to render shortcodes, not all widgets do that. Can you send a sample URL where you are experiencing this issue?

-Nate