|
Danny Long
|
April 17, 2014 at 4:25 am
For reference, here’s our event:
http://sunshinetour.co.uk/events/2014-sunshine-tour/
1. For some reason, I can’t create any additional tickets for an event past a certain amount.
I add them, update the event and then they disappear once the page reloads.
See vid:
http://www.youtube.com/watch?v=Mz8GSFYyL9A
2. We used the workaround suggested by Dean to create the headings and subheadings by setting expired ticket price and qty to { display: none; }
Is there any way to also change the font color for the text corresponding to these expired tickets?
We’re using the My Custom Css plugin. Or if you could let us know which .css file to edit (and which element within the file), we could do that as well.
3. Is it possible to specify a background color for the entire container in which the event registration form displays?
Our current theme background makes it hard to make out the event details.
4. We managed to change the default verbiage in several parts of the registration form using the Quick Localisation plugin as per your documentation.
However, there were several things that we couldn’t change using the plugin. For instance, if you click on “show details” for a ticket, you’ll see “This Ticket Sold”, “This Ticket Left”, etc.
These we couldn’t change. Any way to do it?
5. How can we change the text in the submit button at the end of the registration form? On the first page of event registration it says “register now” which is fine.
However, on the second page it says “proceed to payment options” which we’d like to change to something else.
***
Thanks for your awesome support so far. We’re really impressed and we’ve been talking you up to some of our clients and business friends. Keep up the great work!
Best,
Danny
|
|
Dean
|
April 17, 2014 at 5:37 am
Hi,
First off, thanks for the video, things like that really help.
1) That’s strange. You have about 37-40 tickets. I added 60 tickets without an issue. I tested this out on a few versions of 4.2 and each one correctly saved 50 or more tickets.
Can you try disabling other plugins, perhaps one is inteferring somehow.
2)
.ticket-sales-expired.lt-grey-text { color: #000; }
(can be added to My Custom CSS)
3)
.tkt-slctr-tbl {
background-color: #fff;
padding: 25px; /*looks weird without this*/
}
4) You will need to use:
This Ticket
Sold
This Ticket
Left
etc.
5) You can change it via language files
Proceed to = Proceed%1$sto%1$s
Payment Options = Payment%sOptions
Problem is with Payment Options. Changing this will change it in various places in the checkout, most noticeably at the top http://take.ms/ZGOSe
|
|
Dean
|
April 17, 2014 at 5:48 am
I’ll try number 4 again
4) You will need to use:
This Ticket<br/>Sold
This Ticket<br/>Left
etc.
|
|
Danny Long
|
April 18, 2014 at 1:26 am
Hi Dean, just a thought would you like access into the platform to have a look at this as the management of adding the tickets is a challenge… happy to share the environment with you.
|
|
Dean
|
April 18, 2014 at 3:36 am
Hi Danny,
No need currently. A colleague has recreated the issue locally, so we have raised a ticket. We are still trying to pinpoint the exact issue as I am still able to create 60+ tickets with no issues, whereas he hit the same limit as you (about 36 tickets).
|
|
Danny Long
|
April 20, 2014 at 4:55 am
Hi Dean,
1. Thanks for all the CSS customizations. 🙂
2. I tried deactivating all plugins except EE and adding a ticket. No dice.
Any clue what the issue might be…?
|
|
Dean
|
April 21, 2014 at 12:39 am
Hi,
1) No problem
2) Not yet. I’m still unable to recreate this but my colleague can. We have raised a developer ticket to look into it.
It might be a PHP related issue, where it blocks the number of input variables (form fields, Globals, and more).
Can I ask what version of PHP are you running?
|
|
Danny Long
|
April 21, 2014 at 3:49 am
Dean, we’re running PHP version 5.4.14 and mySQL 5.1.71
Should we upgrade?
|
|
Danny Long
|
April 21, 2014 at 4:06 am
We also managed to remove any pricing verbiage from our event but as you can see, the “Qty*” column got displaced.
http://sunshinetour.co.uk/events/2014-sunshine-tour/
Here’s our custom CSS. Could you please advise how to re-align?
.ticket-sales-expired td:nth-child(2) { display: none; }
.ticket-sales-expired td:nth-child(3) { display: none; }
.ticket-sales-expired .display-tckt-slctr-tkt-details { display: none; }
.ee-icon-event {display: none; }
.ticket-sales-expired.lt-grey-text { color: #215e8e; }
.tkt-slctr-tbl { background-color: #fff; padding: 25px; border-style:solid;
border-width:2px; /*looks weird without this*/ }
.jst-rght.small-text {display: none; }
.currency-code {display: none; }
.jst-rght {display: none; }
Thanks!
|
|
Danny Long
|
April 21, 2014 at 4:18 am
Sorry, please ignore that last post.
What I meant to ask was: how do we get rid of the entire column of prices?
http://sunshinetour.co.uk/events/2014-sunshine-tour/
(all of the £0.00’s)…?
|
|
Dean
|
April 21, 2014 at 4:31 am
Hi,
Dean, we’re running PHP version 5.4.14 and mySQL 5.1.71
Should we upgrade?
That’s up to you but I don’t think it’s necessary. I think that it is due to a change in PHP 5.3 or 5.4 so upgrading probably won’t fix the issue. I’ll need to refer this to a developer.
What I meant to ask was: how do we get rid of the entire column of prices?
CSS to the rescue again! (or you can edit the templates, but this is easier)
.tckt-slctr-tbl-tr td:nth-child(2) { display:none; }
.tkt-slctr-tbl thead tr th:nth-child(2) { display:none; }
This will hide column. You may want to fiddle with the table CSS as this will reduce the tables width.
|
|
Danny Long
|
April 24, 2014 at 1:51 am
Hi Dean
Would you know when the issue might be resolved for the ticket limit as this is causing us a major issue… happy to pay to prioritise this as it is causing us real challenges with the client.
Many thanks
Danny
|
|
Dean
|
April 24, 2014 at 3:46 am
Hi Danny,
The ticket is still being discussed, but here is the current situation. As of PHP 5.3.9 there was a PHP setting introduced called max_input_vars. This is defaulted to 1000. Lots of different things make up that 1000 figure, including but not limited to, EE variables.
(I run PHP 5.3.1 locally so that is why it didn’t cause me any issues).
Now that figure in terms of a general WP and EE setup will max the number of tickets at 36/37.
While we can attempt to reduce the number of variables we use, it’s actually quite hard as even the content of an array count towards the figure.
The best solution we can offer is for you to change the setting in your php.ini file, which you may need to discuss with your host.
max_input_vars = 2000
This will literally double the number of tickets. Our tests show up to 75. However depending on your set up this may differ as other plugins may take up some of that 2000.
I hope that makes sense and helps.
-
This reply was modified 10 years, 7 months ago by
 Dean. Reason: typos galore
|
|
Danny Long
|
April 28, 2014 at 3:18 am
Hi Dean,
You wrote:
“5) You can change it via language files
Proceed to = Proceed%1$sto%1$s
Payment Options = Payment%sOptions
Problem is with Payment Options. Changing this will change it in various places in the checkout, most noticeably at the top http://take.ms/ZGOSe”
My question is: where are the language files?? And you said “files” so I assume I need to change this in several different files or…?
|
|
Dean
|
April 28, 2014 at 3:57 am
Hi Danny,
The language files are available via Github – https://github.com/eventespresso/languages-ee4
There are two files a MO and a PO. You only need to edit the PO it will update the MO for you (if you use Poedit, which is free from poedit.net). Check out this guide here on translating – https://eventespresso.com/wiki/how-to-change-wording-with-poedit/
|
