Forum Replies Created
-
Posts
-
I can confirm that when going previous from the upcoming events view it goes to start of the previous stream((oldest date) instead of the ones just previous to the first most current event.
Access Token Info
App ID 951127374927467 : eastcountyrocks
User ID
10204206823559664 : Doug Knowles
User last installed this app via API v2.x
Issued Unknown
Expires 1449784800 (in about an hour)
Valid True
Origin Unknown
Scopes user_location, user_likes, user_managed_groups, user_events, user_photos, user_friends, user_about_me, user_status, user_tagged_places, user_posts, rsvp_event, email, ads_read, manage_pages, publish_pages, publish_actions, read_custom_friendlists, public_profilethis is what i get all three versions
{
“place”: {
“name”: “The Wrangler Bar”,
“location”: {
“city”: “Elk Grove”,
“country”: “United States”,
“latitude”: 38.4327698,
“longitude”: -121.298111,
“state”: “CA”,
“zip”: “95624”
},
“id”: “109767070727”
},
“start_time”: “2015-11-20T21:30:00-0800”,
“id”: “1013737185323224”
}Ok my app is built on 2.3
App restrictions.
No – contains alcahol
Yes – Social Discovery
Anyone 13+ – age restriction
No – Country RistrictionClient OAuth settings
Yes – Client OAuth Login
Yes – Web Oath Login
Everything else noIf you request just the event’s Id, it returns the whole event including the fields that can’t be return directly due to oauthexception.
It displays them using the place structure in all versions as well as location and venue at the event level are deprecated in 2.5
I can access using my app token on 2.3,2.4 and 2.5 using
10137371853232247?fields=place{name,location{city,country,latitude,longitude,state,zip}}
Geoff, thank you for taking the time to respond. Your answers were reassuring and I am feeling a bit better.
You addressed the duplicate event on auto import, and I appreciate that since based on the previous reply I turned it back on and was able to turn it off before my database started overflowing again with duplicate events.
You did not address the missing Venue issue when importing an event that includes an age restricted venue. As I said before, the plugin was changed to retrieve the venue data object for importing. Previously as well as still, the venue data is also available in the actual event object regardless of any restrictions preventing access to the venue object directly and was previously imported from there. I was told that a future release would capture the venue object error and load whatever venue data was in the event object.
This is still not happening and it is also effecting my ability to use the plugin as it was when I licensed it. It causes me and others to have to manually intervene as well as manually import and as such deleting any cost savings that were available through automation.
I believe that you have a superior product still and it is priced accordingly compared to competitive products, but I am disappointed that it is taking so long to address these issues from September and we are now almost half way through December.
Thank you for your time and help.
I noticed you mentioned Venues not being accessible because of age restrictions. That is a limitation of the Facebook Graph API and we are not able to get around that. Facebook does not allow us to get restricted information through their API. So there is nothing we can do about that as that comes from Facebook.
The functionality was lost when your plugin was updated to get the venue object separate from the event object in hand which already contains the venue data within it. I was told that instead of erring on the venue object that you were going to use the venue data in that is already in the event object. This was to be fixed in a future release.
As for the duplicates we believe we found that error and fixed in 4.0 are you still having issues with it in 4.0?
The thread from October below is still open and I have not seen a post or change log that would tell me that it has been corrected in v4.0. Therefore I have not tested it to validate. In fact in that thread at some point it was stated that it would not likely be fixed until after 4.0 was rolled out because everyone was busy working on the roll out.
I am asking for contact because, I am a business as well and if I am going to continue to be your customer I need assurance that issues with this plugin are as important as the others and that you intend to keep updating it.
Correct… Something about the processing or setup of the custom post type tribe_event is not allowing the tool to work the same as the default post type. [email protected] Has offered to explain anything that you have questions about the plugin and how it works.
Thanks Nico for your help.
Brian, the contact form allows for only two types of contact and neither of them are applicable.
Please, again, would someone from The Facebook import plugin development team and or sales contact me directly or allow me to contact them. There are issues with the product that are effecting its value to me compared to what it’s value was to me when I first licensed it.
Unfortunately, those same issues as I stated before, do not support your statement about advanced warning and a need to only react when future changes to the graph API are announced.
No longer getting the error message
https://www.dropbox.com/s/xsoidznzm7lr94s/File%20Dec%2007%2C%2010%2027%2031%20AM.jpeg?dl=0
Struggling to set up a test site. However, I turned on WP-DEBUG and got an additional message. see below. Let me Know if that helps.
Notice: Tribe__Events__Main::getOption is deprecated since version 4.0! Use Tribe__Settings_Manager::get_option instead. in /srv/eastcountyinfo/wp-includes/functions.php on line 3406 Warning: Illegal string offset 'facebook' in /srv/eastcountyinfo/wp-content/plugins/the-events-calendar/src/Tribe/Importer/Options.php on line 100As I mentioned in my previous reply, I do not have enough licensing to test on another site… I would have to move my licensing from production to the test site, which would effectively take my production site out of service.
