Thanks for the module! Alas, this module does not work with the module profile_privacy turned on. Would be great if it could be used in conjunction with profile_privacy.

Comments

sethcohn’s picture

subscribe

aidanlis’s picture

Both modules override the user/edit page, thus I don't think it's possible to integrate these two modules.

sethcohn’s picture

Might be doing something along these lines, so I'll follow up if I find an answer....

aidanlis’s picture

Status: Active » Postponed (maintainer needs more info)
diego_carrera’s picture

Just found this

http://drupal.org/node/597546

Solves the issue, it is a modified profile privacy module.

aidanlis’s picture

Status: Postponed (maintainer needs more info) » Fixed

Awesome, thanks for posting that link, and thanks to @RTaylor for providing the fix.

sethcohn’s picture

StatusFileSize
new963 bytes

Yes, Ray and Chris both rock, two great Drupal developers I'm very proud to work with...

If someone wants to just make the stock modules (Profile Privacy and One Page Profile) with as little other change as possible, the actual patch needed is pretty small. Attached.

aidanlis’s picture

Status: Fixed » Closed (fixed)
Carsten Müller’s picture

Project: One page profile » Profile Privacy
Version: 6.x-1.4 » 6.x-1.2
Component: Miscellaneous » Code

For everybody who does not know haw to apply a patch. You can downdload the patched module at http://drupal.cocomore.com/de/project/profile_privacy

quicksketch’s picture

Status: Closed (fixed) » Needs review

It doesn't look like this was ever committed to the project. Seems like something worthwhile that should be added directly rather than having users apply patches.

sethcohn’s picture

+1, though I no longer have a need for it... but someone out there might...

Fresh eyeballs welcome, it's a really simple patch.

mbricola’s picture

Hi I have tried to use this version http://ftp.drupal.org/files/projects/profile_privacy-6.x-1.2.tar.gz, then the cocomore one http://drupal.cocomore.com/de/project/profile_privacy and also is not working on my drupal 6.19 installation. I have checked the Issues queue but I cannot really find a similar problem to mine. I can see the check boxes in the pages, as well once enabled I can see them in the user profile, but then they seem to no have any effect, since i can still see as normal member, (even as visitor accessing a listing page) those field which should have been set private from the user.

Any help will be more than welcome!

Thanks for the GREAT job,
Maurizio

bryancasler’s picture

subscribe

seaneffel’s picture

Title: Profile Privacy » Conflict between Profile Privacy and One Page Profile modules
Category: feature » support
Status: Needs review » Reviewed & tested by the community

I've confirmed that the patch in #7 makes it possible to use both Profile Policy and One Page Profile modules together in Drupal 6.20. I can edit a profile page displaying all editable field categories as well as checkboxes to set profile fields as public. Good work on that little fix.

I believe this patch should be committed rather than let inexperienced Drupal users toil with patching it on their own.

Now, if only Profile Privacy settings were respected by Views... http://drupal.org/node/311301

cor3huis’s picture

Category: support » bug
Priority: Minor » Major

Bumped, since there is a simple patch, it ould be so great if maintainer could apply it to the 6.x Git or version of liking.

IMHO it would be good to also have a DEV release for the module 6.x at the current state with as much patches applied as possible, after all that is what a dev is for.

cor3huis’s picture

Status: Reviewed & tested by the community » Patch (to be ported)
StatusFileSize
new1.04 KB

Patch incuded against D6.x v1.2

cpliakas’s picture

Version: 6.x-1.2 » 6.x-2.x-dev
Status: Patch (to be ported) » Reviewed & tested by the community

Marking patch at #16 as RTBC, bumping to the 6.x-2.x branch.

cpliakas’s picture

Status: Reviewed & tested by the community » Fixed

Resolved in the 6.x-2.x branch. This was rolled up into the original commit at f400499.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.