-
-
Notifications
You must be signed in to change notification settings - Fork 436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Table 'dbName.core_file_storage' doesn't exist #2614
Comments
You can search for the error with Google because there are many references over the years. In a post on Stackexchange, someone recommended creating that table in the database, if it doesn't exist. You can also go to the Backend > System > Configuration and check if there is anything stored in the database. If not just press the [Save] configuration button. I faced this problem when I switched from PHP 7.0 to 8.1 and upgrading Magento old versions to OpenMage. If I remember correctly this is how I solved it. |
Nice catch. This table does no exist in "sample date" too, but is created when you change media storage to DB. So if you migrate a shop where config is set to use DB, but the table does not exist, you may run into this error. Quick fix: got to admin section, set media storage to DB and hit "Synchronize". |
should we do something about this or not? |
We can do more but we have to simulate the issue to understand how it happens. I fixed it then but honestly speaking I didn't make it public, nor could I replicate it afterwards. Either we will have to change something in the code or mention a solution in the README file. I personally don't like the idea of creating that table in the database just to make the error disappear, I've never used the facility to store media files in the database. |
I received that error message without having the modification in the Backend as in your image. I solved it by changing the "Media Storage" value with saving then going back to the initial value also with saving. I didn't want to create the table. |
@fballiano I never had DB as media storage (nor do I really want to have it) Isn't it possible to query this setting before executing this code block (or using core/file_storage_database )? For the time beeing I just commented out the exception printing like it was before - but it feels wrong to handle it this way. /Edit: "Dummy-synchronizing" is, in my eyes, a bad idea, too. |
#2627 should fix your issue. |
I am on OpenMage 20.0.16 and PHP8.0
In the Exception.log, I see the following entries:
The requested images to not exist (as far as I checked - probably someone should do a cleanup there) - The table does not exist.
I don't really get, what the corresponding code really does? ( Starting here:
magento-lts/get.php
Line 143 in 37642ed
Can I savely ignore these Exceptions? Is something really broken? Is this code a left-over from some cleanup?
/Edit: Media is saved on the file system, not in the database.
/Edit 2: So, the same file on a 20.0.14 installation ignores this exception per comment and also does not have this table.
-> So... These questions remain:
The text was updated successfully, but these errors were encountered: