The change in profile , for example, user picture, etc. is seen only in case of admin.
Other users profile is as it is.
I have enabled access own profile.

CommentFileSizeAuthor
#7 test.png105.93 KBnikkubhai

Comments

lelizondo’s picture

I'm not sure what you mean, do you mean all profiles look the same old-way for all users except for admins?

nikkubhai’s picture

Yes.all profiles look the same old-way for all users except for admins

lelizondo’s picture

Are you using other modules that could be hacking the Profile page?

lelizondo’s picture

I'm testing this in a fresh new site and I don't have the behavior you're experiencing.

nikkubhai’s picture

Let me tell you the changes clearly.

Profile and Settings page are two different pages for both admins and authenticated users and are as designed.

But,
In case of admins, user picture is removed . But, in case of auth, user picture is still present under profile tab.

The about me block works only for admin.

lelizondo’s picture

Well, the Settings depends on multiple permissions so that's kind of hard to test, you'll have to check up your permissions.

The profiles depend on one permission. What method are you using to theme your profiles, are you using blocks? are you using context module? maybe custom theming?

Also, it would be easier if you could post some screenshots.

nikkubhai’s picture

StatusFileSize
new105.93 KB

I have attached the pic of a user. See the fact that his picture is still under the profile tab.

lelizondo’s picture

That's weird, this commit should had fixed the picture in the profile http://drupalcode.org/project/pux.git/blobdiff/fd3bc0093655224407b8aec2c...

I see that the Profile is enabled (because the "View" tab is replaced by "Profile") but, could it be possible that you changed your configuration in "admin/config/people/accounts/display"? If you change your configuration after you install this module, you can still active some parts of the old profiles.

Also, there are some modules that you have installed that includes permissions / settings / etc. so the possible combinations for why the profiles are looking different for users and admins are way too many. We'll have to narrow them down to the minimum.

nikkubhai’s picture

The only thing I am concerned is about the picture under profile tab.
Rest can be changed by manage display in people/accounts. But, I don't see any way of hiding that picture.

I dont think its because of other modules, because picture is removed in admin and module works fine in case of admin

lelizondo’s picture

The only way to see what's going on is for you to install the devel module, look at the function pux_profile_page_alter() and add this line dsm($page);

Then please post everything that has something to do with user_picture

nikkubhai’s picture

Now, I get the problem. Most probably it has to deal with access own profile.
Admin sees his and other users profile just the way it is supposed to be.
But, a user doesn't see his or others profile correctly;look at the screenshot in above comments.

lelizondo’s picture

I have two questions:

1. What are the differences between what a normal user sees when he/she visits his/her own profile with what an admin sees?
2. Could that differences, if they exist, could be caused by other modules, whether they are permissions or configuration?

nikkubhai’s picture

1. I difference is of the picture as I mentioned earlier.
The other difference is that the "about user" block works only for admin not for others.

2. I am not sure about how other modules may affect it. I have OG, views, private msg, user relationships and several other modules installed.

I have one more question. I don't have context installed. In documentation you have written that we should use context. But, why and how is not mentioned. What's the purpose of using context? And is this problem because of not using it?

lelizondo’s picture

The Context module is great, if you haven't you should start using it, it has better performance over the "traditional block system", it is also so cool because you can apply reactions for conditions, let me give you an example.

You could set a condition to a path 'user', and apply a reaction, as a reaction you could have a menu link selected as active, you could show blocks in any region, you could change your theme, you could even change the layout, that's why is so powerful, because you could have multiple reactions depending on a path or other conditions, something that is really hard to do with the traditional block system, probably you'll have to do it with php. They also are exportable through features which make them even greater.

I'll give it a test to the about user block, but as far as the picture, you have to do 3 things:

1. Check if both users you're testing does have a picture.
2. Try to detect if no other modules are creating this problem (I had set a site from scratch and I don't have this problem)
3. Do what I suggested in #10

nikkubhai’s picture

I understood the reason.After installing the module on production site, I can't change or edit profiles. I am getting this error : Fatal error: Call to undefined function user_profile_form_submit() in public_html/includes/form.inc on line 1390 .

But, on dev site with same modules installed, everything is working fine. I really dont know what to do now :(

lelizondo’s picture

That's weird, because that function is in user.pages.inc and is used when you submit a form in the user settings. Did you clear the cache?

nikkubhai’s picture

Yeah. I cleared cache many times. After enabling these module on my production site, I was unable to change anything in profile fields because when I submitted the form I got that error.And there is no prob on production site after disabling pux.
The weird thing is:
There is no prob on dev site when pux is enabled with same modules as production sites.

lelizondo’s picture

Well, I don't know what could be causing it. Run update.php just to see what happens.

nikkubhai’s picture

I already did that too. Ran update.php :(

lelizondo’s picture

Status: Active » Closed (cannot reproduce)