[Josh]

Hey Tamara,

Awesome! Glad you were able to find the culprit and that it didn’t impact the functioning of your site to remove. Always a nice thing when that happens 🙂

I’ll go ahead and close this thread for now. If you have any further questions, please don’t hesitate to open a new one.

Thanks!

[Josh]

Hey,

Thanks for following up and providing the screenshots!

I’ve tried to recreate this issue using the following steps:

• Updated my date formats to match your screenshot exactly
• Created a new event
• Added a ticket to the event
• Published event and reviewed correct date on the front-end of the site
• Clicked “Edit Event” in the admin bar
• Start and end date remained correct
• Modified the event details and clicked “Update”
• Start and end date remained correct

I tried this in both English and with the WordPress install switched to German.

However, I’m still not convinced this isn’t a bug on our end though since changing date format resolves the issue for you. Was the date reset happening on all events for you or was it only on particular events? Do you happen to have a link to an event that this was happening on so I can review the event settings to see if there is a particular setting on the event side that could be causing this one?

Thanks!

[Josh]

Hey,

Thanks for following up here.

I don’t currently have a copy of the Checkout Fields Manager plugin available. For further testing though, do our forms show correctly on the initial Add to Cart screen if the Checkout Fields Manager is disabled?

Thanks!

[Josh]

Hey Joseph,

I took a look through our importer code there and it appears that the check prior to import checks to see if there is an existing Organizer based on the Organizer’s Facebook ID which gets set when an event is imported from Facebook and the new organizer is created.

That being the case, I’m not sure there is a straightforward way to prevent the duplication of an existing Organizers. However, depending on how you’re using your site, there are a couple of options that you may consider.

• If you have an existing organizer that will match one that would be associated with a Facebook import, you could go ahead and assign meta to that organizer with their Facebook ID with the “_OrganizerFacebookID” key. This will prevent a re-import of that organizer from Facebook.
• You could delete the existing Organizer and re-assing the events that were associated with those to the new Organizer created from the Facebook import.

I apologizer for the inconvenience of this particular. Hopefully one of the above options may be a good fit for your site.

Thanks!

 

[Josh]

Hey,

Thanks for following up here!

I’m trying to test this out on my local install so I can create a bug ticket for this one. Would you mind sending me a screenshot of all the settings within the Date Format section of the Event Settings > Display tab?

Thanks!

[Josh]

Hey Anthony,

Thanks for reaching out to us!

When we originally built our ticketing solutions we had PDFs by default, however there was a larger demand for a simpler ability to customize the tickets so there was a decision early on to move away from the PDFs.

However, there is some discussion on this topic on our UserVoice page where you can vote for that feature if you’d like.

I’ll go ahead and close this thread for now. If you have any further questions, please don’t hesitate to open a new one.

Thanks!

[Josh]

Hey Kate,

Thanks for reaching out to us!

It looks like you’ll need to upgrade to the latest version of Event Tickets Plus (version 4.1.2). This should allow you to see an additional checkbox there at the bottom of the ticket to add your additional fields for the tickets.

Let me know if this helps.

Thanks!

[Josh]

Hey Daniel,

Thanks for reaching out to us!

The attendee information should show on both new and existing tickets. As an initial step, can you check the edit screen on the older event and click to edit the existing ticket and verify that the additional information fields are showing on the ticket?

Thanks!

[Josh]

Hey Debra,

Thanks for reaching out to us!

This would be the right space to be looking to modify the output of the events within the list view. Personally, I would probably pursue creating a custom view for outputting the events in this way. This would give you a little more control from the start with how you wanted to pull and display the events rather than having to filter the default loop for the archive view there.

Let me know if this helps.

Thanks!

[Josh]

Hey Tamara,

Thanks for reaching out to us!

I took a look at your site and was able to see the issue you’re describing. As an initial step here, can you try following the Testing for Conflicts procedures to see if there is a conflict with an existing plugin or theme on the site? This will help us narrow in on the potential issue here.

Let me know what you find.

Thanks!

[Josh]

Hey,

Thanks for reaching out and thanks for providing the steps to reproduce as well as your system information!

I followed the steps you describe here using the same event I created for your previous thread as well as with a new event and wasn’t able to recreate.

As additional tests here, could you try changing your date format and trying again? If that changes anything it’ll help us narrow in on if this is a potential bug here.

Thanks!

[Josh]

Hey,

Thanks for reaching out to us!

This feature is currently available with EDD. I did a quick test on my local install with the latest versions of the plugin and was able to verify that multiple additional field blocks showed based on the number of tickets I had selected to purchase.

As an initial step here, have you tried following our Testing for Conflicts procedures to ensure there isn’t a conflict here with another plugin or an existing theme?

Let me know if this reveals anything here.

Thanks!

[Josh]

Hey Tac,

Thanks for providing this log! I’ll follow this up with one of our developers.

Thanks!

[Josh]

Hey Greg,

Thanks for reaching out to us! Also, thanks for providing the screenshot with the appropriate settings.

I’ve tested this on my local install and was able to get the exclusion rules to work as expected using the settings you’ve provided.

When this isn’t working for you, is it ignoring the exclusions completely or is one working and not the other? Additionally, are you updated to the latest version of the plugin and tried following the Testing for Conflicts procedures?

Let me know if this reveals anything.

Thanks!

 

[Josh]

Hey Thierry,

Thanks for reaching out to us!

Unfortunately that isn’t the way that option is designed to function. The events will display in normal WordPress loops for the home page when that option is selected.

There are two options here though. The recommended option would be to filter the module that DIVI uses and have it include posts of the “tribe_events” type. This will prevent duplicate content from being shown on your site.

The other would be to utilize the “wp_insert_post()” function and have it fire on tribe events save. You could grab the necessary information and have the post created that way.

I’m sorry I wasn’t able to give you a direct answer here but hopefully this helps to get you pointed in the right direction.

Thanks!

[Author]

Posts