Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted October 5, 20222 yr To reproduce the issue easily go to upload on chunk basis by adding following to your htaccess: <If "^%{REQUEST_URI} == '/files/file/*' AND %{QUERY_STRING} == 'do=newVersion'$ OR ^%{REQUEST_URI} == '/files/submit/*' AND %{QUERY_STRING} == 'do=submit&category=(.+)'$"> php_value post_max_size 2M </If> Now try to upload file larger than example 2 MB. You will notice that after submitting the upload the uploaded file record will look like follows: 189416541_filename.rar where it should be only filename.rar. System adds some sort of prefix. Can you please get a rid of the prefix please? Uploading on chunk basis is necessary in some cases when running e.g. free plan of cloud flare.
October 6, 20222 yr Community Expert There have been issues with numbers being added to file names which have been resolved in the latest releases. Please let us know if you have any issues with this after upgrading to 4.7.3
November 17, 20222 yr Author @Marc Stridgen, @Matt Isn't fixed in 4.7.4, Became even worst, every upload now gets numbered prefix. 1. Upload files 2. Submit 3. Try to download Edited November 17, 20222 yr by PatrickRQ
November 17, 20222 yr Community Expert Thank you for reporting. I have opened another bug report on this
November 18, 20222 yr Author Thanks. Hoping to get it fixed in next release. it is annoying to be in need to fix all records manually in DB after upload.
January 9, 20232 yr Author @Daniel F @Marc Stridgen I see you started working on 4.7.6. I beg you, fix this finally. Issue happens when you start upload on junk basis. Lower post max size as suggested and upload larger file. Submit it and see result. Edited January 9, 20232 yr by PatrickRQ
January 9, 20232 yr Community Expert This issue has been fixed, however since it was quite a central low level change it will be in the an upcoming feature release of Invision Community (Feb).
February 8, 20232 yr Community Expert This was resolved in the latest 4.7.7 release. Please upgrade your site to resolve this issue, and if you are still seeing any issues at that point, please let us know