Articles

/themes/custom/zyxpro_light/images/placeholder.png
06th August 2020 Drupal 7 , Drupal 9
close

on 06th August 2020 / by webmaster
The greatest and latest release of Drupal - Drupal 9 has been released in June 2020. Since the release of Drupal 8, the release model of Drupal is designed to support innovation. Every 6 months there will be a new release with a set of bug fixes and feature additions. If you are still in Drupal 7, it is time to think about migrating to Drupal 9 as Drupal 7 will reach end of life in November 2022. Drupal 8 will reach end of life before that, but if you are in Drupal 8, you do not have to worry much, Drupal 8 to 9 upgradation is easier as you do a minor update in Drupal. But in the case of Drupal 7 or Drupal 6 to Drupal 9, things are much more complex.   Since Drupal 7 and Drupal 9 are based on two different code bases, to migrate from one to another, a new Drupal 9 instance needs to be setup with the required modules enabled and then execute the migration process to pull content and configuration from the Drupal 7 database.  If you do not plan it well, there is a high risk involved. The first step in the planning process is to assess the complexity of the existing website and come up with a migration strategy that is suitable for your website. Since this is a new build in Drupal 9 and migrating the content from your Drupal 7, the following information from your existing Drupal 7 website will help you estimate the complexity of the website as well as the effort required for migration. List of contributed modules with their D9 readiness List of custom modules with lines of code and key hooks used List of content types with number of content as well as fields List of views List of features List of vocabularies and number of terms List of themes with the templates used List of CSS/JS files used Number of lines of code in template.php file To help you quickly get this information, we have created a Drush command that helps you prepare a report from your Drupal 7 site with all the required information for an estimation.     Leave a reply Your email address will not be published. Required fields are marked *
/sites/default/files/2020-08/Teaser.png
06th August 2020 Drupal 7 , Drupal MIgration
close

on 06th August 2020 / by webmaster
For those who are using Drupal 7 will get some more breathing time to plan for their Drupal 9 upgrade. The Drupal security team announced (on 2020-June-24) that they are extending the End of Life of Drupal 7 until November 28, 2022. This means that the standard security process for Drupal 7 core and contributed modules will be followed for an additional year. Drupal 8’s end of life will be the same as earlier announced which is November 2021. This decision has been made in response to the current Covid-19 situation which impacted budgets and businesses. This community effort will give site owners more time while budgets recover, but on the other side, it demands more effort from the Drupal community at large and security team in particular to review security reports, create patches, and release security advisories for Drupal 7. Everyone who is benefited from Drupal is requested to support the Drupal community in this special situation by generously donating to the Drupal association’s security fund. If you are a Drupal 7 site owner If you already have plans for a Drupal 9 upgrade, this is the right time to do it as Drupal 9 comes with a lot of features and benefits that accelerate your organization's digital transformation initiatives. Drupal 7 to Drupal 9 migration is fully supported by Drupal 9 Migration API system and associated contributed modules. If you have a budget constraint or have larger plans in your roadmap which require more time to start working on a Drupal 7 to Drupal 9 migration, you get time till November 2022. Your Drupal 7 core and contributed modules will be constantly under the radar of Drupal Security Team and you will get regular security patches and updates till the end of 2022. As long as you keep updating your PHP versions to the latest one that is supported by Drupal 7 and apply security patches to your core and contributed modules you are safe. If you are planning a major revamp in the UI, make sure that you invest in implementing a living style guide using Pattern lab or KSS or any similar systems so that you can easily convert that to a twig based Drupal 9 theme when you are ready for Drupal 9. If you are planning a major functionality implementation in your Drupal 7 website, Make sure that the contributed modules you use have a Drupal 9 upgrade path Create custom modules in such a way that it can be easily ported to Drupal 9. If you are a Drupal 8 site owner Since Drupal 9 is built on top of Drupal 8 code base, there is a well established upgrade path from Drupal 8 to Drupal 9 and the process is much easier than the Drupal 7 to Drupal 9 upgrade. If your code base does not have any deprecated functions and all the modules you use in Drupal 8 is compatible with Drupal 9, you can move to Drupal 9 as you do a minor security update in Drupal 8. Drupal 8 site owners can check your sites Drupal 9 compatibility with Drupal Check and if there are any deprecated functions, use Drupal Rector to fix those issues automatically. Conclusion Do generously support the Drupal Security Team by donating to the Drupal Association Security Fund Drupal 7 site owners get an additional year to plan for their Drupal 9 migrations. When you plan for any major new features in your Drupal 7 websites, think of it in such a way that it can be ported to Drupal 9 easily when you are ready for Drupal 9 before the end of 2022 There is no change in Drupal 8 EOL - which will happen at the end of 2021. Drupal 8 site owners need not worry about this much, you can migrate to Drupal 9 as easy as you do a minor update in your current Drupal 8 version Leave a reply Your email address will not be published. Required fields are marked *
/themes/custom/zyxpro_light/images/placeholder.png
31st July 2020 Case Study , Education
close

