Plugin Author
Tim W
(@timwhitlock)
sounds like a silent fatal error halting further output.
I’d need further information to debug this.
Lets start with where the HTML document gets halted. How far does the page generation get?
Also, what version are of everything are you running? version of plugin, version of WP, version of PHP, etc..
it is a local environment with a vagrant setup and php 5.5.9
with latest WordPress (3.8.1) and Loco (1.4.3)
Anyway, when I wanted to look at the code, it showed everything as expected, so I came back to my timeout or overload theory. After closing some processes in the local machine, I see something now. It takes a while to load the main page, but works now. When on a subpage, the performance is no problem.
Plugin Author
Tim W
(@timwhitlock)
Are you using Vagrant synced folders? If so, this will be your problem.
With loco inspecting lots of files (as it has to) Vagrant won’t handle this unless you speed up folder syncing.
I had the same problem recently with Symfony, which uses a lot of files due to its cache. The solution was to use NFS folder syncing. Although that has its own complications.
Let me know if I can close this, as it doesn’t sound like a bug in the plugin. If you find something else out, do let me know.
You are right, doesn’t seem like a plugin bug. I did expect that, but didn’t want to miss the chance to tell you in case this might be one.
Great response time though!
Thanks
Plugin Author
Tim W
(@timwhitlock)
Cool. I’m happy to give my 2 cents and it confirms what I’d already discovered as a bump in the road when using vagrant.
For the record, Loco used to be more aggressive about caching file and folder information for better performance. Unfortunately it meant you couldn’t move files about or edit them independently, so I had to go back to doing a lot more file checks on that initial screen.
