Closed (fixed)
Project:
One page profile
Version:
6.x-1.4
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
29 Jun 2009 at 21:35 UTC
Updated:
11 Oct 2009 at 09:00 UTC
This module works fine with just Profile module enabled. However, in scenarios where the Profile and Content Profile Module are enabled.
The problem is as follows:
All the fields defined/created using the Profile module are ok and displayed on a single page as one would expect.
All the fields defined/created using the Content Profile module disappear without a trace.
Is there any workaround or patch to resolve this issue.
P.S Thanks for the module.
Comments
Comment #1
johnhanley commentedIt would help to know how you have Content Profile configured (with or w/o tabs, etc.)
That said, I would recommend choosing one or the other and not try to use both together.
Comment #2
aidanlis commentedThis is something that the author of the Content profile module will have to discuss with me. I don't have any idea for rectifying it currently.
Comment #3
iaminawe commentedIt is common use to use Content Profile for CCK fields and core profile for fields on the registration form. You get the benefits of asking for few details upfront and then using the CP included rule sto automatically redirect a user to their content profile to create which has more fields.
This module seems great but it just removes all other contrib module sub tabs from the users profile which is not really an acceptable workaround to this solution.
Any way to get this working without removing all other sub tabs?
Thanks
Comment #4
kenorb commentedCreated related issue: #577036: Working with onepageprofile module
Comment #5
aidanlis commentedOkay - I've patched this module to not unset tabs that we haven't incorporated into the single edit page.