We'll check this but can you find a pattern for the misidentified files? Some specific extension? Uppercase extensions?

I managed to recreate this issue.

I tried to recreate it several times and was unable to get the same results. I then started everything from fresh and discovered that after an upgrade if the system is unable to access/read the file it is marked as "other". If after this, access to the file becomes available then the file remains as "other" and is not updated to "image"

This was because I upgraded the site and then after trying to display/render the front end I realized I never transferred the images over from the old version root to the new. Of course after transferring the images after the site front end was rendered was pointless since by then the table file_type was already updated to "other" and now images weren't "recognized" in the filelist.

@achillis thanks for notifying even if it wasn't a problem with the upgrade process itself. Users are supposed to put all files in place before to start upgrading.

Maybe a rescan routine might be useful in cases like this, but I don't know how often users will have this problem in order to worth the inclusion of such a tool like that in the standard release. In any case, if somebody else have this very issue, the attached file contents the code to implement a new back-office cleanup tool called "Scan File objects and define file types - DB only" (see the image above).

Just take the attached file (scan_filetypes.zip) and unzip it in the root of your b2evolution site, replacing all the files contained (three).

Warning: Please consider that this hack is based on the 6.1.2-alpha release made on Apr/02/2015. For different versions, the code should be patched manually in order to avoid further issues. I encourage novice readers to ask for help before to apply this solution and always make a backup of your site, as well.

• scan_filetypes-2.zip (14 KB)

@mgsolipa thanks for this, will give it a go. I can't help to ask for a scope, when could a stable V6 be expected?

Also, perhaps the title for this post should be changed incase someone else is trying to search for the same issue regarding V6?

@achillis well, we are not really sure about the timing regarding to have a stable release of v6. There are still some urgent and important tasks that must be performed before, and also a beta testing period.

I renamed and moved the post into a different category.

Thanks.

@mgsolipa can you add this tool to SVN. It guess it won't hurt to have it in the backoffice when anyone needs it.

@achillis best guesstimate is beta in 2 weeks and stable in 1 to 2 months. The alpha works though. It just contains some ugly things we don't want to stamp as "stable" as long as we haven't removed them.