Great, great work, Michelle... I keep repeating myself!
I hit a glitch - and I think it's pretty important - perhaps I'm doing something wrong. See post here - in short, it doesn't look like APK is respecting CCK Field Privacy fieldset visibility settings. It struck me only after posting this that if CCKFP is, indeed, properly changing db values, then there's not much more one could expect it to do.
I'm aware there's an inherent conflict with CCKFP's current inability to "dig down" into fieldsets and APK's default panel fieldset display (ultra-cool.) Or is this a "Panels" issue? With the complex interaction of four different projects including Content Profile (five, if you count Author Pane separately), I understand how this could be a real poser.
In any event, privacy is a critical issue and CCKFP certainly seems like the best - and possibly only - option. Any ideas here?
Thanks, as always, for taking the time and for all the work you do... rock on!
| Comment | File | Size | Author |
|---|---|---|---|
| #18 | content_panels-361473-18.patch | 1.07 KB | markus_petrux |
| #17 | content_panels-361473-17.patch | 1.08 KB | markus_petrux |
Comments
Comment #1
bcobin commentedOops! I referenced the wrong post. The correct post is here.
Comment #2
michelleI'd say it's either a panels or cck issue. APK is just a set of panels bits and views and so APK itself wouldn't be causing this. I'll leave this here for the moment because I don't know which is causing the problem. If it's CCK, then it's something I need to look into, anyway, as I maintain the CCK/Panels fieldgroup integration.
Michelle
Comment #3
bcobin commentedThanks, Michelle - much appreciated. (Is there anything you don't do?)
;-)
Comment #4
michelleLOL! Oh, yeah, there's plenty I don't do. I'm pretty narrowly focused on the social networking sites. I hear rumors that people use Drupal for other kinds of sites... ;)
Michelle
Comment #5
bcobin commentedNot true! Don't believe a word of it - it's SocNet or nothing!
(One could make a case that with all the activity over here, Drupal is just an excuse for all the propeller-heads to hang out on the site.)
Wondering if you've had any progress on the Privacy issue - I've discovered the solution for an unrelated Panels issue in the meantime (which I've posted elsewhere) where Image Attach needs to be disabled on Panel pages to add custom content... just in case you run into it.
Hope your projects are progressing well - I'll be checking in. The Privacy issue is pretty much a show-stopper at this point.
Thanks, as always!
Comment #6
michelleNo progress yet. The paid for project that was funding APK blew up (not because of APK) which means APK is back firmly in the working for free camp. I'll still work on it, but it won't get done as fast now that it's not sponsored.
Michelle
Comment #7
bcobin commentedThanks for the update, Michelle - sorry about the project; that sort of thing seems to be happening a lot these days. (Or not happening, as the case may be.)
:-(
Am I correct in assuming that CCKFP is the only game in town as far as profile privacy in D6 is concerned? Thanks, as always for your brain-power...
Comment #8
michelleI think there's some node access built into user relationships but I haven't looked into it, yet.
Michelle
Comment #9
michelleI was just talking to the maintainer on IRC and it looks like the CCK panels integration is where the fault likely is so I'm going to move this over to CCK's queue.
Karen / yched - don't worry about this issue. I will be looking into it with the CCK field privacy maintainer soon as we have time. I'll submit a patch when we have a fix.
Michelle
Comment #10
bcobin commentedGlad to see you're "on the case" here, Michelle - this is really the missing piece...
Comment #11
jogebau commentedany update on this?
Comment #12
asak commentedI'll patiently wait.
Thanks you.
Comment #13
michelleSorry, won't be coming from my end any time soon. Still something I need to get sorted at some point but I don't know when.
Michelle
Comment #14
obsidiandesign commentedSubscribing - hopefully in the near future Michelle and I will be able to work on this (I maintain CCK Field Privacy).
Bryan O'Shea
Comment #15
michelleI don't remember what the issue was anymore... But I'm in the process of redoing the panels/cck integration for panels 3 so I guess we'll see if it's still a problem. :)
Michelle
Comment #16
ayalon commentedAny hints on this issue or a short explanation how to start to create a patch?
Comment #17
markus_petrux commentedHere's a patch that tries to fix the field access issue, and also loads field information for the specific content type.
Comment #18
markus_petrux commentedRe-rolled. The content_type render callback should return a $block object or nothing (null), not an empty string.
It would be much appreciated if someone could test this, so we can get it in. Thanks :)
Comment #19
yched commentedLooks good to me :-)
Comment #20
markus_petrux commentedCommitted to CVS. Thanks again. :)
Now, I'll re-roll the other patch related to Panels 3 integration, as the patch here alters offsets, etc.
For reference: #505278: Panels 3 and multiple node type fields.