accounts info update in the "accounts view"

Support / help / discussion forum for twitter bot
rt2
Posts: 132
Joined: Thu Nov 05, 2015 3:05 am

accounts info update in the "accounts view"

Post by rt2 »

Hi Martin

using 1.373

the accounts block date is always showing year 2116 (2116-11-21 2100)

also, the accounts fields (last login, failed last login, suspended) are not updated after successful auth or after removing the block either by right click then remove blocks, or inside the account then show optional advanced

if I remove the block it still says blocked and show as the above date.

Regards.
support@rootjazz
Posts: 2317
Joined: Tue Feb 02, 2016 1:58 pm

Re: accounts info update in the "accounts view"

Post by support@rootjazz »

rt2 wrote: Tue Nov 28, 2017 5:30 am Hi Martin

using 1.373

the accounts block date is always showing year 2116 (2116-11-21 2100)

also, the accounts fields (last login, failed last login, suspended) are not updated after successful auth or after removing the block either by right click then remove blocks, or inside the account then show optional advanced

if I remove the block it still says blocked and show as the above date.

Regards.
I have checked it and it is working fine.
Did you try restarting twitterdub after block removal and successful auth?
rt2
Posts: 132
Joined: Thu Nov 05, 2015 3:05 am

Re: accounts info update in the "accounts view"

Post by rt2 »

Hi

if I restart then I'll stop all processes and i think it will restart over again..

it should update immedietly, right?

its always happening here with all updates i installed!

Thank you
support@rootjazz
Posts: 2317
Joined: Tue Feb 02, 2016 1:58 pm

Re: accounts info update in the "accounts view"

Post by support@rootjazz »

rt2 wrote: Tue Nov 28, 2017 9:08 am Hi

if I restart then I'll stop all processes and i think it will restart over again..

it should update immedietly, right?

its always happening here with all updates i installed!

Thank you
You should always use latest version in order get latest features and bug fixed.
if I restart then I'll stop all processes and i think it will restart over again..
After restart, your processor should start from where it was stopped.
rt2
Posts: 132
Joined: Thu Nov 05, 2015 3:05 am

Re: accounts info update in the "accounts view"

Post by rt2 »

well, why do I have to restart TD to get the info updated?

wonder why its working for you as you mentioned but not with me?

hope this to be solved soon so I dont have to shutdown/restart whenever I change an account

Thank you.
rt2
Posts: 132
Joined: Thu Nov 05, 2015 3:05 am

Re: accounts info update in the "accounts view"

Post by rt2 »

support@rootjazz wrote: Tue Nov 28, 2017 10:37 am
You should always use latest version in order get latest features and bug fixed.
I'm using the latest ver (1.373) as mentioned above :)

Regards
support@rootjazz
Posts: 2317
Joined: Tue Feb 02, 2016 1:58 pm

Re: accounts info update in the "accounts view"

Post by support@rootjazz »

rt2 wrote: Tue Nov 28, 2017 1:08 pm
support@rootjazz wrote: Tue Nov 28, 2017 10:37 am
You should always use latest version in order get latest features and bug fixed.
I'm using the latest ver (1.373) as mentioned above :)

Regards
Hi,

Let me clear you something. I assumed you created 1 stats scrape routine. Account view details will change only after the scrape of details.
But i think i am confused now. Are you talking about followers / followings / likes details in accounts tab? Right?
rt2
Posts: 132
Joined: Thu Nov 05, 2015 3:05 am

Re: accounts info update in the "accounts view"

Post by rt2 »

support@rootjazz wrote: Tue Nov 28, 2017 10:37 am
Hi,

Let me clear you something. I assumed you created 1 stats scrape routine. Account view details will change only after the scrape of details.
But i think i am confused now. Are you talking about followers / followings / likes details in accounts tab? Right?
I know other field should be updated after stats scrape

I wasnt talking about the follow/unfollow/tweets column, but I meant the date of "blocked" and the "x" in the "failed last login" and "x" in the field "suspended"

these 3 are not updated immediately after removing the block and successfully authenticated

Thank you.
rt2
Posts: 132
Joined: Thu Nov 05, 2015 3:05 am

Re: accounts info update in the "accounts view"

Post by rt2 »

Hi again

I just tried one account and here is what happened:

1- the account is blocked, date (2116-11-21 2140)
2- right click and selected (bulk remove blocked accts)

the blocked date in the accounts listing wasnt removed

I double clicked the same account, then "show optional advanced", the "blocked until) field is blank!!

now, if I save with "validate on save", the date in the accounts listing disappear

I installed the 1.375 and the year is still shown 2116, that happens only in automatic block

but if I double click on the account then optional advanced then click on the blocked until and enter a date, the blocked date show the correct year (not 2116).

Regards
support@rootjazz
Posts: 2317
Joined: Tue Feb 02, 2016 1:58 pm

Re: accounts info update in the "accounts view"

Post by support@rootjazz »

rt2 wrote: Thu Nov 30, 2017 5:32 am Hi again

I just tried one account and here is what happened:

1- the account is blocked, date (2116-11-21 2140)
2- right click and selected (bulk remove blocked accts)

the blocked date in the accounts listing wasnt removed

I double clicked the same account, then "show optional advanced", the "blocked until) field is blank!!

now, if I save with "validate on save", the date in the accounts listing disappear

I installed the 1.375 and the year is still shown 2116, that happens only in automatic block

but if I double click on the account then optional advanced then click on the blocked until and enter a date, the blocked date show the correct year (not 2116).

Regards
Damn. I have reported it to martin and he will tell you what to do.

But please check using below steps


1) Check your machine date?

2) Delete the account or create new instance by going FILe > Custom DB instance > instance name > OK

Add that account on new instance and perform some action ( if everything goes well then you have a problem with that instance DB )


We are very sorry for the inconvenience as it was never happened. But we are trying to fix it.
Post Reply