Thanks a lot! I'll update the script so it can detect captcha on both sites and open the link on the correct site.@Johnnyrs - That worked for the alert. Will need to update the link to open job on the new worker site to type in the captcha as well, its opening the www site even though the alert popped on the worker site.
Yes the import deletes the jobs or alarms and then replaces them with the imported data only. I never thought about a sync but this could be a good future feature. It will only add new jobs from the imported file but not delete anything. Having it delete jobs that aren't in the import file could get tricky. So for now you can't do it but you can try to always export a file every time you switch computers. I'll think about how to get a sync working for the future.
I use this to detect catpchas on both.
if (document.querySelector(`img[src^="https://opfcaptcha-prod.s3.amazonaws.com/"]`))Thanks! I'll try that out. Usually I don't use querySelector because it's a bit slower but for this it probably will take the same time or faster.
Yeah, I only mentioned it because it might be faster than running 2 getclesses, but I didn't bother with a jsperf for anything.
Thank you very much. Didn't realize that was happening because I haven't worked from batch like that to test it. I have a fix for it and I will update it sometime today. Found some other bugs while I was fixing this one too.
Its working on both sites
I am getting PRE's on the www. page that I dont think I should be getting, but I cant decipher what is happening. I turned debugging on, but the console doesnt show the expected "got a PRE for a search or pantha on: " + finalUrl. They are all listed as Normal PRE's, I have even turned it down to 1 request every 1000ms and I still see them periodically. Is there any other causes for the PRE count to increase besides true PRE's?
Well I know that the worker and www site have separate PRE counts because I am using both without getting too many PRE's today. I actually have only 10 PRE's on the www site and 0 on the worker site. I do recommend not using the www site and new site at the same time on the same browser. There is a bug on mturk that will cause hits not to be submitted sometimes because of some cookie thing they set. I use regular chrome for www site and worker on chrome portable. Also remember if you are using hit finder or other scripts be sure to know what site you are using them on so you know what your timer should be to accommodate other scripts. I also don't recommend to work off the queue from the new site because not all hits work there and it doesn't advance to next hit without using a script. Also check to see if you have auto slowdown stopped. Now the script remembers what you have it set at so that could cause PRE's if you don't let it slowdown automatically again. Best way to test things is turn off all scripts and turn on 1 by 1 after a few minutes to see which one is conflicting and then decide what the timers should be at.Its working on both sites
~edit~ Rolled back to 0.4.4, and still occuring. Maybe mTurk fixed it so Worker and WWW share PRE count lol
Yeah, it seems to be a conflicting script issue. Just a matter of figuring out which one it is. I disabled all scripts except Panda Crazy, no PRE's. Re-added Queue Helper, no pre's. Will continue to add 1 at a time until I find the culprit
As for www and worker, I have them running on 2 seperate machines, so no issue with conflict there
It's recommended to run PC in a window of it's own so it won't be slowed down by browser security features. I haven't tested the disabling the background tab throttling so I have no idea if it works or they might decide to have it not work so I can't recommend it. It's easier just to pull the PC tab out into it's own window and keep it in the background under other windows so you can also see the queue watch if you have a big screen.
That does not work either. It will not stay running at all. It used to work, but now it will not, even though I have turned off tab throttling.