on 31st July 2020 / by webmaster
Introduction As one of the world's leading and largest graduate business schools, INSEAD offers participants a truly global educational experience. Established in 1957, the institution has a history of bringing an open-minded learning culture into its multi-campus model. Harvard Business School, INSEAD and ICFAI Business School Hyderabad are the world’s top three Business Case Study publishers.  The Case Studies published by INSEAD are widely consumed by academicians and industry leaders alike. INSEAD wrote 6 of the 10 best-selling cases distributed by the Case Centre in the past 40 years. INSEAD cases were the Overall Winner of 5 of the last 10 Case Centre Global Case Awards and are used in more than 100 business schools and universities around the world. They also wanted to reduce the dependency on third party portals to sell the case studies and wanted to offer a very elegant and smooth e-commerce experience to their users. The key points we looked at while mulling over the project resonated with INSEAD’s innovative mindset and its legacy as a business force that encourages diversity and risks in their entrepreneurial venture. Thus, our journey with them catered to their international brand image with a touch of unique quality Zyxware Technologies brings in each of the digital projects we have executed. The Challenge  INSEAD wanted to establish its brand as one of the world’s leading business schools. Highlighting the widely consumed and appreciated case studies they are publishing was one of the key strategies. In order to do this, they wanted to build a direct to consumer channel for marketing and selling case studies. In order to serve this purpose INSEAD needed to build a portal which showcases the high-quality case studies, they are publishing and highlight the brand value in front of its audience.  It was decided that the portal should enable case authors or their associates to create and publish value-added content associated with the case study they have written in the form of case microsites. This portal also needed to work as a thoroughly SEO optimised content marketing engine which will draw users on to the platform and help them understand the quality of the cases being published. A very clear focus was given to enabling a smooth experience for the user to evaluate the cases before purchasing those. Overall the key objectives of INSEAD were to Take control of the entire case publishing and sales system and drive sales activities Provide better digital experience to the case study consumers by providing   Improved search Improved navigation Personalized recommendations Digital assets associated with case studies as a value add Seamless case study purchase experience Dashboard to access purchased case studies and recommendations   Provide better digital experience to the case study team internally by providing   Full control of editorial and publishing workflows Option to build microsites for selected case studies to present related materials of a case study Option to present the case study in such a way that it will prompt the potential visitors to purchase it Tight integration with AKDMIA an internal system that host the case studies Case studies analytics dashboard   Promote INSEAD brand through the cases portal and thus improve the sales of case studies Capture the data required to provide insights to improve and optimize the conversion rate Implement tools to support and execute digital marketing campaigns   The road to the solution  A partner was identified to conduct the UX research along with our discovery workshops and to provide the designs for the project. The various stakeholders at INSEAD had done their prep work in detail and had every workflow clearly defined. Our UX partner who had vast experience in designing the user experience for some of the world’s most recognised brands helped us in bringing the research output into a design. They delivered excellent prototypes, information architecture, layout, and UI designs as per the accessibility guidelines adopted by INSEAD. After long deliberations with the INSEAD technology team, it was decided that Drupal would be the best choice for a webCMS for the entire web ecosystem of INSEAD. With this vision in mind and also encouraged by the availability of a variety of reusable components, Drupal 8 was chosen for the project. The checkout process would be handled on a Magento based system which was being used as a single e-commerce backend system used by the entire organisation. Easy discoverability of the case studies and filtering them using various facets was important for the success of the portal and Solr search was identified as the search solution. The publishing team wanted the capability to create new landing pages independently for new case studies being published without bothering the development team. Strict access controls were to be implemented as per the policies of INSEAD for each piece of content. A user management solution which ensures hassle-free user creation and assigning required privileges was also created. A key capability which needed to be built was the ability to provide personalized watermarks which will help customers to claim the ownership of cases that they purchased. INSEAD can also prevent unauthorized usage of case studies with the help of this. AWS S3, SQS and Lambda Amazon were chosen for watermarking to build a highly scalable environment for handling watermarking requests from any number of concurrent users. The watermarking system was built in such a way that it can be reused by the INSEAD IT team for other use cases by cloning it. An active directory based (ADFS) single sign-on was integrated to help INSEAD users to access the portal with their INSEAD login system. This made it easier to provide access rights to research associates, faculty assistants and various other internal stakeholders based on their role in the ADFS implementation. Project implementation  The project was delivered in an Agile SCRUM model. The entirety of the project was followed through these phases: Project Discovery phase  During this phase, we had multiple discussions between the project manager, technical lead, and also the UX design lead. Extensive research was conducted to understand the working of INSEAD and discovery workshops were managed to relay the thoughts on both sides. A project inception report that includes the communication plan, Project Charter, RACI matrix, escalation mechanism and high-level project plan was submitted at the end of this phase. Requirements Analysis Phase This phase itself was divided into three sprints, and more workshops to understand requirement elaboration was conducted during each sprint. This not only ensured proper communication but also delivered clarity to all the parties involved in it. The Product Backlog thus contained user stories that were revised and looked at during the grooming sessions that were conducted in the next phase. Development and Testing Phase Since we followed an Agile methodology, separate time was not required for developing and then testing as these happened simultaneously.  Deployment phase This is the end phase of the project wherein we focused on content migration, training, final configuration, and deployment. We also managed all change requests during this time. The basic outline of the workflow we formed helped in managing the voices of three different organisations together. The project manager of Zyxware Technologies remained as the single point of contact. Regular meetings and utmost transparency helped in pushing this project forward a seamless task for INSEAD and the UX collaborator too. Results  The end product we handed over to INSEAD was a fully functional Cases Publishing Portal with a revamped design and an innovative User Experience. We included a well-documented technical report and a user manual along with it. With the help of the portal, INSEAD got higher control and visibility over the marketing and sales of their Case Studies. The publishing workflows were also optimised and collaboration has been seamless since the launch.   Case Study Education Disintermediation Ecommerce Magento Drupal 8 Apache Solr
/themes/custom/zyxpro_light/images/placeholder.png
30th July 2020 Magento , Case Study
close

