4
Sorry but that might prove difficult:
All of us involved with wf-projects.com took over wf-sections with version 2.x which was a complete rewrite. None of us is really in with the old version.
Just wild guessing:
Could it be a limit in a database field? How many files are in your database? Can you upload another file if you remove an existing one first?
Also you could do the following:
Edit the file
/wfsection/admin/index.php. Look for these lines (should start around line 204)
echo ""
._AM_UPDATEFAIL."";
if (!$upload->isAllowedMineType()) echo _AM_NOTALLOWEDMINETYPE."";
if (!$upload->isAllowedFileSize()) echo _AM_FILETOOBIG."";
echo"";
Insert an additional line:
echo ""
._AM_UPDATEFAIL."";
if (!$upload->isAllowedMineType()) echo _AM_NOTALLOWEDMINETYPE."";
if (!$upload->isAllowedFileSize()) echo _AM_FILETOOBIG."";
echo "This name was created: ".$filename;
echo"";
This should add a line to the error message which gives the name wf-sections is trying to use for storing the file.
Maybe this gives a clue what happens.
(Bad thing is ... i am no programmer so i am not sure this line does what i hope it does but i think the syntax is correct. However backup or rename the original file first to restore the original condition easily)
If it does what it should ... tell us what it prints to the screen
