Support has been upgraded!
The Support Forum is closed. Not to worry! Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.
Premium Support
Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?
Please open a Support Ticket in your user account.
Free Support
Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.
Please open a new support topic in the WordPress support forums for Connections.
Tagged: 8.6.9, shortcode, upcoming_list, visibility
- This topic has 5 replies, 2 voices, and was last updated 6 years, 3 months ago by
Robert Shaw.
-
AuthorPosts
-
08/12/2017 at 9:10 am #432118
Robert Shaw
ParticipantAlthough I have marked all birthdates as private, the upcoming list still shows them to users who are not logged in.
08/15/2017 at 1:23 pm #432376Steven Zahm
Keymaster@ Robert
My best guess this is due to the page was cached while the/a user was logged in and the cached page is being served by WP Super Cache. My suggestion would be to purge your page page cache and make sure WP Super Cache is not configured to serve cached pages to logged in users.
Hope this helps, let me know.
08/15/2017 at 1:25 pm #432377Steven Zahm
Keymaster@ Robert
Oh, another thought… did you sent the entry or just the birthday to private? If it was the later, that is by design. Make sure you set the entry itself to “Private” not just the date.
08/16/2017 at 10:46 am #432481Robert Shaw
ParticipantThus the entry visibility overrides the visibility of data fields, at least for Birthdays set to “Private”. So what then is the use of setting visibility at the level of any field if [Upcoming_list] will override it?
What will happen for birthdays set as “Unlisted”? Will the entry level visibility override that as well?
[uocoming_list] seems to also override the visibility set in user roles tab, for I have also required users to be logged in at the Contributor level or higher to see “Public” data.
Please make this “feature” part of your documentation, as I would consider it a serious design flaw, in that I can no longer trust the visibility settings of any field.
08/17/2017 at 3:49 pm #432660Steven Zahm
Keymaster@ Robert
RE: Thus the entry visibility overrides the visibility of data fields, at least for Birthdays set to “Private”. So what then is the use of setting visibility at the level of any field if [Upcoming_list] will override it?
The upcoming list only purpose is to display the anniversary or birthday. The visibility of other fields will have no effect because they are not displayed because they do not exist in the template which displays the entry. So those fields will not be overridden.
The feature of displaying the public and private upcoming anniversaries and birthdays was designed and coded to deliver what was being requested by users at the time. This is the reason is why it only the first name is displayed by default. The users that requested the upcoming list and its features were other church leaders looking to put their directory online.
RE: What will happen for birthdays set as “Unlisted”? Will the entry level visibility override that as well?
Yes, anniversaries and birthdays set as unlisted will be displayed.
RE: [uocoming_list] seems to also override the visibility set in user roles tab, for I have also required users to be logged in at the Contributor level or higher to see “Public” data.
Yes, correct, the code does not take the user role into account when displaying the anniversaries or birthdays in the upcoming list.
RE: Please make this “feature” part of your documentation
Yes, this should definitely be in the docs. I’ll add it today.
….
I wrote the above long reply then it occurred to me that those that requested the upcoming list, that was quite a long time ago perhaps I change the its functionality or add a new shortcode and leave the other intact and replace the documentation for the old with the new.
Would you be will to test the change if I make it?
08/17/2017 at 4:10 pm #432662Robert Shaw
ParticipantYes, Steven, I am most willing to assist with testing and drafting documentation for changes to [upcoming_list].
FWIW, I also have experience as a Senior Systems Engineer for military systems.
For backward compatibility, could you add short code(s) to effect privacy of data fields and make the default to show the data?
-
AuthorPosts
You must be logged in to reply to this topic.