17.gif

Search (advanced search)
Use this Search form before posting, asking or make a new thread.
Tips: Use Quotation mark to search words (eg. "How To Make Money Online")

12-01-2013, 02:52 AM
Post: #81
RE:
(11-24-2013 01:44 AM)yjose Wrote:  i have this prb can you help me plaese

Exception: 200: Must have a valid access_token to access this endpoint Warning: usort() expects parameter 1 to be array, null given in /home/u143076967/public_html/wp-content/plugins/socialgroupinflitratorpro/class.groupsTable.php on line 193 Warning: array_slice() expects parameter 1 to be array, null given in /home/u143076967/public_html/wp-content/plugins/socialgroupinflitratorpro/class.groupsTable.php on line 212

solution reset App Secret: or your access internet time out
12-03-2013, 05:51 AM
Post: #82
RE:
Hello friends,

I'm getting a problem with this plugin.
The cron job is generating autopost.php files on my root directory, which is causing some issues on my server.
Any cron job creates a file like autopost.php.1, and today i access my FTP account and i saw i was on autopost.php.13XXX!!!!

Is this normal? i dont think so.

Any advice? Anyone with the same problem?
12-03-2013, 02:46 PM
Post: #83
RE:
thanks man .. rep added
12-26-2013, 03:53 AM (This post was last modified: 12-28-2013 04:34 AM by thealexangroup.)
Post: #84
RE: speaking of SGI errors...
in "Posting History" i am now getting this error under message status:

OAuthException: An unexpected error has occurred. Please retry your request later.

all my SGI/blog/FB settings/config running on this/other hosting sites, etc. exactly the same, running good. only diff [for this] is i have 2 SGI apps installed on this one FB acct. would having 2 SGI apps in same acct. be the problem? sounds unlikely though.

UPDATE:
tried disabling all plugins but SGI, reset app 'secret', disable/enable sgi. so it probably has something to do on FB end. don't think it is the cron. was running well 2 days ago, then added a new message set is about all i did different and error shows itself... again. this has happened on 2 diff set ups on 2 diff hosts. Sad Angry




44.gif