A quick follow-up here.
Found an old installation (v1.0.9.2.5), same issue. Here as well: No console errors.
I have to mention that I need to make some tweaks to use Local WP in general:
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.
I installed Local WP on a different device today.
No changes were made inside the server configuration, no changes were made at all.
It took me around 30min to install the Cwicly plugin and theme, create a menu and place it inside the index template.
But I deciced to go for it, since I needed to investigate further.
Plugins: Cwicly
Themes: Cwicly
Results are the same.
Tried with Edge and Firefox.
Is there anyone who is using Cwicly with Local WP on a Windows (11) machine?
Yes I do with USBWebserver
It is quite about 5 minutes to create a new install from scratch.
It is 100% portable and very light.
Thanks for your input @weedor.
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.
ok, sorry for the mistake.
I don’t know anything about this tool. I clicked on the link and I think I will dig up a bit. I am always interested by new tools (for me). I discovered Figma like that!
Hello @Marius,
It still isn’t clear from your posts what error you’re getting.
Are you still getting this error?
Here is my console log:
Hey @Louis.
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.
I haven’t tried the menu, but Cwicly runs super fast on Local + Mac & Firefox for me.
Thanks for the feedback, much appreciated.
I think Louis mentioned as well they do use it on a daily basis without issues but I think they are on Mac as well.
Which conclusion could I draw from doing that @dranzer?
Do you think it could be a general Windows issue, rather than a LocalWP/Cwicly one?
@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.
Yes. I did notice some improvement tweaking router mode, disabling php xdebug and some more tweaks I don’t remember now. But I found Laragon to be most performant. It’s GUI consumes too low resources, more flexible and open source. GitHub - leokhoa/laragon: Laragon is a portable, isolated, fast & powerful universal development environment for PHP, Node.js, Python, Java, Go, Ruby. It is fast, lightweight, easy-to-use and easy-to-extend.
I definitely will have a look at it but to be honest I don’t have plans to change tools.
Not sure if there is even room for noticeable performance improvements.
In addition, it’s so easy to use.
Workarounds are fine but never can replace actual fixes.
Hi @Marius,
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.
Thanks for your patience.
A workaround is provided here:
Thanks for that!
Moving to fixed.
