XenSocialize Pro [Paid] [Deleted]

When I make a post it posts to my wall and not to the page even though I have Page selected as well as the page ID. Am I doing something wrong? My username is associated with my Facebook account. Would this be the reason it's posting on the wall and not on the page?
Can you post a screenshot of your Facebook configuration page (blur out the app id and key, even better: PM me)
 
OK thanks mate. I unchecked "post to user profile" in the forum configuration and it posted directly to my site's Facebook page. Thanks for your quick help.
 
I started to get this error:

#0 /home/user/public_html/library/GFNCoders/XenSocialize/Helper/Fallback/FacebookBase.php(875): BaseFacebook->throwAPIException(Array)
#1 [internal function]: BaseFacebook->_graph('/10000453522829...', 'POST', Array)
#2 /home/user/public_html/library/GFNCoders/XenSocialize/Helper/Fallback/FacebookBase.php(649): call_user_func_array(Array, Array)
#3 /home/user/public_html/library/GFNCoders/XenSocialize/Helper/Facebook.php(45): BaseFacebook->api('/10000453522829...', 'POST', Array)
#4 /home/user/public_html/library/GFNCoders/XenSocialize/DataWriter/Extended/DiscussionThread.php(41): GFNCoders_XenSocialize_Helper_Facebook::postStatus(Array, Array)
#5 /home/user/public_html/library/XenForo/DataWriter/Discussion.php(391): GFNCoders_XenSocialize_DataWriter_Extended_DiscussionThread->_discussionPostSave(Array)
#6 /home/user/public_html/library/XenForo/DataWriter.php(1385): XenForo_DataWriter_Discussion->_postSave()
#7 /home/user/public_html/library/XenForo/ControllerPublic/Forum.php(490): XenForo_DataWriter->save()
#8 /home/user/public_html/library/TMDb/ControllerPublic/Forum.php(16): XenForo_ControllerPublic_Forum->actionAddThread()
#9 /home/user/public_html/library/Waindigo/PostAsUser/ControllerPublic/Forum.php(44): TMDb_ControllerPublic_Forum->actionAddThread()
#10 /home/user/public_html/library/Tinhte/XenTag/XenForo/ControllerPublic/Forum.php(23): Waindigo_PostAsUser_ControllerPublic_Forum->actionAddThread()
#11 /home/user/public_html/library/XenForo/FrontController.php(310): Tinhte_XenTag_XenForo_ControllerPublic_Forum->actionAddThread()
#12 /home/user/public_html/library/XenForo/FrontController.php(132): XenForo_FrontController->dispatch(Object(XenForo_RouteMatch))
#13 /home/user/public_html/index.php(13): XenForo_FrontController->run()
#14 {main}

FacebookApiException: Error validating access token: The session has been invalidated because the user has changed the password. - library/GFNCoders/XenSocialize/Helper/Fallback/FacebookBase.php:1249

When a user opens a thread it returns with a "requested thread not found" error.
 
The reason for the exception is already included:
Error validating access token: The session has been invalidated because the user has changed the password.
Try re-associating your account.

I'll work on a work-around tonight and will definitely have something by tomorrow (fixing all the available bugs)
 
