Skip navigation
SteveCTWriter
Currently Being Moderated

Has anyone else experienced this problem?

Jul 26, 2012 10:38 AM

My project crashed again (second time in 3 weeks) when I was editing a topic in HTML view.

 

Just like last time, I had just deleted the <?rh-glo-start> tag on one of the lines in the topic (this is leftover "junk code" as a result of having imported a help topic generated from a RH output by mistake).

Also just like last time, I couldn't open the project after it crashed, using all the hints and tools suggested to me earlier (see http://forums.adobe.com/message/4551128#4551128). Consequently, I had to go back to my last archived version from the night before (and lost a 1/2 day's work in the process).

 

I can't reproduce the problem on demand. However, both incidents occurred when I did a "Save Component" while in HTML view mode.

 

Perhaps as a test (or a workaround), I should try switching to Design mode before I do a save (if I am editing HTML code)?

 
Replies
  • Currently Being Moderated
    Jul 26, 2012 11:35 PM   in reply to SteveCTWriter

    Hi,

     

    I have noticed that RH sometimes freezes when you create such invalid HTML that even RH chokes. In those cases I found that thrashing the CPD and replacing the last modified topic with one from a backup normally fixes the problem. You would then only have to modify the last topic again.

     

    Greet,

     

    Willam

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 27, 2012 12:05 AM   in reply to SteveCTWriter

    When you switch from HTML View to Design View, RoboHelp does some code cleaning. For example, if you remove an opening span tag in HTML View, you don't need to remove the closing span tag, RoboHelp will do it for you.

     

    Concurring with what Willam has said, I suspect that somewhere along the line you made an unintended change and by not going back to Design View, you didn't allow RoboHelp to fix it. In the case RoboHelp could not fix it, you would likely have found something wrong in Design View that you could either fix or escape from by closing that one topic unsaved.

     


    See www.grainge.org for RoboHelp and Authoring tips

     

     

    @petergrainge

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 30, 2012 11:44 AM   in reply to SteveCTWriter

    Yes it can be the case that you simply cannot reopen a project but mercifully it is not that common. It does not mean the other topics are corrupted though, just that the rogue topic is preventing opening. Deleting it in Windows Explorer should fix that as RoboHelp should open and just show the topic as missing. Not sure what is wrong here at the moment.

     

    You haven't started the thread with you version of RoboHelp. Also do you have all the patches applied.

     


    See www.grainge.org for RoboHelp and Authoring tips

     

     

    @petergrainge

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 30, 2012 11:47 PM   in reply to SteveCTWriter

    Wouldn't Post 5 have been better placed in the thread where you first raised it? It might be worth copying that part of the post to the old thread in case someone can match a previous poist with this one and identify the problem.

     

    To deal with any bug, it has to be reproduceable and right now even you cannot do that at will. I don't mean that to sound unhelpful, it's just a statement of fact. Would it be worth doing the things you use keyboard commands for in some other way to confirm or rule out the commands as the cause?

     


    See www.grainge.org for RoboHelp and Authoring tips

     

     

    @petergrainge

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points