|
Ed Evans
|
October 4, 2017 at 2:37 pm
using EE4 Everything on a relatively new install hosted on wp-engine. This is the first event that has been created. Administrator and client roles can register for events, but subscribers and visitors can not. I have checked through the documentation and other posts but, am at a loss as to where to go from here. What ee_permissions actually give the role the ability to register? Or someone who is not signed in as a role at all? Directory permissions for wp-content/uploads/expresso/templates is 755 and the fills are 664.
Thanks
|
|
Josh
|
October 4, 2017 at 3:22 pm
Hi Ed,
This doesn’t sound like a file/directory permissions issue. What this looks like is the contents of the /registration-checkout/ page has been restricted to specific roles. Do you have a plugin set up to restrict content on specific pages? In any case, you can go to edit the /registration-checkout/ page and check for any content restrictions set there. The same will also apply for the /thank-you/ page too.
|
|
Ed Evans
|
October 4, 2017 at 3:54 pm
Hi Josh,
I went to the /registration-checkout/ page and it was checked to restrict the content to the role of administrator only.
I unchecked the block and left all of the checkboxes blank.
I created a test event and still get the same result.
Below is the link to the test event:
https://www.dubell.com/events/architects-lunch-learn-3/
Thanks
|
|
Josh
|
October 4, 2017 at 4:09 pm
Hi Ed,
I’m sorry but I’m not familiar with the plugin that you’re using to restrict content to user roles, so I don’t know whether unchecking boxes would be the way forward. I do know that WPEngine has some aggressive caching in place if the user is not logged in, so it may help to go to your WP dashboard > WPEngine dashboard page and hit the button to Purge All Caches.
Also related to the above, if you haven’t already done so, you’ll need to contact WPEngine support and ask them to exclude caching for the pages that handle the registration process. There’s more specifics in the documentation:
https://eventespresso.com/wiki/setup-wpengine-hosting-event-espresso/
|
|
Ed Evans
|
October 4, 2017 at 4:18 pm
I can now register for an event as a subscriber with no extra permissions but, not as a visitor. I would like to be able to allow users to register for an event without having a role.
|
|
Josh
|
October 4, 2017 at 4:21 pm
Normally you can because out of the box Event Espresso doesn’t restrict being able to register if you’re not logged in. Something unique was set up with your site to restrict this. Have you tried purging the cache?
|
|
Ed Evans
|
October 4, 2017 at 4:31 pm
I did purge the cache and just did again , still the same.
|
|
Josh
|
October 4, 2017 at 4:38 pm
Do you have the documentation for the content restriction plugin that shows how to remove all content restrictions?
|
|
Ed Evans
|
October 4, 2017 at 6:09 pm
Hi Josh – the plugin is Members by Justin Tadlock. I see that it was recommended in this article:
https://eventespresso.com/wiki/event-espresso-4-roles-permissions/
I can confirm that the conflict is with the plugin since deactivating it resolves the permissions issue.
|
|
Josh
|
October 4, 2017 at 8:31 pm
I’m afraid that doesn’t actually confirm there’s a conflict. I’ve got the same plugin loaded up on my site that has Event Espresso and there’s no conflict there.
Here’s a link to the documentation for the Content Permissions feature of the Members plugin:
https://github.com/justintadlock/members/blob/master/readme.md#content-permissions-feature
It seems that on your site the registration checkout and thank you pages had some roles selected, which would cause the issue you reported here. One thing to verify is you’ll make sure to scroll down to confirm all boxes are unchecked.
|
|
Ed Evans
|
October 5, 2017 at 5:58 am
The problem ended up being two-fold.
The “Content Permissions” feature of the Members plugin needed to be disabled and also there was a caching problem with WP Engine. I had to contact them and have them stop the following from being cached:
/upcoming-events/
/registration-checkout/
/transactions/
/thank-you/
/registration-cancelled/
After adjusting those two things, it works correctly now.
|
