|
jacl
|
February 19, 2018 at 11:10 am
Hi
Just launched my first Event Espresso site after 12 months of development 🙂
Client loves the frontend but are finding the backend time consuming to add registrations and payments.
They take quite a lot of payments over the phone and often give $10 off if booked via a certain site so I think to save them time i need to let them register people via the frontend website as then at least the admin can use an unknown promotion code to give the $10 off….In the backend is they put a payment through $10 less it had a status of payment pending in red.
BUT they wont always have the card details and right now the only payment option we offer via frontend is Authorize.net (credit/debit cards)
I have flexible payment methods and payment methods pro installed and was hoping we could add an option for cash or manual payment but ONLY show that for admins when logged in to frontend so this is not an option for customers?
If there is no option in the settings to hide on frontend from certain user groups then do you think if i try hiding that second payment option for non admins on main website using CSS it might work?
Thanks
Jonathan
|
|
Josh
|
February 19, 2018 at 1:46 pm
Hi Jonathan,
If your WordPress theme uses the body_class() function, e.g. in header.php
<body <?php body_class(); ?>>
then you can add CSS like this to hide the invoice payment method from logged out users:
#ee-available-payment-method-inputs-invoice-lbl img,
#ee-available-payment-method-inputs-invoice-lbl input{
display: none;
}
.logged-in #ee-available-payment-method-inputs-invoice-lbl img,
.logged-in #ee-available-payment-method-inputs-invoice-lbl input{
display: inline-block;
}
|
|
jacl
|
February 19, 2018 at 1:56 pm
OK thanks Josh and hiding it with css wont break anything… great ill give that a go…. the client also just asked about how to archive events but have seen that its not possible so just wondered if there are any performance issues when it reaches a few thousand expired events?
|
|
Josh
|
February 19, 2018 at 2:21 pm
Hiding the Payment method with CSS will not break anything, but you’ll be sure to not set that one to “Open by Default”. It might be a good idea to set the only visible to all payment method to “Open by Default” though.
You won’t see performance issues when there are thousands of expired events because Event Espresso doesn’t load expired events from the database for most requests. There are exceptions (like if you have a shortcode on a page like [ESPRESSO_EVENTS show_expired=true]) but even with exceptions there will be pagination so it won’t try to load all of the events in one request.
|
