Book Image

Modernizing Enterprise CMS Using Pimcore

By : Daniele Fontani, Marco Guiducci, Francesco Minà
Book Image

Modernizing Enterprise CMS Using Pimcore

By: Daniele Fontani, Marco Guiducci, Francesco Minà

Overview of this book

Used by over eighty thousand companies worldwide, Pimcore is the leading open source enterprise-level content management system (CMS) solution. It is an impressive alternative to conventional CMSes and is ideal for creating e-commerce and complex enterprise websites. This book helps developers working with standard CMSes such as WordPress and Drupal to use their knowledge of CMSes to learn Pimcore CMS in a practical way. You'll start by learning what Pimcore is and explore its various services such as PIM, MDM, and DAM. The book then shows you various techniques for developing custom websites in Pimcore based on the scale of your organization. You'll learn how to use Pimcore to improve the digital transformation of a company by implementing enterprise Pimcore features. As you advance, you'll discover Pimcore's capabilities and features that make it a faster and more secure alternative to traditional CMSes. As well as demonstrating practical use cases, Modernizing Enterprise CMS Using Pimcore can help you understand the benefits of using Pimcore as a CMS solution, sharing best practices and proven techniques for designing professional Pimcore sites. By the end of this book, you'll be a trained Pimcore developer, able to create complex websites, and be well-versed in Pimcore's enterprise features such as MDM, PIM, and DAM.
Table of Contents (16 chapters)

Editing the Controller for our blog

Everything about the controller has been explained in the previous chapter, Chapter 8, Creating Custom CMS Pages, and therefore in this chapter, we limit the scope to just see which changes we need to make for the blog to work properly.

What we are interested in doing now is to create actions that correspond to the rules we have just finished configuring in the previous section. In fact, if we look at the configuration, we can see that the Controller field contains the name of the bundle (BlogBundle), followed by the Controller keyword, followed by the name of the controller (BlogController). The last part is the name of the action (articleAction) to be called when the browser URL matches the routing rule.

To clarify these ideas, imagine we write this URL in our browser: https://myblog.com/blog/article/my-first-article. We uniquely identify a blog_article_by_slug rule. This rule, written in the configuration, indicates that the articleAction...