[Cyrus]

@Victor – Unfortunately this issue is not resolved. Previously events imported from a Page had their “Organizer” field set to the Facebook Event Host. Now, after the fix these events are imported with – BLANK – Organizer content.

I am seeing MANY “–Blank–” organizer values in our imported events queue now.

STEPS TO REPRODUCE:

• Create a Scheduled Import for the url https://www.facebook.com/YavapaiReentryProject/
• wait for the scheduled import to run
• view the imported events

EXPECTED RESULTS:
All imported events should reflect the the Facebook Event Host(s) as their Organizer. Review the imported event for https://www.facebook.com/events/209298732977765/?event_time_id=237707306803574.
NOTE that there are two hosts.

ACTUAL RESULTS:
The referenced event is displayed in the pending event queue with -BLANK- organizer. There is no organizer associated with the event.

ADDITIONAL INFO
I am seeing tons of events with no organizer information being imported now that we have applied this update. The problem may be related to recurring events.

[Cyrus]

@Victor I’m still unable to import events from the public Facebook Page https://facebook.com/azresist using the latest version of The Events Calendar. I receive the same error message cited in the original description on both our production and development environments.

[Cyrus]

Refer to pinned post: https://theeventscalendar.com/support/forums/topic/importing-from-facebook-please-read-this-notice/

[Cyrus]

Yes @jaimetri-be we have disconnected and reconnected our Facebook account as a troubleshooting step. We have also tried using multiple different Facebook accounts.

[Cyrus]

@Jamie – no resolution from disconnecting and reconnecting facebook accounts to the import plugin.

[Cyrus]

There is nothing in the logs.
[18-Feb-2018 01:22:07 UTC] the-events-calendar/common - Log: Initializing Tribe Events on Feb, 18th at 01:02:07 am
[18-Feb-2018 01:22:13 UTC] the-events-calendar/common - Log: Initializing Tribe Events on Feb, 18th at 01:02:13 am
[18-Feb-2018 01:22:42 UTC] the-events-calendar/common - Log: Initializing Tribe Events on Feb, 18th at 01:02:42 am
[18-Feb-2018 01:23:11 UTC] the-events-calendar/common - Log: Initializing Tribe Events on Feb, 18th at 01:02:11 am
[18-Feb-2018 01:23:54 UTC] the-events-calendar/common - Log: Initializing Tribe Events on Feb, 18th at 01:02:54 am
[18-Feb-2018 01:24:01 UTC] the-events-calendar/common - Log: Initializing Tribe Events on Feb, 18th at 01:02:01 am
[18-Feb-2018 01:24:01 UTC] the-events-calendar/common - Log: Initializing Tribe Events on Feb, 18th at 01:02:01 am
[18-Feb-2018 01:24:13 UTC] the-events-calendar/common - Log: Initializing Tribe Events on Feb, 18th at 01:02:13 am
[18-Feb-2018 01:24:14 UTC] the-events-calendar/common - Log: Initializing Tribe Events on Feb, 18th at 01:02:14 am
[18-Feb-2018 01:24:48 UTC] the-events-calendar/common - Log: Initializing Tribe Events on Feb, 18th at 01:02:48 am
[18-Feb-2018 01:24:49 UTC] the-events-calendar/common - Log: Initializing Tribe Events on Feb, 18th at 01:02:49 am
[18-Feb-2018 01:24:51 UTC] the-events-calendar/common - Log: Initializing Tribe Events on Feb, 18th at 01:02:51 am
[18-Feb-2018 01:25:06 UTC] the-events-calendar/common - Log: Initializing Tribe Events on Feb, 18th at 01:02:06 am
[18-Feb-2018 01:25:06 UTC] the-events-calendar/common - Log: Initializing Tribe Events on Feb, 18th at 01:02:06 am
There is nothing in the PHP Error logs.

Can you once more please replicate the issue and report it to your development team. Create an import for the Facebook Page: http://facebook.com/azresist. You will note that the import source cannot be successfully imported. This is a bug in the Event Aggregator Service. This is not a problem with the facebook page configuration. It is not a conflict either, the issue occurs on my development environment when there are no customizations applied or theme conflicts. I WAS able to import from this source previously and using the Xylus Import Facebook Events plugin.

Thanks again for your time Jaime

[Cyrus]

The previous logs I provided already had debug logging enabled. No relevant messages are logged.

[Cyrus]

Hi @jaimetri-be ! Any updates from the team? We have not been able to get any information about the non-descript error occurring when importing from this import source and would appreciate your continued assistance.

[Cyrus]

@Jaimetri-be it would be great if you could provide me with more details regarding the specific inquiry that you believe I should pose to my hosting provider. I’m still confused on how an issue that you can replicate can be the fault of my hosting provider. Again, this is 1 out of 751 import sources causing a failure every time we attempt to import. It just so happens that this import source is the most critical one to our organization.

The exception being generated is in Tribe code, obfuscated behind the Event Aggregator service. Can you escalate this to a developer to test this failure on the event aggregator server side?

[Cyrus]

@Sky – I appreciate the follow up. Can you confirm the behavior that Event Update Authority setting with relation to tags that have been applied to imported events? Will local changes to tags be impacted by utilizing the “Overwrite my event…” setting?

Will you be reporting the venue update issue to the Dev team for the “preserve local changes” event update authority setting?

[Cyrus]

Jaime, you said in your reply on the 24th “I tested the URL for the Facebook group’s event page and experienced the same error as you.”

If you can reproduce the error then why are you having me test for conflicts? There are no conflicts on my system if you are encountering the same failure in your test environment. I have 749 other import sources that work just fine. The problem is likely related to the sheer number of events in this Facebook Page’s Event Feed and a timeout adjustment being needed somewhere.

My status indicators are all green. You can find event logs from the EA help screen for the past 24 hours at https://azresist.org/tribe-log-2018-01-27.txt

Please advise.

[Cyrus]

This reply is private.

[Cyrus]

I do believe this has been resolved through both some fixes on the Event Aggregator servers as well as a patch. Are there still Event Aggregator import issues or has this problem been resolved? Can you close this issue if the problems have been resolved?

[Cyrus]

Jaime this will not work. Our calendar aggregates from over 1000 Facebook event sources. Blaming this on Facebook is not an adequate explanation either. We are currently using Import Facebook Events plugin by Xylus and their import plugin does not have this problem with organizers. (it has others, which is why we want to use the native Tribe extensions).

This is a bug with Event Aggregator that will prevent us from utilizing the extension. This bug will cause weeks of lost development time on our part. We have spent time implementing customization utilizing hooks provided by your plugin’s APIs. I can’t imagine that your team won’t see the necessity for an expedient fix for this issue. We literally import hundreds of events daily, we cannot do any manual categorization or modification of imported events, we don’t have the manpower!

[Cyrus]

In an effort to be as exhaustive as possible I have also downloaded and activated the Twenty Fourteen theme. This also did not resolve the issue. In an import of 25 events from facebook.com/azresist only 8 have the correct organizer associated with them.

[Author]

Posts