It isn't fixed. The dev team feel that 'no one is yelling about it so it can't be an issue to worry about'.

I'm still using the hack I described in the defect report.

Do you stil have any old backups of the pre-upgrade db? Would you share them? I know I have to face down this issue sometime becuase my DB is broken. Sadly I did not discover it until all the older backups had gone.

---

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk

Hi Richard

I'm still busy trying to clean up my db so that i can send it to you, i've also tried what you've just suggested and it take me to the right page which is my profile page.

 

I have this issue as well with one portal that I upgraded from 4.9.5 to 6.2.1 (I used the recommended upgrade path, and most of the things work fine).

In my case I realized the following: Under "Assigned Premium Modules" both of the boxes "UnAssigned" and "Assigned" were empty. The workaround was to assign the module definition to the portal in the "PortalModuleDefinitions" table - after clearing the cache, the module was (is) available.

I reported this in this thread, but still was too lazy to report it in Gemini.

I hope this helps...

Best wishes
Michael

---