Exactly right, since the form would be in the plugin, you can extend
it differently for each app.
Daniel
On May 5, 12:59 pm, OnDistantShores cameron.r...@gmail.com wrote:
Oh so I'd put the whole module in the plugin then? Do I then get the
chance to then override it within each app? Because
You put all the common stuff in a plugin, that is the proper way to reuse
components across different apps.
gabriel
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the
Thanks for your response.
I have my form component in libs (this was part of the generated
code). But the actual form display logic is part of the _form.php
partial, which is in the layouts directory, which is obviously
specific to a module. How can this be shared from the libs directory?
On May
Yep, Symfony 1 :-)
On May 5, 11:27 pm, OnDistantShores cameron.r...@gmail.com wrote:
Thanks for your response.
I have my form component in libs (this was part of the generated
code). But the actual form display logic is part of the _form.php
partial, which is in the layouts directory, which
Just create a plugin (I usually call it AppSharedPlugin or so), put
a module with your template inside and enable it in whatever apps you
want to share it in.
Daniel
On May 5, 6:30 am, OnDistantShores cameron.r...@gmail.com wrote:
Yep, Symfony 1 :-)
On May 5, 11:27 pm, OnDistantShores
Oh so I'd put the whole module in the plugin then? Do I then get the
chance to then override it within each app? Because otherwise I
wouldn't be able to make one editable and one create-only...
On May 6, 4:45 am, Richtermeister nex...@gmail.com wrote:
Just create a plugin (I usually call it
