Skip to main content
V
Vertifi
Participating Frequently
March 31, 2021
Answered

RoboHELP 2020.4 WebHelp output adds broken link to Twitter widgets.js

  • March 31, 2021
  • 9 replies
  • 814 views

We're using RoboHELP version 2020.4.105.  When loading the initial screen of our WebHelp output there is a lengthy hang, followed by a message in Chrome console indicating a failed attempt to load https://platform.twitter.com/widgets.js.

 

The WebHelp output is adding this block of code at the very end of the main HTM file:

 

<script>//<![CDATA[

if(useTwitter === true) {
!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');
}

//]]></script>

 

we found removing this script  (manually) resolved the slow load issue.

 

Is there a way via project settings to remove this?  Or is this just a plain old bug that needs attention at Adobe?

 

The code appears at the very end of the HTM page, in the "Scripts" section:

 

<!-- Scripts -->
<script src="template/single_page/usersettings.js" type="text/javascript"></script>
<script>//<![CDATA[

if(useTwitter === true) {
!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');
}

//]]></script>

    This topic has been closed for replies.
    Correct answer Peter Grainge

    You are using a skin whether or not there is one listed. I suspect a default is applied. I suggest you add a frameless skin such as Orange and a reponsive skin such as Azure blue. Try with both of them and let us know how that goes.

    ________________________________________________________
    See www.grainge.org for free Authoring and RoboHelp Information

    9 replies

    Peter Grainge
    Community Expert
    Peter GraingeCommunity Expert
    Community Expert
    April 1, 2021

    A search of the output shows the word Twitter is in the following files.

     

     

    My first thought was that you have the Twitter icon enabled but you don't. My best guess is that RoboHelp injects the script regardless but only works if the button is enabled in the skin editor.

     

    You found the script through the Chrome console but from time to time I see posts saying some check saying some such console is reporting something from the minor to the end of the world is nigh, OK a bit of an exageration but you get the point.

     

    In this case you now say it is not causing a problem. 

     

    The reason you looked for issues was slow loading and I think you will find that is better in Update 4. If not then I think that is something for another thread.

    ________________________________________________________
    See www.grainge.org for free Authoring and RoboHelp Information

    Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.
    V
    VertifiAuthor
    Participating Frequently
    April 1, 2021

    Thanks again for your time, I agree with what you've described.  Please note the slow loading was painfully slow, a minute or so, before any UI was displayed.  The platform.twitter.com/widgets.js link was in the content <body> and was delaying the DOM load.  The Chrome console confirmed this, as the page would finally appear exactly when the 404 error appeared for this widgets.js link.

     

    I suspect that for some reason the JS code if (useTwitter === true) was somehow evaluating to TRUE, even though we didn't even have a defined Skin.  Once defining the Skin (with Twitter disabled), it seemed to resolve the issue.  The help content loads instantly 

    Peter Grainge
    Community Expert
    Peter GraingeCommunity Expert
    Community Expert
    March 31, 2021

    I will download and take a look tomorrow. 

    ________________________________________________________
    See www.grainge.org for free Authoring and RoboHelp Information

    Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.
    Peter Grainge
    Community Expert
    Peter GraingeCommunity Expert
    Community Expert
    March 31, 2021

    Can you share the project? If you can, then see the Contact page on my site and send the project as instructed there. Do make sure you include a link to this thread and please do not email the project direct.

     

    Something is wrong.

    ________________________________________________________
    See www.grainge.org for free Authoring and RoboHelp Information

    Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.
    V
    VertifiAuthor
    Participating Frequently
    March 31, 2021

    I have sent one of our projects, we have around 10 of them, all doing the same thing.  All of these are "legacy" projects that have been around for quite awhile, and have each been Updated for RoboHELP 2020 recently.

     

    Just to be clear, adding the Skin seemed to resolve the issue, though that odd looking Twitter related JS code is still present.  We initially had no skin defined in our projects so I suspect default behavior would evaluate this code:

     

    if (useTwitter === true)

     

    to true, and attempt to load a broken link, causing a lengthy hang in presenting the initial screen.

     

    Chris

    Peter Grainge
    Community Expert
    Peter GraingeCommunity ExpertCorrect answer
    Community Expert
    March 31, 2021

    You are using a skin whether or not there is one listed. I suspect a default is applied. I suggest you add a frameless skin such as Orange and a reponsive skin such as Azure blue. Try with both of them and let us know how that goes.

    ________________________________________________________
    See www.grainge.org for free Authoring and RoboHelp Information

    Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.
    V
    VertifiAuthor
    Participating Frequently
    March 31, 2021

    Hello Peter,

     

    Thanks so much for your guidance.  I added these default skins ... while I observed that the same code was being put into the HTM file, i.e. 

     

    <script>//<![CDATA[

    if(useTwitter === true) {
    !function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');
    }

    //]]></script>

     

    that it did not execute the function, in other words (useTwitter === true) must no longer succeed.  I think there is a bug here somewhere, but am satisfied with this solution.

     

    Again I thank you very much for your time and suggestions!

    Chris @ Vertifi

    Peter Grainge
    Community Expert
    Peter GraingeCommunity Expert
    Community Expert
    March 31, 2021

    Let us know if you have trouble downloading, you might with that build. In Skins then try a fresh version of the skin. 

    ________________________________________________________
    See www.grainge.org for free Authoring and RoboHelp Information

    Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.
    V
    VertifiAuthor
    Participating Frequently
    March 31, 2021

    Thank you for the feedback.  We do not use "Skins" (i.e. there are none listed), but will experiment with this

    Jeff_Coatsworth
    Community Expert
    Jeff_CoatsworthCommunity Expert
    Community Expert
    March 31, 2021

    Ok, then a new layout seems to be in order (btw - you know that there's really no WebHelp anymore in RH2020 - it's just responsive HTML5 with the responsiveness turned off)

    Jeff_Coatsworth
    Community Expert
    Jeff_CoatsworthCommunity Expert
    Community Expert
    March 31, 2021

    And did you have this Twitter widget hooked up before?

    V
    VertifiAuthor
    Participating Frequently
    March 31, 2021

    Not intentionally 😉

     

    We're a long-time user of RoboHELP, only recently upgrade to Robo 2020, and this is when we noticed the troubles.  We are surely not expert in use of the software, but this has us very puzzled.

    Peter Grainge
    Community Expert
    Peter GraingeCommunity Expert
    Community Expert
    March 31, 2021

    I'm surprised but at least that clarifies things. 

     

    Maybe just try a new skin. 

    ________________________________________________________
    See www.grainge.org for free Authoring and RoboHelp Information

    Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.
    V
    VertifiAuthor
    Participating Frequently
    March 31, 2021

    I've downloaded the update (my bad for not checking this first!), but am seeing the same behavior with 2020.4.173.

     

     

    Peter Grainge
    Community Expert
    Peter GraingeCommunity Expert
    Community Expert
    March 31, 2021

    I am not suggesting you are knowingly using a pirate copy but it looks as you that is what you may have. Where did you download it from?

     

    The released version of Update 4 has a build number of 173 giving a full reference of 2020.4.173 and certainly would not be adding code like that.

    ________________________________________________________
    See www.grainge.org for free Authoring and RoboHelp Information

    Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.
    V
    VertifiAuthor
    Participating Frequently
    March 31, 2021

    Peter, thank you for replying!  We'd received this release [apparently] from Adobe support recently in response to an unrelated issue.  I will get build 173 and report back on the forum.

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