[Barry]

Hi Christoph,

I’m really sorry to hear you’ve experienced difficulties.

Can you share the Facebook URLs you are importing from (by private reply if you prefer)? Do you find the imports work if you run them manually, or do they still fail?

It would be great if you could visit the Events → Help screen and enable debug-level logging, then let the importer run (or trigger it manually) and see if this captures any useful information.

Thanks!

---

Hallo Christoph,

Es tut mir wirklich leid, dass du Schwierigkeiten hast.

Können Sie die Facebook-URLs, die Sie importieren (von privater Antwort, wenn Sie bevorzugen)? Finden Sie die Importe arbeiten, wenn Sie Sie manuell ausführen oder Scheitern Sie noch?

Es würdet sein groß falls Sie können besuchen die Ereignisse → abhelfen Schirm und aktivieren Debug Ebene Protokollierung, derzeitig lassen die Einfuhr verkehren (oder auch auslösen es manuell) und übersehen falls dieses fängt beliebig zweckdienlich Aufschluß.

Dank!

[Barry]

This reply is private.

[Barry]

My pleasure 🙂

I’ll go ahead and close this topic since you marked it ‘resolved’, but of course if we can help with anything else please don’t hesitate to post a fresh topic and one of the team will be only too happy to assist.

Thanks!

[Barry]

Hi Derek,

I wanted to drop a brief update in here. Though we don’t have a fix available just yet, we’ve pinpointed what we hope is the underlying bug and are now working toward a definitive fix.

As ever, we’ll keep you posted: I’d advise also that the very next release of The Events Calendar is unlikely to contain the fix — but we’ll certainly strive to get it in place thereafter.

Thanks again for your support and patience while we looked into this.

[Barry]

Hi Kim,

I wanted to drop a brief update in here. Though we don’t have a fix available just yet, we’ve pinpointed what we hope is the underlying bug and are now working toward a definitive fix.

As ever, we’ll keep you posted: I’d advise also that the very next release of The Events Calendar is unlikely to contain the fix — but we’ll certainly strive to get it in place thereafter.

Thanks again for your support and patience while we looked into this.

[Barry]

Hi Marcus,

I wanted to drop a brief update in here. Though we don’t have a fix available just yet, we’ve pinpointed what we hope is the underlying bug and are now working toward a definitive fix.

As ever, we’ll keep you posted: I’d advise also that the very next release of The Events Calendar is unlikely to contain the fix — but we’ll certainly strive to get it in place thereafter.

Thanks again for your support and patience while we looked into this.

[Barry]

Hi Dirk,

I’m really sorry about this — but I see the same thing locally and so will file a bug report for the team to review.

In the meantime, I’ll set this topic to “Pending Fix” and of course we’ll update you as soon as a substantive update resolving this is available.

Thanks for your patience in the interim 🙂

[Barry]

Hi Jonathan,

My apologies for the delay – I should have replied yesterday to let you know we were doing further testing on this: with that said, please do be aware that we do not typically provide support over weekends (though there can be exceptions, generally we’re online in the working week during normal office hours in the continental US range of timezones).

So far, though, even after testing a range of multisite configurations (sub-domain based, sub directory based, etc) we seem unable to replicate the cited error.

Generally we wouldn’t ask this, but given the difficulties in reproducing would you be open to sharing access to your site so we can login and see the problem first hand? If you’re happy to do that, please provide credentials via private reply. If you prefer not to, that’s fine: we can look at other options such as sharing a database dump.

Thanks!

[Barry]

Do these problems only happen when you edit events? If you (temporarily) deactivate our plugins, are the problems resolved elsewhere such as when working with regular WordPress posts and pages?

This can indicate an overloaded, under-powered, or misconfigured server.

This advice could be accurate: perhaps the hosting package you are currently using is underpowered or there is a more suitable alternative that your host can provide?

[Barry]

Hi Jovany,

Thanks for considering our plugins and apologies for the late response!

What you see at wpshindig.com is indeed a basic WordPress site with a number of our plugins installed, including:

• The Events Calendar
• Filter Bar

Event Tickets is also running there, but if it is the calendar itself you are interested in then all you need is the first of those plugins – The Events Calendar – which is also free 🙂

Our other plugins add additional capabilities and features on top of this.

Let me know if you have any further questions!

[Barry]

I’m sorry to hear that, Leslie. To better help you I’d love to gather some more information:

• Approximately how many events do you currently have in total?
• How many of those have expired/are in the past (and might you consider cleaning them up)?
• Approximately how many blog posts/pages do you currently have in total?
• Can you tell me who your web host is and what sort of hosting plan you are currently using?

It certainly seems odd that when editing events you are losing the connection. Is it possible that is a local internet connectivity problem? If not, have you approached your web host to try and determine what’s going wrong from their perspective?

Thanks!

[Barry]

Thanks for the update, Angie: for one or two of the recently failed Facebook imports can you share the corresponding Facebook URL to help us do a spot of local testing?

Thanks!

[Barry]

You’re welcome 🙂

[Barry]

Sorry if I’m missing some via the list of Facebook URLs you supplied earlier – but could you share further URLs for one or two of the failed imports shared in your more recent screenshots?

[Barry]

Hi Gordon,

It’s hard to know precisely what’s gone wrong here without knowing what exactly you cleaned up (and how you did it).

My guess though is that the sales count you are seeing relates to a record of the sales made per product, maintained by WooCommerce.

This is stored as a piece of post meta data named “_total_sales” and you would need to remove/zero those out also.

Alternatively: if you’re seeking a completely clean start, why not setup some brand new ticket products and delete the old ones – might that work here?

[Author]

Posts