lottos
Administrator       
Posts: 486
Registered: 6-3-2002
Member Is Offline
Mood: pass me a TimTam
|
|
[Fixed] upgrade clarity
When planning to run upgrade scripts, visiting example.com/forum doesn't appear to allow logins once the new script files are uploaded,
irrespective of whether bbstatus is on or off.
Then when going to example.com/forum/upgrade, it states you need to login as super admin, so some like me, might attempt to go back to
example.com/forum to login - it would be helpful if the login form was on the example.com/forum/upgrade page or it was more clear to login from that
link on that page.
|
|
miqrogroove
|
|
I see it's not mentioned in the readme either. Would you like to add this on the bug tracker?
|
|
lottos
Administrator       
Posts: 486
Registered: 6-3-2002
Member Is Offline
Mood: pass me a TimTam
|
|
|
|
flushedpancake
Member  
Posts: 114
Registered: 4-1-2024 Location: England
Member Is Offline
Mood: Pretty good.
|
|
Can confirm that the installer works on my localhost absolutely fine now using the svn. Thank you very much miqrogroove and lottos for continuing to
care after all these years.
Also, there's additional whitespace after "XMB 1.9.12" in the GPLv3.
|
|
lottos
Administrator       
Posts: 486
Registered: 6-3-2002
Member Is Offline
Mood: pass me a TimTam
|
|
Quote: Originally posted by flushedpancake  | Can confirm that the installer works on my localhost absolutely fine now using the svn. Thank you very much miqrogroove and lottos for continuing to
care after all these years. 
Also, there's additional whitespace after "XMB 1.9.12" in the GPLv3. |
Did you edit this as I'm sure you mentioned a version issue still existed? Cache issue?
|
|
flushedpancake
Member  
Posts: 114
Registered: 4-1-2024 Location: England
Member Is Offline
Mood: Pretty good.
|
|
Yeah, pretty sure it was a cache issue, since it only happened on localhost.
|
|
miqrogroove
|
|
The upgrade login page in v1.9.12 doesn't work sometimes. I've narrowed the problem down to only running the upgrade script after upgrading
to v1.9.12. That's where the bug was. I knew it had to be working at least some of the time.
|
|