another thing:
the xens.co service... is it possible that in case of the worst scenario (finger crossed) that service will be down? :( Is it possible to have the possibility to choose to using also a "robust" alternative service?
any words about this?
 
I mean to say only Facebook posting is available to me and whenever i am trying to configure twitter it is giving me below error msg.

5g9Wlx5.png
 
I mean to say only Facebook posting is available to me and whenever i am trying to configure twitter it is giving me below error msg.

5g9Wlx5.png
An error will be logged... go to AdminCP -> Tools -> Server Error Log and check if there's anything related to /GFNCoders/XenSocialize/ControllerAdmin/XenSocialize.php
I'll work on a work-around tonight and will definitely have something by tomorrow (fixing all the available bugs)
no updates :( ... Couldn't find anything for the auto posting for RSS...
 
An error will be logged... go to AdminCP -> Tools -> Server Error Log and check if there's anything related to /GFNCoders/XenSocialize/ControllerAdmin/XenSocialize.php

Yes, I am getting this error

Zend_Oauth_Exception: Could not retrieve a valid Token response from Token URL: <?xml version="1.0" encoding="UTF-8"?> <hash> <request>/oauth/request_token?oauth_consumer_key=swhMRwpfcVqnTDgwOJspQ&amp;oauth_nonce=c131bd879b02cd99928cc685dc2c5bec&amp;oauth_timestamp=1359553420&amp;oauth_signature_method=HMAC-SHA1&amp;oauth_version=1.0&amp;oauth_callback=http%3A%2F%2Fwww.indiamatic.com%2Fadmin.php%3Fxensocialize%2Ffetch%2Ftwitter-token%2Fprocess&amp;oauth_signature=fWca5EsSG2N2k0XXfPCEjRb8yLQ%3D</request> <error>Desktop applications only support the oauth_callback value 'oob'</error> </hash> - library/Zend/Oauth/Http.php:234
 
Hello, I would like to know how to be added to the profile.
Tw icons and Fb.
Since not appear.

s.webp

I would also like to know how you can remove the warning that continuing to associate a notification appears.
Thank you.

.webp
 
Have you changed the way it makes the posts? It worked fine in Version 1 and obviously there has been no update for XenForo itself to change anything.
Yeah, ver 2 is using 'postSave' instead of 'save' to fix the issue with the import... I might have to change it back since it's causing some issues... but I am not getting enough time lately... :(
Hello, I would like to know how to be added to the profile.
Tw icons and Fb.
Since not appear.

View attachment 39981
The latest version only includes the images for the pop'd up user menu...

I would also like to know how you can remove the warning that continuing to associate a notification appears.
Thank you.

View attachment 39982
This has been fixed (hopefully)... I'll be posting an update once others are fixed. But the notice should go away once you go to another page...
 
Are we tracking on the "Breaking FaceBook" API changes?

February 6, 2013

The following change will go into effect on February 6th, 2013:​
End of custom actions for content consumption
We will no longer show Custom Open Graph actions that were published simply by a user consuming content. If you own one of these actions and it was previously approved, you will have received an email from us. Developers should stop publishing these actions as doing so will return an error starting February 6th. The only actions that can be published upon a user simply consuming content are built-in actions. For more info, see this blog post.​
The following changes can be enabled/disabled using the "February 2013 Breaking Changes" migration until February 6th when it will go into effect permanently for everyone:​
Authenticated referrals going away
We will remove the Authenticated Referrals feature. You should instead use the Login Dialog.
Create_event permission required to remove attendees from event
We will require the create_event permission in order to remove attendees from an event a user admins.
Minor change to admin.getAppProperties call
When making an admin.getAppProperties call, we will now return an empty Android Key Hash field as [] instead of [""].
Canonical URLs used when fetching Open Graph objects
We will start using canonical URLs (e.g. the URL set in an og:url tag, 301/302 redirects, etc.) when fetching objects (e.g. http://graph.facebook.com?ids=http://developers.facebook.com).
Offset no longer allowed when searching posts
We will no longer allow the offset parameter to be used when searching stream posts (e.g. https://graph.facebook.com/search?q=watermelon&type=post). Please use since and until to do paging instead. For more info, check out this blog post.
Curly bracket syntax for mentioning users in notifications going away
We will no longer allow the curly bracket syntax ({USER_ID}) for mentioning users in notifications. Developers should instead use the new syntax (@[USER_ID]).
Removing ability to post to friends walls via Graph API
We will remove the ability to post to a user's friends' walls via the Graph API. Specifically, posts against [user_id]/feed where [user_id] is different from the session user, or stream.publish calls where the target_id user is different from the session user, will fail. If you want to allow people to post to their friends' timelines, invoke the feed dialog. Stories that include friends via user mentions tagging or action tagging will show up on the friend’s timeline (assuming the friend approves the tag). For more info, see this blog post.​
The following change can be enabled/disabled using the "Picture as Dictionary" migration until February 6th when it will go into effect permanently for everyone:​
Picture connection/field may return a dictionary
We will start returning a dictionary containing the fields url, height, width, and is_silhouette when accessing the /picture connection for an object and specifying a callback property, a redirect=false parameter, or getting the picture field as part of a larger JSON response.​
March 6, 2013

The following changes can be enabled/disabled using the "March 2013 Breaking Changes" migration until March 6th when they will go into effect permanently for everyone:​
No more accessing mailbox FQL tables without a user session
It will not longer be possible to access the message, thread, or mailbox_folder FQL tables without a user session.
Removing apps from /me/accounts/
We will no longer show apps under /me/accounts/ in the Graph API. You can access the list of apps a user is a developer on by hitting /me/applications/developer/.
Removing redirect to docs when hitting graph.facebook.com
We will no longer return a redirect to the Graph API docs when hitting the URL http(s)://graph.facebook.com with no path.​
April 3, 2013

The following changes can be enabled/disabled using the "April 2013 Breaking Changes" migration until April 3rd when they will go into effect permanently for everyone:​
Removing ability to POST to USER_ID/questions
As it's no longer possible for users to create questions, we will remove this functionality from the Graph API. POSTs to USER_ID/questions will fail.
Removing version property/column
We will remove the 'version' column from the 'group' FQL table and the 'group' Graph API object.​
 
Top Bottom