Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I've had a stab at using this module but although it's impressive, I think it's overkill for what I need. So I'd like to remove it, but:
- there's no obvious way to remove the backreference field in Manage Fields
- if I disable the module without removing the backreference field, I get lots of error messages
Any suggestions please?
Comments
Comment #1
markus_petrux CreditAttribution: markus_petrux commentedOops! It seems I forgot to deal with this. I'm very sorry.
One way to resolve this issue is going to the "Back references" tab of the content types and remove the fields from there.
I'll work on a patch as soon as possible.
Comment #2
markus_petrux CreditAttribution: markus_petrux commentedBetter title.
Comment #3
markus_petrux CreditAttribution: markus_petrux commentedOk, patch committed to CVS.
http://drupal.org/cvs?commit=266014
Comment #4
adam_b CreditAttribution: adam_b commentedThanks for this - it seems to have done the trick.
However, it appears to work differently from the CCK norm, which requires you to remove the relevant fields before uninstalling the relevant module, in order to avoid it complaining bitterly about widgets evermore afterwards when you go to the Manage Fields page.
Personally I think this makes more sense - you uninstall and that's it - but it might be a good idea to give details in the documentation.
Comment #5
markus_petrux CreditAttribution: markus_petrux commentedRe: "it might be a good idea to give details in the documentation"
I'm not sure about this. Note that the fields are created automatically. And the "Back references fields" feature is here just to bring you the power of the "Manage fields" screen and other CCK related features related to fields (Display fields options, planels integration, etc.), but still, there's no real data behind these back reference fields, and it is just as easy to re-create them if the module is re-installed after it has been completely uninstalled.
We create these fields automatically, hence we should remove them automatically too, but only if/when the module is uninstalled. Note that the fields are disabled when the module is disabled, and you'll get them there as-is if you re-enable the module. So there's no harm in this approach, I think.
I would be fine to add a notice somewhere, but I'm not really sure where.