Fresh Install From Master, Why Do I Get Stuck On Login Page While URL in ../Z_UpgradeDatabase.php? #310
-
Fresh install from master, why do I get stuck on login page while URL in ...../Z_UpgradeDatabase.php? |
Beta Was this translation helpful? Give feedback.
Replies: 12 comments 8 replies
-
I also have this issue today with a fresh install. |
Beta Was this translation helpful? Give feedback.
-
This may be related to my last reply to issue #297 (#297 (reply in thread)) |
Beta Was this translation helpful? Give feedback.
-
Here is the web server error log I'm getting which appears to relate to login_data:
|
Beta Was this translation helpful? Give feedback.
-
The trouble is I'm not getting this problem. I have however done some
changes to:
install/index.php
includes/session.php
includes/header.php
I am attaching them here for people to test before I commit them.
Tim
…On Wed, 18 Dec 2024 at 19:42, Craig Parker ***@***.***> wrote:
Tim just gave me a new header.php, and while the apache error log is not
longer giving me that message, I'm still getting redirected to
Z_UpgradeDatabase.php.
—
Reply to this email directly, view it on GitHub
<#310 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAL6LE4X37XFAVZXBXUVL32GHF37AVCNFSM6AAAAABTTA2ERGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNRQHE3TGOA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
Does it matter that I'm using MariaDB? I've unzipped the new version, stuck these files where they go, and still not up and running. I did notice that whatever I stuck in for a db name, my apache error logs kept saying weberpdemo wasn't available. When I set up another instance and created a db called weberpdemo, that error disappeared. I did try commenting out the if loop (around line 236 in session.php) and didn't get any farther. Except wait! I just tried commenting that out again and now I'm sitting at a login screen. I'm going to go wipe/reinstall before I get too excited... |
Beta Was this translation helpful? Give feedback.
-
Craig, when you sent me a link earlier I was able to log in, so your
install is working, but it's that link at the end of the install to restart
that is failing.
…On Wed, 18 Dec 2024 at 21:12, Craig Parker ***@***.***> wrote:
Does it matter that I'm using MariaDB? I've unzipped the new version,
stuck these files where they go, and still not up and running.
I did notice that whatever I stuck in for a db name, my apache error logs
kept saying weberpdemo wasn't available. When I set up another instance and
created a db called weberpdemo, that error disappeared.
I did try commenting out the if loop (around line 236 in session.php) and
didn't get any farther.
Except wait! I just tried commenting that out again and now I'm sitting at
a login screen. I'm going to go wipe/reinstall before I get too excited...
—
Reply to this email directly, view it on GitHub
<#310 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAL6LC33HJ2YOJYLX5ZQN32GHQK3AVCNFSM6AAAAABTTA2ERGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNRRGA2DCMY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
@timschofield, I can't see the attachments which you mention above. Can you try attaching them again or send them by email please? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
I think I located the root issue. In the latest code there is a CREATE TABLE login_data in sql/updates/11.php but there is NO equivalent for a fresh install (no file in install/pages or install/tables takes action to create this login_data table. That's why it does work for people upgrading their installation but can't work for fresh installations. I created an install/tables/login_data.sql that should fix it. |
Beta Was this translation helpful? Give feedback.
-
Does this code look correct for login_data.sql ?
|
Beta Was this translation helpful? Give feedback.
-
Hi @andrewcouling: I committed install/tables/login_data.sql table that was a copy of the same SQL used by sql/updates/11.php, so a fresh start installation or an old one being updated should result with the same table: CREATE TABLE In your version maybe the "PRIMARY" should be added to KEY, |
Beta Was this translation helpful? Give feedback.
-
Thanks @pakricard . |
Beta Was this translation helpful? Give feedback.
I think I located the root issue.
In the latest code there is a CREATE TABLE login_data in sql/updates/11.php but there is NO equivalent for a fresh install (no file in install/pages or install/tables takes action to create this login_data table.
That's why it does work for people upgrading their installation but can't work for fresh installations.
I created an install/tables/login_data.sql that should fix it.