Closed (outdated)
Project:
Ubercart / Salesforce Integration
Version:
6.x-1.0-alpha3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 May 2011 at 23:12 UTC
Updated:
7 Mar 2016 at 12:24 UTC
Jump to comment: Most recent
Comments
Comment #1
EvanDonovan commentedI believe that the content type is created using a Features-like system, which may be why, since it is defined in code. I'll have to look into this, but I'm tremendously busy with client work this month.
Comment #2
EvanDonovan commentedI am probably going to simply remove this content type in the next release - see #993776: Refactor the OpportunityContactRole integration into a separate module, and make it not based on nodes.
Comment #3
drupalsteve commentedThanks; I'll check back on this issue over the next few weeks. I just want to remove the content type so it doesn't clutter up the interface and confuse backend users.
Comment #4
EvanDonovan commentedTo update on the progress of #993776: Refactor the OpportunityContactRole integration into a separate module, and make it not based on nodes - I am about halfway to removing the content type. This next alpha will still have it, but the next one after that should not.
Comment #5
EvanDonovan commentedAs for disabling the module, you should also remove the code from your system. That should solve the issue described in your OP, in which case I will mark this as "fixed". Can you let me know if that works?
Comment #6
EvanDonovan commentedI just removed this content type from the dev release. I don't know why this happens though - have my instructions solved this?
Comment #7
drupalsteve commentedSorry for the slow response. To clarify - by "remove the code from your system", do you mean I should go into the mySQL table and remove some information? If so, could you provide some guidance as to what exactly I should do?
I already disabled and uninstalled the module, then deleted the code from my sites/all/modules folder.
Thanks.
Comment #8
EvanDonovan commentedI actually have encountered this issue with other modules that provide content types that I later disabled. I think it is possibly something with Drupal core itself.
Comment #9
kenorb commentedClosed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.