linux4me2

Thanks @anastas10s, I wanted to make sure I wasn’t missing anything in the Editor with the Product Catalog template.

I added the Enhancement Request here.

• This reply was modified 1 year, 7 months ago by linux4me2.

Thanks @anastas10s, it must be something else in my setup. I will mark this as resolved, as it doesn’t appear to be a bug, and post back if I find a fix.

Same here. Of 10 sites, 5 gets disconnected every time the sync goes on. plus, it shows updates for some sites, but cannot do them.

@wp800s

If you deactivate/activate the child plugin, then reconnect from the MainWP Dashboard, you should be good to go again. I’ve now done that on about 12 of 20 sites, and now everything is working as it should again.

I don’t mean to hijack this thread, just adding info since I’m experiencing the same issue and submitted a ticket as requested.

I tried deactivating and reactivating the child plugin on one site that was experiencing the disconnection on syncing/attempted plugin updates, and reconnected it via the Dashboard. The Dashboard reported it was reconnected successfully, but the child site still showed the warning saying it was not connected, despite clearing the browser cache and reloading the page.

The fix was to attempt to resync via the Dashboard after the Dashboard reported the disconnection, which then reported the child site was not connected. I reconnected again, and now I can sync that site without it disconnecting, so it appears to fix the issue with the disconnects.

I tried deactivating/reactivating another problem site, and was able to get it reconnected and syncing as well.

Hi @brisch, it’s really nice to hear that you love my plugin. If WordPress drops the classic menu system, which Menu In Post relies on, supporting it would be difficult, but for now, I am continuing to keep it updated.

I recently added the capability to bring the classic menu system menu entry back to the Appearance menu when using a block-based theme that hides it, and yesterday I released a version with some PHP 8.2-compatibility fixes, so I have not given up on it yet.

Hi @jordesign

The workaround @damen02 came up with worked for me, so I don’t need to open a new thread. Thanks though. There’s no reason to keep this thread open for me.

If your question has been answered, we would love if you would mark this topic as resolved in the sidebar.

Thanks @jordesign, already marked it as resolved.

Hi @jordesign,

It’s interesting that you can’t reproduce it. The workaround does seem to solve the problem.

I’m not the original poster, so I can’t mark this as resolved. That will be up to @damen02. : )

Hi @thelmachido, in order to reproduce it, I have to use menus created with the old menu system (Appearance > Menus), so with an old non-block-based theme active, then activate a block-based theme like Twenty Twenty Three and attempt to import the old, classic menu into the Navigation Block and not make any changes to it before saving it and viewing it in the front end.

Hi @ninjateamwp,

I can pull up his site just fine. It looks like the problem in that regard may be on your end?

Hi @xkahn,

It sounds like what’s happening is that the Filebird Gallery plugin isn’t doing what it needs to do to get the necessary CSS file to load in Twenty Twenty Three, and by adding the regular gallery block–which does load the required CSS–you fixed the problem. I recall reading somewhere that the new block themes’ efficiency is partly due to their ability to load only the required CSS.

It does look like the developers of the Filebird Gallery need to add some code to make sure the required CSS is loaded on pages where their gallery is used.

Hi @jordesign

As much as I like these block patterns, I kind of miss the days when a theme included recommendations for image sizes.

As a rule of thumb I would say you could consider something like this:

• For patterns/block which are going to be content width or ‘wide’ width – 1200px is probably great.
• For patterns/blocks which are going to be full width – you could go up to something like 1800px wide – but i’d find a balance between that resolution, and the file size ??

That’s really helpful. I think what I’ll have to do is take it on a pattern-by-pattern basis, and maybe do some Pagespeed testing with different image/file sizes to see what I can manage.

Hi @qtwrk,

I got the message back from Google that the snippet you gave me for my .htaccess fixed the problem, so I’m going to mark this as resolved.

Thanks again for the help.

Hi @thelmachido,

I’m not working with a specific pattern yet, just preparing to do so on a site I’m converting to TT3 which will use several of them.

I actually saw that article when I was searching. It really doesn’t address full-width pattern block images, and the largest it discusses that I saw is 1200 x 675. I think that will work in most of the patterns I’ve previewed, but some will be larger than that on the crazy high resolution monitors, I believe.

If I use WEBP images, I can probably get away with using something a little larger, just in case.

I may be overthinking this. : )

Hi @damen02,

The solution was picking a menu item in Editor, changing its label, and then Save. Now the old classic menu is converted to a new navigation block and “Shows perfect on front-end”. That’s all.

Nice work!

It does sound like there’s a bug in the Navigation block.