Skip to main content
Bob_Elmore
Bob_Elmore
Known Participant
January 25, 2017
Answered

Open URL not working correctly

  • January 25, 2017
  • 2 replies
  • 5248 views

I am building an exam in Captivate 9, and on certain screens I need the learner to view an image.  Since my options are limited, I am using a shape with the "Open URL or file" option.

This works fine when the URL contains no spaces, but when the URL has spaces Captivate inserts additional text into the URL, and then it does not work.

For example, I enter this URL in Captivate,

and Captivate changes it to this incorrect URL at runtime,

Note that it changes the %20 to %2520, which of course does not work.

Has anyone else run into this?  Adobe, is there a reason for this?

Obviously the easy solution would be to remove the spaces, but I don't have access to this website.

Thanks.

    This topic has been closed for replies.
    Correct answer RodWard

    This is default behaviour due to the fact that it's a rule of the internet that there should be no spaces in HTTP web URLs.  Having spaces in the links would cause those links to break when users try to browse content on the web because web browsers are programmed to assume that the space means the end of a link. 

    It's quite common for computer users to be confused about this behaviour because the same does not happen when dealing with links on a local networked LAN or for links to files on your own computer hard drive.  In a non-HTTP environment, such as a LAN network, spaces in links don't stop them from working.

    I would suggest that you ensure any files you intend to link to use underscore characters (_) instead of spaces.  Then you won't find Captivate trying to make them web-compliant by adding these extra characters.

    A better alternative would be to avoid trying to use Open URL or File actions at all inside a quiz but instead add Smart Shape Buttons to those quiz questions where you need to have an image appear and use Advanced Actions and Variables to toggle the visibility of the images by clicking on the button.

    2 replies

    Jefferbob12055564
    Jefferbob12055564
    Inspiring
    January 26, 2017

    Enter the URL into Captivate **with** spaces instead of the %20 encodings. Captivate will do the encoding. As you have it now, Captivate is encoding the % to be %25, then adding the 20.

    Bob_Elmore
    Bob_ElmoreAuthor
    Known Participant
    January 26, 2017

    OK, thanks.  I suppose that makes sense, from Adobe's perspective. Too bad Adobe doesn't recognize the %20 as the space inserted on web pages.

    Though, as Rod pointed out, best to avoid the spaces if you can, but we don't always have access to edit the web pages we are referencing.

    RodWard
    Community Expert
    RodWardCommunity ExpertCorrect answer
    Community Expert
    January 26, 2017

    This is default behaviour due to the fact that it's a rule of the internet that there should be no spaces in HTTP web URLs.  Having spaces in the links would cause those links to break when users try to browse content on the web because web browsers are programmed to assume that the space means the end of a link. 

    It's quite common for computer users to be confused about this behaviour because the same does not happen when dealing with links on a local networked LAN or for links to files on your own computer hard drive.  In a non-HTTP environment, such as a LAN network, spaces in links don't stop them from working.

    I would suggest that you ensure any files you intend to link to use underscore characters (_) instead of spaces.  Then you won't find Captivate trying to make them web-compliant by adding these extra characters.

    A better alternative would be to avoid trying to use Open URL or File actions at all inside a quiz but instead add Smart Shape Buttons to those quiz questions where you need to have an image appear and use Advanced Actions and Variables to toggle the visibility of the images by clicking on the button.

    Bob_Elmore
    Bob_ElmoreAuthor
    Known Participant
    January 26, 2017

    Thanks Rod.  I will look into your suggestion.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices