Thread

ks808,

That sounds like a workable solution, since the bug is triggered by the destination being empty. Post back with your results, if you don’t mind 😊

Thanks!

Dan,

Populating the images directory with files removed the error and the Safecracker did work when selecting an existing image from the Safecracker file field drop-down.  The entry was successfully updated and successfully displayed an ajax success message.  However, when uploading a new image through the Safecracker file field from the SAEF, I get no ajax response, but the file does upload.  When I tried the file upload through the CP entry form, I still get the “Fatal Error” message posted above.  So it kind of works. =)

@ks808 - I would definitely recommend against setting your memory limit to -1. That’s a pretty unsafe thing to do, and it’s likely the cause of your fatal error depending on the security software installed on your server. Try changing that to 64MB or 128MB and see if that takes care of things. If not, let me ask that you open up a new thread about this one. Looks like it’s unrelated to the problem at hand.

@all - Everyone else taken care of? If there’s anything else we need to help with related to the issue in the initial post, let me know.

Kevin, Thanks for the suggestion.  I didn’t think setting the memory limit to a specific size would be the culprit.  It worked however! Thanks for the suggestion!

I had this same issue too and can confirm that uploading at least one item into the appropriate folder removed the issue.

However a real fix would be useful so I don’t have to have a dummy file sitting there.

Thanks!

@David - Don’t worry, we’re not considering this a long-term fix. Just a temporary workaround for now.

If anyone has continuing issues, feel free to open up a new related thread by clicking the button below.