|
SeamusTRNR
|
March 20, 2022 at 6:06 pm
We have several concurrent events and we see people accidentally double booking. I don’t see a way for EE4 to prevent or flag that, and I would like to search the exported csv file for conflicting events. I think the ticket ID would be the quickest way to identify the events. Or I could work with the event end datetime, but I don’t see that in the csv file either. Thank you.
|
|
Tony
|
March 21, 2022 at 11:39 am
Hi there,
We don’t include every detail within the CSV, based on feedback from EE3 and early EE4 testing we found most users didn’t want every details and would request a method to limit/reduce the columns (which we still get even now with minimal data).
The CSV is filtered so it is possible to add/remove details from the CSV, however…
If you only add the Ticket ID you would then need to match up ticket IDs to know which events conflicted, which seems a little, long-winded (noting all the ticket IDs which could conflict to then compare against)?
Datetime end date could be added but what if a ticket is assigned to multiple datetimes? I would assume just list all dates separated by a comma in a single column.
|
|
SeamusTRNR
|
March 21, 2022 at 4:58 pm
OK – I think we can keep the ticket names unique for every event datetime and form tables of conflicts that I can search – but that’s even longer winded than IDs!
We have a separate ticket for each event datetime, but I see your point on the end datetime for the more general case. Thanks for thinking about it.
|
|
Tony
|
March 22, 2022 at 6:33 am
OK – I think we can keep the ticket names unique for every event datetime and form tables of conflicts that I can search – but that’s even longer winded than IDs!
You could and I agree it is, but I’m not sure where that has come from as I didn’t mention using the ticket names?
We have a separate ticket for each event datetime, but I see your point on the end datetime for the more general case. Thanks for thinking about it.
Adding a snippet like this:
https://gist.github.com/Pebblo/9825cc82f8829ba2dfcf355dfdd6014d
Will add a ‘Start Datetime’ and ‘End Datetime’ to the CSV which I think should help here.
You can add that to a custom functions plugin on your site, we have some documentation on creating one here:
https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/
|
|
SeamusTRNR
|
March 24, 2022 at 3:42 am
I have added the directory and file:
~/public_html/wp-content/plugins/eea-add-datetime-columns/eea-add-datetime-columns.php
I have tried a few changes to the name, but none of them appears as the other eea- plugins do on my backend Plugins page. I do not see the added columns in the csv file. (Start datetime was already there. I have 31 columns total.) Permissions on the file are owner rw, group and world just read, but that seems to be the same as, for example, eea-attendee-mover.php. My ignorance is getting in the way here. Btw, should I be upgrading 4.10.26.p to 29.p, or wait until the event is over? Thanks again.
|
|
SeamusTRNR
|
March 24, 2022 at 4:14 am
Never mind! I did get it, by changing the name within the header area to Event Espresso – Add Datetime Columns. It then appeared on my plugins page and I was able to activate it. 33 columns, start datetime is redundant but I think I can remove that if I want. The editor could see the file but it was not listed on the plugins page until I did that. Thanks.
|
|
Tony
|
March 24, 2022 at 4:31 am
If you followed the guide above the file is a ‘standard’ WordPress plugin so the first few lines:
<?php
/*
Plugin Name: Site plugin for myexamplesite.com
Description: Site specific code for myexamplesite.com
*/
Are what WordPress uses to display the plugin (the above would display as “Site plugin for myexamplesite.com”), the eea- name convention is ours but wont do anything within a standard plugin like the above (doesn’t hurt to use it thought).
Anyway, you’ve fixed it now 🙂 just wanted to add some info on what I think was happening.
To remove Start Datetime just comment out line 33, so add // to the beginning of the line. The function will still be pulling in the start datetime but wont include it in the CSV, you could also comment out Lines 19 – 23 to prevent that.
|
|
SeamusTRNR
|
April 2, 2022 at 8:45 am
This works perfectly. The two new columns showing up last give a simple way to check for overlaps in Excel (subtracting datetimes after sorting properly) and displaying each individual’s attendance on a pert-chart like schedule (using conditional formatting). Thanks again.
|
|
Tony
|
April 4, 2022 at 7:06 am
You’re most welcome, glad it helped 🙂
|
