Drupal 6

Zyxware default image2
| 2 min read
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.
Zyxware default image2
| 3 min read
You might be getting the most from your Drupal 6 website, but with versions 7 and 8 already on full gear, you might hurt your web presence sooner than later. Drupal 7 And 8 Offerings You Cannot Disregard It’s time to make a planned move to a more recent Drupal version now. Some of the features that make Drupal 8 move worthwhile include: Better Content Management Experience The content management experience is even more flexible and efficient with in place editing and advanced image handling.
Zyxware default image3
| 3 min read
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. In this respect, it is likely that Drupal 8 provides a much easier transition to a great working site. Advantages for Webmasters:
Zyxware default image3
| 3 min read
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.
Zyxware default image2
| 3 min read
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.
Zyxware default image1
| 3 min read
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.
Zyxware default image2
| 1 min read
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:
Zyxware default image4
| 3 min read
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.
Zyxware default image1
| 2 min read
1. hook_init() 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. 2. hook_views_api() hook_views_api() is not a Drupal core hook but one from the Views module .It is used to register Views API information (including the necessary files for Views) usually for implementing hook_views_default_views().
Zyxware default image4
| 4 min read
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.
Zyxware default image4
| 2 min read
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.
Zyxware default image1
| 3 min read
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.
Zyxware default image2
| 2 min read
There is no Drupal website with out a block. As a Drupal developer there are certain cases we need to create custom blocks programatically. While working in a project I faced an issue with a custom Drupal block creation in Drupal 6 version. I think some of you also faced the same situation,Custom block creation in Drupal 6 is not a big issue. I think the below code will help to handle the situation.
Zyxware default image4
| 1 min read
In my previous article "How to create a php script to add a new set of category by using existing taxonomy term as reference id in Drupal 6 ?" I have explained upto replacing taxonomy term using term id. In this article replacing taxonomy term using term name and also how to create a crone job for executing the script in regular intervals.
Zyxware default image3
| 3 min read
Social media marketing plays a significant role in promoting a company's products, driving more traffic to the website, and attracting potential customers. Needless to say, if your social media strategy is implemented correctly, it can bring a whole lot of profit to your business.
Zyxware default image3
| 1 min read
Zyxware Technologies is extremely honoured to be part of this month's Drupal Meetup Singapore. Drupal Meetup Singapore is a series of community meetups that connects Drupal enthusiasts, developers, users, and people who are curious to know more about Drupal. The events are organized by Drupal Developer Network (Singapore) RoS Registered with UEN T12SS0015F.
Zyxware default image2
| 2 min read
Awareness about context plays a key role in effectiveness of each task we have to do because clear thought and action is mostly not possible with vaugue assumptions or guesses. In case of web development using Drupal framework, better if we predefine each and every context we have to go through and it is very important to save our time and helps us to work efficiently. So if you are a web developer and have Drupal in your toolkit, there is an interesting module called Context, which helps you to define contexts and set up your web application based on the defined contexts. This article helps you to start with context module.