Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Template improvements #299

Open
plozmun opened this issue Sep 1, 2021 · 1 comment
Open

Template improvements #299

plozmun opened this issue Sep 1, 2021 · 1 comment

Comments

@plozmun
Copy link
Contributor

plozmun commented Sep 1, 2021

Q A
Bug? no
New Feature? Yes
Bundle Version -
Sulu Version 3.0?
Browser Version All

Actual Behavior

Currently the templates of both the fields and the general form are defined by default and are not overwritable. It's possible to override some services but it would be nice to make it simple.

Expected Behavior

Some suggestions to improve the bundle:

  • Allow to override main template to remove or add some custom fields ( remove email section or add new section to integrate with CRM`s or similar )
  • Templates: It would be nice to create templates for forms. Example: Two columns forms , step forms, etc..
@alexander-schranz
Copy link
Member

Thanks for creating this issue.

Allow to override main template to remove or add some custom fields ( remove email section or add new section to integrate with CRM`s or similar )

This is something I already have in mind that Email part should be optional. Also the email configuration should not be in the same tab as the form configuration. For this already #32 was created.

Templates: It would be nice to create templates for forms. Example: Two columns forms , step forms, etc..

I'm not sure if I want to implement this things. If a Form is shown as step by step form or as grid form depends on the design or theme. In sulu we always try to separate the content from its presentation. I'm not sure yet if we would add something like that, as a Theme A could show the form as step by step form and Theme B as normal column form. So the implemented theme itself would and should have the control how the form is shown and the form bundle itself should not care about it. Still it should be able that the form entity is extendable with custom fields by overwrite the form_details.xml with new fields and by decorating the FormManager service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants