Hi Ted,
Thanks for the detailed error report - very helpful!
I'm going to look through the code now. I can't reproduce it myself, but my hunch is it's a permissions problem.
Here's the thing: by default all Export Types within the HTML/Printer-friendly Export Group generate files with the same filename: "submissions-{$M}.{$j}.html".
So, once the file has been generated, I'm wondering if subsequent attempts are simply throwing the (invalid!) error that you spotted.
Try this: on your server, take a look at the file permissions of the generated file. It's found in your Form Tools /upload folder. What is it set to? Some servers create files with something like 600 permissions, which forbids overwriting. Try deleting the file, then re-generate it through the Form Tools interface. Does that work?
Yup! That's the right way to upgrade - you did nothing wrong at all.
[EDIT: I just updated the Database Integrity module - that problem is unrelated, don't worry! The latest version of the module won't spot any (invalid) errors]
Thanks SO much! And I'm sorry for all the trouble.
- Ben
Thanks for the detailed error report - very helpful!
I'm going to look through the code now. I can't reproduce it myself, but my hunch is it's a permissions problem.
Here's the thing: by default all Export Types within the HTML/Printer-friendly Export Group generate files with the same filename: "submissions-{$M}.{$j}.html".
So, once the file has been generated, I'm wondering if subsequent attempts are simply throwing the (invalid!) error that you spotted.
Try this: on your server, take a look at the file permissions of the generated file. It's found in your Form Tools /upload folder. What is it set to? Some servers create files with something like 600 permissions, which forbids overwriting. Try deleting the file, then re-generate it through the Form Tools interface. Does that work?
Quote:NOTE ‐ to update I run the update from FT and copy over the files into the FT directory. I then get a message that says I am updated. I hope this is the correct way to apply an update otherwise please let me know and I can apply it properly.
Yup! That's the right way to upgrade - you did nothing wrong at all.
[EDIT: I just updated the Database Integrity module - that problem is unrelated, don't worry! The latest version of the module won't spot any (invalid) errors]
Thanks SO much! And I'm sorry for all the trouble.
- Ben