Download the PHP package blast-project/utils-bundle without Composer
On this page you can find all versions of the php package blast-project/utils-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download blast-project/utils-bundle
More information about blast-project/utils-bundle
Files in blast-project/utils-bundle
Package utils-bundle
Short Description All kinds of goodies for the BlastCoreBundle
License LGPL-3.0
Homepage https://github.com/blast-project/UtilsBundle
Informations about the package utils-bundle
Blast UtilsBundle
Features
Blast Choices
Documentation to be writen
Blast Hooks
This bundle introduce a hook feature that is really basic hook management.
You can define in your views any hook you want.
Declare the hook target location in a view
A hook can be declared without using any parameters. If so, the « hook block » won't have any parameters defined in handleParameters
's method parameter (var $hookParameters
will be an empty array).
Declare your Hook class
This class will manage rendering of the hook content by setting view parameters
(act as a controller)
Note: you can get the current hook name (configured in service definition) in attribute AbstractHook::hookName
ans the configured template in AbstractHook::template
Register the hook class as service
The hook configuration are sets in the service tag :
name
: the service tag name (must beblast.hook
)hook
: the target hook where the « block » will be renderedtemplate
: the twig template of the « block »
Please don't forget the tag blast.hook
in order to register your service as a hook
Create your hook template
And voila, you should have this rendered content :
Blast Custom Filters
Enable the feature in config.yml
Optionnaly, you can define your own customFilter entity by setting it as below (don't forget to set the associated repository in order to override createNewCustomFilter
method) :
You only have to set your User class entity in application config.yml (see https://symfony.com/doc/current/doctrine/resolve_target_entity.html for more informations)
If you're using Sylius, setting the doctrine.orm resolve_target_entities
key will not work because Sylius is already using this system. You can declare your Interface / Entity replacement within SyliusResource
configuration :
Blast User Interface
In order to set User mapping with utils entity, the mapping with Interface is used.
There are 2 ways for configuring the real class that will replace the UserInterface :
Using Sylius
declare, via resources, the class that will replace the model interface
Using Syfony's Doctrine target entity resolver :
All versions of utils-bundle with dependencies
symfony/symfony Version >=3.2
sonata-project/doctrine-orm-admin-bundle Version >=3.1
blast-project/core-bundle Version self.version
stfalcon/tinymce-bundle Version >=2.1