Please Log in or Create an account to join the conversation.
It should display fine on registration. Ensure your field is available on registration and it has privacy controls enabled. The source code checks for edit and registry modes to determine if it should show privacy controls or not.1. First weird thing is that the privacy options do not show on registration. Howsever they do show on profile edit.
When profile edit and registration is saved is when the privacy settings will save. You can't determine a users privacy if they don't have a privacy settings unless you've set default privacy values for your fields. In which case the default will take affect if they've no privacy row.2. When I monitor the privacy plugins database table, I cannot find the latest registered users in it. At what point do they get stored into the privacy database table and how to determine programmatically a users privacy settings if a user is not present in there?
Yes, but it's due to a bug. Turn off hiding of empty fields or review the fixes shown in the below topic.3. Is it correct that userlist does not respect CB privacy settings? Either way I have to find a way to display only public users in a public user list and all users (public an private)
Please Log in or Create an account to join the conversation.
It seems that it is showing now. I have no idea why. It might be some caching issue. I have just moved it to another tab and will check later if this has worked as well.krileon wrote: It should display fine on registration. Ensure your field is available on registration and it has privacy controls enabled. The source code checks for edit and registry modes to determine if it should show privacy controls or not.
So this means if privacy is set to be required on registration every user registering after that should have an entry in the privacy table. Right? For some reason this did not work. The privacy table does not reflect values for some users although it was set to be mandatory. I guess this happened due to the privacy field not showing up on registration.krileon wrote: When profile edit and registration is saved is when the privacy settings will save. You can't determine a users privacy if they don't have a privacy settings unless you've set default privacy values for your fields. In which case the default will take affect if they've no privacy row.
The issue still persists after applying the patch and regardless what I set "hiding of empty fields" to.krileon wrote: Yes, but it's due to a bug. Turn off hiding of empty fields or review the fixes shown in the below topic.
www.joomlapolis.com/forum/154-advanced-members-support/223359-solved-cb-privacy-plugin-not-showing-quserq-option?start=24#237108
Please Log in or Create an account to join the conversation.
It has to exist in the POST for it to do anything with it. So, yeah that could be a result of it not showing up. It doesn't matter though if you have a default privacy set as the default will always take affect if there's no privacy row.So this means if privacy is set to be required on registration every user registering after that should have an entry in the privacy table. Right? For some reason this did not work. The privacy table does not reflect values for some users although it was set to be mandatory. I guess this happened due to the privacy field not showing up on registration.
Are you having issues with the privacy not working at all on userlists or the ", 1" issue with image fields? That won't fix the image field issue, but it should fix the issue of privacy not working on userlists. The image field issue will be fixed in next release; I don't have a quickfix for that at this time.The issue still persists after applying the patch and regardless what I set "hiding of empty fields" to.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
It can't remove the user from initial display. It only removes them from the results when a search is made on a field they have protected for example (this bubbles up to tab privacy then profile private, etc..).CB Privacy seems to work on the userlist. But it looks like any user that should be removed from the list by CB Privacy will show up with this ",1" issue instead of not showing up.
After CB 2.0 goes stable CB Auto Actions, CB Conditional, and CB Privacy will receive their upgrades first. Until then all projects are on hold as right now CB 2.0 has priority. That isn't actually a bug though, it's just not possible to do in CB 1.x. You're seeing the ", 1" for image fields, because it's not doing very well at grabbing an image field with no value; that'll be fixed for next release though.When can we expect a fix for this as this is keeping my website on hold in offline mode.
That filter isn't valid. It should be as follows.Edit: When I use following code as filter
Your query becoming invalid is likely what's causing odd behavior.1. The userlist returns 0 users when I leave all search input fields empty. When I fill up a search input field or use an asterisk, then the search returns an appropriate userlist.
2. The second weird part is that for the returned user list the search form (search criteria) remains visible all the time and does not get hidden anymore.
Please Log in or Create an account to join the conversation.