on 30th July 2020 / by webmaster
Introduction The client, a Europe based Food & Beverages giant, wanted to build a direct to consumer business for the first time. They wanted to speak directly and interact directly with their consumers. The project was conceptualised as an omnichannel experience in which the consumers could buy their amazing bespoke and hand crafted products and have them delivered to their homes. The consumer was being given the option to experiment with the flavours and personalise the confectionery as per their taste. They had around 1,500 combinations of ingredients and product types to create their own personalised product.The consumer also had the option of personalising the packaging and adding messages to the cover in case they wanted to gift the product. This was to be made available to the consumers from branded boutique confectionery stores, from an online portal and also from Kiosks placed in premium confectionery partner stores. The client had onboarded one of the world’s largest marketing and advertising firms to solve the primary problem of the lack of a direct to consumer touchpoints. Objective Setting up direct to consumer touchpoints was a challenge as they did not have the means to look at primary data on consumer behaviour. They were also trying to address customer shopping behaviour change due to the arrival of large online retailers. Spiralling marketing spend on various platforms was also a growing concern for the client. The marketing consultants wanted to build a platform which could offer Fluid interface with an app like experience Unified customer profile management Frictionless onboarding of customers Online shopping Ability to update / revamp the user interface without reworking the e-commerce part A closed network of kiosks in an offline mode Detailed reporting capabilities Multi channel order notification including SMS Tracking of parcels on multiple service providers Validation of deliverability based on postcode DIsplay of Instagram feed on home page The system should offer the ability to End-User a) Create a custom product based on type, ingredients and size b) Customise packaging and messages Administrator Order moderation workflow Order verification workflow Generate job cards for kitchen staff Ability to input ingredient and nutrition info Print ready PDF Solution Zyxware was chosen for the project primarily because of our expertise in building e-commerce portals and experience of having delivered projects in a timely manner for our enterprise clients. Our history of working in tandem with branding and advertisement companies to engineer their vision also played to our advantage. A tech stack of headless Magento to handle the eCommerce part and an Angular JS based front end UI was chosen for the project. The backend build is based on a KOT (Kitchen Order Tickets) workflow. It basically deals with transferring an order from the table to the kitchen. We have created a custom extension in Magento for implementing the same. It has been built with a drag and drop interface so that the kitchen and consumer can use it easily with a touch screen device. SAP’s Customer Identity and Access Management software (Formerly Gigya) was chosen as the tool to build silo-less customer profiles which can provide customers with a seamless and personalized experience across all digital channels. We have used ‘Worldpay’  as the payment gateway solution because of its state of art payment solutions. Worldpay offers quick checkout, easy order management and highly detailed and flexible reporting which made it a very easy choice. It did not have a Magento extension available at the moment and we have created a custom extension built for that. Another service integration done was for Route Genie - a leader in carrier management service. They provide complete control and visibility over the management of carriers, optimising the processing of collections and labelling through to track and trace all the way to the final destination. Route Genie is integrated with the leading carriers and provides real-time consignment tracking of parcels from retailer to the consumer. Route Genie also did not have a Magento 2 extension which was custom built by us. We’ve also integrated a solution to check the serviceability of the location to which the products are being shipped. The client also wanted to promote its Instagram channel which was being used by them to communicate directly with their consumers. An integration was provided to showcase the instagram feed on the home page. The project had multiple stakeholders for design, SEO compliance etc. So it is a complex project management environment. Results The website was launched to much fanfare and media publicity in the UK as a pilot in Q3 2019. Encouraged by the runaway success of the project, the client has replicated the same model in 5 more countries. The platform is now also being reused for another brand of the same client. Magento Case Study Disintermediation Digital Transformation Ecommerce
/themes/custom/zyxpro_light/images/placeholder.png
BY vimal
13th July 2020 Drupal 9 , Drupal Contribution
close

on 13th July 2020 / by vimal
A new version of Disable Messages has been released on the same day Drupal 9 has been released. This version fully supports Drupal 9. With this release, the module chose to go with the fully semantic versioning model, which means, the version 2.0.0 supports Drupal Core 8.8.3 or higher version. The 8.x-1.0 release will be there for some more time to support older versions. The 2.0.0 release mainly removes the deprecated code and uses the new solution that is supported by Drupal 9. For those who are new to Disable messages module Disable Messages gives a site owner options to disable specific messages shown to end users. The core drupal message system as offered by \Drupal::messenger() is an excellent way for modules to send out messages to the end users. However not all drupal site owners are keen to show all the messages sent out by drupal core and all modules to their users. This module gives site administrators a reasonably powerful way to filter out messages shown to the end users. Zyxware Technologies as a Free Software Company has been one of the flag bearers for the Free and Open Source Software movement in India. Since our inception in 2006, we have been actively promoting the idea of FOSS and related freedoms through various activities like Freedom Walk to spread the message of Freedom, Freedom Toaster for making Free Software accessible to the public, contributions to Swathanthra Malayalam Computing, development of a real-time epidemic outbreak tracking system for Ministry of Health and Family Welfare, Kerala and much more. Zyxware Technologies is one of the top ten contributors to Drupal, we have delivered more than 200 Drupal projects across diverse sectors and currently, more than 60,000 websites use modules and themes contributed and maintained by us. We have also been an active member in the Drupal community in the USA, Australia, and India.   You can find the full changelog here - https://www.drupal.org/project/disable_messages/releases/2.0.0 Download it and try it out from https://www.drupal.org/project/disable_messages Features Filter out messages that match a full-text string exactly. Filter out messages that match a regular expression. Permissions to specifically hide all messages of a given type from any role. Disable all filtering for specific users. Disable all filtering for specific paths. Apply filtering only for specific paths. Debug system to get messages in the HTML without showing it to the end users.   Leave a reply Your email address will not be published. Required fields are marked *
/sites/default/files/2020-07/Teaser%20Images.png
10th July 2020 Drupal 7 , Drupal MIgration
close

on 10th July 2020 / by webmaster
Congratulations on your decision to migrate to Drupal 9. This is going to be one of the best decisions you’ve made as a technology leader. As you’d be aware, since the release of Drupal 8 in 2015, Drupal has been considered a leader in the object-oriented, enterprise-class, modern web content management framework. Now that Drupal 9 is also released in June 2020, the Drupal community has kept its word and has proven that the version upgrade to the new version is a walk in the park. But what about migrating from Drupal 7 to 9? Is there some new advancements that have made that easier? Well, we’re glad you asked. We might have something for you. We have built a tool to do a full site audit to capture the essential elements required for assessing the complexity of your Drupal 7 site. Even though the actual effort will remain the same, we can help you plan the migration in such a way that no mistakes will be made and right protocols will be followed to ensure you get the best out of Drupal 9. Since Drupal 7 and Drupal 9 are based on two different codebases, to migrate from one to another, a new Drupal 9 instance needs to be set up with the required modules enabled and then execute the migration process to pull content and configuration from the Drupal 7 database. If you do not plan it well, there is a high risk involved. The first step in the planning process is to assess the complexity of the existing website and come up with a migration strategy that is suitable for your website. Manually doing this check can take a few day's time, which costs money and there is always the possibility of human error and ignorance. The Drupal 7 audit module we created can help you solve this.         Drupal 7 Audit The Drupal 7 audit is a Drush command which can do a full site audit to capture the essential elements required for assessing the complexity of your Drupal 7 site. The script will capture the following elements and prepare a neat report which can be given to any Drupal vendor to get an estimate of your Drupal 7 to 9 migration. The following properties will be analyzed and reported.  Sl. No Properties 1 Basic Information 1.1 Site ID 1.2 Domain name 1.3 Database size 1.4 Drupal 7 version 2 Content 2.1 List of content types with a number of fields and number of published nodes 2.2 List of web forms with the total number of submissions 2.3 Number of files uploaded 2.4 List of vocabularies and number of terms 2.5 List of enabled views with a number of displays 2.6 List of enabled blocks and regions 3 Modules 3.1 List of contributed modules with its Drupal 8/9 readiness status 3.2 List of custom modules enabled with the number of lines of code 3.3 List of enabled features 4 Theme 4.1 List of templates from the default theme 4.2 The number of lines of code and list of functions from the template.php 4.3 List of CSS and JS files used 5 Users 5.1 List of user roles with a number of users 5.2 List of permissions 6 Cron jobs 6.1 List of custom cron jobs   A sample report is given below for your reference Summary     Leave a reply Your email address will not be published. Required fields are marked *
/themes/custom/zyxpro_light/images/placeholder.png
25th June 2020 jitsi
close

