Hi,

The paramters will be saved. But if you're editing the link, they will be deleted if you're not re-adding them again.

This goes for all link tools in EPiServer. Would be nice with an extra field for querystrings...

Hi Johan,

Thank you for your response. I'll have to dig this a little bit deeper. There might be something wrong in my own code then.

I have this same problem, but my site consists of a lot of one-pagers where the user navigate using hashtags, in this case I want the user to link to an internal page with a hashtag-argument, but everything after the hash is stripped. Could the link-tool somehow be extended to not strip the hash?

@dagstuan, we have similiar issue and I have reported it as a bug (doesn't seem to show up in the bug list).

Anyways I'm assuming you are here talking about the XhtmlString property (TinyMCE editor).

Step one, there is the original LInk tool button for TinyMCE that you can add to the editor toolbar (in admin mode change what buttons are in the toolbar or use the new feature to do it from code).

With that link button you can add any kind of link manually (if you use the filefolder icon in the popup it only allows to select images etc content) by entering the value to the field -> also preserves anchor link values when re-opening the editor.

Next step is to override the XhtmlString rendering

• add a display template for the XhtmlString (/Views/Shared/DisplayTemplates/XhtmlString.cshtml)
• you can look at the original display template in the: EPiServer.Cms.Shell.UI.zip (extract, Util\Views\Shared\DisplayTemplates\XhtmlString.ascx)
• you need to do a custom implementation of the RenderXhtmlString extension method
• bascially copy EPiServer code and in your implementation add the fragment to the url
• use ILSpy for example to see the original implementation, the issue is with the original implementation if the page is resolved to EPiServer page the url fragment is not added (see EPiServer.Web.Mvc.Html.XhtmlStringExtensions EPiServer.dll, the issue method is the private RenderFragment method calling urlresolver.GetShortCutAwareUrl which doesn't add the url fragment to the produced url)

Using EPiServer 7.14 we've found this is a problem triggered by links by a the pattern of something like "?id=12345". Our workaround was to replace the links with something like "?foo=bar&id=12345". Somewhat ugly, but works.