Feature Long Description Text and Hyperlink on one line

Jeff Ashton

6. September 2018 05:14

I have just updated to 4.10.1.61 Essentials and Viewer for HTML5 2.11.1

 

The code used for the feature long description is shown below and the result appeared on one line

 

Now every hyperlink appears on a separate line which is not what we want

 

Is there any code which may fix this?

 

<div><strong>Property No: </strong><a href="command:RunWorkflowWithArguments?workflowId=Open_URL_Property_No&amp;PropertyNumber={Property_No}" target="_blank">{Property_No}</a></div>

 

This is how it used to appear

 

Property No: {Property_No}

 

This is how it now appears

 

Property No: 

 

{Property_No}

0

• 

  Mike Ketler

  5. Oktober 2018 22:03

  Hi Jeff,

   

  I tested your HTML using the LA County Demo site that comes with Essentials and it shows up as one line for me. Can you try clearing the Feature Description completely of any HTML, saving the site, and then reapplying the HTML?

   

  _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=907f2000000Xdjq&feoid=Body&refid=0EMf2000000YC7p"_/_img_

   

  Thanks,

   

  Mike Ketler

  0
• 

  Jeff Ashton

  7. Oktober 2018 20:35

  I tried clearing the Feature Description and saving the site.

   

  It still shows up on multiple lines

  0
• 

  Permanently deleted user

  9. Oktober 2018 06:22

  I have same issue and I think its related to the version we used

  0
• 

  Berend Veldkamp

  9. Oktober 2018 12:55

  Could this be a word wrapping issue? How long are the values in the Property_No field?

  0
• 

  Jeff Ashton

  9. Oktober 2018 20:26

  No. Its not a word wrapping issue

   

  The values in the property number field are only 6 characters

  0
• 

  Jeff Ashton

  10. Oktober 2018 00:26

  I have found part of a solution

   

  I created a new Site and it worked

   

  Thing is...I dont want to create this site from scratch...Can I just copy the Desktop.json.js file across? 

  0
• 

  Jeff Ashton

  12. Oktober 2018 02:57

  I ended up copying the Desktop.json.js file across and redoing all the menus and customisations

   

  It now works fine...Thanks for the comments

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.