@royalmice - Talked to James about this. He said, "unfortunately still working on that.. when we do testing with our own client (and not SER), it will run for days and no crashes.. we are looking into several workaround and will implement them as soon as utf8 version is live."
@shaun - Well that would still require a lot of development. The tool they have is for testing/debugging and James mentioned he's always designed it to integrate with SER from the beginning.
I may have missed this, but, in scheduled posting, "link only on last article", it's broken. I get links from multiple posts, not the last one.
Also, I have it set to create maximum posts per account: 5. This should be I can also get 1 article per account? Why not have minimum posts per account choice?
Currently getting all except FC2, "failed with display - captcha error"
@Metster - That is something I think Sven would need to look into
@kajzer - All engines are showing up on my end? Do you still have this problem?
@antonearn - Hmm, doesn't seem to be happening on my end but anything that's related to SER options is something Sven would work on, not James (SERengines).
Unfortunately, last night as I was running projects on my server we discovered some problems so James decided it was best to revert back to the previous version. Sorry guys, he's working on it.
@antonearn - He has developers already. It's just not that straight forward because it involves him and Sven having to debug things from both SER and SERengines DLL to find the problem. I doubt either one of them want new developers to have access to the source. New developers aren't going to speed things up unfortunately.
@Anth20 - Keep in mind the updated engines are the "Beta SERengines" - the other web 2.0's might eat up some captchas and don't run on the same submission engine. The documentation might be for the old web 2.0's if its the .PDF.
You don't really need to monitor them, but imo its best if you set SERengines as their own project and run the standard engines that come with SER in a diff project. This way you can fine tune things. SERengines is better set to use a captcha service while the standard engines in SER can run off CB + fallback service.
You can easily create a project and have it set for SERengines, duplicate it, switch out emails, and select the other engines you want to use. There might be other options you might want to tweak as well but it doesn't take that much time to setup 2 separate projects. You can do whatever works best for you though
@mcsappum - Can you try reinstalling the plugin? Go to: C:/Users/<current user>/App Data/Roaming GSA Search Engine Ranker/serengines and delete all the files in there ... (make sure SER is closed down before deleting the files) Then start SER and start a SERengines project and that should reinstall the plugin.
If Serengines is still in Beta, why does it not mention it anywhere on the sales page ? It only show Beta after buying and installing it.
I think James should mention this on the sales page to avoid complaints later. On the moment it still show "High PR Web 2.0 Profiles - Currently Supported: 22 (and growing fast!):" which is not what you get when buying.
Comments
Best Regards.
Also, I have it set to create maximum posts per account: 5. This should be I can also get 1 article per account?
Why not have minimum posts per account choice?
Currently getting all except FC2, "failed with display - captcha error"
First run SEREngines WITHOUT the scheduler, then stop the projects and rerun them WITH the scheduler.
Yes, it's still something Sven has to fix...
Not sure if this is what you're looking into but I get this error when running the Beta serengines: