Load Balanced Instanced (such as servd.host) fail to import JSON Files.

[J-Protz]

Describe the bug

Took me a while to figure this one out - but on my local and staging environments, importing a form via the JSON Import was working flawlessly, but when I went to production, it kept giving me errors saying the requested URL didn't exist. One out of maybe 30 tries got me through and I was finally able to import the form.

Anyway, I learned through servd support that temp uploads in load balanced environments can be wonky, so they advised I made a filesystem and pointed craft to this for temp asset uploads, however this weirdly didn't seem to solve the problem either. After some investigation, it seems the JSON files get put under runtime/temp, instead of the configurable asset temp directory, so I've been unable to find a solution to get imports working.

Thanks!

Steps to reproduce

1. Use a Craft 5.8.21 instance with Formie 3.1.6
2. Make a form on your local enviroment
3. Set up a load balanced environment (on servd.host ideally, haven't tested elsewhere)
4. Export the form from local as JSON
5. Import the form on the load balanced environment

Form settings

• Multi-page form: Yes
• Submission Method: Ajax
• Client-side Validation: No
• Custom Form Templates: Yes

Craft CMS version

5.8.21

Plugin version

3.1.6

Multi-site?

Yes

Additional context

We tested making the servd staging environment load balanced, and this reproduced the issue, where previously it only happened on production. I think making the temp upload location configurable or defaulting to the asset temp location would work well.

[engram-design]

We actually piggyback off Craft's Craft::$app->getPath()->getTempPath() path, which I would've thought be fine for Servd/Craft Cloud.

Just to confirm though, are you setting the tempAssetUploadFs config setting? I can't actually see anywhere you can set the temp path otherwise anymore.

[J-Protz]

@engram-design No I didn't try it on production because it seemed to not change where the JSON files ended up locally. I can do so if you think it may resolve the issue!

[engram-design]

Just to clarify your comment - I made a filesystem and pointed craft to this for temp asset uploads - how did you do that? Formie should indeed already be using whatever Craft does, but just wanted to confirm I'm following your same steps?

[J-Protz]

I used this article! https://servd.host/docs/temp-uploads-location#craft-5 and when I tried uploading a JSON file, it was going to runtime/temp, and not the new filesystem (i checked with cyberduck). Could be on me/user error, as I'm fairly new to messing with the temp uploads.

[engram-design]

Right, it's setting the tempAssetUploadFs (either using the .env variable or the general config setting).

Should be fixed for the next release. To get this early, run composer require verbb/formie:"dev-craft-5 as 3.1.6".