Update Drupal Core

And post number 3 on updating Drupal.

Again about updating the core. I already talked about doing it on an Acquia Drupal Install.

Now: Just a normal update.

After my post about updating the Drupal core on an Acquia Install – now how to update pre-installed modules.

SECURITY: I don’t know if this will work for you (it should!) so go on and back up your database and your code basically your site (database backup and copy of all files in your Drupal install). If something goes wrong and you don’t have a backup – it’s on your head. Try at own risk.

Download and extract the new release of Drupal. Open your folder and delete all files and folders of your old install without the sites/ folder. Now insert the new files and folders again without the sites/folder. And your done.

Don’t forget to run the update.php script!

Update Modules on an Acquia Drupal Install

After my post about updating the Drupal core on an Acquia Install now how to update pre-installed modules.

SECURITY: I don’t know if this will work for you (it should!) so go on and back up your database and your code basically your site (database backup and copy of all files in your Drupal install). If something goes wrong and you don’t have a backup – it’s on your head. Try at own risk.

When you get the message you need to update some modules (I know you can update modules from inside Drupal – how cool is that? – sadly it didn’t work with my Acquia install – and I couldn’t test it somewhere else until now) you would normally look for the modules in the sites/all/modules folder (or where ever you stored your modules). But the pre-installed modules aren’t there…

The pre-installed modules coming with Acquia are in the profiles/acquia/modules folder. There you can delete the modules and insert the new version of your modules.

Don’t forget to run the update.php script!

Update Drupal Core on an Acquia Drupal Install

As I work on my project I try to do the module testing (does the module do what I want to do) on my local install and not on the actual server where the site is running (yes it is already on the server – I am not the only one working on this project).

My local install is a Acquia Drupal install (it is very easy to install – and I like the interface of the Control Panel). Now I installed it some time ago and I actually ignored the updates for quite some time (I didn’t use it that much – so I skipped updating – not so good).

But now development of the project is well under way and I use my local install so I had to update the modules… I will talk about Acquia Drupal module updates on my next post.

For understanding: Drupal Core has minor and major releases – major are Drupal 7.x, minor 7.4. I will talk about doing a minor update (major releases are referred to as upgrades – minor are updates). You can find more information in the documentation.

SECURITY: I don’t know if this will work for you (it should!) so go on and back up your database and your code basically your site (database backup and copy of all files in your Drupal install). If something goes wrong and you don’t have a backup – it’s on your head. Try at own risk.

Now Drupal also told my that there is a new Core Version required (Security update yay). Now I know how to update the core for a normal Drupal install (you can find it on Drupal.org I didn’t find it there ask Google for the time being – I will do a post of this as well soon) but I didn’t know how to do it for Acquia (and I didn’t find it either – Google isn’t nice to me).

Acquia comes with some modules pre-installed and they are not in the sites/all/module folder…since I didn’t know what else Acquia changed I downloaded the new core release and unpacked it. I opened up the folders of my Acquia Drupal site and the new core and copied it folder for folder after checking if there was a difference between the folders (other files/folder not in the core) – if there was I let the “not” core files/folders in it and just copied the files from the new release (you don’t copy the sites folder at all). I had 2 differences between Acquia and core (without sites/) one was in includes/ and one was another profile in profile/ .

Run the update.php script (modules page at the  top – there should be a reference to it or in the home menu for administration menu user) and hopefully you’re done with it (read carefully possible messages after update.php has run.

Hide Author and post date from content

Okay in Drupal 6 to hide “Submitted by” author “on” a date and time you would go to the themes and specify on which content types that information should be displayed and on which not.

In Drupal 7 you can change these settings under Structure > Content types when you edit the content type you want to change.

Of cause for a more a more customized approach what to show and what not you have to work on template.php.

Hide Error Massages

As I started developing my new project in Drupal 7 I stumbled over a couple of Menu changes…

There are several changes (mostly for the better, I think) but for Drupal 6 users it can become quit frustrating to look for a functionality and not finding it where you expect it (happened several times for me already…)

Before I start with my first menu change tip an information for you: I use the Administration Menu module for better access to the admin area of Drupal. And it still is a release candidate so there are still some problems with the themes but otherwise it works fine for me.

On to the tip:

When you want to hide Error reports (showing up at the top of a page) from all users and just log them in the database for the administrators to see:

Got to Development > Logging and errors and choose > None.