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.

Sign up for GitHub

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

Jump to bottom

Database Test #3811

Closed
TrueHatori opened this issue May 23, 2019 · 9 comments
Closed

Database Test #3811

TrueHatori opened this issue May 23, 2019 · 9 comments
Labels
status: awaiting feedback This issue may be fixed and is awaiting the original poster to confirm the fix.

Comments

@TrueHatori
Copy link

TrueHatori commented May 23, 2019 •
edited
Loading

Can everyone tell me, what this is and how I can repair it? This is for 32 tables the same, I want not make a so big Picture.

image
@tgtje
Copy link
Contributor

tgtje commented May 23, 2019

Related or identical #3800

@TrueHatori
Copy link
Author

TrueHatori commented May 23, 2019 •
edited
Loading

Not quite. My English is not so good, but if I understood correctly, it is in xampp. For me it's about a live server.
Apache API Version 20120211, MySQL Server Version: 5.6.43-84.3-log, PHP Version 7.2.18-he.0
I do not know if that is relevant, but something should be done … ;)
And it is not a new installation but an attempt to update.
image
image

@Moc
Copy link
Member

Moc commented May 24, 2019

Are you using the latest files from Github?

@tgtje
Copy link
Contributor

tgtje commented May 24, 2019

Yes testcases are primary local, but (can be sql related for you too) If it happens local, it could indicate (hence tests) live has/gets issues too... This case similarity is to be seen in both cases...

@TrueHatori
Copy link
Author

@Moc: Whether it's the very latest, I do not know, got the last time in mid-March, all files from Github.

@Moc
Copy link
Member

Moc commented May 24, 2019

@TrueHatori In that case, I do recommend updating to the latest files from Github to make sure you have all fixes included.

Then clear your e107 cache and see if the issue persists.

@Moc Moc added the status: testing required Someone needs to confirm this issue's existence and write a test to prevent the fix from regressing. label May 24, 2019
@TrueHatori
Copy link
Author

Ok, I did, the problem is the same as before. In addition, the admin theme tabbed does not work anymore.

@Moc
Copy link
Member

Moc commented May 29, 2019 •
edited
Loading

@TrueHatori The database update message should be fixed with the latest files. Please check.

If the admin theme tabbed is still not working for you, please create a new issue with screenshot and further explanation.

@Moc Moc added status: awaiting feedback This issue may be fixed and is awaiting the original poster to confirm the fix. and removed status: testing required Someone needs to confirm this issue's existence and write a test to prevent the fix from regressing. labels May 29, 2019
@Moc Moc added this to the e107 2.2.1 milestone May 29, 2019
@CaMer0n CaMer0n modified the milestones: e107 2.2.1, e107 2.2.2 May 29, 2019
@TrueHatori
Copy link
Author

Yes, with v2.2.1 it works ;)

@Moc Moc closed this as completed May 31, 2019
@CaMer0n CaMer0n removed this from the e107 2.2.2 milestone Jun 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: awaiting feedback This issue may be fixed and is awaiting the original poster to confirm the fix.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Moc @tgtje @CaMer0n @TrueHatori