Attempting to create a new autohandler template when one exists will reactivate deleted element templates
Reported by Matthew Rolf | August 1st, 2010 @ 06:43 PM | in 2.0.1
1) Make sure you have an autohandler template at /
2) Attempt to create a new category template at /
3) The first deactivated element template for that output channel
will be reactivated.
Instead of doing this, the system should probably just tell you one already exists.
Comments and changes to this ticket
-
theory August 1st, 2010 @ 07:59 PM
- State changed from “new” to “invalid”
Dude, this is a feature. It's true for all templates. If you don't want the existing one, delete its content and re-use it.
-
Matthew Rolf August 1st, 2010 @ 08:28 PM
I agree that it shouldn't overwrite the autohandler that is there - in doing this I had in fact forgotten that there already was one. But I don't think it should reactive a random element template that the user probably has no intention of using. What sense does that make?
-
theory August 1st, 2010 @ 11:58 PM
in cas you'd like to re-use the code that was there before. Think of it this way: You're creating exactly the same template.
-
Matthew Rolf August 2nd, 2010 @ 01:28 AM
No, you're not.
You're creating a category template.
It reactivates an element template.
So you try to create an autohandler, and it it ends up reactivating a "page" or "pull quote."
-
theory August 2nd, 2010 @ 02:30 AM
- State changed from “invalid” to “open”
- Milestone set to “2.0.1”
- Milestone order changed from “3” to “0”
Oh, that sounds like a bug.
-
phillipadsmith October 29th, 2010 @ 10:59 PM
- Assigned user changed from “Bugs (at bricolage)” to “theory”
Confirmed on current (2.1.0) 'master'. Steps to repeat from default install:
- Delete / deactivate the book_review.mc template
- Add new category template for in /
- book_review.mc will be reactivated:
Deactivated template was reactivated.
Template "/book_review.mc" saved. -
Bugs (at bricolage) January 18th, 2011 @ 12:44 AM
- State changed from “open” to “resolved”
- Milestone order changed from “9” to “0”
(from [120f26efc4a6c554667137513d24f81109ebe3da]) Don't reactivate element template when creating category template.
Done by adding
tplate_typeto the search for existing templates. Needed to
add support for that parameter toBric::Bus::Asset::Template->list().
[#195 state:resolved] https://github.com/bricoleurs/bricolage/commit/120f26efc4a6c5546671... -
Bugs (at bricolage) January 18th, 2011 @ 12:44 AM
(from [400886402fc1411bd36099e0408e1f06aa20a015]) Don't reactivate element template when creating category template.
Done by adding
tplate_typeto the search for existing templates. Needed to
add support for that parameter toBric::Bus::Asset::Template->list().
[#195 state:resolved] https://github.com/bricoleurs/bricolage/commit/400886402fc1411bd360...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
People watching this ticket
Bugs (at bricolage)
Matthew Rolf
phillipadsmith
theoryReferenced by
-
#195 Attempting to create a new autohandler template when one exists will reactivate deleted element templates
Done by adding tplate_type to the search for
existing tem...
-
#195 Attempting to create a new autohandler template when one exists will reactivate deleted element templates
Done by adding tplate_type to the search for
existing tem...