on 25th June 2020 / by sandeep.sasikumar
Jitsi is a collection of free and Open Source Multi-Platform VOIP, video conferencing applications for different web platforms. Jitsi comprises the Jitsi Video bridge and Jitsi Meet which lets you have conferences over the internet. With a lot of video conferencing tools around the place what are the key features that make Jisti different from the top competitors in the industry? Yes, Jitsi is the favorite for people who consider privacy as a concern. The key features are as below: 1) Unlike other video conferencing technologies, Jitsi Bridge passes everyone's video and audio to all participants rather than mixing this up. This provides better quality and lower latency solution. 2) You will be able to run your own service in a more scalable and inexpensive manner. 3) Jitsi supports advanced video routing mechanisms such as bandwidth estimations, scalable video coding, etc. 4) Jitsi is compatible with WebRTC, the open standard for web communication. 5) The installation and configuration of Jitsi in a self-hosted environment are easier. 6) The integration part is also an added feature, Jitsi is much easier to integrate with chat environments like Mattermost. For example, You have to follow some detailed configuration steps to integrate Zoom with Mattermost. Considering Jitsi, it is far easier. Please refer below links for the different steps on how to install and configure Jitsi as a self-hosted solution and also on the different Jitsi projects. How to install and configure Jitsi Meet on an Ubuntu server How to integrate Jitsi Meet with Mattermost   Leave a reply Your email address will not be published. Required fields are marked *
/themes/custom/zyxpro_light/images/placeholder.png
25th June 2020 Letsencrypt , Ssl
close

on 25th June 2020 / by sandeep.sasikumar
The Let’s Encrypt SSL certificate is valid for 90 days and the users will need to renew the SSL certificate every 90 days. So in order to make this automated, we will be setting up a cron job that will automatically renew the SSL certificates which are about to expire. The Certbot auto-renew option provides the user to auto-renew your Let's Encrypt SSL certificate automatically through a cron job. In certain cases in which the OS version is Ubuntu 12.04 LTS the certbot auto-renew option will stop working with the following error. /opt/eff.org/certbot/venv/bin/python: No module named pip.__main__; 'pip' is a package and cannot be directly executed Traceback (most recent call last):   File "/tmp/tmp.fpN7wJrJm9/pipstrap.py", line 177, in <module>     sys.exit(main())   File "/tmp/tmp.fpN7wJrJm9/pipstrap.py", line 149, in main     pip_version = StrictVersion(check_output([python, '-m', 'pip', '--version'])   File "/usr/lib/python2.7/subprocess.py", line 544, in check_output     raise CalledProcessError(retcode, cmd, output=output) subprocess.CalledProcessError: Command '['/opt/eff.org/certbot/venv/bin/python', '-m', 'pip', '--version']' returned non-zero exit status 1 The cause of the issue is with the use of python command in the local version of certbot which is no longer supported in Ubuntu 12.04 version which is outdated. You need to modify your local version of certbot-auto to use pip install instead of python -m pip AND use --no-self-upgrade.  The solution for the problem is to either upgrade the OS version to the latest LTS which is always the recommended option. Also, as a quick fix, you will be able to revert the certbot version to 0.31 and re-run the SSL renewal commands. Please see below the commands for this fix: wget https://raw.githubusercontent.com/certbot/certbot/75499277be6699fd5a9b884837546391950a3ec9/certbot-auto chmod +x ./certbot-auto ./certbot-auto --no-self-upgrade Leave a reply Your email address will not be published. Required fields are marked *
/themes/custom/zyxpro_light/images/placeholder.png
25th June 2020 jitsi , Installation
close

