huppbrian

I spoke too soon. Re-enabling the REST API did NOT resolve the issue after all. I’m not sure why it was working for a while, but I still have the same issue.

Note that in the meantime, I have migrated from dynamic Login/Logout menu items set up in the ASE plugin to similar dynamic menus set up with the UsersWP plugin and I’m still having the same issue when Litespeed is activated. Deactivating Litespeed resolve the issue.

FIXED – I had disabled the REST API in the Admin and Site Enhancements plugin. After restoring the REST API everything works as hoped for. Sorry to bother you. Please mark closed.

Yep. That’s why I think I must have something configured wrong. Does the plugin have the capability to generate a settings dump file for review?

Here’s the info you requested (all with browser cache disabled):

New visit to home page and also after login…

Response Headers

x-litespeed-cache: hit

Request Headers

Cache-Control: no-cache

No x-litespeed-cache-control in either case.

After page refresh following login…

Response Headers

cache-control: no-cache, must-revalidate, max-age=0, no-store, private

x-litespeed-cache: miss

x-litespeed-cache-control: private,max-age=1800

Request Headers

Cache-Control: no-cache

Just to make sure I understand, you want me to check these fields…

1. As a website visitor to the site home page
2. After clicking Login
3. After logging in (when the issue I reported is exhibited – that is the menu isn’t updated)
4. After going back to the home page (when the issue is cleared)

Do I have that right?

Could you walk me through this? Baby steps and monosyllables, please. I do want to help troubleshoot, but I’m not the brightest bulb on the string.

BTW – I have tried the various presets from Advanced down to Essentials. All exhibit the same issue.

Report Number – KZPJOHUG

Looks like the offending line is in this function…

public function getOnlyBelongsFilters( $sets )
    {
        $relevantFilters = [];

        foreach ( $sets as $set ) {
            $relevantFilters[] = $this->selectOnlySetFilters( $set['ID'] );
        }

        $relevantFilters = flrt_remove_level_array($relevantFilters);

        return $this->extractBelongsFilters($relevantFilters);
    }

   

May I suggest adding an if ($sets) before the foreach loop to cover the case where no filters have been configured. I suspect that my issue will go away once I configure some filters.

• This reply was modified 1 year, 1 month ago by huppbrian.

Sorry. I can’t reproduce the issue. I had an issue with another plugin Church Admin that has subsequently been fixed by the plugin author. Once that was done, the problem with the Litespeed update went away. For the record though the error was that the Advanced Sermons sermon archive couldn’t be found. This archive isn’t a page. I believe it is a custom post type.

So no comments from anybody at all about this, huh? I guess I must be the only one who uses this. Guess it’s back to the old “classic” block for me to regain the functionality the other blocks once had in Gutenberg. Don’t worry. We know what’s best for you. You didn’t really want this capability in the first place. You’ll thank us later.

This issue was being caused by a plugin I was using called EditorsKit. The plugin adds some rich text controls (e.g. subscript and superscript) to the <p> block context menu in the Gutenberg editor. I disabled that plugin and Gutenberg performance over the satellite is much improved. I think we can put this one to bed. Thanks for the help.

This issue was being caused by a plugin I was using called EditorsKit. The plugin adds some rich text controls (e.g. subscript and superscript) to the <p> block context menu in the Gutenberg editor. I disabled that plugin and haven’t seen the featured image dropout again yet. Of course, that doesn’t mean I won’t see it again the next time I use the editor, but in the meantime, I think we can put this one to bed. Thanks for the help.

BTW – As noted in another post, it would be REALLY nice if the Gutenberg <p> block context menu supported some more rich text options like subscript and superscript. I use these a LOT, and it’s a pain to have to put in the HTML tags manually. There are plugins available to provide these options, but as noted above, they come with issues of their own.

Right you are, Marius. It was the Yoast SEO plugin (now deactivated – soon to be deleted.
Thanks.