Dreamweaver still encodes special characters in URL - Bug?

Dreamweaver 6 is still encoding my special characters when I enter a URL through the control panel AND hit enter. When I paste the link in code view or just paste it in the control panel Link field without hitting Enter, no formatting occurs.
I have the setting under Code Rewriting in Preferences set to "Do not encode special characters", but regardless the reformatting occurs whenever I hit enter in the Link field in the Control Panel.
For example:
The link I'm pasting in is a dynamic one and is set to %%DC%%
If I just paste the link into the control panel then click elsewhere the link is set and no formatting occurs. If I paste it in, then hit Enter the URL changes to %Ü%%
Is this a bug or am I doing something incorrectly?

I just tried it and it's happening in both.
How it's occuring to me:
- Open a new or old document.
- Type in a random set of letters, highlight, then click inside in the Link field on the Control Panel
- Type %%DC%%
- Click off the random set of letters, and in code view the Link is still set to %%DC%% (so far so good)
Now if you click back onto the random letters that are now linked, you'll see that the URL in the Link field now changes to %Ü%%, but the actual link in Code View remains %%DC%%.
- Now click inside the link field in the control panel, but don't type or change the URL.
- Click somewhere else to move the cursor out of the control panel
- The link is now set to %Ü%% in both Code View and in the control panel

