Hide specific information at events

Thanks so much for reaching out!

As a first step, I’d recommend taking a look at this article on our integration with Ultimate Member: https://theeventscalendar.com/knowledgebase/k/integrating-ultimate-member-with-the-events-calendar/

Let me know if that helps!

Thanks,
Jaime

Hi @jaimemarchwinski,

thank you very much! Access to the individual event is prevented, but the information mentioned (location, time, description) is already displayed in the overview (domain.com/events).

Best regards
Bj?rn

Hi @bkiehle

Thanks for your reply! Ah I understand. It seems like you are looking to hide information from the main calendar page. Unfortunately, I’m not quite sure of how to do that with our plugin out of the box.

Alternatively, you should be able to restrict access to the calendar page entirely.

Let me know if that helps!

Thanks,
Jaime

Hi @jaimemarchwinski,

can you please tell me how to restrict access to the whole calendar page?

Best regards
Bj?rn

Hi @bkiehle, it is another plugin that should be able to restrict content on the frontend, Restrict Content — https://theeventscalendar.com/knowledgebase/k/integrating-restrict-content-pro-with-the-events-calendar/.

Let me know if this helps. Have a great day.

Best,
Abz

Hi @abzlevelup,

Yesterday I sent you the access data to my website. The information is visible despite the plug-in. “Restricted Content” is displayed instead of the title in the event overview, but above it the time and below it the location.

Best regards
Bj?rn

Hi @bkiehle, appreciate you providing us with more details here. I’d be conversing with you on the email thread. This is for us to track down issues/threads more efficiently.

Best,
Abz

Yesterday I sent you the access data to my website.

That’s really bad. Please read the whole reply.

Anyone may be banned from this site if you have a repeat accessing a forum user’s site again. And it will come out if that happens again. It always comes out.

To plugin support: please take this seriously, you are putting this plugin in jeopardy on the WordPress repo and confirm that you are not accessing a forum user’s site in reply.

While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.

If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.

Thankfully are other ways to get information you need:

• Ask the user to install the Health Check plugin and get the data that way.
• Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
• Ask the user to create and post a link to their phpinfo(); output.
• Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
• Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
• Ask the user for the step-by-step directions on how they can reproduce the problem.

You get the idea.

We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.

Hi @jdembowski,

as the website was still under development, it was protected by a password (.htaccess). This is not (!) the website login data! I only had to give the support of The Events Calendar read access from the outside.

@abzlevelup only had the access that everyone has now (the website is now finished).

Best regards
Bj?rn

Hi @bkiehle,

Apologies for the delay here.

It would still be part of the guidelines including the tests (development site), regardless if it is the front or back end. Moving forward please refrain from sharing any credentials.

Please feel free to open a new thread if any other questions come up, and we’d be happy to help.

Cheers,
Abz

Hi @abzlevelup,

sorry about that, I thought it would be ok for the frontend.

Thank you very much!

Best regards
Bj?rn