Users getting this error: "You cannot view posts because you do not have sufficient privilege." I am a full admin and getting these errors. Please advise. Great app!
Hi bposner, Can you please let me know the url of the post which have this error? And have you used the lastest version of iphone app & server plugin. The older version has some privilige issue in 3G network. Thanks, Yao
Thank you for your quick reply... Well the forums vary, no pattern I can tell. The server software was downloaded and installed yesterday. The app is being downloaded today.
So both already last version. If the issue continue happens, please let me know. I will come your forum to take a look.
bposner, we have registered a test account on your site - please activate it so we can try reproduce your problem. the account name is "tapatalk"
Ok, should be good to go. Haven't seen this error since this morning, but others are reporting them occasionally. Probably be hard to track down.
Hi, can you try it with wifi network see if the same issue appears? Sent from my iPod touch using Tapatalk
I haven't gotten any with 2 tests, having users test as well. Will keep you updated. Thanks for the great support
I'm still having this issue as well, I was waiting for the next official release to do any more testing since I've had this problem a lot in the past.
have yawl made this change to ur vb forums http://www.tapatalk.com/forum/showthread.php?t=130 once i did that the issue stopped for me
I have this privilege error and Im using my wireless network at home ( no IP Changes and cellular stuff). I'm using Server 0.9.11 on Vb 3.8.2 and tapatal 1.1.5 on OS 3.0! any reason why is that and any solutions?
Hi shaynab, Can you create a test account for us (send us the login info via PM) that can reproduce the issue and we will look into this accordingly. Thanks!
I'll pm the user/pass in a min. the problem I have reported wasn't there in the first use! but when i closed Tapatalk and then reopened it there it was!
Shayanb, Got your test account, thanks. Let's wait for the version 1.2 on app store I believe the newer version should solve this problem.
