Ben wrote
Thanks Steve, is there any test plans we can run to help you with?
Ben, just do as I am doing... Each time Steve is publishing a new dev build, install it, and test it intensively... I do not know if this gives satisfaction to Steve, but I do so.
Personnaly, each time new dev build arrive, I INSTALL TWO NEW DNN (4.5.5 and 4.7.0). On 4.5.5, I install the latest official build, and I upgrade with the new dev build. On the 4.7.0, I directly install the dev build. Then, I do some basic testing>
Finally, if everything is fine, I upgrade my PROD live website. I have 245 files in one repository, 200 in the other one, and lots of visitors. I asked my admin to test everything. New upload, editing, approbation, etc... And generally, I see the problem in live on the prod website... The test is normally performed in less than one day, which is sufficient for me to revert to the yesterday backup (taking into account any modification which arrises, comments on other pages, etc...)
This way, you help the community, and you have a tool which is working as you expect ! ;-)
Steve, I am also eager to have the release. Normally, to my point of view, the last critical point is the one concerning the new feature you included "ALL Items". If you remove the old "ALL" category, you loose the possibility to view all the items when you reach the page for the first time (of course, I have tick the "Allow users to view All files").
The last two minor problems (not bug and we can live with it - but would need a fix later on):
1/
Form.html - Editing old item with new [URLIMAGE] token
If you edit an "old item" (one with the old system of file upload [FILE]), the path for the image is not shown ... Consequently, if you edit it and you submit it, you loose the image (image not shown, no image). --> Each time you edit an old item, it is necessary to find the image you put in the past... It would be great that the system point to the image directly. Do you see what I mean ? I had a look into the database, this is due to the way it was referred in the past (to the file).
Otherwise, it would be great that you provide a SQL statement that modify the database
I am not so strong in SQL, but it is necessary to JOIN the two tables Repository and the one with "file system". To find the name of the repository file, to take the File ID, and to inject in the table repository the file ID.
2/
- When someone upload an item and the item is not approved immediately, the category in which the item is listed is used in the counting, and displayed in the dashboard.
DV