Login to download the latest version of Mint and your favorite Pepper, purchase additional licenses, or post in the Forum. Don't have an account? Create one!
I just updated both the sites that use Mint - the first site update went swimmingly. However, something horrid has happened the second time. Perhaps I did things in the wrong order when updating the main Mint install. Now when I go to myglasseye.net/mint there’s simply nothing there.
I tried reinstalling again, this time making absolutely sure I did everything in the exact right order, over the top of the apparently broken install, but nothing.
Is it screwed beyond repair?
Did your previous version of Mint require an .htaccess file to properly configure the include_path? (If that doesn’t sound familiar then probably not.) If so, is that .htaccess file still present after updating? I’ve tried appending ?errors to your Mint installs url but that doesn’t change the output which suggests an include_path issue.
This certainly isn’t screwed beyond repair. It’s likely a PHP parsing error that is preventing the page from displaying, your data should be fine.
Shaun to the rescue… ;)
Hmm. I don’t recall tinkering with .htaccess, but then I’ve not updated for quite a long time - since the time when it made Mint count hundreds more visitors than were actually occurring, if you recall those days?
What’s an ‘include_path’ issue, and why would it be working fine on my other install (which is on a subdomain) but not this one?
I remember that I might have renamed appnew to app and deleted appold BEFORE I uploaded index and styles, and that when I uploaded them it said something about appold directory not existing. I wasn’t sure why it would even be looking for them… I then realised I’d done something out of order and when it failed to work I overwrote the update by doing it all again in the correct order, but no dice…
What happens if you upload a fresh unmodified, unconfigured copy of Mint to a separate directory off the root of your site (eg. domain.com/mint-alt/)? Do you get anther blank page or a database connection error message? (Trying to determine if it’s your server or if one of the files you previously uploaded was corrupted somehow.)
Done that, and I get Mint showing up telling me it can’t connect to a database - just as it should do, correct?
Correct, that means that in your original, problem installation a file was corrupted during upload or you have an error in your config/db.php.
To update try this: Copy your Pepper from the old installation into the fresh installation. Then check to makes sure you still see the database connection error. If not, and the page is blank, one of the Pepper you uploaded during the update is at fault. Otherwise, copy your config/db.php from the old installation into the fresh one. Don’t visit the fresh copy in a browser yet. Rename the old Mint directory to something like mint-broken and rename the fresh directory to the original directories name, mint, then visit in a browser.
Blank page or your Mint working normally? If it’s still a blank page there’s a problem in your config/db.php. Compare your db.php with a fresh one using this FAQ as reference. Any glaring errors (unclosed quotes, unintentionally replaced array keys, missing commas or semi-colons)?
I just made a boo-boo that revealed the problem. While ‘dragging’ the peppers over, instead of copying (duh) I accidentally also loaded my broken mint and it worked, but missing some peppers.
Then I remembered that I’d done something daft with the ‘orderedlist’ folder which contains the ‘downloads’ pepper, when I was updating before. So, I removed that folder and hey presto, I’m back.
Cheers for suggesting it was the peppers. I wouldn’t have worked that out myself.
I think I’ll just delete the downloads pepper there, it wasn’t very helpful anyway. ;)
You must be logged in to reply. Login above or create an account
