Category: Technology

Angular 7 upgrade | What will you miss if you ignore?

Posted on by galaxy-admin

Angular 6, released earlier in May 2018 didn’t offer much improvements on the performance part. It was mainly focused on making Angular migration-friendly. Google dropped Angular 7 just after four months of development and it seems to make up for that part of the framework.

The upgrade was released on October 18 followed by an incremental update 7.1 on November 28.

Angular 7 version upgrade is not a feature-intense update, instead it focuses on the core framework. As a result you get better performing applications with small packages and faster response.

The long-due Ivy compiler is still under works but other things were delivered as promised.

CLI prompts

Angular CLI can prompt users to help them make decisions. ng new prompts users of routes and styles to use, while ng add @angular/material asks users what theme they want and if they want gestures or animations.

Performance

Application performance has been improved by automatically adding or removing the reflect metadata polyfill, making applications smaller in production.

Angular Material and CDK (Component Dev Kit)

Angular 7 features virtual scrolling, for dynamically loading and unloading items from DOM according to the visible parts of the lists. Also, applications can be fitted with a drag-and-drop capability. Angular Elements components now support content projection via slots.

Why Angular 7?

Why not when it offers brilliant perks like these.

  • Comes with better mobile and desktop application support.
  • Application packages are smaller and efficient.
  • CLI prompts help you make decisions and code faster.
  • Angular 7 now features budget bundle. It warns when application exceeds the default size
  • Fast rendering of large lists with virtual scrolling
  • Upgrade takes less than 10 minutes for most of the apps.

Things that were further improved with the latest incremental update Angular 7.1

  • A bug fix to the Ivy compiler so it now can generate inputs and aliases properly. The compiler had been generating an outdated input property format.
  • Also in the compiler, a bug fix generates a relative path only in summary file errors.
  • Previously, errors in the summary file included absolute file names.
  • The compiler now can mark an InvokeFunctionExpr as pure.
  • For the core of the framework, a static dependency to @angular/compiler has been removed from @angular/core.
  • A regression in the router has been fixed in which the navigateByUrl promise did not resolve on CanLoad failure.
  • For service workers, typing has been added to the public API guard and lint errors have been fixed.

Planning an Angular 7 upgrade? Mind these prerequisites.

For apps that are running on Angular 6 & RxJS 6 use this command:

$ ng update @angular/cli @angular/core

And for the apps running Angular Material

$ ng update @angular/material

Upgrading Angular is a hassle-free process but more often than not version upgrades can mess your app’s current state. Upgrade failures are universal for every software so it is highly advised that you perform the upgrade with the help of an Angular expert. Speaking of which, you can get in touch with us.

Developing Custom Softwares, the Agile Way

Posted on by galaxy-admin

Agile blog image 3

The dynamic business environment with rapid technological changes have resulted in subsequent changes in customer requirements. They now look forward to options which have an ability to deliver quick and better solutions. As a result, the web development companies long for such approaches which enables them deliver softwares accordingly. The companies turned to Agile Development approach which consists of Iterative and incremental approach for faster and better software development.

In sharp contrast to traditional software development practices, agile is all about teamwork, flexibility, periodic assessments, feedback integration, quick delivery and better products.

At Galaxy Weblinks, Agile development methodology remains a guiding principle for software development practices to offer unique deliveries and be a frontrunner. There exists some compelling reasons why, we choose to do so.

Let’s capture some advantages of this methodology:

Speed and Flexibility

Fast deliveries, regular iterations and flexibility remains the norm of the software development. With exhaustive project development and management strategies in place, Agile holds the prominence. It permits developers to manage and improve priorities at each phase and stage of project.

Customer Collaboration

One of the prime approaches Galaxy Weblinks believes in, is Customer Collaboration. There exists some good reasons behind it. One, it lets us understand the customer’s point of view at each step and second, it develops a strong understanding as to what the client requirements are and lets us visualise deliveries from their perspective. We seek inputs at each step from them to ensure that their requirements are met.

Customer Collaboration 1(1)

Our designers work in continuous collaboration with team members so that the customers feedback gets integrated at each iterations and the next one gets enhanced than previous.

Iterative and Incremental Development

Agile focuses on incremental and iterative development. Hence, the entire project gets broken down into iterations or sprints, at the end of which feedback is sought from client and reflecting transparency, customer orientation and scope for product improvements.

Improved Communication

Team member interactions and client collaborations are one of the key driving practices in Agile. With a channel of feedback in place and iterative cycles of development, the communication structure remains well defined and let exchange developers, clients and project manager’s view on projects fruitfully to carve out a refined product delivery.

Time to Market

Adopting Agile methodology lets team plan and deliver the iteration in a timely manner. The entire project phases – planning, coding & development, creation of rapid prototypes or delivery, all gets empanelled w.r.t. time frame. The clients doesn’t have to wait for the entire software to be developed. They get a basic framework or a prototype to assess operability and functionalities and suggest improvements if any. These minor alterations get integrated at the very same stage. Thus resulting in delivering a better, novel product in a faster manner.

Predictable Costs

The project under agile is divided in sprints with a duration. The cost of development gets better managed as the work to be performed by team is in a fixed schedule. With these, the client is better able to understand the tentative cost of each functionality/ feature.

Improved products

With high involvement of customers in project development, they get an opportunity to understand, interpret and give inputs at all stages. This opens a window of continuous improvement to make software developed a perfect fit, as per the business requirements. Thus, enabling an improved software/ application being developed

To conclude, Agile processes brings in focussed development, which lets deliver a tangible product, engaging all stakeholders at each step resulting in saving time and money with better business products for clients.

Galaxy Weblinks offers a custom software and web development solutions employing Agile. Contact us to find how we can improve your online business remarkably.

Craft & its Plugins | A transforming workflow

Posted on by galaxy-admin
We like to think of Craft CMS as a Transformer (one with BumbleBee as his friend) and plugins as its Jet Pack. And every time we develop a plugin for Craft, it helps our Craft projects reach client’s expectations. Craft is a powerful CMS and its developers have left a lot of scope for extensibility. Plugins do the things that Craft CMS cannot. In our workflow Craft plugins help us do more than what Craft can do. Often our clients steer clear of plugin development because of the extra work and vulnerabilities it brings. That’s not the case with Craft plugins. You can read about plugin vulnerabilities in our Craft Vs WordPress blog. Before diving into our plugin development workflow you should know about Composer and Pluginfactory. Craft CMS 3 is highly dependent on the Composer for its development. Composer is a PHP package manager that helps Craft with PHP dependencies. Pluginfactory on the other hand is a different tool altogether it creates scaffolding for plugins. We use the scaffolding to configure our code in it. After defining the need we get on to the business of building the plugins. Craft documentation has a pretty straightforward approach to plugin development. Being big fans of Craft’s coding techniques we looked no further for inspiration. Our plugin development process is as simple as Craft’s.

Building “The Jet Pack” for Craft CMS

Image credit: pixabay

Nomenclature for the assembly

Like the parts of a Jet Pack, parts of the plugin should be named in a consistent format so that they can be identified easily. We follow the naming guidelines whether we’re naming packages or handles. It is safe and efficient to follow a particular nomenclature.

According to the Craft’s documentation-

  • Plugin handle must have lowercase letters, numbers, and dashes. All in Kebab case
  • Package name should have Craft- prefixed to it, after the ‘/’

Creating blueprint for “The Jet Pack”

Image credit: matej

Before we found out about pluginfactory, like every other developer we used to make our plugin structure manually. Pluginfactory creates a skeleton for your plugin in just a few clicks. It is created by a Craft developer named Andrew Welch. The scaffolding on pluginfactory are made using the Yeoman generator.

Details needed to create the scaffolding

  • API version
  • Plugin name
  • Description
  • Initial version
  • Plugin vendor
  • Plugin author
  • Author URL
  • Github name
When the structure is ready we feed our code into it and voila! Our plugin is ready.

Installing “The Jet Pack”

Image credit: jaguarmena

Plugins are written as composer packages. For Craft to recognize the plugin we have to install it as a composer dependency of the project. The installation depends on the nature of plugin whether it’s local or public. If it’s local we install it by configuring the composer.json and adding a new path repository record. The path must point toward the plugin’s root. If a plugin is made for a public release then it can also be installed directly via composer. After registering the plugin as a new composer package on Packagist, a require package command in composer fetches the package and installs it.

Final word: Plugins are essential

Image credit: jaguarmena

