Symfony's Third Generated PHP File

This is a correction to a previous post where I asserted the Symfony framework (which OroCRM is built in), has two generated PHP files to contend with. There are actually (at least) three. In addition to the app container file and the bootstrap cache file, there's also an application class…

OroCRM Virtual Machine

The OroCRM has has released a virtual machine containing the latest source as a virtual machine. This is welcome news for developers who hate setting things up themselves, and also welcome news for developers looking for a reference implementation.…

Twig Templates, Initial Cache Hit

OroCRM uses Symfony's delegate template engine, which means developers are free to use any template service added to the Symfony configuration. This usually means twig. I'm tracing the execution of a full twig render, and I'm starting to see why twig's initial cache hit is so performance heavy. Here's one…

Symfony, OroCRM, and Views

The concept of a "view" is a little tricky in Symfony, which makes it a little tricky in OroCRM/OroBAP. As of Symfony 2.4 (the latest version) and 2.3 (the latest version used with OroCRM), there are two primary ways for a controller action method to hand off…

Symfony's Two Generated PHP Files

Update: The information in the post below is correct, except for the part where it talks about Symfony have two generated PHP files. It actually has three. More as a reminder to myself than anything else, it's important to remember a Symfony application has two generated PHP files. The first…

Symfony Aliases and the Event Dispatcher

In what I hope is the last word on the previously discussed event_dispatcher service, I downloaded the latest version of Symfony (2.4.1, the OroCRM Beta 6 uses Symfony 2.3.6), and discovered a change in the generated dev container file. Specifically, #File: app/cache/dev/appDevDebugProjectContainer.…