Saturday, 20 October 2012

new start

Big business can pay for people to be polite to the executives by over-chargingAfter a day trying to change the Drupal version XXXfecking!x core, I decided that maybe someone else will work-out how to do this more simply in future as has been very well done for modules. I am still happy each time I download a module in a lazy way, knowing what a chore it was to move files about and read or amend text files next to them a year or two ago; so much depends on things that vary between individual users, like whether I had put my altered & site-specific files in a folder called "sites" away from the default files, and whether I have read the text tile called readme.txt which tells me to rename the default.settings.txt file to "settings.txt" and change a line in it. All fine if you're used to it and good at it but otherwise a bit like trying to fly before there were seats on cheap airlines; the choice is pay or make your own plane and ask strangers online for advice while they can't see what you are building. And if you're selling honest goods made in a democratic welfare state, there isn't the margin to pay, as McDonalds still do, to get a good version of Commerce Kickstart going.

Following the Youtube video by Tom Geller that I transcribed before, I'm using Aquia Drupal's stack installer. Can I just adapt the Aquia Drupal that comes with it from scratch? There is a nag message that says I should disable and delete all their chosen extra modules before it goes, and then says that some of the modules cannot be disabled. I ask the sales chat thingey: "How do I uninstall the Aquia modules? (I want to keep things simple for now and maybe use Aquia help later, so I want to start with core drupal and nothing else)"
Answer: "just go to and download Drupal 7 core". So I am back to following the Youtube video by Tom Geller that I transcribed before.

/q=user (when locked out after trying to replace drupal core)

Upgrading Drupal Core. Why? Because the machine told me to, and because I can't upgrade Kickstarter 1 to Kickstarter 2 and an old Drupal Core might be the reason.

How to upgrade? I've forgotten. It's about moving a bunch of default files to the right directory, which you have to be able to find, and changing "default.settings.php" to "settings.php" with a line changed to "TRUE" instead of "FALSE" if you are locked out of your site. I can't keep track of what I've done or explain it, but after a day searching for any files with "TRUE" or "FALSE" in them on my hard disc and changing about all of them, I was still locked out until finding this post: which suggests as a way to log-on.

It only works on one of my sites.
The site is still using the old version of Drupal core which I thought I had deleted.
But something has happened, anyway.