Skip to content
This repository has been archived by the owner on Sep 16, 2021. It is now read-only.

Use Sonata defaults in form #143

Open
wouterj opened this issue Apr 14, 2014 · 5 comments
Open

Use Sonata defaults in form #143

wouterj opened this issue Apr 14, 2014 · 5 comments

Comments

@wouterj
Copy link
Member

wouterj commented Apr 14, 2014

The form in the admin panel should not only show the values of the SeoMetadata, but also the defaults of the Sonata page service if no value was found for it in SeoMetadata

@dbu
Copy link
Member

dbu commented Apr 14, 2014

would be nice, but must be done in a way that on save, we do not duplicate the defaults into the SeoMetadata.

@ElectricMaxxx
Copy link
Member

👍 @dbu
It makes no sense to persist stuff, wich is set as default in cmf/sonata seo setting.
In general We need a clear line of handling both kinds of default values. Which are used in which situation, that's an issue i have with the current version.
But i would be a solution to just "show" the default values or show the result with the current setting - based on that clear line We need.

@ElectricMaxxx
Copy link
Member

Btw i won't see this thing as a "bug". It's a feature for the admin form extension support. :-)

@ElectricMaxxx
Copy link
Member

An other question would be: How do you want to display the existing values for all ExtraProperties. Would never be possible to show them while adding a new one. Whith sonatas "show-action" we could add a "view", means a list, of the current state after save. Maybe with a contrast between default and content's values.

@wouterj wouterj removed this from the init version 1.0 milestone Apr 16, 2014
@dbu
Copy link
Member

dbu commented May 2, 2014

maybe we should solve that by showing a hint with the base value that is going to be used if field is left empty?

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

No branches or pull requests

3 participants