Skip to content
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

Issue: Database Update from 2.1.8 to 2.1.9+ #3311

Closed
LaocheXe opened this issue Jul 22, 2018 · 7 comments
Closed

Issue: Database Update from 2.1.8 to 2.1.9+ #3311

LaocheXe opened this issue Jul 22, 2018 · 7 comments
Labels
type: bug A problem that should not be happening
Milestone

Comments

@LaocheXe
Copy link
Member

So I just updated my site (sync to github) - updated the database from 2.1.7 to 2.1.8 - then 2.1.8 to 2.1.9 - says it's complete but the button to update the database to it is still available.

Next thing, I went to Preferences - Notice this:
capture1

Viewing the Image
capture2

I don't know if this was intended - use to display the images in the first screenshot.

@CaMer0n
Copy link
Member

CaMer0n commented Jul 22, 2018

@LaocheXe The thumbnail issue should be resolved. (please sync again)
For the update, please check if you have a _common_videos entry in the e107_core_media_cat database table.

@LaocheXe
Copy link
Member Author

I do not see a _common_videos entity - _common_image and _common_file

db-capture

@CaMer0n
Copy link
Member

CaMer0n commented Jul 24, 2018

@LaocheXe Thanks. Did you run the update already?

@LaocheXe
Copy link
Member Author

Yes I did

@CaMer0n
Copy link
Member

CaMer0n commented Jul 25, 2018

@LaocheXe Are you still seeing a button to update 2.1.8 > 2.1.9 ? (after upgrading from github)

@LaocheXe
Copy link
Member Author

Yes

@CaMer0n CaMer0n added the type: bug A problem that should not be happening label Jul 26, 2018
@CaMer0n CaMer0n added this to the e107 2.1.9 milestone Jul 26, 2018
CaMer0n added a commit that referenced this issue Jul 26, 2018
@CaMer0n
Copy link
Member

CaMer0n commented Jul 26, 2018

@LaocheXe Should be fixed now. Thank you!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A problem that should not be happening
Projects
None yet
Development

No branches or pull requests

2 participants