It hangs on the publish and the only way I can recover is to Force Quit Elements.
For context, I am using Elements on a Mac mini M4 Pro with 64GB ram.
I can’t put my finger on what is causing the hangs. I thought it might be due to the use of nested sub-folders and so have removed all of those and all pages are now in folders at the root level except the home page.
If I cancel the publish and try and save the Elements project, I get the spinning beachball.
So I just added a Layout Component containing a grid and grid items and tried to publish that and it hung on publishing. Elements continued to exhibit this behaviour even after a restart. So I deleted the Layout Component and contents, re-published and it worked OK.
It sounds like you could be hitting a threading issue within Elements, are you able to upload the project to Elements Cloud so I can take a look at what’s happening?
@logrunner Another user reported a similar issue, and I was able to reproduce it here. I’ve added a fix for this in the next release. Hopefully, you won’t encounter the problem again.
I am having this exact problem right now. Everything had been working just fine, I was publishing, all good. Then lately it just hangs up every time I try to publish. Try to save and I get the beachball and have to force quit. My website is fairly simple, I’m not doing anything too complex. Not sure why the problems all of a sudden.
We’re looking into publishing issues again this week, @tpbradley will let you know if he needs anything from you.
In the meantime can you run through the publishing checklist, and let us know how you get on:
P.S. You should be able to export your site locally, and use a third-party FTP client to upload it. This is just a temp workaround to enable you to get your site updates online.
I publish it through Elements, like I did with RapidWeaver. Just hit publish and all good until about a week ago. Now it won’t do anything, just hangs up until I quit.
I have two other websites and have been able to update, save, and publish with both of those. So it appears that the problem is just with the one website.
