Jump to content
UBot Underground

Luke

Fellow UBotter
  • Content Count

    396
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by Luke

  1. Exactly what are you putting that sequence after? Every Nav? Form Submissions? Anything else? I'm trying it both ways, same problem. This reminds me of the early days of SENuke... There was a time before they multi-threaded too, and as they grew it became more necessary to use multiple threads. Of course they called it a "feature," but you may be on to something... Perhaps the nature of working with this medium requires lots of threading... I'd love to hear Seth's take on this. Your seomated site looks great! I wish you luck with your launch. If you haven't already studied Launch proc
  2. I've had similar issues, not that one exactly. Let me ask you these first: 1. At the start of those individual subs to go to each social site, do you use a NAV command and the whole path to get there each time? 2. Are you using a single or shared variable repeatedly for the different sites that may be not passed to your next subs' Nav? 3. Is there adequate Error-checking at the end of each of those individual subs to make sure it can't leave any sub until completed successfully? 4. Does the logic that decides which sub to go into next reside OUTSIDE the subs themselves?
  3. Arrrggh... You're scaring me, Abs, I haven't even tried a 'wait for' directly after a 'wait finish' yet... Was going to try that today. Sounds like you're ahead of me on this one... Are you also having the problem where sometimes the endusers' machine won't check boxes that your machine does? The Wordpress plugins screen is currently doing this to me. I've got a bot (taken out of my big bot to run stand-alone) that goes to the WP plugin page, checks every checkbox on the page, enables them all, and then picks six plugins specifically by attribute to disable. Compiled Bots can do the fir
  4. Luke

    Drag + Drop

    Hi Buddy, Well right now I'm trying to figure out how to use the Live Headers firefox plugin to request changes through uBot instead of directly speaking to the page itself like we were taught to do. My overall goal? Let's see... In wordpress, on the widgets.php page where you normally drag & drop ajax widgets around I've set my bot to simply change the text in all of my widgets to what I want them to be, click the checkboxes, and then the 'save widget' buttons. And of course you can't "Drag" anything through ubot, so I was pausing the script and letting humans drag at that point
  5. Luke

    Drag + Drop

    This tool appears to have Sooooooooooooooo much promise for uBot but is way out of my immediate realm of knowledge. I'm just trying to CONFIGURE the widgets in wordpress, much less move them, so I found this thread and instantly downloaded this program. I'm AMAZED at how much 1 page on the web can communicate back and forth with my browser. I mean WOW. That's a lotta chatter. Anyway, I experimented and found a POST request under the Generation tab that appears to be sending all the information I want sent... But I can't NAV to it: Can someone tell me what I'm doing wrong? Do I need to
  6. Yes, but I need to install the Dev suite on a second PC now to test what the heck is going wrong over there with the compiled bots I'm running just fine here. I've now got three completely separate bots that work great at my dev station and fail miserably on a laptop in the next room. I've given them all more wait finishes and delays, no matter what, things just aren't working on the other PC even though they never fail on mine. It's gotten to the point, in fact, that I've DE-AUTOMATED parts of my process so that things get done. Bots have to stop and have human intervention for three or
  7. Does this work better than NAVing away and then back again? So far this hasn't worked for me at all, it just freezes up the bot. (Both with and without the word true inbetween the ().
  8. Yeah, I knew this would be an impossible to replicate problem simply because I can't replicate it myself on my own machine. That really leaves the target machine as the culprit... It's got better hardware than my machine so I'm going to focus looking in the area of Javascript settings and versions and the like... Something related to IE and the overall software environment. Of the top of your head, do you know what software setting or version would have to be lacking in order for Compiled uBots to not be able to check boxes anymore? (But of course still run the overall bot completely thr
  9. -But not so easy licensing. I'd actually be interested in finding a good deal on virtualization to run bots from... Imagine having 100 Cloud-based "PCs" all with their own IP addresses running bots for you 24/7... Anyway, I'm finding this to be a real hard problem to get around. The problem I see appears to be a timing problem, but I can't tell for sure exactly. So I've loaded up tons and tons of 'wait fors,' 'wait finishes,' and 10-60 second delays throughout and still, the problem never occurs on my Dev PC, but always happens on the Lenovo. If UBot offered a 2nd license I'd insta
  10. I always try to use a wait for whenever it's possible... Sometimes the exact same page is loading though so its' not, and sometimes a page isn't even loading, I'm just trying to make something on the page finish like a menu retract or something. In those times I've tried delays and like webautomationlab says, wait-finish-then-delay-2s. I'm up against one now that none of these are working on. Everything I do allows it to work on my Dev machine, but none of those bots (compiled) work on the afore-mentioned lenovo. Now I'm wondering if the javascript refresh could help this... I assume t
  11. Does anyone here have experience making bots that are intended to work well across many different computers? I just last night for the first time tried to load my biggest bot (Compiled) on a couple of different computers to use away from this PC I've got uBot Dev on. The results: An Acer netbook with an Atom chip (wimpy wimpy) Fizzled... It couldn't get 20 seconds in. I think the chip fried. A new Lenovo laptop with great specs handled it fast... Er, too fast, and seemed to wait only 2 seconds every time I put in a 5 second delay! That resulted in many occurrences where the current
  12. Very nice! It can really give your endusers an idea what's happening and what the bot is 'thinking' at any given moment. I love it. Will use soon! Luke
  13. No problem, I'm sure you know where it can help the most people. When you get around to filming tuts I think this is a subject that can use some deep exploration. Cheers, Luke
  14. A big thank you to Meter, Andy, and of course Alex, and all else who helped me whoop this one... I've got it now and I've even created the following thread for others to avoid the same fate as me: /topic/3918-how-to-error-check-each-sub-properly/ BTW, this is a HUGELY important part of making bots... And I guess all programming in any language... There really should have been more docs about this as it appears to be pretty straightforward once you know how to do it. Thanks again, Luke
  15. What a coincidence... I just placed a post about exactly how to do this bug-free: /topic/3918-how-to-error-check-each-sub-properly/ Cheers! Luke
  16. After much time asking others here how to make more stable and trustworthy code, I've finally figured out the formula to make exactly that... And I'm no programmer, so I thought I'd put this chart together for other newbs/non-programmers here on exactly how to properly code parts of your bot so that every part of your bot fires off correctly and everything actually gets done. The secret is to split up every chunk of functionality into its' own sub first, and then code the following in each: If you don't use the optional node there, it will still keep looping until the job is done in the
  17. Awesome... Just the kind of tip I was fishing for here today. I knew talking to programmers would help me learn to... Um, program. I had used While before but on a much smaller scale... Didn't know it was intended for whole chunks of the bot! Ok, just so I completely understand the instruction, I've drawn one last piccy of the flow: Does this about sum it up? Anything I left out? Thanks! Luke
  18. How about a sub calling itself if it keeps failing for a long time? Example: a sub to upload a theme has a checker at the end that calls the whole Sub again if it fails. (With the Run Sub inside of the sub its' running.) Thanks for looking at it. It looks more complicated than it is. Assume first that I have a string of Run-Subs at the top of my bot, and the subs below are called in the same order for simplicity. Only rarely is a sub called from inside another sub. Then assume for every chunk of functionality, which we can simply call a Sub, I am trying to do this: 1) Check t
  19. I guess I can't escape that fact that to run a Big bot, I absolutely require each functionality to : 1) Check to see if it has been done yet. 2) Do it. (If 1 = False) 3) Check to see if it was done correctly. (If not, goto 2) It seems to me that Big Bots require these three steps to be programmed for each Sub inside of it that represents a single functionality. (Example: A theme uploader sub.) Before yesterday I had only been doing #2, and at the end of it I made it wait for a "update successful" message on the page before going to the next chunk of functionality. Now I see I ne
  20. Umm, this is already FAR past simple for me. I guess any error checking would have to be. In fact, if I wasn't using paper or notepad plus an excel spreadsheet all to document this stuff as I went along I would have returned uBot months ago! My problem with testing big bots is that I only have a few hundred domains to use them on in total... So basically as I build the bot I use a couple of domains up, and then I test again to find big error #1, which I solve and test with another, then test again to find error #2, then solve it to test with another, and so on and so on until I run out of
  21. Oh my. So the trick here is to break it up s simple as possible and use lots and lots of subs, meanwhile trying hard not to let subs be inside subs too much or allow a sub to loop back on itself infinitely? It's getting too much in the hardcore C++ Guru mode for me here... I wish there was just a rule sheet of exactly what NOT to do, such as "make a Run-Sub call the Sub it is in" and other potential stuff like that. In fact, it would be awesome if all of these possible stack overflow actions could be detected by uBot itself and not allowed at the time you attempt them. So, meter, what d
  22. Thanks for speaking up, Buddy. Sounds like you may have the overall answer I'm seeking here... I've taken some HTML and just a tad of Visual Basic (v3, in 1993) but I've never had the honor of taking any course that teaches the fundamentals of modular programming, and if that is what it sounds like, then it's what I'm desperately lacking here. Could you please look at the image of Post #4 of this thread and let me know if its' feasible, too much, too little, or basically too nutty of a plan for any reason? Thanks in advance, Luke
  23. Now I've got to worry about stack overflows too? That tears it! Arrrrrggggh. I've come to the conclusion that big bots simply can't be made with uBot yet. It's just still too lightweight. My 3 MB bot carried about 50 variables (Most of which it scraped from other websites online) and configured whole, complete wordpress builds from install to driving traffic. It was far bigger than your average uBot that people build here, just over 3 MB in total and over 5 after compiling. (As of ubot version 3.31) The structure inside was about 20 main subs and about half of those subs had multiple su
  24. It's very pretty Frank, but how can its' framework help us? It doesn't even look like we can set it going on a dedicate PC overnight or anything... It's just an account creator & submitter, as far as I can tell. (And you gotta make the content to submit all by your lonesome.) Honestly, I can't find an improvement in it other than the speed at which you can create the individual content submitters.
×
×
  • Create New...