No clue if this could be related.
I know this is probably an individual issue and not Cwicly related, so I appreciate any input.
At some point, I need to get these 2 tools work together, so I start digging now.
It’s actually about Local WP, not about local WordPress installations in general.
But I do appreciate your feedback.
Well, the installation is not the issue, it takes under a minute.
There is a general problem/conflict with this tool when using it on Windows, tons of threads exist about it in their forum.
Not everyone is facing it, I think it’s still unclear what the actual issue is.
There is a workaround and I learned today that this is not linked to it which I considered in the post before.
Local WP is a great tool. It’s blazing fast and comes with a really good user experience.
I don’t know about any other tool which comes close, so I’m a bit concerned if I can ever use it with Cwicly.
It’s not only about the mentioned issue with the Menu Block here.
I need to know what’s actually going on before starting a project with this tool.
The error only occurs when the plugin is active. It is not related to the issue.
As stated earlier today, I installed Local WP on another device.
The only installed and active tools were the Cwicly theme and plugin.
The only thing i did was creating a menu and tested it inside the index template.
Nothing were changed inside the installation/server files.
No errors do appear in the console.
@Marius, thanks for the precision. Are you sure there are not any warnings in the browser console? As said further up, Gutenberg fetches editor files. If the menu and other styling options are not correctly shown in the Site Editor, this means there is some type of access issue.
@Marius I am just replying in relation to the slowness you faced with LocalWP. Many users in Bricks forum also had difficulty with speed using LocalWP on windows. Mac version had no such issue. Laragon is more performant.
We will be checking this out on a Windows environment as soon as we are able to and see if we can recreate the issue with Local WP + Windows 11.
From there, we will be able to confirm if it’s a unique situation or more generalised.