I have tried this question, days ago, in the g.d.o. with no help.

I don't know if this is a bug or not. But, I think that this might have caused the problem:

In a marathon of updates (D6.16-->D6.17 and about 20 contrib mods, which a well-intentioned client planned to do (first timer) herself), including update nag for Content Profile, I inadvertently "updated" Content Profile from 6.x-1.0-beta4 to 6.x.-1.10. Ack! As a result, I have broken links for user/register, user/user/create, and no surprise user profile.

On testing site, I tried uninstalling (yes, through modules page) 6.x.-1.0; deleting the module folder; then re-installing 6.x.-1.0. Also tried reinstalling 6.x-1.0-beta4. Still have the broken links issue. I thought that the uninstall cleaned house.

How can I resolve without jeopardizing any of the existing profile data (which should be safe since it is a node.)

What tables in the database are affected by the module? I see no table for content profile and only 1 reference to it in System table.

Thank you.

Comments

greta_drupal’s picture

greta_drupal commented

I just tried again to uninstall (through Drupal) the beta module. Deleted the module folder, and deleted all references to Content Profile in the System table. Ran update.php. I then reinstalled and enabled 6.x.-1.0; ran update.php.

It seems that this module is in conflict with some other module. However, I merely updated existing modules with which it played nicely for a long time. I did not add any new modules. Any known conflicts with this version? The problem definitely is with/affecting Content Profile, as when I disable the module, the problem is resolved.

This is a member organization site, with member directory a key feature -- it relies heavily on Content Profile module.

greta_drupal’s picture

greta_drupal commented
Priority: Normal » Critical

Really? No reply still?

greta_drupal’s picture

greta_drupal commented

Issue unresolved. If module developer or maintainer has no intention of addressing my issues post, please be honest and just so state you are refusing support.

My only option is to ditch Content Profile and employ a very costly workaround. Is that really necessary?

(Frankly, I don't think that I installed the wrong update. I think that it is a bug in Content Profile. I've asked a simple question: where all are the references to the module in database so that I can try to eliminate them and reinstall without the same problem.)

greta_drupal’s picture

greta_drupal commented

Turns out that I had not improperly rolled back the module. The Date and/or Calendar modules latest update was in conflict with Content Profile latest update.

Ref: http://drupal.org/node/905868
Ref: http://drupal.org/node/905866