There’s a new build on auto-update. It’s so fresh I have yet to update my site with the new link (soon, tho). It may have an impact on the crash-while exploding partial/template.
I fielded a bunch of support last night about crashes while publishing. OK, turned out only 4 separate crashes – but one guy emailed me about 15 times.
In two of the cases, I’ll just have to dig deeper and I don’t have enough data yet to say. But in the other two, both users were running a bunch of other older plugins. Once those older plugins were removed/updated the crashes went away.
I don’t yet know which plugins were the root cause – I’ll let you know if I find out.
So the message is:
Please please please deactivate plugins you aren’t using. And help your fellow crash forum posters check that first. And update stacks, because it’s nice to have a couple quick bug fixes.
After you get your old crashy plugins out – and you’re still having problems, send your RW details over to my support link and I’ll give you a hand.
Morning, afternoon, whatever (the concept of time differences still confuses me!).
I’ve not rolled back, and this project is almost always crashing on exploding partials, so after I get a break to walk the dogs I’ll update and report back.
Quick question…
I have two files called StacksGroups.db in my addons folder. See screenshot. Are these Stacks related (opposed to stacks) and can they be removed?
Well, I rescued my project in a pruned RW, and it was working fine. I installed the latest 4.1 build 5296, via auto-update, and it starts crashing again. For now, I’m reverting to 4.0.4, which is stable for my setup and at least enables me to work on the project.
Hi TemplateRepo, seems they are FileMaker dbase files. I’ve also them - without (2). Once I played around with AirPublisher from Tim Dietrich. Here vs. 1.0.
Maybe you installed them too - two times…?
Best
Roger
Mm, hold on a mo, are you sure about that? They are clearly database files, as they’ve got a .bd extension, and if FMP is installed they will possibly use the FMP icon, but that don’t make them FMP files.
I say this as having looked a bit more, I can see I’ve also got several bookmarks.db files, which if I open it in a text editor, is clearly RW’s server bookmarks.
EDIT: Just opened one of the StackGroups files, it has reference to Yourhead plus other RW things.
Ok yes, you are right - I opened it with TextWrangler. Not connected to AirPublisher…
Inside a lot of strings to installed stacks. Last saving at the 29. Oct 2020
Roger
These store the data and organization that you have setup in the Stacks library. You can remove them but then you will lose all o your groups. There should actually only be one. The one with the 2 is probably a dup created somehow, possibly cloud sync service?
It just gets better. After spending a whole day yesterday stripping, pruning, re-installing, and starting over multiple times, this morning, the files that worked yesterday now won’t even open. RW just sits at the ‘opening’ stage, not crashed, but a never-moving progress bar. The max I waited before Force Quit was 40 mins.
These are files that were working fine yesterday, but are now useless.
Even reverting to a previous version of Stacks has not helped; it seems that the act of installing the newer version has broken RW to the point that we can’t consistently work with files that were previously fine.
@isaiah has been working around the clock to fix those crashing issues, and late yesterday he pushed out V4.1.2 . This version fixes many of those issues, including all of the ones that I had reported. Download it and give it try.
Yes, I can imagine @isaiah has been pretty strung-out – but I should say that I appreciate all his hard work and efforts, and I think all posting here do.
I have tried V4.1.2 today, but no joy; opening any file makes RW quit. Some files will quit after publishing, some will quit when selecting a page. Others will quite randomly when sat doing nothing.
I’ve managed to create a stable (mostly) setup here to edit work files, but we tested 4.1.2 with this, had to revert, and now it’s not as stable as pre-revertion. We do have many master projects, and many addons, but everything was working fine until our attempted 4.1 upgrade, which is the most frustrating part. I’m having to reverse engineer updates that I cannot access in recent files, but going on this experience, I’m concerned that newer files could become unusable.
Sorry to hear that v4.1.2 did not fix your crashing issues.
One thing that would be helpful to @isaiah is the crash reports and maybe a copy of the project that crashes on opening. You can PM him both.
Also did try disabling all plugin in RW that you don’t need and see if that makes any difference?
Lastly, you can always revert to 4.0.4 until the dust settles, but before you do that… those crash reports would really help him.
After continued faffing with two copies of RW – one with Stacks 4.04, one with Stacks 4.1.2 – two versions of a large RW project, and two Macs, I’ve managed to get the worst offending file to open and be operable.
When I opened my test project on the non-working Mac, I kept getting an error saying the particular network volume couldn’t be found. I couldn’t dismiss the error (it popped up as soon as it was dismissed), so had to force quit. BUT, I searched for the network volume (our local network has a few), mounted this before launching the project, and it was fine.
Going through the Resources pane, I can see there were multiple items referenced / added from this network volume, and RW was attempting to connect for each of these resources as the file was opening.
I’ve pruned as many local and local-network resources as I can find, replacing with warehoused items on our web server, and now it opens fine, and I seem to be able to work as normal. I have plenty of stuff to test further, so I won’t say it’s fixed yet, but it may be that requests for remote resources, or broken internal resource links, was causing my issue.
Sorry @RicardoR ; I forgot to say that I did that, although all projects combined (about six) was too much to send over our network. I did send one of our smaller project files, and the MyAddons needed for that project, but mainly in case it helped @isaiah.
My troubleshooting started from scratch, with a clean RW install, then slowly adding-back the items needed for each project. It was a tad painful, given the many items we’ve added to RW. But it was a good lesson in streamlining and pruning. (Wouldn’t it be great if RW had an InDesign-like ‘package’ feature, or an auto-enable feature that enable only the necessary stacks / addons when initially opening a project?!)
My main concern was that reverting to 4.0.4 didn’t make the file operable again; the file seemed to have been permanently altered. It’s possible a component that was installed had became damaged during the crash I suppose. As an update, some of the test files that refused to open under 4.1 still don’t open on my 4.1.2 setup, so it may be the case that there are internal project changes that affect them.
However, I think my particular crashes could be related to network assets (I just posted about this, so fingers crossed).
Hi There, My first post here but I read the forum a lot so it feels familiar.
Just want to remark that Stacks 4.1.1 worked fine for my here on High Sierra but this afternoon I updated to 4.1.2 and my latest foundation project just went completely A-Wall. Drop down menu’s, lightboxes, accordeons and any form of animation/motion of drop downs do not work anymore.
I deleted the Stacks 4.1.2. plugin and replaced it with the 4.1.1 version but no luck.
My test machine is still running HS with the latest Stacks version. I’ve got Foundation (not 6). If you want to share the project I’d be happy to open it and see if I’m getting the same issues.
Thanks for the offer but I’m not allowed to share the project. Its part of a webshop running Rapid Cart Pro.
However, I traced some of the problems back to some php issues which I resolved for now. But still have some odd behavior that RW doesn’t show me the page content of some of my pages in edit mode. Maybe this has to do with the fact I downgraded my stacks to 4.1.1. I just restarted RW and the problem is gone for now. I have to finish the site now and upgrade to 4.1.2 just to be save.
To many updates of RW Foundation, Stacks and RCP in a short time. Hard to keep.
Regarding StacksGroups.db – this is a binary file that stores the state of which things in your info-sidebar are open and which are closed (and a bunch of other similar and related user-state that’s a bit too large to be stored in the preferences file.
There’s no harm in deleting the file, it will just reset the state of your sidebar back to its default. If you have one with the number “2” in it – then somehow more than one got copied in there somehow, probably during a backup/restore or something similar. Stack’s won’t look at the second one, so you should probably just delete it.
There’s no point in trying to open the file, it’s just a binary blob of data. If Stacks were an app, I’d assign an icon to this file, but Stacks is a plugin, so I don’t get that privilege – and the Finder will apply whatever icon it thinks might be appropriate.
