Installing latest SourceBans from the Github
So I'm installing the latest SourceBans from the GitHub, and the installation screen's height is a tad off, which cuts off the last two items in the checklist ("Runtime Folder Writable (/application/runtime)" and "Database Config Writable (/application/config/sourcebans.php)" checks)
Here's the CSS fix: Change this: Code:
.step, .slider { To this: Code:
.step, .slider { As well, it's looking to check the "/assets" and "/demos" folder to see if they're writable.....except they don't seem to exist. Was I supposed to keep the old SourceBans install? I can't go forward in the installation because of the missing folders from the old installation. I did manage to go forward by manually creating both folders and CHMOD'ing them to 777. |
Re: Installing latest SourceBans from the Github
The installation tries to create the folders. If it fails, then of course you have to create them yourself and make them writable.
|
Re: Installing latest SourceBans from the Github
Quote:
Well I finished installation, now I've got a nice big error page for my index.php: Code:
CException Code:
CException |
Re: Installing latest SourceBans from the Github
Tried to install Sourcebans 2.0. Got a new error upon going to the dashboard after installation:
Code:
CDbException |
Re: Installing latest SourceBans from the Github
Sounds to me like the settings table isn't in your database.
Can you log into a panel and check? Also, apparently tsunami has updated the repository to include for error checking on the installer. |
Re: Installing latest SourceBans from the Github
Quote:
|
Re: Installing latest SourceBans from the Github
Yes, most likely the installation failed and the tables don't exist. I added a basic alert to the installer today for when an error occurs, so at least you know something went wrong.
|
Re: Installing latest SourceBans from the Github
To doubly confirm Tsunami's statement, before this error checking occurred, there was an improperly formatted SQL file for the install (references to fields as null when those fields couldn't be null). I had to manually edit the install.sql until I got it to work (then submitted my changes to the github repository)
I was having the same issue as you. |
Re: Installing latest SourceBans from the Github
Everything seems to work now. Web panel finally got set up correctly, though I had to delete the original database (which I forgot to backup, so there go all the original bans I had submitted ages ago) in order to finalize the installation.
It was detecting that the sb_ databases already existed, so I'd drop them, hit finish again....and it would detect the databases again after it created them, thus stopping installation. |
Re: Installing latest SourceBans from the Github
If you're working on the same db you probably should have used a different prefix.
But hind sight is 20/20 right? |
All times are GMT -4. The time now is 09:32. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.