For those of you playing along at home (@Isaiah, @teefers, @robbeattie, @Fuellemann, @peterdanckwerts, @yabdab, @dan ):
https://u.pcloud.link/publink/show?code=XZWnp2XZiP3ddojYULBWzcb85wwTMVs8WvG7
But your data is stored locally, so you do not use the iCloud desktop?
Correct, this an export to a local folder.
I am not talking about the export, but of your files and documents. Are you using iCloud Drive for your documents and finder?
No…
We’ve had no other reports of this in RapidWeaver itself. As it’s only happening in FormLoom I’d probably say the issue is with the plugin. Have you contacted @yabdab about this?
You could also try starting a new project with just the FormLoom plugin and see if the issue persists. If it does, please send the project to @yabdab and myself (dan@realmacsoftware.com).
Thanks,
Dan
1 Like
Thanks everyone. I understand it’s complicated with so many working pieces. I can see why it would be a Rapidweaver publishing issue, a FormLoom publishing issue, or a combination of both. So I appreciate you all agreeing to take a deeper look.
I’ll report anything here as it comes to hand.
I’ve been using FormLoom for a very long time and I’ve never had a publishing problem, so I wonder if it might be some interaction between different plugins.
I’ve managed to recreate the issue here on my intel based Mac, so it looks like it’s not an M1 issue.
I believe this is a bug with FormLoom 4 as it’s only this plugin showing the issue.
@Custard-Apple have you emailed @yabdab directly and heard back from him yet?
Will investigate a little more here and report back.
Many Thanks,
Dan
Thanks Dan, I’ve reproduced it on Intel/Catalina now too. The project file is with yabdab, he’s going to take a look and I’m waiting to hear back at this stage.
@Custard-Apple Good news. I have a solution for you!
Okay, so myself and @tpbradley have spent the last hour or so looking into this.
At first Tom couldn’t re-create the issue, and then we narrowed it down to the fact he was using Stacks 4.2.0 — Once he updated to Stacks 4.2.2 he was able to re-create the issue!
I downgraded to Stacks 4.2.0 and the issue went away.
So it seems the issue is something to do with Stacks 4.2.2. For now, you can download Stacks 4.2 here to get back up and running.
If issues pop up like this in the future it’s always best to try and work out what you updated recently.
I’ll let @Isaiah take over from here and narrow down what the difference is between the two versions of Stacks.
Cheers!
Thanks Dan, I’ll try that. Thing is, I updated everything recently 
Hi @dan, unfortunately I can reproduce the issue with Stacks 4.2.0.
I’ve just emailed you the entire project file (I had scaled it down before). It seems to me the more forms in the project, the less reliable it becomes.
Even when I get what seems to be a complete set of files, I have issues.
See here:
I get a “timeout” when submitting the form and the emailed receipt is missing an embedded graphic – for some receipts, the graphic works.
Oh dear, I have just run the test on the new project file you sent and yeah it’s still reproducible with Stacks 4.2.0 — So perhaps it’s not Stacks after all…
I’ll go back to my initial assessment: The fact that it’s just the resource files for FormLoom 4, makes me think it’s something to do with that plugin.
Now, it could well be RapidWeaver and we’re looking into that further, but it would be good to hear from @yabdab on this issue as it’s happening with his plugin only. Other FormLoom users must be seeing this…
@Custard-Apple have you tried starting a new simple project with just one FormLoom page and seeing if the issue persists?
@dan from memory reducing the project to just one form seemed to then be OK… Problem is my entire enrolment system is now broken and it’s getting pretty urgent. 
@Custard-Apple I’m trying to help, but I can only go so far when there’s third-party plugins involved.
You really need @yabdab to take a look at this issue. We’re looking more into it here, but so far it’s looking like a third-party issue, not a RapidWeaver issue… I’ll report back ASAP.
btw. What was your set-up before this, when it was all working?
Okay… I’ve started to narrow it down…
- New FormLoom projects work just fine. I have a new site with 4 FormLoom pages and it publishes correctly every time.
- As soon as I drag over “Form_CM (new)” from your project to my working project, the publishing breaks.
Anyway, it seems to be something to do with a setting in your FormLoom plugin pages… what that is I don’t know yet.
Next step is to start deleting form elements and see if it makes a difference, and then try and revert the plugin settings back to default values.
btw. Anyone can do this kind of debugging, it just takes time. You just have to work through things methodically…
@dan I appreciate the help. I’ve just sent @yabdab the full file. I know he’s looking, but hasn’t found anything yet.
The setup which worked was Intel/Catalina/RW7/Stacks3/FL3. And in fact FL4 in that config but only with a project containing one form. FL3 doesn’t write to the rw_common folder. I actually had two multi-form projects working fine in RW7/FL3.
@dan yes, believe me I’ve been working through it. I might just have to start from scratch like you say.