Forum

Ask, reply and learn. Join the community of Akaunting.

New Discussion

After Update 2.1.15 i can't access last 2 days

Jahangir Mohammad Ali Siddique   ( User )

Commented 3 years ago

what the problem is this. last 2 days i can't access. giving 500 error.
how to fixed it can u tell me plz

SQLSTATE[42S22]: Column not found: 1054 Unknown column 'rnw_media.company_id' in 'where clause' (SQL: select `rnw_media`.*, `rnw_mediables`.`mediable_id` as `pivot_mediable_id`, `rnw_mediables`.`media_id` as `pivot_media_id`, `rnw_mediables`.`mediable_type` as `pivot_mediable_type`, `rnw_mediables`.`tag` as `pivot_tag`, `rnw_mediables`.`order` as `pivot_order` from `rnw_media` inner join `rnw_mediables` on `rnw_media`.`id` = `rnw_mediables`.`media_id` where `rnw_mediables`.`mediable_id` = 1 and `rnw_mediables`.`mediable_type` = users and `deleted_at` is null and `rnw_media`.`deleted_at` is null and `rnw_media`.`company_id` = 1 order by `order` asc) (View: /home/adibtrad/adibs.com.bd/ac/resources/views/partials/admin/navbar.blade.php) (View: /home/adibtrad/adibs.com.bd/ac/resources/views/partials/admin/navbar.blade.php) (View: /home/adibtrad/adibs.com.bd/ac/resources/views/partials/admin/navbar.blade.php)

Jhay Pqb   ( User )

Commented 3 years ago

If there's no help available, the best way is to restore (if you have a backup) :(

Rusdy   ( User )

Commented 3 years ago

Same to me. Anyone how to backup @ restore to 2.1.10?

I got this error after updating from 2.1.10 to 2.1.15

Valentina   ( User )

Commented 3 years ago

Having the same error. No idea why they put to update something that will break our sites.

Angel Roa   ( User )

Commented 3 years ago

I fixed just changing my php version from 8 to 7.4

Jahangir Mohammad Ali Siddique   ( User )

Commented 3 years ago

I have just change media table on database

Faiz   ( User )

Commented 3 years ago

They added new columns into _media and _mediables table

You can create these columns in numbered order to solve this issue.

_media table
1. media_id (primary, int)
2. company_id (index, int)
3. mediable_type (primary, index, varchar(191))
4. mediable_id (primary, index, int)
5. tag (primary, index, varchar(191))
6. order (index, int)

_mediables table
1. media_id (primary, int)
2. company_id (index, int)
3. mediable_type (primary, index, varchar(191))
4. mediable_id (primary, index, int)
5. tag (primary, index, varchar(191))
6. order (index, int)

The changes are very subtle, but causing worldwide ruckus.

Faiz   ( User )

Commented 3 years ago

Sorry, wrong column for _media table, here the real one

_media table
1. id (primary, int)
2. company_id (index, int)
3. disk (index, varchar(32))
4. directory (index, varchar(191))
5. filename (index, varchar(191))
6. extension (index, varchar(32))
7. mime_type (varchar(128))
8. aggregate_type (index, varchar(32))
9. size (int)
10. variant_name (varchar(255))
11. original_media_id (index, int)
12. created_at (timestamp)
13. updated_at (timestamp)
14. deleted_at (index, timestamp)

Thirsty Crow   ( User )

Commented 3 years ago

Faiz,
I know just enough to be able to modify my database. However, with the columns that get added that require an index, such as 11. original_media_id(index, int), I don't know which index to provide. I'm not really a DB admin, so I could use a little help making sure I point that to the correct place.

Please login or register to leave a response.

Showing 1 to 9 of 9 discussions