Plugins are not a crucial part of a CMS but it sure is important to achieve something out of the box based on client’s requirement. We find plugins to be extremely powerful and time-saving. The most important function of a plugin is to eliminate tedious and repetitive tasks by automating it. Some examples might put its importance into perspective.
  • SEO plugins make search engine optimization easier
  • E-commerce plugins improve customer journey.
  • Analytic plugins help with insights on page performance
  • Text and image editor plugins provide rich editing functionalities
If you’re looking to transform your Craft CMS experience — visual or performance — then plugins can help. As for the development of the plugin, talk to us here.

How Zeplin Transforms Agile Workflows?

Posted on by galaxy-admin
With 71% of businesses using Agile approaches, tools like Zeplin are becoming more and more important. They’re not just facilitating smoother workflows; they’re reshaping how teams collaborate on software development. Zeplin, specifically, has made notable strides in this area, revolutionizing the way design and development teams interact.

Design Systems and Zeplin: A Synergy for Success

Zeplin’s role in reinforcing design systems is vital in an Agile environment. By providing a unified platform for design elements, it ensures coherence and uniformity across projects. A notable example is Airbnb’s design system, which utilizes tools like Zeplin to maintain a consistent brand and user experience across their digital platforms. By streamlining their design process, Airbnb has managed to reduce design discrepancies significantly, leading to a more cohesive user interface.

Streamlining UI/UX Feedback with Zeplin

Feedback loops are essential in Agile development, and Zeplin optimizes this by bridging the communication gap between designers and developers. For instance, Dropbox reported enhanced efficiency in their design process after integrating Zeplin. The platform allowed for quicker feedback and iterations, reducing their design revision time by approximately 30%. UI/UX designers can utilize Zeplin’s interactive environment to rapidly prototype and iterate designs, ensuring faster approvals and implementation.

Effective Collaboration through Zeplin Integrations

Zeplin’s ability to integrate with tools like Slack and JIRA enhances its effectiveness in Agile workflows. Shopify’s integration of Zeplin with Slack serves as a great example. This integration has facilitated faster updates and feedback within their teams, leading to improved project management and a more synchronized workflow. Such integrations demonstrate Zeplin’s versatility and its capacity to adapt to various team dynamics and project requirements. Teams should explore Zeplin’s integration capabilities to enhance real-time collaboration and project tracking, ensuring a more aligned and efficient workflow.

Overcoming Communication Challenges in Design with Zeplin

Communication is a pivotal aspect of project management, and Zeplin addresses this by providing clear and organized design specifications. IBM’s design team has utilized Zeplin to effectively manage communication among their globally distributed teams. This has led to a more streamlined and efficient design process, significantly reducing misunderstandings and delays in project timelines.

Quantifying Zeplin’s Impact on Agile Workflows

The measurable impact of Zeplin in Agile workflows is seen in the improvements in team productivity and project timelines. According to recent statistics, companies leveraging Zeplin have reported a 20-25% improvement in project turnaround times. This demonstrates Zeplin’s profound impact on enhancing efficiency and streamlining processes in Agile environments.

Galaxy Weblinks: Pioneering Agile Excellence with Zeplin

Navigating the complexities of UI/UX design, web development, and Agile methodologies requires more than just understanding; it demands the right tools and expertise. Galaxy Weblinks, with its deep-rooted experience in Agile practices and a suite of services including UI/UX and web development, is uniquely positioned to help businesses harness the full potential of tools like Zeplin. We specialize in fine-tuning Agile processes, ensuring our clients not only keep pace but lead in the competitive tech landscape. Reach out to us and transform your Agile journey into a story of success and innovation.

Drupal 8.6 update. What’s new?

Posted on by galaxy-admin

Keeping up with the promises made during earlier announcements, Drupal released the 8.6 version on September 5. The update comes with significant additions.

Drupal 8.6 now supports MySQL 8. Also, with this update a monolingual Drupal 6 site can be migrated to Drupal 8 directly from the user interface. Multilingual website migration using the UI is still under development. Apart from these changes, other important changes are listed below.

Easier Drupal installations

Installations on Drupal have been made easier. There are two ways to install Drupal.

  1. A quick start command installs Drupal within 2 minutes using PHP’s built in web server and SQlite database.
  2. Drupal’s installer now recognizes existing configurations and provides an option to install updates for that configuration.

Test environment to showcase features

Image source: drupal.org

Drupal now provides an easy-to-install test environment in a demo website called umami. The demo profile can be used to showcase Drupal’s data modeling, listing, page composition, and content moderation capabilities to prospects. It will also help in onboarding new users.

Support for remote media types

Image source: drupal.org

This Drupal update adds support for remote media types. You can now easily embed YouTube and Vimeo videos.

Experimental features

Image source: drupal.org

Workspace module and layout builder are some of the experimental features that are introduced with this update.

Workspace module lets you work on different projects simultaneously. You can segregate your projects using workspaces.

Content layout builder is an under-development experimental version. The stable version will be a powerful tool against authoring challenges.

Drupal 8.6 update package brings some much-needed additions to the table, such as:

  • Nightwatch.js and Prettier is added to make it more familiar to Javascript and PHP developers.
  • Tests are converted from SimpleTest to PHPUnit.

Whereas, JSON API was skipped in this update.

Any updates, whether it’s incremental or critical, means a mandatory upgrade for the older versions. Drupal will end support for Drupal 6 but support for Drupal 7 will continue.

Upgrade to Drupal 8.6 now.

Get in touch with our Drupal experts here!

ACF vs Visual Composer website builder: Which is better?

Posted on by galaxy-admin
Building a WordPress website? The WordPress community provides you with plenty of options. You can either make an easy one using WordPress themes or a custom one using website builders. A website builder is the most convenient way to make a personalised website. WordPress community provides you with a ton of free and paid builders as per your needs and levels of expertise. Once you make up your mind on what you plan to do with your website, then you can chalk-out the structure and the elements that you’re going to need for the website to function. After locking in your requirements, you can choose your website builder. We recommend using two of our recent favorites.
  • ACF
  • Visual Composer

ACF

Image Source: advancedcustomfields.com

The interface of the Advanced Custom Fields is simple. It lets you create dynamic fields for individual elements of your website. Installation and activation of ACF adds Custom Fields to your WordPress dashboard. From the Custom Fields menu you can take full control of your edit screen & custom field data. The minimalistic interface of ACF can be mistaken for an under equipped website builder. You can make some of the most complex and powerful websites with ACF. The best thing about ACF’s interface is that it doesn’t try to overwhelm you. It only shows the functions that you need. ACF gives you the full control of your website right from header to footer. You can build individual elements of your website with custom fields. There are 25+ different field types to choose from, vis-a-vis. text, image, gallery and WYSIWYG editor. These fields are dynamic. You can use them to give your client an easy way to update their website according to their liking.

Visual Composer

Image Source: visualcomposer.io

It has a clean and modern interface which allows you to make basic layouts with ease. The interface lets you work on different elements of the website, right then and there. Visual Composer has a floating window which pops up every time you’re trying to add or edit an element. The window is movable and resizable, you can place it anywhere if it’s obstructing your view. Visual Composer gives you the best of both worlds with its backend and frontend editor. While building, you can easily choose from the ready-made layouts of landing page, call to action page, feature list, description page, service list or a product page. Adding elements in the website is also easy with the element window. The drag and drop visuals come at a cost of short codes. Migrating to another website builder or uninstalling Visual Composer leaves short codes in the content, rendering it unreadable. Fixing these short codes is an another chore on its own.

Which one do we prefer over another, you ask?

Well it’s a tough choice but…ACF! ACF and Visual Composer are serving two different audiences. ACF is focused on developers. Visual Composer on the other hand targets the people with little to no knowledge of website development. In case of both the builders. the audiences don’t need to have an extensive coding knowledge. Visual Composer focuses on making the website building experience as easy as it can be. Visual Composer is not made for complex websites it will only provide you with enough elements to get your website up and running.

Why ACF?

ACF does a commendable job with its active development and incredible support. The developers are constantly working to keep the plugin current. The heavily themed interface of Visual Composer is slow. The floating window takes time to load the elements, and the builder shows glitches when you switch from frontend to backend. Visual Composer is affordable for personal license but expensive for client work. ‘Advanced Custom Fields’ is more affordable and provides value for money. Another thing that doesn’t work in Visual Composer’s favor is that the pre-sales service and overall support for Visual Composer is terrible. It comes as no surprise that ACF has 900,000+ active installations compared to Visual Composer’s 500,000+. You can save your time and money with theme-based websites but you might not get the exact thing you’re looking for. Themes are designed keeping a universal requirement in mind. Your unique requirement might not fit in those templates everytime. But, if you have unique requirements and want the best for your website, then website builder is the right bid. Making custom websites is a hectic process. We can make that process easier. Our expert development team knows website builders like the back of their hands. Hit us up here if you’re looking for WordPress development partners.

WhatsApp Business API: What’s in the limited public preview?

Posted on by galaxy-admin

Facebook has finally decided to monetize WhatsApp.

Earlier this month, on August 1, Facebook rolled its long-in-development WhatsApp Business API for medium to large businesses. This is not to be confused with WhatsApp business application, which is only meant for small businesses.

The business API will let you communicate with your customers all over the world, in real time.

The API allows you to make a business profile on WhatsApp. You can include all the necessary information like address, business description, email address, phone numbers, and website.

The motive of the API is to bridge the gap between businesses and their customers. WhatsApp currently has an active user base of 1.2 billion members. The business API might become the goldmine for customer services and marketing. It is the most convenient place to provide services and support to your customers.

You can use the API to send notifications such as shipping confirmations, appointment reminders, event tickets, tracking details etc.

For the initial release though, the API comes with some limitations.

Businesses cannot send messages to WhatsApp users until the users have initiated a contact, for example making an order or booking a ticket.

There is also a limit on outbound message rates. The tested maximum outbound message rate is 15 message/second.

The API not only allows you to connect directly to your customers but it also keeps an insight on the messages and response rates. You can access these message analytics in the dashboard.

The business API comes with some useful features:

  • Instance monitoring- You can export internal metrics in prometheus text format and use the obtained data to analyse the performance.
  • Message templates- You can create different message templates for different instances & situations. You can also set locales for different languages.
  • Verified name- Your business profile gets a verified name with which you can communicate with your customers. The verification badge ensures authenticity and establishes trust amongst the users.
  • Labels- The chat can get clumsy. Labels can help you sort your customers and chats. Create Labels and organize your chats accordingly.

Similar to the basic WhatsApp app, all the information between the business and the clients will remain end-to-end encrypted.

The API is currently in a limited public preview. You can submit your application here for consideration if you want to get the business API.

How to use Macros with Twig in Craft CMS — DRY

Posted on by galaxy-admin

Templating is one of the most commonly used processes in web development. It helps with easier management during the development & design process. Apart from the management, templating helps with keeping the visual consistency.

Craft CMS comes with a cool templating engine — Twig. And we love to use macros to work on redundant parts while working on a Craft CMS project. Macros can be compared to ‘functions’ in PHP also known as DRY templating in other languages. We usually use it to generate markups that have slight final variations in the implementation.

To simplify your code you must first make a visual hierarchy of the page you’re working on. That way you can determine the components you’re going to need. Make macros for those components in the twig templating engine.

Macro implementations can be changed based on the parameters passed to it. For instance footers, dates, images and other media are a recurring part of a website. You can make macros for these components.

Skeleton of Twig Macro

{% macro coolMacroName (parameter 1,…..) %} {content of macro goes here} {% endmacro %}

To call the macro – {% import ‘_macroFilename’ as ‘macroVariable’ %} {{ macrovariable.coolMacroName(parameter1, parameter2,….) }}

The best practice is to add the relevant macros to a file and then call the file as a variable. Use the variable to call the macro at the places you need.

The first Macro we use often is-

Macro for responsive image component in Craft CMS

You can reduce and automate a lot of work which goes in responsive image formatting. Utilize Craft’s ‘Image transforms’ with a twig for images and define your transform macros in it. You will also have to define different types of macros for different image formatting needs.

A macro for Device-pixel ratio adaptable fixed size images and other one for variable size responsive images. Also add an internal class to call it inside your twig image file for additional attributes.

Macro for video component in Craft CMS

Videos are an integral part of every website, so making a twig component for it seems practical, otherwise you will spend your precious time writing and tweaking html code for videos.

In the macro define the logic of the video component. The file should have proper information about the component, the parameters which are accepted, the value each parameter requires, and whether the parameter is optional or not. You also need to mention, what the arrays and objects are made of because without that information you yourself and other developers won’t know, what information can/must or cannot be passed while calling the component.

Making macros for date formatting in Craft CMS

Dates might look like a trivial part of a template but it gets tedious and complex when you have to define its format in every other template.

You can contain different modifiable date formats in a macro. It saves you the effort of having to define it time and again and maintaining consistency all along. Short or long, just define the format in a macro and call it wherever you need it.

Reduce repeated reference of paths in Craft CMS

Include tag in twig allows you to call a template within a template. Each one you make gets stored in /templates/ folder by default, even your include templates.

You can call these partial templates separately followed by the same path or make a macro instead to reduce the repeated reference of path.

To achieve code consistency, store your ‘include’ templates separately. So that you can call the include templates within the macro. You can also call your ‘include templates’ from multiple locations.

Final words

That’s pretty much it. Apart from few other variations, creating macros for page components is a good and effective way to reduce the redundancy and complexity of the code. You can always go through this detailed video for macros here.

We’ve been experimenting with several DRY techniques ourselves. It improves the speed of our work cycle.

How are you using Twig & its components? If you need help with your Craft CMS project, connect with us right away.

Craft Vs Perch: A Clash Of Customizable CMSs

Posted on by galaxy-admin
In our earlier blogs we’ve favoured Craft CMS heavily because of its ‘content first’ philosophy. Perch also majorly focuses on the content but with functionality shredded down to the absolute basics. It’s so minimalistic and that it is considered to be appropriate for small-scale projects only. Anyways, Perch has its perks as compared to conventional CMSs. Let’s put it to the test against the reigning champion, Craft CMS.

Feature comparison of Craft & Perch

Craft is loaded with crucial features, vis-a-vis:

Live Preview

Craft allows you to review the edits as you’re making them in a split screen window mode.

Matrix

Gives you the full control of your content, from layout and placement to the order.

Localization

You can create locales for the desired language and enable with just a click.

One-click updates

Simply update everything with one click from the control panel. The updater even notifies you according to the nature of the update; whether it’s incremental or critical.

Built from scratch

Craft CMS team clearly states that we don’t make any assumptions about your content. You get full control of your website and you can craft it the way you want. On the other hand, Perch has the following features to offer:

Preview

You get to see the changes only after when they are saved in the draft. A bit old fashioned to be honest but it goes with Perch’s tagline of ‘a very little CMS’

Custom Fields

The feature lets you create custom fields throughout the page.

Localization

Perch lets you localize your webpages by creating separate pages or duplicating regions for each language.

Updates

Updating in Perch is a bit cumbersome. You need to replace the old files with the new ones.

Retrofit or build from scratch

You can retrofit an existing website or build a minimal website from scratch.

Documentation comparison of Craft & Perch

Documentation is a crucial part of a CMS. It is important to define the features and inner workings of a CMS so that the new users know how to use it. It’s a map for the CMS users. Documentation, if not done properly, might mislead your users. There is nothing more off-putting than lack of documentation. Users are trying to find their way around the new CMS and if there is no good map, they’ll probably get lost and bounce-off faster than light from a mirror.

Craft

As far as the documentation is concerned Craft excels at it. You will immediately find everything you’re looking for. From update logs and feature definitions to essential how tos; Craft’s documentation has got it all.

Perch

Being the older CMS of the two, extra years in development hasn’t added much in favour of Perch CMS. Perch documentation is enough to get a hold of the basics but it disappoints when you’re half-way into the development process. Especially when you’re trying to give additional functionalities to your CMS with add-ons.

Community Support comparison of Craft & Perch

Documentation can only do so much, the real knowledge and solutions are derived from the dedicated communities formed around the CMS. The community makes up for the lack of documentation and helps you solve on-site issues.

Craft

Craft has a proactive community of dedicated developers and users that help to keep Craft as current as it can be. The Craft community just keeps growing as more people fall in love with the CMS.

Perch

Perch doesn’t aim to be a big CMS and hence it remains that way with 0.1% of the market share. It has a simple and functional CMS to offer but it’s not backed by convenient documentation and a good community support.
  • Perch Slack channel is no longer active
  • 3725 followers on Twitter
  • 615 fans on Facebook

User Interface comparison of Craft & Perch

User interface determines how you interact with the content. Both the CMSs provide you with a dashboard to edit and manipulate your content using the interface. The simpler the interface the lesser the struggle to understand it.

Craft

Craft focuses on providing powerful and bespoke results. The interface hence is equipped with essential functionalities to handle large amounts of data gracefully. Although it is considered to be highly-technical and dev-friendly, Craft CMS offers a conveniently easy drag and drop interface for layout design.

Perch

Perch on the other hand stays true to its principle of being basic with the user interface too. It is comprehensive and doesn’t require extensive technical expertise. However to people who want more control over their content it is basically under equipped.

Development Cycle comparison of Craft & Perch

Craft uses an unconventional and complex data structure, hence the bigger learning curve. Singles, structures, and channels as data structures give you unmatched control and editing capabilities. For front-end development Craft utilizes Twig templating engine for advanced templates and data manipulation. Perch uses PHP functions for the development as compared to Twig in Craft. The content structure is pretty straight forward, it features pages, regions, and shared regions for data manipulation. For the added functionality of reusing content throughout the page you need to upgrade to larger version of Perch which is Perch Runway. Both the CMSs have their benefits but it is rather important and practical to go with the CMS which is flexible and future-proof. While Perch is a straight forward CMS which doesn’t try too hard to be something it’s not, it is only good for small projects and businesses with a tight budget. On the contrary, Craft CMS provides necessary functionalities paired with high-end security. It is a capable and viable choice for both developers and content editors. Looking at the security track record of Craft we’ve always chosen Craft CMS over every other CMS for our clients. In case you are confused about how

How to migrate a Craft 2 project to Craft 3?

Posted on by galaxy-admin

Craft 3 update changed a lot of things. Added functionalities aside, the process of installing and maintaining the CMS also changed with this breakpoint release.

Craft 3 almost makes it necessary to migrate your website from Craft 2. It is better in every aspect, including security and the extended plugin store. The store comes with plugin trials and 30-day license return policy.

For the incremental updates, you just had to click on a button. But with the breakpoint release, Craft CMS tweaked its ways of handling things.

It is advised to get an expert’s help for the migration because there are a lot of things that can go wrong with the migration, for instance:

  • Control panel prompting to install Craft instead of the update database dialogue.
  • Database configuration settings which are no longer needed

Also, to avoid errors, you have to follow the same naming schemes that were used in your old database; like using same prefixes with the new database connection settings.

There are two steps involved in the migration process of a Craft 2 project.

  • Craft 3 Installation
  • Manual Migration

Step 1: Craft 3 Installation

To install Craft 3, follow the same steps as mentioned in ‘How to setup a new Craft CMS project’ and then proceed with the migration.

You need to take care of the following requirements before proceeding with the installation:

  • Craft 3 requires PHP 7+ and at least 256 MB of memory for PHP
  • The installation requires Craft 2.6.2788
  • Make sure that your plugins are ported to Craft 3 (check the status at the bottom of the update page)
  • Keep a backup of your old database.

After the installation, proceed with the migration process. According to the Craft 3 upgrade documentation following are the steps you need to follow to migrate your Craft 2 project to Craft 3.

Step 2: Manual Migration

Import your database connection settings from your old database file craft/config/db.php to your .env file in the Craft 3 directory.

Now copy the following settings and configuration files from the old Craft 2 directory to the new Craft 3 directory.

  • Copy settings from craft/config/general.php to config/general.php
  • Copy craft/config/license.key file to config/
  • Copy configuration files from craft/config/redactor/ to config/redactor/
  • Copy files from craft/storage/rebrand/ to storage/rebrand/
  • Copy photos from craft/storage/userphotos/ to storage/userphotos/
  • Copy templates from craft/templates/ to templates/
  • Copy the changes made, if any, from public/index.php file to web/index.php file
  • Copy other files from old public/ to web/ directory.

After copying the files to the web/directory, update the web server to point to it. Enter the Craft’s control panel URL in the browser. It should prompt you to update your database.

Known problems with the migration from Craft 2 to Craft 3

If all goes well you will be able to run the latest Craft 3 with your old database intact. If not then you might be facing the following problems.

Craft installer pops up when accessing the control panel

Your old database connection settings are not matching with the new .env file. It is most likely happening because of a wrong DB_TABLE_PREFIX.

“Setting unknown property:

craft\config\DbConfig::initSQLs” error.

The initSQLs database configuration setting was used in Craft 2 to fix MySQL 5.7 support. It is redundant in Craft 3. Remove the line beginning with ‘initSQLs’ in the config/db.php file to delete the setting.

To avoid major hassles and loss of database, it is recommended that you get a Craft partner onboard. In case you have further queries, you can connect with our Craft CMS experts here.