You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a few extensions in Radiant that add custom fields to the Snippets Edit Form (and also to the Snippets index). After the upgrade to Radiant 1.1.1 and beginning to use the new Snippets extension, added fields and labels appear multiple times. This isn't a problem for fields we add to Layouts (or other core Radiant admin pages), just Snippets.
An example of how we're adding them, in the *_extension.rb config file:
admin.snippet.edit.add :form, "mobile_content", :after => "edit_content"
The text was updated successfully, but these errors were encountered:
Update to this ticket: The behavior is actually that the first time you load a Snippet page of any kind, everything renders once. Every time you load a new page, or reload a current page, any added fields render an extra time. So, if you reload a page 10 times, you end up with every custom field being rendered 10 times.
One more update: The problem seems to be that every time a page is loaded, the extension initializer re-adds the field to the snippets model. This isn't happening with any core radiant features, only with extensions.
I've come up with a fix to stop it from happening in my extensions, but I think there might be something up with how this is being handled as an extension than when snippets was part of Radiant core.
We have a few extensions in Radiant that add custom fields to the Snippets Edit Form (and also to the Snippets index). After the upgrade to Radiant 1.1.1 and beginning to use the new Snippets extension, added fields and labels appear multiple times. This isn't a problem for fields we add to Layouts (or other core Radiant admin pages), just Snippets.
An example of how we're adding them, in the *_extension.rb config file:
admin.snippet.edit.add :form, "mobile_content", :after => "edit_content"
The text was updated successfully, but these errors were encountered: