<div dir="ltr">then , there is no solution in 5.x for that content type problem !!<br><br><div class="gmail_quote">On Wed, Jul 30, 2008 at 7:54 PM, Marc Poris <span dir="ltr"><<a href="mailto:marc@funnymonkey.com">marc@funnymonkey.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">In 6.3 there's already an excellent warning in the confirmation<br>
message. Try it out slowly.<br>
<font color="#888888"><br>
Marc<br>
</font><div><div></div><div class="Wj3C7c"><br>
<br>
Earnie Boyd wrote:<br>
> Quoting Bill Fitzgerald <<a href="mailto:bill@funnymonkey.com">bill@funnymonkey.com</a>>:<br>
><br>
><br>
>> My .02 --<br>
>><br>
>> I don't really see this as a bug, but as a feature that protects a site<br>
>> from mass content deletion if a node type is inadvertently deleted.<br>
>><br>
>><br>
><br>
> It is a bug that you don't get the warning you mention below.<br>
><br>
><br>
>> One possible fix, which would be more of a feature: if there are nodes<br>
>> of any content type, flash a warning onscreen if a user is attempting to<br>
>> delete the node type.<br>
>><br>
>><br>
><br>
> Yes, and if it doesn't stop the user from deleting the content type<br>
> with content assigned without deleting the content then it is a design<br>
> flaw, IMNSHO. The lack of foreign key relationships is the reason that<br>
> this design can flourish.<br>
><br>
><br>
>> Generally, though, the ability to delete node types should only be given<br>
>> to highly trusted -- and highly competent -- users.<br>
>><br>
>><br>
><br>
> I agree but that doesn't negate the flawed design feature.<br>
><br>
><br>
>> Cheers,<br>
>><br>
>> Bill<br>
>><br>
>> bharani kumar wrote:<br>
>><br>
>>> Hi<br>
>>><br>
>>><br>
>>> The steps to generate the bug are:<br>
>>><br>
>>> 1. Create a Content type (eg: Content type 1)<br>
>>><br>
>>> 2. Create a content(eg: content-1) of the same content type (Content type<br>
>>> 1).<br>
>>> 3. Delete the Content type (i.e., Content type 1).<br>
>>> 4. Try to edit the content (content-1).<br>
>>><br>
>>> The browser will show warning,<br>
>>> and you wont be able to edit the<br>
>>> contents.<br>
>>><br>
>>> 5. Now create a content-type with the same name, which you have deleted<br>
>>> (i.e., Content type 1), and you will be able to edit or delete your content<br>
>>> (i.e., content-1).<br>
>>><br>
>>><br>
>>> ???Any solution<br>
>>><br>
>>><br>
><br>
> Create a module to hook_form_alter and add a #validate function that<br>
> will be called and add form_error() message if the content type has<br>
> content.<br>
><br>
> Earnie -- <a href="http://for-my-kids.com/" target="_blank">http://for-my-kids.com/</a><br>
> -- <a href="http://give-me-an-offer.com/" target="_blank">http://give-me-an-offer.com/</a><br>
><br>
><br>
<br>
<br>
--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
</div></div></blockquote></div><br></div>