(2015-02-09, 00:08)shaktoo Wrote: even if one is pulling directly from GIT ?I have a script that is pulling from dev branch ..
I see 4 hours ago you have reverted the version number ?
I take this chance to thank you for putting up with all us ignoramuses . Your work is hugely appreciated.
@
shaktoo
i believe u will find that his latest commit corrected it, ill update with links but it is working for me now after experiencing script errors on startup
if i understand correctly and it is in fact the same issue i can offer the following fyi, an issue was opened for this problem, it was closed after the problem was resolved via last commit, a link to the now closed issue follows:
https://github.com/Razzeee/script.trakt/issues/88
as i understand it the commit below corrected the problem:
https://github.com/Razzeee/script.trakt/...115c8fcd17
so if u download and install latest -dev it may no longer b an issue, it is working for me, hope thats it
(2015-02-08, 19:32)asiuhas Wrote: Yeah right, I should expect an addon to practically destroy my trakt account just because of dev branch. Right. That's not the idea someone gave when linking to the addon.
there were a couple posts or comments that prompt me to write the rest of this post, addressing the comment above first, i have submitted at least two detailed posts in this thread warning the 'average' user to stick with the last working version or avoid both until a stable version of the upgraded add-on is released, others have recommended same or similar, if u do use it b prepared for issues and dont complain when u encounter them, wouldnt count on support but he is trying to do that too, a little patience goes a long way and u should always check to see if an issue has already been opened on github, after receiving the error discussed above i spent some time making sure it wasnt a problem on my end, by the time i got to github an issue had already been created, looking thru the comments it was clear razzee was aware of it so it was just a matter of waiting for a commit to fix it, not out to offend anyone but if u arent familiar enough with github to post and check for issues there u may want to consider waiting for a beta release (at least), regardless we definitely need to be really patient and understand that every minute spent answering the same question multiple times or dealing with situations unique to one specific configuration will delay release of a stable version significantly
certainly dont want to offend but didnt think the comments were fair and feel many may still have unreasonable expectations