This could just be a mistake on my part. Hopefully someone could give me some hints on this. I have created my fields in my Content Profile node type. There are 4 groups of fields. Now that the fields are made (a process which took an hour or so), I am creating my "user/%user" panel page. The problem is that I don't see any of my Content Profile fields! When I go to add content to a panel, I do not see any of the fields I just created.

Am I missing a step? Do I need to group these fields into custom Views and then put the new views into my panels? Or is there a less time-consuming way of doing this?

Thanks for reading!

Comments

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented
Component: Theming » Miscellaneous
Status: Active » Postponed (maintainer needs more info)

First off, if you are creating all of your own fields instead of using the ones APK provides, make sure you even need APK. Not that it's a heavy module or anything but no sense having it enabled if you aren't even using it.

Second, make sure you have a relationship set between the user and the profile node. APK comes with that set but that's set to use the node type that APK provides. You'll need to manually add the relationship to use your node type.

Michelle

reydempto’s picture

reydempto commented
Component: Miscellaneous » Theming
Status: Postponed (maintainer needs more info) » Active

EDIT: I am attempting to use a combination of both the APK and my custom fields, so yes, APK is necessary for me :)

Excuse my ignorance, but how does one go about adding this relationship?

Oh, and thanks for the mega-speedy response! I almost got whiplash.

reydempto’s picture

reydempto commented

Oh shoot, this comment was a total accident.

reydempto’s picture

reydempto commented

Wait--you're talking about the relationship settings in the panel page's 'contexts' tab? Because if this is so, the relationship is already there..yet they don't appear in the 'add content' window in my content panel.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented
Title: Content Profile fields and APK not playing nice together » Content Profile fields not accessable
Project: Advanced Profile Kit » Content Profile
Component: Theming » Miscellaneous

I'm speedy if I happen to be at the computer... That's hit and miss. :)

Ok, trying to figure out where you're at here... It sounds like the only part of APK you're using is the included views, then? So APK isn't involved in this issue anymore... It's between Content Profile and Page Manager. When you added your relationship to your profile node type, did you delete the one that APK provided? It shouldn't interfere but you never know... Make sure it's only the one you added there and see if that helps. The fields should all show up under "node".

I don't have more ideas beyond that... If the relationship is set correctly, it should just work. At any rate, this part you're stuck on is in Content Profile, not APK, so moving the issue there.

Michelle

reydempto’s picture

reydempto commented
Component: Miscellaneous » Panels integration
Status: Active » Closed (fixed)

I fixed it! Here's my problem: The relationship is automatically added, but the 'add content' form in panels wouldn't recognise this until I did a quick edit-then-save of the options. Very strange, must have been a bug, or something I overlooked at some point.

Hey Michelle--you're awesome, which is to be expected from us Midwesterners. (Illinois originally here) Thanks a lot for your help, your hints led me right to the answer I sought.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

Weird... the automatically added relationship from APK shouldn't work at all unless you named your custom node type uprofile as well. Glad you got it working, though. :)

Michelle

mikedotexe’s picture

mikedotexe commented

Yes, it worked for me. I had go to Contexts.. Under Relationships, remove the item "Profile Node", update and save. Then Add Relationship with Profile Node selected, and it's working.

Thanks for the idea.