# in url not considered in Touch UI author editing mode | Community
Skip to main content
selvaganesh
selvaganesh
New Participant
October 16, 2015
Solved

# in url not considered in Touch UI author editing mode

  • October 16, 2015
  • 7 replies
  • 2651 views

I have some urls having # in authoring page. The part after # in the URL is not recognized in authoring mode in touch UI and hence the functionality is breaking. Is there any way to recognize # in touch UI. 

Works fine in classic UI

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by heim0

Hi,

Can you confirm how exactly you're trying to use the # ?

Is it as part of a link - and when you're editing the page (with the touch-optimized UI) you cannot navigate to such a link?

If so, then you'll have to switch to Preview mode. Links are not accessible in the Edit mode. See:

and

I hope that helps, if not feel free to contact us again - preferably with an example of your URL and the behaviour you're seeing.

7 replies

H
heim0Accepted solution
Employee
October 16, 2015

Hi,

Can you confirm how exactly you're trying to use the # ?

Is it as part of a link - and when you're editing the page (with the touch-optimized UI) you cannot navigate to such a link?

If so, then you'll have to switch to Preview mode. Links are not accessible in the Edit mode. See:

and

I hope that helps, if not feel free to contact us again - preferably with an example of your URL and the behaviour you're seeing.

selvaganesh
selvaganeshAuthor
New Participant
October 16, 2015
Seems like touch ui is html5 based. I am able to navigate to URL from links inside the page in preview mode rather than hitting the URL directly
selvaganesh
selvaganeshAuthor
New Participant
October 16, 2015
        It is resolved.
selvaganesh
selvaganeshAuthor
New Participant
October 16, 2015

I have angular application in AEM. It has # in its url and renders pages based on the url after #.

G
GillesKnobloch
Employee
October 16, 2015

Could you please provide some details, in case further people encounter the same kind of issue?

H
heim0
Employee
October 16, 2015

I have asked the Engineering group that deal with this to have a look. They should respond as soon as possible.

G
GillesKnobloch
Employee
October 16, 2015

The issue is now marked as resolved.

Did you figure out the solution or do you need further help?

Terms & ConditionsAccessibility statement

Loading footer...