on 25th June 2020 / by sandeep.sasikumar
Jitsi meet is a free open source video conferencing web application. Just like Google Meet and Zoom, Jitsi meet provides the option to easily create a meeting in a browser within seconds without additional software or browser extensions. Jitsi doesn't require an account to use its additional features like Screen Sharing, Group chat, Integration with different chat platforms like Mattermost or Slack. Below are the steps to install and configure Jitsi on an Ubuntu server. Step 1: You will need to have a server with SSH root access. Step 2: Install the Jitsi repository key using the below command. wget -qO - https://download.jitsi.org/jitsi-key.gpg.key | sudo apt-key add -  Step 3: We need to create a new repository source file – sources.list.d – for the Jitsi repo: sudo sh -c "echo 'deb https://download.jitsi.org stable/' > /etc/apt/sources.list.d/jitsi-stable.list" Step 4: Install apt-transport-https to access packages with an SSL (HTTPS) connection: sudo apt-get install apt-transport-https Step 5: Update your Ubuntu server package lists: sudo apt-get -y update Step 6: Install the Jitsi Meet full suite: sudo apt-get -y install jitsi-meet Step 7: When prompted, type your intended hostname or domain for the Jitsi URL Step 8: Once the above steps are completed we will need to install an SSL certificate for the domain. You will be able to install a self-signed SSL or your an owned SSL certificate. Leave a reply Your email address will not be published. Required fields are marked *
/themes/custom/zyxpro_light/images/placeholder.png
24th June 2020 Drupal 9 , Drupal Contribution
close

on 24th June 2020 / by webmaster
  We are glad to announce that a new version of Search404 2.0.0 was released on the same day Drupal 9 was released. This version fully supports Drupal 9.  In this release of the module, we’ve chosen to go with the fully semantic versioning model, which means, the version 2.0.0 supports Drupal Core 8.8.3 or higher version. The 8.x-1.0 release will be there for some more time to support older versions. The 2.0.0 release mainly removes the deprecated code and uses the new solution that is supported by Drupal 9. You can find the full changelog here - https://www.drupal.org/project/search404/releases/2.0.0 Download it and try it out from https://www.drupal.org/project/search404 A demo installation is available at https://search404.demos.zyxware.com/ for those who want to try it without installing it. Zyxware Technologies as a Free Software Company has been one of the flag bearers for the Free and Open Source Software movement in India. Since our inception in 2006, we have been actively promoting the idea of FOSS and related freedoms through various activities like Freedom Walk to spread the message of Freedom, Freedom Toaster for making Free Software accessible to public, contributions to Swathanthra Malayalam Computing, development of a real time epidemic outbreak tracking system for Ministry of Health and Family Welfare, Kerala and much more. Zyxware Technologies is one of the top ten contributors to Drupal, we have delivered more than 200 Drupal projects across diverse sectors and currently more than 60,000 websites use modules and themes contributed and maintained by us. We have also been an active member in the Drupal community in the USA, Australia and India.   For those who are new to Search404 Search404 is an alternative to showing the standard “404 Page Not Found”. When a 404 error occurs, this module does a search on the keywords in the URL, e.g, if a user goes to http://example.com/does/not/exist , this module will do a search for “does not exist” and show the result of the search instead of the 404 page. This should help retain visitors coming in from old URLs linked from other sites or from search indices. Features Jump directly to the search result when there is only one result   Jump directly to the first search result even when there are multiple results   Do a "Search" with custom path instead of a Drupal Search when a 404 occurs   Use a 301 Redirect instead of 302 Redirect   Use OR between keywords when searching   Ignore specific words from search query   Ignore specific paths   Ignore specific extensions   Custom error message   Custom page title   Custom page text   Redirection URL for empty search results   This module fully supports the default Drupal Search as well as any other search engines used with SearchAPI or any other means with custom search URL functionality.  We sincerely thank all the community members who contributed to the porting of the module. These are the people who primarily helped the d9 release,  Frederick Henderson Vimal Joseph Byron Duvall Barbara Bombachini Martin Anderson-Clutz Sarath Kumar Mahipal Purohit  Leave a reply Your email address will not be published. Required fields are marked *
Subscribe to