Hey Felds, In the past I have dealt with this by just putting a "SettingsForm" into the admin area (styling it to look the same as an admin module), and writing the settings to a yml file. During runtime I then load the file and merge it with the settings in sfConfig. This way I can allow admins to override specific app_ or sf_ settings throughout the app. Since the logic which fields you want to expose, and how you want to validate them is completely contained inside the form class, it's really quite easy to manage for me.
That help? Daniel On Feb 14, 5:20 am, Felds Liscia <luizlis...@gmail.com> wrote: > This is more of a conceptual question. > > Sometimes I have to make some configs available to my clients but > those configs don't fit in a CRUD pattern, like tuning promos on/off, > setting metas, titles, and those things. > > In your opinion, what is the best way to build this kind of > preferences panel using the admin generator? > > I often strip down the module actions to execute only the Edit and > Update actions, but the routing becomes a mess and I'm not sure if > this kind of things should go on a DB table with a single row. > It's far from perfect. > > Thank you in advance. ;-) > > @felds -- 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 Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
