[George]

Hey Paul,

I reached out to some other support team members for insight on this issue, as your behavior is indeed quite odd and I cannot recreate it myself.

One thing that seems worthy of testing (or re-testing, specifically) is ensuring that you disable WP Rocket Caching – you should also be sure to clear any effects from that previously-active caching, which may not require any extra additional steps, but you should check the WP Rocket caching documentation or support team for full instructions on how to completely shut off the caching.

If you can do this, let us know what you find. And again: thank you for your patience with the issue.

George

[George]

Thank you for clarifying Jennifer, I apologize for my misreading of your issue.

Unfortunately, I do not know how to add custom fields to that plugin.

There are many solutions for custom CSV exporting for WordPress out there, and it unfortunately seems that a solution like one of these plugins is the best option here – The Events Calendar and its add-ons do not have the specific CSV export functionality you are looking for.

I’m sorry for the disappointments Jennifer. Let us know if you have any further questions or concerns here.

— George

[George]

Thanks for the update James, definitely keep us posted on how upgrading WordPress affects this (if at all)!

[George]

Hey Tomek,

I hate to disappoint you and to bear bad news, but in some playing around with ideas and looking through code I was not able to come up with something here.

There are a few ideas remaining that I can think of – if your events aren’t happening until into 2016, is it possible to just slowly add tickets to events a little bit each day as the events approach? So that you don’t have to try adding 3200 tickets all at once or anything. This is still a bit of manual work, so I understand if it’s not a helpful idea, but I’m just curious.

The other option I can think of would be hiring someone to build out this functionality for you.

Either way, we do have official support for recurring tickets coming some time in the next several months – if you can make it until then, our official solution will be released and hopefully relieve a lot of this stress for you and other users seeking this functionality.

I’m very sorry for the disappointment Tomek – let us know if you have any other questions or concerns.

— George

[George]

Hi Mitchell,

From my understanding about your use of the word “subscribe”, no, it is not possible.

— George

[George]

Hey Ellen,

Damn, I’m sorry to hear that your theme developer dropped out like that. I’m curious about what the issues could be, sometimes it’s something very simple – if this is not the case, and there’s a complex conflict here, then unfortunately there is little that we can do from our end.

One thing that might help is to activate your problematic theme, and see if any errors pop up on your site if you head to your site’s wp-config.php file and change this line of code:

define('WP_DEBUG', false);

to this:

define('WP_DEBUG', true);

If not, then if you upload a .zip of your theme to a site like Dropbox.com or http://ge.tt, and then a share a link to that download here in this thread, we can download it and give it a few minutes of testing to see if the issue is a simple one to fix – if so, we might be able to patch it for you 🙂 But if it’s not clear what the problem is, or it’s a very complex one, we won’t be able to delve into it.

I’m sorry about the disappointments here, please let us know what you find by doing that WP_DEBUG test, and if you can upload the theme .zip anywhere for us to download it.

Thank you!
George

[George]

Thanks for the update and for sharing what worked for you Philip!

Best of luck with your project!
George

[George]

Hey Simon,

We cannot support customizations or custom code, especially one as complex as this.

I feel like the code you’ve already written could cause serious problems on your site, and the code in that other ticket is not secure.

So, even though this customization is a bit outside the scope of the support here, I will show you the general ideas of how to do this – you can take the reins from there and look up online anything you’re not very familiar with.

So let’s break this down: in our example, I will be pulling in the user’s browser data since it is a Meta Value on the order – your custom “guest name” information seems to as well, so just adapt the get_post_meta() calls to your own needs.

—

Part One: Registering the table column

Plugin: The Events Calendar
File: lib/tickets/tribe-tickets-attendees.php

Look for the get_columns() method in this file’s main class. It should look something like this by default → https://cloudup.com/ccTBZ9polwG

You can add a column header here following the pattern described in the comments above this function – for our demo here, we’ll use the very clever column handler example_testing and the header name Example. Adjust these values to your needs, but keep them consistent for your whole customization.

Here’s how that get_columns() method looks after adding a new column header → https://cloudup.com/cxO4Sv5C_kO

—

Part Two: Populating the new custom table column with data

Plugin: None – Go to your active theme instead.
File: Your theme’s functions.php file

In your theme’s functions.php file, add a filter to The Events Calendar’s attendees table like so:

