in reply to Automating backup with WWW::Scripter

hit the page manually with a browser, view source, search for the form and verify that the field names you are using match the form's.

  • Comment on Re: Automating backup with WWW::Scripter

Replies are listed 'Best First'.
Re^2: Automating backup with WWW::Scripter
by bachoA4o (Sexton) on Apr 16, 2019 at 10:37 UTC
    I've already checked that . Here is sample of the HTML
    <ul> <li id="unLi" class="unLi"><input class="text" id="userName" type="tex +t" maxlength="15" /></li> <li class="blank"></li> <li id="pwLi" class="pwLi"><input class="text" id="pcPassword" type="p +assword" maxlength="15"/></li> </ul>
    I think that the parameters are passed to JavaScript function and I'm not passing them properly because the script pass them to the html form and I'm not sure if it passes them to the function as well
    unction CheckUserPswInvalid() { var userName = $("userName"); var pcPassword = $("pcPassword"); if(!CheckUserPswChars(userName.value)) { userName.select(); userName.focus(); return false; } if(!CheckUserPswChars(pcPassword.value)) { pcPassword.select(); pcPassword.focus(); return false; } return true; }

      Before you proceed it's worth also checking the form name.

      Maybe all you want is to POST a form and get a cookie back?

      I can't help with WWW::Scripter. But here is an idea about debugging: save html and all javascript dependencies locally, modify with alert() and point Scripter to these files to verify that the javascript plugin at least works.