I've been trying to use the realname module with advanced profile kit. It works, but it also changes the url path to use the realname. It's not going to be very good if users profile page URL's change any time they change their real name display. Is their a way to prevent this? maybe something in the bypass form settings? It seems fixed in the current realname dev version - but the username appearing on the APK profile is not substituted with the realname.

Thanks for any info.

Comments

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Status: Active » Postponed

I never heard of APK before. It says you have to be able to work with Panels. I don't have Panels, nor the time to install and learn it. Since I don't, I really am confused by "changes the url path" statement.

plan9’s picture

plan9 commented
Status: Postponed » Closed (fixed)

Thanks for getting back to me on this. I've discovered that the problem was in fact being caused by the Gallery module 'Full Name' settings and not Advanced profile kit. I've disabled full name support in the gallery module and now realname and APK work fine together.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

Great, thanks for updating the issue. You might want to open an issue against Gallery to use theme('username',...).

plan9’s picture

plan9 commented
Status: Closed (fixed) » Active

Looks like I spoke to soon. The behaviour is back - I enabled caching at some point and this confused the issue. Basically when the realname first and last name fields are updated a new usernode is created...(!)

Because I use the usernode entries in many of my views listings this also means I get duplicate entries for users each time they change their realname settings.

I'm using First / Last name fields in the profile 'Display Information' settings which also show up in APK. I've tried renaming the machine name of the fields in case of collisions but it made no difference. When I uncheck the 'Override username theme' option in realname module it fixes the issue - I keep realnames in nodes but I lose the realname subsitution on the advanced profile page.

The easiest fix would be to keep 'Override username theme' unchecked and modify the APK theme / css somehow? But what to add / remove?

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

Panels may be the problem. I've had other problems with that in another module; it seems that Panels wants to change things.

plan9’s picture

plan9 commented
Status: Active » Closed (fixed)

OK - I've finally pinned down what is happening here. I had CCK field permissions enabled on certain APK fields which was causing APK to generate a new usernode. This obviously has nothing to do with realname module.

I also had Pathauto aliasing set on changes to: delete old alias and create a new one. This is where the realname value was being used to name the new advanced profile URL path alias. I set pathauto to: on changes do nothing and now this is fixed.

Finally - even with gallery 'full name support' disabled realname still changes gallery user name to the realname value when a user sync is performed. So, certainly there appears to be a problem between gallery and realname modules.
And to confirm (and close this thread) advanced profile kit is compatible with realname module.

rem_rks’s picture

rem_rks commented

What exactly did you do to make it work?
I'm trying to figure out the same thing, but I seem to not be having the same luck as you.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Status: Closed (fixed) » Fixed

Let's leave this as "fixed" so it continues to show up for 2 weeks. Thanks very much for figuring out what the problem was.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Status: Fixed » Closed (fixed)

Cleaning up the issue queue.

michelle’s picture

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

Just stumbled across this... No need to reopen it but wanted to point out in case anyone else runs into this that "which was causing APK to generate a new usernode" is not actually possible. APK doesn't have anything to do with making usernodes. That would be the usernode module.

Michelle

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

Nor does Realname. Thanks, Michelle.

plan9’s picture

plan9 commented

I've finally tracked this duplicate account creation down to a demonstrable incompatibility between realname and gallery module. I suspected this was the case before but having gallery, realname and APK all on the same site makes things tricky to debug. In the end I did it by examining the gallery2 user field using phpMyAdmin and witnessed the creation of the duplicate accounts. Typically a username would appear like 'jsmith' then a minute later a new user called 'John Smith' would appear - while in Drupal there appears only one user - username jsmith, real name John Smith.

At some point in the proceedings I had to perform a manual sync with gallery - and the the duplicate g2 accounts created even more duplicate Drupal accounts!!!! Hence the aforementioned usernode mystery. I disabled realname and the behaviour stopped. I've now got the latest 5.x dev version of realname which does not conflict with gallery - but it also doesn't show realnames in menus or profile pages. In my reckless enthusiasm for maximum functionality I've messed up my live gallery database with all of this and I'm spending tonight reverting to a backup which means I've lost 2 weeks worth of uploaded images, but I'm just relieved that I've finally found out what was causing this. I'm still a big fan of realname though and gallery module and hope there will be a new compatible 5.x dev release soon.

sh264’s picture

sh264 commented

I'm running drupal 6.13, so not sure this is something for this (or any) issue queue, but I do have a compatibility problem with RealName 6.x-1.2 and Advanced Profile Kit 6.x-1.0-beta1. Someone else may find the same problem and this thread so I thought best to at least mention it.
Basically, having RealName on disables the 'user_view' needed for the APK user profile display and the 'user_view' cannot be re-enabled.
In the admin/build/pages, Error reads: "Page manager module is unable to enable user/%user because some other module already has overridden with realname_user_view."
Turning off RealName allows 'user_view' (and thus my APK profile) to be enabled.
I have the 'Display Name' in my user profiles, so now I'm looking for a way to utilize that without needing RealName. :(
This might be one for APK? but maybe its just me and not a real issue.

ianchan’s picture

ianchan commented
Status: Closed (fixed) » Active

I'm running into the same problem as in #13.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented
Status: Active » Closed (fixed)

The issue in #13 is totally off topic. It is a duplicate of #443880: REALNAME module stops panel override from working

Michelle

merakli’s picture

merakli commented

Following APK documentation, my admin/build/pages is NOT showing pages at all, instead I see 

Site building

Blocks

Contact form

Flags

ImageCache

Menus

Mini panels
....

etc. But no pages, thus no user_view.

I don't see any error messages either. I disabled RealName but the page didn't change.

michelle’s picture

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

@merakli: You need to enable Page Manager in CTools. Please file issues in the appropriate places. I deleted your comment on the handbook page and this doesn't belong in the RealName queue, either.

Michelle

merakli’s picture

merakli commented
Version: 5.x-1.1 » 6.x-1.2

Enabling Page Tools solved my issue. Thanks so much!