Drupal 8 was released on Nov 19th, 2015. Though Drupal 6 end of life was declared on February 24th, 2016, there are still over 84,845 Drupal 6 websites on the web. What does end of life mean for Drupal 6? As per Drupal 6 end of life, the security team will no longer provide support or security advisories for Drupal 6 and the core of Drupal 6 will no longer receive community support. For those users that still have an installation of Drupal 6 and are unable to upgrade to Drupal 7 or Drupal 8, a D6LTS (Drupal 6 Long Term Support) has been created to provide long-term support for Drupal 6. By updating Drupal 6 to Pressflow, you get the solution provided by the D6LTS in which Drupal 6 site can be made secure at very low cost. There can be two major issues that hold back these Drupal 6 sites from upgrading to Drupal 7 or Drupal 8. If the site is complex, it can be that they are waiting for a stable version of Drupal 8 before migrating to it. Or they do not want to migrate to Drupal 7 when the next version is already available (Drupal 8). The second major issue can be the budget needed to migrate. What is Pressflow? Pressflow is a fully API compatible distribution of Drupal with integrated performance, scalability, availability and testing enhancements. The Drupal 6 Long Term Support (D6LTS) team will be releasing the security fixes in Pressflow. Upgrading Drupal 6 to Pressflow is not time-consuming, and provides a minimal budget solution to keep the Drupal 6 site secure. Pressflow upgrade is recommended by the D6LTS vendors for Drupal 6 websites. Benefits of upgrading a Drupal 6 site to Pressflow Pressflow will be updated with the needed security fixes and release patches Pressflow is open source software Built in support tools for high-performance websites at par with Drupal 7 Allows database replication Support for external reverse proxy caching using Varnish 100% API compliant Optimized for PHP 5 and MySQL 5 Zyxware Technologies, a leading Drupal development company from India, has been at the forefront of Drupal development through all the major version changes in Drupal. We can help map out an upgrade that is to your best interest. We always evaluate the site, take a backup and verify the Drupal patches on the site before we do an upgrade to a site. If you have a Drupal 6 site and would like to know the best options available for you, get in touch with us. References:PressflowComparison of Drupal and PressflowDrupal 6: End of Life Drupal 6 Pressflow Leave a reply Your email address will not be published. Required fields are marker *
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.While some of the content has to be migrated manually depending on the complexity of the site, all default content types will be automatically migrated. Custom content types have to manually migrated.That being said, migrating manually isn’t a big pain when it comes to Drupal. The data is properly structured and all that needs to be done is to write a few sql queries to migrate the tables from the old structure to the new structure. In Drupal 8, a migration path has been provided. This is done by first creating a new Drupal 8 installation either on the same host or a different one, but with access to the database. Drupal 8 provides a Migrate API and a Migrate UI, where we will enter the link to the site to migrate and the destination site to which the migrated content will be pulled by the Migrate API. When it comes to custom content in Drupal 8, it is possible to write custom migrations provided by the migrate API. This is the equivalent of writing mysql queries in versions prior to this. You can see these custom and default migrations available in the migrate UI and decide which ones to run or not! While upgrading the Drupal versions 5 through 7, the most common practice has been to overwrite existing site with the newer version. This may often lead to complications if the content (nodes, entities, contexts etc) are quite complex or if some modules don’t have a higher version. However, it would be easier and less time consuming to have a new Drupal installation and move all the content from the old site to this new Drupal installation. This is what Drupal 8 has done and this explains why moving to Drupal 8 is the easiest and best choice! The new version of drush (Command line utility for Drupal) also provides several helpful Drush commands: migrate-import (mi): Performs one or more migration processes. migrate-manifest: Execute the migrations as specified in a manifest file. migrate-messages: View any messages associated with a migration. migrate-reset-status: Reset an active migration status to idle. migrate-rollback: Rollback one or more migrations. migrate-status (ms): List all migrations with current status. migrate-stop (mst): Stop an active migration The migration process in Drupal 8 is quite impressive; it has become more polished and smoother with the help of Migrate API. After a few test runs of the migration process, it is quite evident that it is quite stable and seamless and a lot less painless than the earlier ones. At Zyxware, we have enabled our clients to make a quick and hassle-free shift to Drupal 8. We have sufficient technical expertise to ensure a smooth and uninterrupted transition, without any visible impact on your business. Call us today to know more about our Drupal development services and understand the fastest way to make the change to Drupal 8 before your competitor does! Resources: Migrate API in Drupal 8 Drupal 8 Upgrade Path A Simple Drupal 7 to Drupal 8 Migration ARCHIVE Introduction to migrate D6 to D8 Drupal Development services Drupal 8 Drupal 6 Drupal 7 Drupal Migration Leave a reply Your email address will not be published. Required fields are marker *
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. Considering all the necessary facts, the question you should ask isn’t “Should I upgrade?” but “Should I upgrade to Drupal 7 or 8?” If you are still stuck with Drupal 6, it is inevitable for you to upgrade ASAP to Drupal 7 or 8 after considering your budget. It will be a great idea not to leave this decision to the last moment when Drupal 6 will turn out to be a liability despite having served you loyally for all these years. If you are an active Drupal 6 user at this stage, here are a few worries that you might encounter: Bug fixing for present projects and new project creation will end on 24 February 2015 There shall be no community support for Drupal 6 users Do not expect any security advice or support for Drupal 6 All Drupal 6 releases on Project pages shall be un-supported Core commits shall not be available post this date Key features of Drupal 8 Drupal 8 has been launched with some awesome features and it is worth taking a peek at them: HTML 5: Drupal 8 has been fortified with the resourceful HTML5; a wonderful ally for mobiles and tablets to be aligned to and that too with minimal changes to the website. The digital world is filled with handheld devices and HTML5 makes a fabulous collaborator for an improved user experience. Building Multilingual websites: Drupal 8 has a lightning fast interface that is ideal for providing language maintenance alternatives to developers and users, hassle-free customization, and fast site translations. Excellent Content Management: Drupal developers have been empowered with the option to make administrative changes to the site using a mobile device and without having to access the back-end from a desktop. This gives immense flexibility as the tablet or smartphone has more accessibility and augurs a better user experience. Introduction of Twig: Known for its flexibility and agility, Twig integration in Drupal 8 has bolstered its security tremendously. Twig also displays better display segregation and logic which enhances Drupal 8’s overall efficiency. Symphony Framework: This framework allows the loading of necessary modules only on to the page, assuring a superior experience for all users. For all worried users of Drupal 6, it is worth mentioning here that Drupal 7 or Drupal 8 are equipped with easy-to-switch tools that will free you from a lot of transition hassles. Make the decision to cross-over and reap the benefits of a much superior CMS. At Zyxware, we are keen to help our clients with this changeover and just one call from you will quickly engage the wheels of change to a much better CMS than before. Connect to us today to know more about our Drupal development services. References: 4 considerations: upgrade Drupal 6 to Drupal 7 or Drupal 8 Drupal 8: Should you upgrade? Yes! Well...no. Maybe? Drupal: Build something amazing Drupal Development services Drupal 6 Drupal 8 Leave a reply Your email address will not be published. Required fields are marker *
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. Let us first look at the realities you may have to face as a Drupal 6 user: There will be no security support or any security advisories for Drupal 6. Community support for Drupal 6 will be withdrawn and bug fixing in current projects, creation of new projects etc. shall cease from 24 February 2015. No more core commits on Drupal 6.x to the official tree shall be made available Project pages of all Drupal 6 releases will be flagged as non-supported If you are a Drupal 6 site owner, you need to be aware of the fact that while the security updates would come to a stop, technically you can keep using your existing site. However, unsupported software is a tricky proposition and you surely do not want to take chances with your business, do you? You would rather work with a supported version like Drupal 8 than on a soon-to-be-taken off the shelf version. As a Drupal 6 site owner, you need to get ready for a smooth and easy upgrade to Drupal 8 and for this ensure that you have the following in place: Drush 8 is necessary if you are planning the upgrade from Drush. Also the module ‘migrate tools’ is required. Core module Migrate Drupal needs to be enabled with a fresh Drupal 8 installation Source site file access is necessary. Access to the Drupal 6 database to the host is required. Before initializing the upgrade from Drupal 6, it is advisable to permit every module on the Drupal 8 site for which content upgrading and configuration is required. The Migrate module is designed to create all content types and fields as part of the migration; so you won’t have to do it manually. Also, since this upgrade will overwrite configuration on the Drupal 8 site, be sure you have not made any configurations unless the entire upgrade is finished. Assuming that you are on Drupal 6 currently, it would make tremendous business sense to move directly to Drupal 8 that has the latest technology under its belt. Why would you want to make a short-term shift to Drupal 7 (will be provided with security updates till end of 2018) when Drupal 8 with migration feature is easily accessible? At Zyxware, we have enabled most of our existing clients and newer ones too to make this shift to Drupal 8 and have a hassle-free and quick migration. We have the technical expertise and experience to ensure a smooth transition, without any visible impact on your business. Call us now to know more about our Drupal development services and understand the fastest way to make the change to Drupal 8 before your competitor does! References: Drupal 6 end-of-life announcementPreparing an upgrade from Drupal 6 or 7 to Drupal 8Still on Drupal 6? Here are your options! Drupal Development services Drupal Migration Drupal 8 Drupal 6 Leave a reply Your email address will not be published. Required fields are marker *
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. Implement hook_mail function First of all, you have to implement the hook hook_mail in your custom module. This hook handles the common things related to different mails. It also allows us to set subject and body according to the mail keys. hook_mail($key, &$message, $params);Here the $key can be used to uniquely identify different mails. The $message will contain the message of the mail(not needed in the mail body, it can be build inside this hook, under corresponding $key). The $params contain the different parameters to the mail. This hook will be called whenever the mail functions like drupal_mail or mime_mail(mimemail module) etc is called. Need of hook_mail? Usually, the mails can be send by just calling drupal_mail or other mail sending functions. But the hook_mail will help you to alter the mail properties like headers, subject or to add attachments to the mail array. Thus, extra attributes can be added by using this hook. Also in this hook it is possible to alter the contents or add headers according to the different key values. Thus we can handle multiple mail sending function calls from this hook implementation. Sending attachments with a mail To send an attachment with a mail you can use the following code. There is bug in Drupal due to which the files with absolute paths will not be sent correctly as attachments. There are proposed solutions, but you can give the absolute file path with the filename parameter which will help to attach the file correctly. However, the problem is that the full file path will be displayed in the mail received. $attachments = array( 'filecontent' => file_get_contents($full_file_path), 'filename' => <full_file_path>, 'filemime' => 'text/csv', );After this, you need to add the attachments array to the attachments key of the $message in hook_mail. $message['attachments'] = $params['attachments'];If there is another attachment, it can be added as another array element to the attachments array. The only thing you need to be careful is that the filename should be given with full path. For more details on the same, please contact us. Drupal Drupal 6 PHP Email Drupal Planet Leave a reply Your email address will not be published. Required fields are marker *
[Solved - internal server error] SoftException in Application.cpp:256: File ".. /public_html/index.php" is writeable by group.
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: [Tue Jul 14 07:21:16 2015] [error] [client 22.214.171.124] File does not exist: /home/mysiteuser/public_html/500.shtml [Tue Jul 14 07:21:16 2015] [error] [client 126.96.36.199] SoftException in Application.cpp:256: File "/home/mysiteuser/public_html/index.php" is writeable by group This is clearly a permissions error and we checked the file permissions. The "/home/mysiteuser/public_html/index.php" was having file permission '0664'. The default file permission should be '0644'. In order to fix the error we did the following and that worked for us. Change the file permissions from '0664' to '0644' Hope this helps. Please feel free to share your thoughts and doubts regarding this here Drupal 6 Drupal 7 Leave a reply Your email address will not be published. Required fields are marker *
[Drupal] [Solved] SoftException in Application.cpp:603: Directory "... /public_html" is writeable by group.
We recently moved our Drupal code to a newly created 'public_html' folder for some reasons and set up the website. But then, our website was showing a 500 Internal Server Error. The interesting part was that, we were actually able to run an HTML file and only php was throwing error. So there was something wrong with the configurations. One should check the server log, to find more about the error and here are the details we found: [Tue Jul 14 01:43:35 2015] [error] [client 188.8.131.52] File does not exist: /home/user/public_html/500.shtml [Fri Jul 10 02:23:35 2015] [error] [client 184.108.40.206] SoftException in Application.cpp:603: Directory "/home/user/public_html" is writeable by groupThis says 'public_html' can be written to by our user's 'group', meaning that the internal server error occured due to an incorrect permission of the 'public_html' folder. The permission was '0775'.For fixing this issue, we changed the permission to '0755'.You can change permissions with the File Manager from cPanel or with the help of an FTP client or using the chmod command via SSH. Drupal 6 Drupal 7 Leave a reply Your email address will not be published. Required fields are marker *