There is a new core upgrade for Drupal, moving from 7.24 to 7.25. It appears to be pretty cut and dried. Once, again, I am using the procedure detailed from the link below.
http://startlearningdrupal.wordpress.com/2013/04/04/core-upgrade
There is a new core upgrade for Drupal, moving from 7.24 to 7.25. It appears to be pretty cut and dried. Once, again, I am using the procedure detailed from the link below.
http://startlearningdrupal.wordpress.com/2013/04/04/core-upgrade
It is that time again. A new version of core is out and i am upgrading today. Quality first then prod.
The upgrade went smoothly, no issues. I followed the proc as below. please mind all the details about OS if you use this procedure!
http://startlearningdrupal.wordpress.com/2013/04/04/core-upgrade
Looks like it is that time again. I’ll be upgrading the Core to 7.22 today. Sand first then prod.
This is the procedure that I am using. I have used it for three previous core upgrades and have never had a problem. Note that I am running Centos 6.3 on both core and sand. I have updated it for this post as well.
The Sand upgrade is completed. No issues. Proceeding to Prod.
Prod upgrade is complete. No issues.
It took me a little longer to get back to this and I am frankly not eager about it. Because Multilingual is hard. There are a LOT of modules and ways to do this. And this myriad of choices makes for a lot of in-the-dark feeling decision making.
Read this first – drupal.org/documentation/multilingual
You might read this post of mine from January when I was neck deep in this stuff. I have a neat Draw file that shows some of the complexity that you can find here.
Drupal 7 Language Modules, Dependencies and a Few Relationships Between Them
I will say though that I have gotten better with Drupal and feel like I have a good shot at making this work.
One of the things that I was really hoping to find was a way to translate stuff automatically. And you can do that to a degree with the Drupal Interfaces. But the content, well I believe that it has to be a manual process. There are good tools available to do that and to manage the process. But NFL …No Free Lunch…
This core upgrade has been installed in the sandbox with no issue.
Upgrade on Production complete. No issues, functionality has been confirmed.
Core update was released yesterday and since these generally address security issues, always a good idea to put it in place ASAP. Plus, then you won’t have to read all those warnings!
I have installed this on my sandbox and had no issues. I’m doing a reboot now and after checking the status report and a few of the features, i’ll install this on prod. I followed the same procedure as before. Here is the link. Will issue a Change Request when I am done.
Make note that I am on Centos 6.3 and the commands are specifically for this OS. BUYER BEWARE!
I’ll be upgrading my core Drupal files to the version that was released this week.
Here is the short link to the proc i use to upgrade core files. I have used it several times and it is sound.
Sand first then prod. I’ll post how it goes later today. shouldn’t take too long.
I’m also going to spend some time in Quality Assurance for Sand, Qual and Prod. Making sure that they are reasonably close in the modules (need to be the same on that) installed and the stylings that are running on prod. Housekeeping. Very important.
here is a good linux command that i always forget. to delete a non-empty linux dir type
rm -rf /dirname
from the directory right above the one that you want to remove.
The core upgrade is complete with no errors/issues. The upgrade was performed on Sand first. No issues there. Cron has run and everything is up to date. Looking good.
this link will take you to a list of all the template files used in the core. this is a great link that has been very useful to me. each template is fully linked to an explanation of the template itself.
these are the files that I am particularly concerned with:
System“modules/system/…”