Following the instructions to upgrade to 6.14 I have the following problem.
I put the site in 'maintenance' mode.... and now... nor the admin page with www..... q?=admin shows up, not the index.php for the public with the maintenance message, too.
Checked in the database and admin is no. 1 role.
Can I put it back to 'online' status in the database to retry? Where to put it back to 'online'?
I try with all the new version before this one 6.x-2.6, even with the 3 dev version but every time I made this update the website completely disappear and only a blank page is showed
This event happen in two different websites
Anyone have the same problem and know how can fix this?
I've harped on this before so I apologize for returning to the same subject. But I just checked a website after a couple of months and find there are a bunch of module updates needed, many of them security issues, and a new core security update. I'm starting dread running the status report because it's such a cumbersome process. I've heard that updating a site takes 15 minutes, but it takes me 2 hours, and it seems I always end up with plenty of errors and confusion! CCK fields go missing, or I forget to turn off a contrib module, etc…. I just can't imagine that everyone who uses drupal is not having the same issues? And as I now have three drupal sites running and many more planned I'm getting worried that the process will become overwhelming.
With everything else that is so awesome about drupal I can't understand why all this update process is not automated? I’m will forever be a newbie with limited programming skills. I hope version 7 will fix streamline or eliminate the update process.
I’ve assembled a list of modules that help with the process below. But if you have any new ideas please let me know. I never got into the 'drush' thing because I completely didn't understand it, but it looks like I will have to take a better look. Let me know your thoughts on it.
Here's a list of files changed by the latest Drupal upgrades. We use this so we don't have to replace the entire Drupal installation, as usually only a few specific files have actually changed.
First of all my apologies in advance for being a dweeb if I post things so basic or in the wrong place ... I have searched the forums already but can't find the solution.
I have bought some webspace off a company and using something called CPanel (which I gather is common for such providers) have installed drupal CMS. I have successfully added the blog and forum standard modules (success inasmuch as the whole things seems to work) and I can configure forums etc. ... I haven't tried the blog or adding web content yet.
I want to restrict access to (and visibility of) some of my forums by groups e.g. an admin only section and a section for privileged users based on groups and my limited research indicates I need the forum access and ACL modules. My problem is I have never added a module before (not surprising since my drupal installation is currently the grand old age of 12hours and 55 minutes) so I
* Download the module (drupal.org)
* Extract The Files (Windows)
* FTP them to site (Filezilla). My site is installed under /cms/ so I need to create subfolders /cms/all/modules ... not sure if each module goes in its own folder under that.
* RTFM (install or readme text files)
* Enable the module (Administer --> Site Building --> Modules)
* Set file permissions (optional and I'm seriously hoping this is not required)
So one of the things that I hate more than anything on an upgrade is having to disable and re-enable all of those darn modules. And when you start getting several sites you get sick of making several hundred clicks. So, to overcome it, I wrote some pretty useful jquery code to do a bunch of work for me. We usually just run this in firebug. All of the javascript here should be run on the modules page 'admin/build/modules'.
This will put out some code that has a nice long string and then some simple javascript code that you will use later. It throws it right above the first fieldset. It is important to copy this code somewhere and hold onto it. Otherwise, you are going to be making lots of clicks later to turn all the modules back on.