Similar Messages

  • 'Do not encode special characters' preference not working

    I have the preferences in Dreamweaver set to "Do not encode
    special characters in url'. However, every time I paste a url in
    the properties box, when I go to the source code, Dreamweaver has
    encoded the special characters, especially the "&". Is there
    another setting I have to change somewhere, or is there an update
    that fixes this?
    Thanks.

    "Jade73" <[email protected]> wrote in
    message
    news:fcbroh$7ih$[email protected]..
    >I have the preferences in Dreamweaver set to "Do not
    encode special
    >characters
    > in url'. However, every time I paste a url in the
    properties box, when I
    > go to
    > the source code, Dreamweaver has encoded the special
    characters,
    > especially the
    > "&". Is there another setting I have to change
    somewhere, or is there an
    > update that fixes this?
    You can find updaters for dreamweaver here
    http://www.adobe.com/support/dreamweaver/downloads_updaters.html

  • Passing values w/special characters in URL into an interactive report

    Hello,
    I have a problem and Ive been all over these forums and reading/trying everything I can to get something to work. I have a page that has a field called Name Search. The field is a TextField with autocomplete type. If I select a company name that contains special characters, like 'Blue Shield of California Life *&* Health Insurance Company', when I click go button (using a branch), it is supposed to pass this value into the URL to populate IR_COMPANY_NAME on the interactive report page to create the report filter. However, when it goes to the IR page, it actually filters on 'Blue Shield of California Life *& amp;* Health Insurance Company' with 'amp;' instead of & and doesnt find any matches. In the page source it is actually 'value="Blue Shield of California Life *& amp; amp ;* Health Insurance Company." Here is the URL that it produces:
    http://webtest2:7775/apex/f?p=102:IRCompanyList:995769774353901::NO:5,RIR:IR_COMPANY_NAME,P5_COMPANY_NAME:Blue%20Shield%20of%20California%20Life%20%26amp%3B%20Health%20Insurance%20Company,Blue%20Shield%20of%20California%20Life%20%26amp%3B%20Health%20Insurance%20Company
    The interesting thing is that I have another page that has a clasic report that lists all compnaies by name and the company_name is a link that passes the company name into the exact same IR and it works fine. In the page source it is value="Blue Shield of California Life *&amp;* Health Insurance Company" Here is the URL that this page produces:
    http://webtest2:7775/apex/f?p=102:5:995769774353901::NO:4,RIR:IR_COMPANY_NAME,P5_COMPANY_NAME:Blue%20Shield%20of%20California%20Life%20%26%20Health%20Insurance%20Company,Blue%20Shield%20of%20California%20Life%20%26%20Health%20Insurance%20Company
    I have modified every field involved changing between encoding, no encoding, changing display types (Standard Report Column, Remove HTML and escape special characters, etc). I have also attempted to encode the value myself prior to sending it to the next page. I have tried variations of the htf.escape_sc etc. I have also tried adding \&P2_COMPANY_NAME.\. I have also tried adding pl/sql to create a collection to store the values and then pl/sql to fill the values on the report page. It gives me the success message I setup, but it never actually fills the value.
    I am also having problems with another field that has a comma in it. I will wait to address that one to see if I can fix this first with hopes that it can be resolved by whatever I do to fix this issue.
    Any suggestions? I appreciate any feedback!
    Jen
    Edited by: J-Lig on Jul 13, 2012 10:20 AM
    Edited by: J-Lig on Jul 13, 2012 10:21 AM

    Thank you for your feedback!
    Yes, I forgot to mention that. It does come from a table, but company_name is not unique in that table. Meaning, it wouldnt know which ID to pass. Perhaps I should seperate the name out into another table and then I could pass the id. I was just hoping to get this to work programatically since the links from classic reports actually work correctly. I am starting to think this is a bug. This issue appears to have been addressed to make the links from reports pass the & correctly, but not in the branching?
    I have attempted to replace and then re-replace but I couldnt get it to work with IR_ fields as the filter fields are generated by the Interactive Report region. Do you have any insight working with those? Are there any tricks to it that I might be missing?

  • Escape special characters in url for redirection

    In my web page, I want all the characters of the URL to be lower case. For that I created the following method:
    private bool UrlFormatoCorrecto(string url)
    bool formatoCorrecto = true;
    bool upperCa = url.Any(c => char.IsUpper(c));
    if (url.Any(c => char.IsUpper(c)))
    formatoCorrecto = false;
    if (url.Contains(" ") || url.Contains("+"))
    formatoCorrecto = false;
    return formatoCorrecto;
    This works like a charm until a special character appears. The url that I get then will be the following:
    http://localhost/web/coches/proven%C3%A7a-aribau,-08036-barcelona,-barcelona
    So I have upper case characters. When I redirect it using the following code:
    if (!UrlFormatoCorrecto(urlActual))
    Response.RedirectPermanent(urlActual.Replace(" ", "-").Replace("+", "-").ToLower());
    I get the code again with the same URL with upper case. How can I escape the special characters so they won't bother me anytime I want to make the redirection?

    hello,
    you could escape special caracters with :
    Regex.Escape Method
    Regards
    Cédric

  • Special characters in URL parameters retrieved as question marks

    Hello,
    I am posting a simple HTML form to a WebDynpro application, and then I retrieve the 2 parameters with the following code :
    IWDWebContextAdapter adapter = WDWebContextAdapter.getWebContextAdapter();
    String comment= adapter.getRequestParameter("comment");
    Problem : some special characters (those with accents for instance) are retrieved as question marks. Their ascii character is always 65533 (unicode rather?).
    I guess this is a problem of charset, but where could I change it ?
    Trying to encode afterwards does not change the characters, I always get the question marks. But I may not do it the right way...
    Any hint on that ?
    Thanks a lot.
    Best Regards,
    Nicolas

    Hi,
    refer to following code.
    Stop using deprecated object IWDWebContextAdapter
    IWDProtocolAdapter adapter = WDProtocolAdapter.getProtocolAdapter();
         try {
              byte comment[]= adapter.getRequestObject().getParameter("comment").getBytes("ASCII");
              String str = new String(comment);
         } catch (UnsupportedEncodingException e) {
              // TODO Auto-generated catch block
              e.printStackTrace();
    Ashu

  • GoLive CS2 doesn't seem to encode special characters - help!

    If you've recently upgraded to CS2 and are having trouble with HTML entities for special characters, see this FAQ topic:
    FAQ 11.11 - Special Character Encoding Problems (CS2)
    Looks like this is going to be a recurring topic for a while as people migrate to CS2, so I'm making this a "sticky" topic at the top of the forum (thanks Martin).

    Thank you all for your posts on this issue. I need to point out a few things.
    1. As a novice, I had assumed that "special characters" included all non-standard characters (those not included in the Basic Latin character set and the Latin-1 Supplement set), and that therefore, all the "other" Unicode characters were special characters. As a result, I had assumed that the original post about Special Characters did indeed have a connection to Unicode input methods. (In fact, I am utterly in the dark as to why it is that it does not. But being a novice I believe you when you say that "special characters" and Unicode characters are two unrelated things, although I have no idea what the difference is. But, for letting me know that there is a difference, for that I truly thank you.
    2. I have read and re-read my comments from earlier and fail to see any "flaming" in it of Nate. Yet the rest of you see it clearly, so it must be there. It must be very disappointing for you to try so hard to help others only to be confronted with someone of ill-manners blasting you for your best efforts. I am truly sorry that I have in my ignorance and in my own frustration caused you to feel this way. Furthermore, since his statements had nothing to do with the issue that is so vexing to me (as you have now shown me), it was completely inappropriate for me to be upset with his answers.
    3. I remain very frustrated with not being able to find an answer to this problem of Unicode entry. I share Dee Bolland's aggravation when he talked about "... patronising people saying 'Didn't you know that?' blah blah." and when he said, " Please don't say 'It works for me!' :< ." When I first read Nate's statement of what to do about special characters, my spirits were excited with hope that it would solve my Unicode issues (because I thought he was talking about that). I was hopeful that I had missed something simple. When I tried it and it didn't work for my problem, I was very disappointed. This is the same frustration that I had when I read Rob Keniger's statement to me that the program can accept input in Source view. I jumped at this with hopeful anticipation, only to be totally and utterly disappointed once again--because it doesn't work for me. I pasted the Unicode text that I had posted above ( ×ֲש×ֶר ×Ö¹× ×Ö¸×Ö·×Ö° ×ַּעֲצַת רְש×ָעִ×× ) into source view, and all I got was the following: "
      " (I've included the tags so you can see the space). In other words, once again my high hopes are dashed and I am left feeling stupid (you say it works for you) and angry such a great program that does so many fantastic things can't do the basic things I want it to do. So, yes, I remain infuriated by the situation, by my inability to get the program to do what (I thought) you all had said it can so easily do. And yet (as I stated earlier in my post to Nate at which he took offense): "I do hope I am missing something simple and that the error is totally mine. However, I have yet to see any directions or examples that will solve the problem. Please, if you know of how to make this work, let me know. I will gladly confess my error in doubting you, if you can show me I am wrong by doing it right."
    So, since my post was not germane to the discussion, I will now bow out of this one. Thank you so much for your efforts to help, though.

  • Problem in encoding special characters

    Hi folks
    In my jsp iam going to populate special characters (<>(*&), it is
    working fine, but if i substring that one to certain limit(for ex:10)
    for example if i give like --> &<> to populate in jsp it is
    taking as --> &<> and it is going to substring and it is
    taking upto--> &<&
    but the xml parser not able to parse and thrown NotWellFormed exception
    how can i overcome this one.
    Advance appreciation for any ideas..
    -Naresh

    Thanks we'll check into it.

  • URL encoding special characters in episode name

    Hello,
    Configuration :
    1 capture agent on a MAC MINI under MAC OS X 10.6.5
    1 PCP2 server on an XServe under MAC OS X 10.6.5
    I encounter this problem since 10.6.5 update :
    When I stop a Podcast capture, if episode name is for example abcd#, '#' character is "URL encoded" to '%23' sequence. So the final file name of the podcast is abcd%23.m4v instead of abcd#.m4v.
    This was not the case under 10.6.4.
    I tried this solution : renaming the file adding a task in the workflow ; this task launches a bash script which renames all files replacing '%23' sequences by a '#' character.
    Files are well renamed, but the task don't give hand back, and XGrid task never ends.
    Got this error in /var/log/system.log :
    sandbox [nnn] : bash(12146) : deny file-ioctl /path/to/bash-script
    Thanks for help

    Problem solved !
    I had a problem with rights on my podcasts directory.
    So, for those who are interested, you can add a task to your workflow, for example a bash batch file which renames all files in your podcast directory whose name contains a special character :
    for fic in `ls`
    do
    mv $fic `echo $fic | sed -e s/%23/#/g`
    done
    the additional workflow task must contain 2 items :
    --- an item "command" of type String with the path of your batch file as value
    --- an item "dependsOnTasks" of type array with an element of type string with "postflight" as value

  • Encoding special characters

    Hi, how can I encode a special character such ' in a xsl page.
    In general, what is the syntax to use.
    Thanks

    To include these characters you use entity references of the form &name;. For example & is inserted with &;. You can check out the XML spec for a complete listing.
    Oracle XMl Team

  • Special characters in URLs

    I've used punctuation in the titles of some of my blog entries (e.g., "Bob's Birthday"). iWeb is including that punctuation in the URLs it generates for the entries. When I publish, I don't have any problem viewing the site and all the links are fine. But when I upload it (over ftp) to my website, those characters get garbled and break the links. (e.g., the apostrophe becomes a ?). I'm using Transmit to upload -- I've tried both ASCII, binary, and auto mode and none of them seem to work.
    Any ideas on how to solve this problem? It seems like it's in the ftp program somehow, since the published website works when I view it straight from my harddrive.
    Thanks!

    I'm using Transmit to upload -- I've tried both ASCII, binary, and auto mode and none of them seem to work.
    Try Cyberduck instead, set to UTF-8. Many have found that uploading with this app will solve the problem.
    The issue is really with the server -- you would have no problem with .Mac.
    Also turning off smart punctuation in the iWeb preferences might fix it.

  • Encode Special Characters to HTML String

    I was wondering that there is no function similar "encodeURL" available to encode strings like "�u" to "&auml;&uuml;" .
    Did I missed something?
    Regards!

    maybe you should try URLEncoder class

  • Why my Dreamweaver CS6 encodes the URL php on MM_goToURL ?

    I have a problem with dreamweaver CS6 because when I use this function MM_goToURL, my dreamweaver encodes the php var, i don't know why, I have my preference well.. I don't know if it is a bug from dreamweaver. i'm using template form dreaweaver.
    this is a real code
    and later when I go to update the template look the url on the function MM_goToURL, this change dreamweaver CS6 encode it
    this doesn't happen on dreamweaver CS5, CS5.5, CS4.
    need some help with this please =).

    Check your Preferences.
    Ctrl + U or Cmd + U (on Mac OS) > Code Rewriting > Check URL encoding. Ensure it is set to 'Do not encode special characters'.

  • Special characters in UCM site URL does not give error

    Hey Experts,
    If we put any special characters in site URL, UCM does not show 404 page .. for e.g.
    site URL is http://www.example.com/abc/xyzs/index.html.... if we add special characters in URL for e.g. http://www.example.com/#$abc/xyzs/index.html...
    then home page of site is displayed .....http://www.example.com/...
    Also http://www.example.com/ abc/xyzs/index.html shows home page ..
    Any idea why it is happening ??

    I would attribute this behavious to the SSUrlMap filter - which has the job of turning the friendly URL's into SS_GET_PAGE service calls. Apparently the way it parses the URLs and looks for the patterns does not consider these characters.
    Is it actually a problem?
    Tim

  • Special Characters in Links

    Hello,
    I work for a software company which offers a web application - an e-mail subscription management service. Our application sends e-mails out to subscribers which include links back to the websites of our clients. The problem we have encountered with some frequency is that some versions of Safari do not seem to like encoding of special characters in URLS. All of the links we send have encoded special characters in them. For example:
    http://service.govdelivery.com/service/edition.html?emailtype=subscription&format=HTML&code=MNMMCD5&date=2006-06-21 00:00:00.0
    We encode each "&" as a character entity in the URL. When encoded this way, the links do not work for many Safari users. If we remove the encoding (character entity) and simply insert an "&", the links will work for them.
    The problem is that the encoded version is the WC3 compliant one. It is not recommended to use special characters in URLs, such as < or &. Is anyone familiar with this issue? Is this true across all versions of Safari?
    Thank you for your help.
    Gabriel Zeck
    GovDelivery, Inc.

    We encode each "&" as a character entity in the URL.
    When encoded this way, the links do not work for many
    Safari users. If we remove the encoding (character
    entity) and simply insert an "&", the links will work
    for them.
    The problem is that the encoded version is the WC3
    compliant one. It is not recommended to use special
    characters in URLs, such as < or &. Is anyone
    familiar with this issue? Is this true across all
    versions of Safari?</div>
    I'm not sure if it is the Mail app or Safari which does this. Whichever, it is too clever by half. If it comes across a &, it changes it to %26, which is fine. But if it comes across a %26 it will re-encode the % and produce %2526, which of course is not.

  • Output proper special characters in JSTL custom tag

    I've written a custom JSTL Tag and want to output proper encoded special characters, like the c:out tag does (example: > to >). Do I have to parse that manually or is there a method within the jsp-api?

    Custom JSTL tag ?????Oops. Custom tag, of course.
    In custom tags, you have to manually parse it AFAIK.Somehow I can't imagine that such a frequently needed feature has do be done manually. Almost every tag that has to output data, has to convert special characters, otherwise cross-side-scripting would be possible.

Maybe you are looking for