!URLCURRENT bug

Support for iMacros. The iMacros software is the unique solution for automating every activity inside a web browser, for data extraction and web testing.
Forum rules
iMacros EOL - Attention!

The renewal maintenance has officially ended for Progress iMacros effective November 20, 2023 and all versions of iMacros are now considered EOL (End-of-Life). The iMacros products will no longer be supported by Progress (aside from customer license issues), and these forums will also no longer be moderated from the Progress side.

Thank you again for your business and support.

Sincerely,
The Progress Team

Before asking a question or reporting an issue:
1. Please review the list of FAQ's.
2. Use the search box (at the top of each forum page) to see if a similar problem or question has already been addressed.
3. Try searching the iMacros Wiki - it contains the complete iMacros reference as well as plenty of samples and tutorials.
4. We can respond much faster to your posts if you include the following information: CLICK HERE FOR IMPORTANT INFORMATION TO INCLUDE IN YOUR POST
Post Reply
tunaSalad
Posts: 26
Joined: Mon Jul 07, 2008 4:24 pm

!URLCURRENT bug

Post by tunaSalad » Tue Apr 28, 2009 11:22 am

Hi iMacros team,

I'm using the contents of !URLCURRENT as part of the filename for my screenshots.

For instance:

URL GOTO=http://foo.bar.com
SAVEAS TYPE=PNG FOLDER=* FILE=Screenshot_{{!URLCURRENT}}

This worked fine with the Firefox add-on and the saved file has a name like: Screenshot_http_foo.bar.com

As you can see, : and // are replaced by an underscore, which is fine.

However I was expecting the same behavior in IE7 plug in or iMacros Browser...

If I run:

URL GOTO=http://foo.bar.com
SAVEAS TYPE=BMP FOLDER=* FILE=Screenshot_{{!URLCURRENT}}

on IE the script just gets stuck in the SAVEAS line.

on iMacros browser I get a message dialog stating that an error occurred saving the file named "Screenshot_http://foo.bar.com"

Looks like the : or // is not being replaced by an underscore?? Could that be the cause why it's failing for both the IE plug-in and the iMacros browser???

I'm using the latest versions to date for all 3 products:

FF3: 6.2.1.4
IE7, iMacros Browser: 6.50 build 101

Thanks in advance.
Post Reply