conversionfoundry / breeze

A Ruby on Rails CMS for brochure-style websites.
Other
3 stars 2 forks source link

Custom types cannot be deleted and recreated - name collision #27

Closed ShaneNZ closed 11 years ago

ShaneNZ commented 11 years ago

Observed on Leftclick site (Breeze version?)

Steps:

  1. Create a custom type called "foo", create a couple of fields within it, save it.
  2. Delete "foo".
  3. Create a new CT called "foo", with different fields in it.
    • Breeze uses the old instance of the CT with the partial and on the front end

NB: reloading the page on the front end updated the fields presented in the content editor, but the partial still expected/required the old fields.

sam-law commented 11 years ago

Once a partial is created, if you modify it, all versions of that partial across the site need to be deleted/re-added.

ShaneNZ commented 11 years ago

When you're talking about "modifying", do you mean partial or custom type?

_Shane Goodwin | User Experience Designer | _LeftClick 31 Elizabeth Street, Christchurch, New Zealand Tel: +64 3 379 8984* |* Web: www.leftclick.com

On 1 November 2012 13:14, Sam Law notifications@github.com wrote:

Once a partial is created, if you modify it, all versions of that partial across the site need to be deleted/re-added.

— Reply to this email directly or view it on GitHubhttps://github.com/leftclick/breeze/issues/27#issuecomment-9967059.

isaacfreeman commented 11 years ago

This is working as intended. Changing a custom type doesn't modify the corresponding partial (if any) because the partial may be highly customised by the designer.

Following Alban's work on custom types, we now have better error messages when a partial doesn't work.