[Josh]

Hey Hans-Gerd,

Thanks for your patience.

I did some further testing and created an internal bug ticket for this issue. I’ve added this thread to that ticket so you’ll be notified as our team reviews the issues here and pursues a solution for this bug.

I apologize for the inconvenience that this has caused. If you have any further questions or concerns please don’t hesitate to ask.

Thanks!

[Josh]

Hey Cristina,

I did some tests but didn’t experience any of the current events associated with the page creating duplicated organizers on initial import or scheduled import.

However, I will say that this has happened in the past where the details and name for a venue will get imported several times depending on the associated event. Usually in these cases though there is something set up in the creation of the event where the venue information is slightly different when created in Facebook so it does end up getting treated as a separate venue.

In the meantime, if you delete the duplicated events do they continue to get duplicated on scheduled ( or manual) imports from the associated page?

Thanks!

[Josh]

Hey!

Just wanted to follow up here.

One of our developers reviewed this and found that this is actually associated with the default way that WooCommerce handles stock. If you would like to reduce the stock when manually adding orders, WooCommerce allows you to do so by checking the box next to the ticket selecting the “Action” dropdown (https://cloudup.com/c8ycTSzdg_e) on the list there and selecting “Reduce Line Item Stock” there.

Since this is the way that it works for all other manual orders and products, we feel that it’s best to stay in line with the way that WooCommerce handles these types of actions.

Let me know if this helps.

Thanks!

[Josh]

Hey Karly,

No problem! Looking back at your site it appears that you’ve already removed the Show Google Map and Link sections from showing on that front-end form? Let me know if I missed something though.

Thanks!

[Josh]

Hey Tom,

Thanks for following up with us.

If the issue persists with our plugins deactivated it sounds like there may be something else going on on the site. If you’re using the default theme you could try downloading the latest version again to see if there was an issue there.

Thanks!

[Josh]

Hey Hans-Gerd,

No problem. Digging through this now and there does appear to be some strange things going on here. I believe there may be a bug on our part here. Doing some further tests to verify and will follow up here shortly.

Thanks!

[Josh]

Hey Mark,

Sorry about the previous reply. Looks like some of our auto formatting got in the way there. The rest of the message was that I was unable to see anything out of the ordinary with the events. However, if you create a new “archive.php” file in your child theme and add the code from the gist above into that file it should address the issue on the tag archive pages.

Let me know if this helps.

Thanks!

[Josh]

Hey Mark,

Thanks for providing this information. I was unable to see anything out of the ordinary that would be causing this issue. I did however come up with a workaround that should work for you here. Within your child theme, create a new “archive.php” file and add this code as the file’s contents.

Let me know if this helps.

Thanks!

[Josh]

Hey Oliver,

Thanks for reaching out to us!

1. You can limit visibility of the form through some minor customizations that we can help you with here in our forums. However, the plugin that you’re suggesting may or may not work with the tickets since the tickets are set to be hidden from most of the default WooCommerce views by default.
2. The meta should persist and checkout information should say the same (part of an answer to number 4 as well) however, the information may not pass to the ticket like you expect. The information will be stored with the order but the ticket won’t store that information as part of say the attendees list.
3. This is something that we should be able to help get you pointed in the right direction with for replicating the admin loops within the front-end of the template.

We offer refunds for 30 days from the time of the original purchase. This is why we typically suggest trying out the plugin to see if it fits your needs. If not, we would be happy to refund your purchase.

Let me know if this helps.

Thanks!

[Josh]

Hey,

Thanks for reaching out to us!

You do have a couple of options, the first would be to modify the way our plugin pulls the venue. However, this would be an extensive customization that we unfortunately wouldn’t be able to guide you through in our support here.

The alternative would be to modify the post type and meta for the current events within the database to have the “tribe_venue” and modify the appropriate contact information meta to have the necessary ids as what’s used in our plugin.

Not sure if I answered your question fully but hopefully this may help in your decision.

Thanks!

[Josh]

Hey Ollie,

Thanks for reaching out to us!

I believe the quickest way to accomplish what you’re describing would be to have your client at the door generate new orders manually within the WordPress dashboard in the WooCommerce orders section. It’s a little bit quicker than having to do it all on the front-end. To see if it works for your use case, the best advice I can give would be to go ahead and give it a try. If you don’t like the process we would be happy to refund your purchase within 3o days.

Thanks!

[Josh]

Hey Karly,

Thanks for reaching out to us!

The best approach would be to hide it via CSS. You can add the following to your theme’s style.css file:

#tribe-community-events .events-community-post-content {
display:none;
}

Let me know if this helps.

Thanks!

[Josh]

Hey Donald,

Thanks for reaching out to us!

This definitely sounds like a strange issue to be having. Are you using any mobile specific plugin that changes the theme for mobile devices? Additionally, have you tried following out Testing for Conflicts procedures to ensure there isn’t a conflict occurring with another plugin?

Thanks!

[Josh]

Hey Sebastien,

Thanks for reaching out to us!

I apologize for the inconvenience you’re experiencing when using our plugin. Would you mind providing us a list of the Facebook pages that you’re attempting to import from so we can do some further testing with those pages.

Additionally, I’m not familiar with the DNS_PROBE_FINISHED_NXDOMAIN issue you describe, however this article may be helpful for that one.

Thanks!

[Josh]

Hey Kevin,

Thanks for reaching out to us!

Unfortunately this isn’t related to our plugins, however this link may help you to change the information you’re looking for.

Thanks!

[Author]

Posts