if ( function_exists( 'tribe_is_event' ) {
	/**
	 * Populates a custom Attendees Table column with data.
	 * @link http://m.tri.be/va
	 */
	function tribe_956198_example_column_testing( $value, $item, $column ) {

		// Notice the 'example_testing' column handle here! Change to your needs.
		if ( 'example_testing' !== $column || ! isset( $item['order_id'] ) || empty( $item['order_id'] ) ) {
			return $value;
		}
	
		return sanitize_text_field( get_post_meta( $item['order_id'], '_customer_user_agent', true ) );
	}

	add_filter( 'tribe_events_tickets_attendees_table_column', 'tribe_956198_example_column_testing', 20, 3 );
}

The use of ‘example_testing’ should instead the custom column handler you made for yourself – and the use of the ‘_customer_user_agent’ meta on the item’s order id should be changed to whatever meta value you need for the Guest Name.

These two steps will add a column header and populate it with the necessary data. Here’s a screenshot of things now by using these two steps on my local test site → https://cloudup.com/cRuOKmr8enF

—

Part Three: Adding the column and its data to the export file

Plugin: the WooCommerce Tickets add-on
File: /classes/class-wootickets.php

The above two steps will not by themselves add the data to the CSV. So, to add this, head into the WooTickets add-on itself, and look for the main class-wootickets.php file.

Once here, find the get_attendees() method, and look for the $attendees array here. It should look something like this → https://cloudup.com/cuwxMXSFSB0

Now, remember in Step Two how we pulled the data for the column by using the get_post_meta() function? And how for my testing purposes, the meta key is ‘_customer_user_agent’? We accessed this data by using the following code:

sanitize_text_field( get_post_meta( $item['order_id'], '_customer_user_agent', true ) );

Here in Part Three in the class-wootickets.php file, we’ll use that same code again. Except instead of using $item[‘order_id’] to access the order ID, in the get_attendees() method we’re customizing we have access to just $order_id.

So go back to that $attendees array screenshotted above, and add a key of the same column handler we started with all the way back in part one – ‘example_testing’, remember? – and the get_post_meta() call above.

Here’s how this would look → https://cloudup.com/cAqUb7LFdPL

—

Conclusion and Warnings

After all this you should have a custom column, and when you “Export”, the column and data should be there. My screenshot cuts some of the data off, but here’s some proof – https://cloudup.com/cBbcNRFyZ5I

There are a few very important things to note here:

1. Auto-updating any of these plugins will over write these customizations and thus break things on your site. So before updating from now on, each time you will have to back up these customizations, update the plugins on your site, and then add the customizations back in manually.

2. We cannot support customizations – if issues arise related to the custom code here, it’s unfortunately something outside the scope of the support forums and something you’d have to manage and wrestle with yourself.

3. If you get this working with these methods, you should get rid of the original code you used and shared in your other forum post – the code that calls the Database directly. That is not safe code to have on your site.

Go through all of this Simon, give it some time and look up anything you’re not familiar with. Let us know if it helps!

— George

[George]

Hey Péter,

I’m sorry you found further issues with the Widgets and category filtering in them – if issues persist, please open up a new ticket here on the forums and we’ll do our best to help address those issues and get a solution in place.

Since you’ve marked this ticket “Resolved” for now, however, I’ll close up this specific ticket. Best of luck with your project in the meantime!

— George

[George]

Hi Eric,

Thanks for sharing the plugin in question – we’ll keep our eye on further reports of conflicts and can investigate further.

I’ll close up this specific for now, but stay tuned to product updates and the changelog for each update – if specific updates are made to improve compatibility with this plugin, they’ll be noted there.

Sorry for the disappointment here Eric! I hope the rest of your project goes smoothly.

Cheers,
George

[George]

Hey TK,

I just shared some ideas in my above post to James that may be helpful to you too, so definitely check them out:

As for SSH Cron, this may be possible, but I don’t know how to write it all specifically in its entirety. Some ideas that come to mind that may be possible are to write a manual cron job that just calls the existing auto-import functions within the Facebook Importer plugin itself – there is a WP_Cron action registered named ‘tribe_fb_auto_import’, so firing this action may work well, but there’s also the method that this action calls itself, named do_auto_import() in the main Facebook Importer class…

I’d recommend studying how the import works, and trying to work backwards from there to figure out how best to automate it in line with your specific needs.

In regards to this forum thread itself, James mentioned that he has another ticket already open and in progress regarding his specific auto-import issues, and there’s little else we can do here for the customized implementing of SSH cron jobs for your projects’ needs. Do you have any further followup questions here? If not, I’ll go ahead and close up this ticket – though you can always come back and open a new ticket if other questions arise! 🙂

[George]

Hey James,

I’m glad to hear you have another thread opened where these specific issues with your import behavior are being addressed.

—

As for SSH Cron, this may be possible, but I don’t know how to write it all specifically in its entirety. Some ideas that come to mind that may be possible are to write a manual cron job that just calls the existing auto-import functions within the Facebook Importer plugin itself – there is a WP_Cron action registered named ‘tribe_fb_auto_import’, so firing this action may work well, but there’s also the method that this action calls itself, named do_auto_import() in the main Facebook Importer class…

I’d recommend studying how the import works, and trying to work backwards from there to figure out how best to automate it in line with your specific needs.

[George]

Thanks for looking into these items Andy – unfortunately, it seems like there might be something deeper going on here, so I think some more thorough troubleshooting steps would be very helpful to help narrow down (or, at least, rule out) possible culprits here.

First, in your original post you say: All was working fine until a few days ago. Does this timeline happen to coincide with any specific changes you made on your site? For example, in “a few days ago” (from the day you posted your original post here), did you update any plugins, themes, or WordPress Core itself on your site? Did you install anything new? Did you make any notable changes with your site settings or configurations? Did you add some custom code? Anything at all like this, if you can remember, might be useful to know.

Next, I’d recommend running through our full set of troubleshooting steps outlined here → https://theeventscalendar.com/knowledgebase/testing-for-conflicts/. The actual process is not nearly as annoying as the article makes it seem! 🙂 The process of deactivating and re-activating things on your site is actually pretty quick, and if you run through those steps and check on this event/tickets behavior after each step (maybe even making a new test event with tickets each time, if you can), it should reveal useful information here.

Finally, as a quick note, your offer to share admin access with us is appreciated, as is the desire to cooperate and work together that it reveals – but unfortunately, we cannot log into user sites for a bevy of security-related reasons (and a touch of legally-related ones, too, in most cases).

Your patience with this issue is appreciated Andy, let us know what you can do with the above information and what you find by doing it!

Cheers,
George

[George]

Hi Shah,

Apologies for the slight delay in response times here – your followup post on the 19th was a Sunday here, and then I was out on the 20th for a local holiday, so I’m catching up with threads I didn’t get back to in that three-day weekend. Thank you for your patience!

—

Now, as for your issues, I appreciate your further elaboration and detail here – your new information above definitely helps clarify your issues a bit more.

I’ll address some specific things you mentioned in order:

We will not be posting any event ourselves on any of our portals. But organizers will post events using Community events. […] We ourselves do not have any interest in having information about attendees neither we want general public to know their details. However, we want organizers who post events to have info. about the number of expected attendees and if possible their names phone etc

The main functionality here depends on what setting you have for the “Allow Anonymous Submissions” option in your Community Events settings page. Here’s a screenshot of that option, for reference → https://cloudup.com/cmlMil9HWXX

If this option is checked, meaning that you do want to allow Anonymous Submissions, then the specific functionality you’re describing is not something possible by default with our plugins. You would have to either write custom code far beyond the scope of our plugin support, or manually share the attendee data with people who submit events upon request or something.

If this option is not checked, then only people who are registered users on your site can submit events. This is a great option. You could require event organizers to sign up on your site – for free, of course – and simply keep their admin accounts at a limited-access user level like Editor or Subscriber or Contributor. This would mean that they can submit community events totally fine, and log into your admin and see the attendee list and such, but not have access to anything sensitive on your site like other content, the site settings, the plugins and themes, other user accounts, etc.

—

If we expand this feature a little more, George will not only say YES but also will be able to add his wife / fiance and say that there are two people coming. If we go a little further George should be able to add his info for example name, address and phone number. Or just name and phone Number. By this Mr. Brown will know who is coming.

These things are technically possible to incorporate into the plugins, but are not already there – you would unfortuantely have to add these features with extensive custom code.

—

If the site has woocommerce ticketing plugin and the event is not free. George may also buy the ticket besides expressing his intentions to join.

You can indeed enable ticketing for community-submitted events, but you as the main site administrator (or another site administrator) would have to manually create the tickets for the submitted event. In other words, at this time users can only submit the price for an event via the “Event Cost” field on the Community Submission form. But they cannot create tickets from there. When you go to a community-submitted event, and add tickets, you’ll see a red notice like this altering you that it came from the community submission form: https://cloudup.com/c44CaMqFjmV

You can then create tickets from there for the event.

—

I hope this information helps clarify things – let us know if it does, or if you have further questions here!

Thanks,
George

[George]

Hey Tevya,

I’m sorry for your disappointments here. There are many features we’d love to have in the codebase, and every release cycle is a balancing act of adding in things we want, things the customers want, things that good performance and security need, but in each case not being unreasonable with our abilities and material constraints to actually do the things on time…

So some of the functionality that you described as missing here is indeed on our radar, and even though you’ve requested a refund, I do encourage you to please stay tuned to our product updates and changelogs! We’ve got new features and improvements coming all the time.

For one example, in your recent post you mention:

I could have sworn I read somewhere that you can’t sell recurring events? That they ticket plugin doesn’t work with them. Or did I misunderstand, since it sounds like that’s what you’re saying I should do? If that does work, can we still display them as single events in the list view? I don’t want 5 different events for each class.

At this time, in the publicly-available versions, it is indeed not possible to sell “recurring tickets”, to describe those features that way. But this functionality is actively in development and coming in a public release very soon.

That’s just an example to show that we are constantly working on these products and improving them. Your feedback in this thread is appreciated, and if you have feature ideas, don’t hesitate sharing them on our official UserVoice page here → http://tribe.uservoice.com/forums/195723-feature-ideas. We take this page very seriously and incorporate a lot of ideas from users here. It’s a great way to have your voice heard as a customer – and supported by other customers who want the same thing! 🙂

Thanks for giving our plugins a try Trevya, hopefully sometime in the future you’ll find our products a bit more suitable for the needs of your projects.

Cheers,
George

[Author]

Posts