Form URL verification not working

[RodrigoDC]

Hello,

I'm a long-term user of FT 1.5.1, s I decided to give 2.0.1 a try, but with very little success.

I have successfully installed it on my server. However, when I create a new form and I try to verify the URL as well as the re-direct URL, I get the following error message:

Not Acceptable

An appropriate representation of the requested resource /formtools/admin/verify_url.php could not be found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

You would think that I have not created the form, which of course I have. All I'm doing is copying and pasting the URL from the online form and redirect page. The problem is that the URL of the pop-up verification page is incorrect, notice the ;ack on the colon (

Code:

http://mydomain.ws/formtools/admin/verify_url.php?form_page=1&url=http%3A//mydomain.ws/productos/form.html

See that "%3A"? I cannot figure why this is appearing, rendering the verification impossible. I realize I can skip this step, but whenever I try to smart fill any fields, FT tells me that

Sorry, we couldn't find a form field with that name on the page specified.

Which I assume is related to the above.

Any help would be appreciated.

Thanks,
Rodrigo

[lsendoya]

I had the same issue, but was gone since I updated to 2.0.3 beta. Hope it will be the same for you, Rodrigo.

[Ben]

Hey guys,

Interesting one. It's odd that it was fixed by upgrading - I actually didn't make any update that that code (that I can recall), so it may have been something that changed in your environment, Luis.

A few questions:
- So this occurs on step 2 of the Add Form pages? Does it happen for the "Verify URL" buttons on both the Form URLs and Redirect URL fields?
- do you type in the URL or copy and paste it in? What OS and browser are you using?

If you're copying and pasting in the URL could you try copying & pasting it in, then delete the colon and type it in on your keyboard? I'm just wondering if maybe the colon is being converted somewhere along the line. This would at least eliminate that as a possibility.

The code does look okay, I must say - but it's very possible I missed something!

Let me know -

Ben