You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and end up looking like [...] WHERE [...] (LOWER(name) LIKE 'extension') (note the field name contains the full file name, not just the extension, so this query doesn't match any rows).
I don't really have a good overview regarding the source code, so I can't tell why it's not using this logic here, which looks more correct. Maybe I might be missing something; but why is this implemented twice in different places?:
GitMate.io thinks the contributor most likely able to help you is @PVince81.
Possibly related issues are #20661 (Update), #21366 (Update), #27585 (mimetype:update-db changes a folder to "audio/*"), #22729 (Improve mimetype repair performance), and #24430 (Maintenance mode).
Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.
Steps to reproduce
run
occ maintenance:mimetype:update-db --repair-filecache
Expected behaviour
Files ending in
.extension
should have theirmimetype
field set to the configured one.Actual behaviour
The field is left untouched, because the SQL queries that run are generated by this line
core/lib/private/Files/Type/Loader.php
Line 172 in 6b36c56
and end up looking like
[...] WHERE [...] (LOWER(name) LIKE 'extension')
(note the fieldname
contains the full file name, not just the extension, so this query doesn't match any rows).I don't really have a good overview regarding the source code, so I can't tell why it's not using this logic here, which looks more correct. Maybe I might be missing something; but why is this implemented twice in different places?:
core/lib/private/Repair/RepairMimeTypes.php
Line 153 in 6b36c56
Server configuration
Operating system: Ubuntu
Database: MariaDB
ownCloud version: 10.0.8
The text was updated successfully, but these errors were encountered: