Drupal vs. PrestaShop

We developed a corporate website using Drupal, which features a large number of static pages and several dynamic functions, including a contact us form, location finder, and job posting. We utilized Drupal with some customization to achieve the desired functionalities. We have also worked on e-commerce sites using Drupal, and there is a scope for improvements, specifically in cataloging.

Incentivized

I really wouldn't recommend PrestaShop to every person or business. This service has very good features to be able to create an online store and allow customers to add products to their cart instantly, it allows to make electronic payments quickly and the money reaches the company's wallet instantly, without However, it has many disadvantages, PrestaShop does not have a technical service to help implement the software on the website, so if you are thinking of using PrestaShop, you must first have a good team of web developers who are capable of integrating PrestaShop with the Wordpress site without any problem, in addition, PrestaShop takes up a lot of space in the Hosting service, each product that you add to the PrestaShop catalog occupies much more Hosting space and this causes the catalog to take longer to load when the client comes to visualize it. To use PrestaShop I recommend a very powerful Hosting that is able to withstand the high consumption it has.

Incentivized

• Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website.
• Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp.
• Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require.

Incentivized

• Quite easy to use compared to other open-source e-commerce software.
• Has lots of free plugins to help you set up a great basic shop.
• You can easily create your own unique site.
• Lots of payment option plugins and you can use them to sell globally.

Incentivized

• Security and new release notifications are a hassle as they happen too often
• Allowing them to write PHP modules is a big advantage, but sometimes integrating them is a small challenge due to the version the developer is working on.
• Steep learning curve, but worth it

Incentivized

• Since it starts as ready to go platform it's difficult to protect your store from being copied by someone else
• Without a developer, you depend on Prestashop's modules marketplace that lacks free extensions
• Since it isn't an enterprise level platform the use of Prestashop is strictly related to the size of your business

Incentivized

I really like Drupal, and besides the one major issue with not being able to update from version 6 to version 7 and I am happy to continuing using it. Hopefully as time goes on they will make it easier to upgrade or provide better tools for mid-level web designers like myself to build out new sites without the help of expensive 3rd party's.

Considering the problems we had and still have, 0.

It has a very steep learning curve. When starting with Drupal, the functionality and setup have to be learned, which is complex in comparison to tools like WordPress. Drupal is more powerful and can create a wider range of applications, but it definitely has a learning curve. I would recommend it to anyone who wants to make a dynamic web application bigger than the scale of a WordPress blog.

Incentivized

The lack of performance and the unstable system make it very hard to use it for a serious e-commerce application.

Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).

100s of implementation and so far no major security breaches.

Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.

Incentivized

Some caching and optimization is definitely needed. However, it is not as bloated as other CMSs with lots of plugins needed.

As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.

Incentivized

Since we use PrestaShop OpenSource there is only community support. What we found is that many other users fight with the same problems and there seems no solution or input from the PrestaShop developers' side.

I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.

The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.

Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%

Incentivized

Drupal's capabilities outpace WordPress by miles. Drupal is more customizable, scales better for larger companies and has advanced content types. If you own a small business or work at a startup company, I would recommend WordPress but if your firm is trying to scale and you have more than 50 employees I would recommend Drupal.

Incentivized

As compared to other open-source systems, PrestaShop has the most elegant backend interface. Most of your standard eCommerce features come default: 1. Invoice and Delivery documents in PDF, 2. Promotion and discount mechanism, 3. SEO functionalities, 4. Quick access, 5. Statistics, 6. Categorization, Brands, Attributes, Features/Filters, sorting, pagination, list or grid view. The next best thing is the stability of versions. Currently, at only ver1.7, this is the only open-source CMS that doesn't require the constant nightmare of updating and breaking the site. The open-source community is still offering modules for ver1.5, 1.6 and 1.7. If you need modules to enhance the features, it is also a one-time cost since the versions are so stable. The experiences with 3rd party module developers are very good so far. Most modules are from EUR49-100.

Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.

Incentivized

This is the best example of "If it's not broken, don't fix it!".

• Drupal helped us launch a creative, marketing- and product-focused website with custom coding integrations tailored to our goals.
• Drupal allows us to rely on secure and consistently updated core code.
• Drupal's code taxing on the server does start to get a bit heavy as you go along with customizations, so at some point, we decided to stop. We want to ensure our Google Page Score remains high, including paying close attention to page load speed.

Incentivized

• If you don't have open source developers on staff it will be costly.
• The out-of-the box solution is not really a solution. Be prepared to hunt down modules to do standard things you'll want to do.
• The interface is unlike the e-commerce usual. There will be a learning curve and don't count on online documentation.

Incentivized