Why add another field for a headline to a custom content element when there's already the default one? Moar fields you say? Nah. Read on.
As mentioned in the previous post the standard menu viewhelper is a Fluid equivalent to the HMENU object in TypoScript. All other menu objects you know from TS are implemented as well with
<v:page.menu.browse /> and
<v:page.menu.directory />. Again, here are some examples.
vhs comes with a range of viewhelpers to render all kinds of menus. To demonstrate its ease of use and flexibility I compiled some examples.
I guess I'm not the only one that came across the annoying
Read PDF/AI...There was no result from the ImageMagick operation message in TYPO3's install tool when performing the image processing tests.
After upgrading an application to Symfony 2.3.x I stumbled across this exception just the other day.
The documentation explains in detail why this can be the case and how to solve the issue.
However, it didn't work for me although ICU 4.8.1 is installed on our server which
phpinfo() clearly stated but
php -i | grep ICU did not.
And this was a hint to the solution: CLI and Apache use different php.ini files thus I had to provide the correct ini when invoking composer:
php -c /path/to/php.ini composer.phar install.
Woot! Look what I just found in my inbox:
SensioLabs is glad to inform you that you've been retroactively graduated the SensioLabs Symfony2 Certified Advanced Developer after you took the Symfony Certification exam between 2012 and 2013.
That makes me one happy guy!