12 Replies Latest reply on Mar 26, 2010 7:11 AM by Willam van Weelden

    Editing topics in the HTML view causes Master page message

    tspaul

      There are four writers in my group using RoboHelp 8. We use master pages to add a special navigation bar to the top of each topic. Whenever most of us edit a topic in the HTML view and then save it, we get a message saying that the topic is using a master page and the header or footer has been modified, even though we have done nothing to the header or footer. We then have the choice of changing the master page or just the topic, neither of which seems to make much difference. The association with the master page becomes lost and needs to be reapplied after this.

       

      In large help projects, this costs us a lot of time and annoyance. It appears to us at least to be a bug. Is it, or is there something we can do either in the topics or in the master page to make this problem go away? Sometimes we can avoid the problem by just editing in teh Design view, but there are times we need to change the code.

       

      I did see another thread on this, but it was marked answered, and there were no helpful answers to us in that thread.

       

      Thank you,

       

      Tammy

        • 1. Re: Editing topics in the HTML view causes Master page message
          RoboColum(n) Level 5

          Hi Tammy.

           

          Can you give us some more detail of what is in this header / navigation bar? It sounds like there is something in it that is being updated each time one of you open a topic.

           


          • Read the RoboColum(n) for a tips, tricks and musings on the Technical Communication Suite products.
          • Follow the RoboColum(n) on Twitter
          • 2. Re: Editing topics in the HTML view causes Master page message
            tspaul Level 1

            Sure! We generate WebHelp, and we don't use the three-pane navigation. Instead, each topic is opened on its own from within our software. To help users with navigation through the help, we use master pages to apply a header that includes 6 buttons: Contents, Index, Search (not the RoboHelp search), Back, Other Help, and Close Help. The code includes JavaScript to make certain button effects work when the user hovers over the buttons or clicks them. It also includes JavaScript to make the Back and Close Help buttons work.

             

            Below I've pasted in the <body> part of the code from the master page. Hopefully this comes through OK in the forums.

             

            The message only seems to appear if we work on the topic in the HTML view.

             

            Tammy

             

            <body>
            <?rh-region_start type="header" style="width: 100%; border-left-color: #0000ff; border-right-color: #0000ff;
                  border-bottom-color: #0000ff;" ?>
            <script type="text/javascript" language="javascript" src="ButtonEffects.js"></script>
            <table style="vertical-align: Center;" cellspacing="0" bgcolor="#009966"
                width="100%">
              <tr style="vertical-align: top;">
               <td style="border: Solid 2px #009966;width: 100%; padding-right: 5px;
                 padding-left: 5px; vertical-align: center; ">
               <div style="margin-top: 0pt;
                 font-size: 8pt; font-family: Verdana, sans-serif; color: #ffffff;"><a
                class="buttons" href="whgdata/whlstt0.htm" onmouseover="return changecontentsImage()"
                onmouseout="return changecontentsImageBack()" onmousedown="return handlecontentsclicked()"
                target="_self"><img name="jsbutton" src="ContentsButton.gif"
                     alt="" width="63" height="16" border="0" /></a><a
                class="buttons" href="whgdata/whlsti0.htm" onmouseover="return changeindexImage()"
                onmouseout="return changeindexImageBack()" onmousedown="return handleindexclicked()"
                target="_self"><img name="ixbutton" src="IndexButton.gif"
                     alt="" width="63" height="16" border="0" /></a><a
                class="buttons" href="../search.aspx" onmouseover="return changesearchImage()"
                onmouseout="return changesearchImageBack()" onmousedown="return handlesearchclicked()"
                target="_self"><img name="srchbutton" src="SearchButton.gif"
                     alt="" width="63" height="16" border="0" /></a><a
                class="buttons" href="Javascript:history.back()" onmouseover="return changeBackButton()"
                onmouseout="return changeBackButtonBack()" onmousedown="return handleBackclicked()"
                style="color: #ffffff;"><br />
               <img name="BackButton" src="BackButton.gif" alt="" width="63"
                 height="16" border="0" /></a><a class="buttons" href="../OtherHelp.aspx"
                         target="_self" onmouseover="return changeOtherHelpButton()"
                         onmouseout="return changeOtherHelpButtonBack()"
                         onmousedown="return handleOtherHelpButtonclicked()"><img
                name="OtherHelpButton" src="OtherHelpButton.gif" alt="" width="63"
                height="16" border="0" /></a><a class="buttons" href="javascript:if( opener != null && opener.ShrinkHelp ){void(opener.ShrinkHelp(this));}else{self.close();}"><span
                onmouseover="return changeCloseHelpButton()" onmouseout="return changeCloseHelpButtonBack()"
                onmousedown="return handleCloseHelpButtonclicked()"><font
                color="#FFFFFF"><img name="CloseHelpButton" src="CloseHelpButton.gif"
                      alt="" width="63" height="16" border="0" /></font></span></a></div></td>
              </tr>
            </table>
            <p><img src="amhelp.gif" style="border: none;" alt="" width="102" height="34"
                border="0" /></p>
            <?rh-region_end type="header" ?>
            <div class="contentArea">
            <?rh-region_start type="body" ?>
            <h1>&#160;</h1>
            <p>&#160;</p>
            <p>&#160;</p>
            <p>&#160;</p>
            <?rh-region_end type="body" ?>
            </div>
            </body>
            </html>

            • 3. Re: Editing topics in the HTML view causes Master page message
              Willam van Weelden Adobe Community Professional & MVP

              Hi,

               

              Is the HTML-view by any change changing the line ends of the header? I can imagine that RH sees that as a modification in the header.

               

              Greet,

               

              Willam

               

              This e-mail is personal. For our full disclaimer, please visit www.centric.eu/disclaimer.

              • 4. Re: Editing topics in the HTML view causes Master page message
                Author care Level 2

                Hi,

                I've also been experiencing this bug on a regular basis since I've been using RH8 under very similar conditions. I'd also be very interested to know what's going on here.

                 

                One thought I have is that it's somehow connected with the different ways that RH6 and RH8 do what used to be called templates and are now called master pages...

                 

                This is the sort of problem that Adobe really need to get a handle on..

                 

                 

                • 5. Re: Editing topics in the HTML view causes Master page message
                  tspaul Level 1

                  I'm not quite sure what you mean by line ends. Could you be more specific? If you mean the tag ends, the

                  /> format is already being used.

                  • 6. Re: Editing topics in the HTML view causes Master page message
                    Willam van Weelden Adobe Community Professional & MVP

                    Hi,

                     

                    I mean the line ends. When you open the topic in HTML view, RoboHelp adds line breaks to improve the readability of the HTML code.

                     

                    Greet,

                     

                    Willam

                     

                    This e-mail is personal. For our full disclaimer, please visit www.centric.eu/disclaimer.

                    • 7. Re: Editing topics in the HTML view causes Master page message
                      tspaul Level 1

                      Would it make that change every time? If so, then there would be no solution to this problem.

                      • 8. Re: Editing topics in the HTML view causes Master page message
                        Willam van Weelden Adobe Community Professional & MVP

                        You'd have to test that. It's more of a guess from me, but the only thing I can think of now.

                        What happens if you:

                        1. edit a topic in HTML (add a space somewhere), go back to Design mode.

                        2. Reassign the master page, whilst keeping the topic open in Design mode.

                        3. Go to HTML mode and remove the edit.

                         

                        Do you get the same message?

                        I'll test a bit when I get home to see if I can find anything.

                         

                        Greet,

                         

                        Willam

                         

                        This e-mail is personal. For our full disclaimer, please visit www.centric.eu/disclaimer.

                        • 9. Re: Editing topics in the HTML view causes Master page message
                          tspaul Level 1

                          Yes, I get the same message when I follow those steps. In fact, we get the message when saving *whenever* we change something on the HTML tab, whether it's the first time we've done so or not.

                          • 10. Re: Editing topics in the HTML view causes Master page message
                            Willam van Weelden Adobe Community Professional & MVP

                            Hi,

                             

                            The (html of the) header is quite large. What happens if you delete most of the header, leaving only one cell or something like that? (In a copy of your project ofcourse.)

                             

                            If this is causing the problem,  I can think of two way's of solving it:

                             

                            1. If you create WebHelp/FlashHelp: Add a unique string of characters in the heading, instead of the table. It has to something that will NEVER be used in any topic or script. When you created your output, use a find and replace operation to replace the unique character string with the table.

                            2. You can dynamically build the table with a javascript. You will have to make an extra function that writes the table. In the header, you'll only have to call that function.

                             

                            Greet,

                             

                            Willam

                            • 11. Re: Editing topics in the HTML view causes Master page message
                              tspaul Level 1

                              We are aleady doing a lot of manipulation of our help files afterwards to get everything to work the way we want. (Come on, Adobe, make single-frame help possible in WebHelp, not just AIR help!) I don't want to add to that burden, and the solutions you suggest seem to do that, but I do appreciate the thought you put into them. Living with the problem, however annoying, sounds less painful, but I don't want to if we don't have to.

                               

                              Anyone else have any ideas? It still sounds to me like this is a bug.

                               

                              Tammy

                              • 12. Re: Editing topics in the HTML view causes Master page message
                                Willam van Weelden Adobe Community Professional & MVP

                                It might help to delete all inline styling and replace that by css classes. That will save a lot of text and perhaps solve the problem.

                                 

                                Greet,

                                 

                                Willam

                                 

                                This e-mail is personal. For our full disclaimer, please visit www.centric.eu/disclaimer.