Bit Che > Bugs & Feature Requests

[Old] - Bit Che 2.0 Release Candidate 4 - Build 35

<< < (40/46) > >>

chip!:

--- Quote from: Bovski on November 06, 2012, 09:58:11 am ---Did you build in the "special.exe" if not where does it go or does it need to be put into every script folder?

and do we use

--- Code: ---pwd=1
version=2
special=1

[login]
failed=Click to Login
failed2=@home/login

[home]
1=http://Webop.me
2=http://Webop.me.proxy.piratenpartij.nl

[profiles]
all=/torrents?terms=%SEARCH%&area[]=name&mode=and

[special]
page=@home/
post=@home/login
csrf_test_name

--- End code ---

--- End quote ---


Oh, I havent got to the Special Login Tool yet..

but, I think its currently set to be in %APPDIR%\scripts\special.exe

and


--- Quote ---[script]
pwd=1
version=2
special=1
--- End quote ---

no [login] or [special] for those scripts.

I think there is a good chance it will work on Build 27 but we can test and I'll update accordingly.

I'm not sure I can bake in "special.exe" since it uses special Internet Explorer references but that would be nice too.

chip!:
i just did a quick test, but looks like Special Login Tool is not working.. I will have to do more testing (and/or fix) tomorrow.

Bovski:
Just wondering if it was the @home the special tool I used worked on the script for 1.60 but not on 2.0 RC1


--- Code: ---[special]
page=@home/
post=@home/login

--- End code ---

chip!:

--- Quote from: Bovski on November 07, 2012, 03:21:51 am ---Just wondering if it was the @home the special tool I used worked on the script for 1.60 but not on 2.0 RC1


--- Code: ---[special]
page=@home/
post=@home/login

--- End code ---

--- End quote ---

when special=1 flag is set in [script], no other .INI sections are needed.  EDIT: not true, 1.0: [special] page= and 2.0 [login] login= is required.

the tool for 1.60 should "work" for 2.0 -- BUT -- how it is launched and the parameters I guess are incorrect with 2.0 RC1, so I have to take a look at it tonight. Possibly just incorporate special.exe into bit_che.exe  instead of fixing whatever problem is currently there.

also note, @home can only be used inside the script code execution [code1] since its the engine itself that interrupts and translates..    but i can make changes if we need @home used elsewhere in the script config?

chip!:
looking at this now.. looks like special.exe does require:


--- Code: ---[special]
page=the page
--- End code ---

... looking into this more.


problem is special.exe requires a bunch of dependencies and I'm not sure I can come up with work arounds in order to incorporate directly with bit_che.exe...  :-\

Navigation

[0] Message Index

[#] Next page

[*] Previous page