For a client who owns an active Drupal 6 website, Drupal 8 promises a whole lot of opportunities. Although we know that Drupal 6 can cater to everything that is needed to create a platform that fits our requirement, Drupal 8 offers the extra edge which allows us to build something faster and more stable. And this is the key for any modernized platform.
As we all know, the official support from Drupal.org for Drupal 6 is going to cease and the security updates will no longer be available. However, there is no reason to get upset; in fact, there is nothing in the code that will cause Drupal 6 site to stop functioning after February 24th, 2016. If you choose to keep running the code, it will run as long as your hosting company allows to do so. Then, why would anybody want their website to be migrated to Drupal 8 ? The answer is quite simple, nobody wants to stay behind. It's actually a step forward.
The term ‘Migrate’ in the context of Drupal means re-creating the content and configuration of a source site (usually Drupal 6 or Drupal 7) in a new Drupal 8 installation. In earlier versions of Drupal, the common practice was to provide an upgrade path. i.e., update the code to the latest version and then upgrade the database structure according to the code. Once it is done, the content is updated separately.
Come 24 February 2016 and Drupal 6 will reach its end-of-life and will no longer have active community support. The newly-launched Drupal 8 and Drupal 7 will be the community’s focus and Drupal 6 will not receive security updates which are so important for the functioning of a website. It will also be a prudent move not to launch a new project with Drupal 6 and get stuck with a soon-to-be-obsolete Drupal version.
The excitement of the Drupal 8 launch is yet to subside and the buzz it has created is truly phenomenal. However, the users of Drupal 6 are worried about the impact and the challenges they may have to face due to this new release. Come 24 February 2016, Drupal 6’s EOL (end of life) will be a reality and will no longer be supported by Drupal.
While working on a Drupal 6 project, I came across the requirement to send some mails. Interestingly, I couldn't find any good articles or procedures on the same. So, here, I am going to explain how to send mails in Drupal 6 with attachments. If you need any business support, get in touch immediately.
We were setting up a development environment for one of our sites for maintenance purposes. During that process, we've copied the Drupal code to the 'dev' folder from live. Everything was set proper, including database, settings.php and 'files' folder. However the site was showing 500 internal server error. When we checked the error log we found the following error:
After the core update, the site will definitely be malfunctioning as expected, as long as it isn't WSOD, you're fine! Ignore it and move forward with the migration process. If you were using a custom theme, then in all probability your site will appear broken because your theme was designed for Drupal 6 and the core is now Drupal 7. If you were using custom or contrib modules to display content or blocks the same would happen because the modules are disabled and still Drupal 6.
It gets called at the beginning of a page request (but after the modules and themes are loaded into memory) and it?s typically used to set global parameters that may be needed in the request. One thing to note about it is that it is not run on cached pages.
Migrating or upgrading a Drupal website is a relatively easy process. But to any change there is a certain risk associated with it, more so in this case depending on the variability of content and complexity of theme. The least troublesome to migrate would be a site with little to no custom code or modules. But this wasn't the case for zyxware.com. This article outlines the migration process and links will be provided to detailed descriptions from all of these outlines.
This step may seem irrelevant, but is absolutely necessary as the minor versions may have database changes which maybe reflected in major upgrade. (Minor upgrade example : 6.11 to 6.19 and major upgrade example : 6.19 to 7.34). If you are using git, make sure to checkout a new branch before updating code so that the code is backed up and take a dump of the local database you are working on.
This is probably the part that will crash your site, so proceed with extreme caution! Migration actually starts here. Unlike the previous steps you will not be able to use drush to overwrite your core to Drupal 7. This has to be done manually. You have to download the latest stable version of Drupal 7 and paste into the root folder of your website. Make sure to not overwrite .htaccess and robots.txt. When you overwrite, merge into the folders and replace the files. That being said, there are some prerequisites to this step.
We were working on a Drupal website which was handed to us by one of our Drupal clients. We were required to add a new content type to the Drupal site and create the associated views with it. While working on adding a feature we found that the taxonomy terms (tags) were not appearing on the node page of any content type. If you find that the tags have been missing then read on to know the most likely source of the issue.
Adding extra plugins to the CKEditor is like extending Drupal by installing new modules. Plugins can be used to add more functionalities to the CKEditor. In this article I will be explaining how to create a simple custom plugin and how to configure it in Drupal 6.
Some alignment issues occurring in IE may be a test for your patience. We had once worked in a Drupal 6 site, and the design look well every where, but there is a small alignment problem shown up in IE. Applying a conditional style sheet saved our time. Read on to know about how to apply conditional css in a Drupal 6 site.