A week or two after I have updated the site (drupal) from 4-point-something to 6.4 I got a message from the drupal.org that they have fixed some bugs in 6.4 and have released 6.5.
Ok, so that is something I consider a minor upgrade. Since my own website also uses drupal I decided to upgrade that one first. That went without a hitch. Now Allacrost self. Being a good IT specialist I backup the database but since I assumed there wouldn't be any problems with this installation as well, I decided to go for it and just ignore the backup of the site itself.
Using the same procedure (copy the files to another location) I do the same and there I hit problem number one. I couldn't replace certain files. Even though the file said it had all the rights (read, write and execute on every level) I still couldn't replace. When MindFlayer pointed out if I had the rights on the directory I suddenly understood what had gone wrong. Problem solved, or so I think...
When I try to run the update I suddenly get an error of which I have no idea where it came from. When I try to restart the installation I was stuck again. I try everything I can but the only result were more problems. I then finally decide to let it go and look at it tomorrow (being pissed however I was more thinking in the terms "either the site goes or I go").
But now it is the next day, I have completely reinstalled the website, following the same procedure as I did on my own website and now everything seems to work again. I didn’t get any warnings this time however I still feel a bit reserved as so far I haven’t had much with the Allacrost server but I hope that this will be the last time this happens.
Now I will be smart and backup the entire site and entire database, one more time, so that in the event something does go wrong I can just revert the entire website.
PS: Sorry for the extend downtime
- ElonNarai
Since we are busy with getting the organization behind Allacrost up and running we have also been thinking how to provide the public with an informal yet formal means of telling how to progress goes.
After a bit of discussion the idea of team blogs came up and we all agreed that the idea is pretty awesome. The idea is simple. Every member on the development team is able to post on the website having its own blog.
Since those blogs are informal and don't relate to the product itself they won't appear on the front page, but on the right side you can view the latest entries. What is even cooler is that all though every member has its own individual blog, the RSS feed can show you all entries of the team blog.
So what is the purpose of these “team blogs†and where do we want to go with?
Well basically it’s up to the individual members. They can talk about pretty much anything and it doesn’t even have to be related to Hero of Allacrost, however they can use it to tell how their personal progress is going or what they are really excited about at the moment.