RH 2019: Project folder name with . causes strange behavior

[Karin Albrecht]

Hi All,

This might be an unusual case, but I came across some strange behavior. My project folder contained a . (dot), cause our product name contains a dot (RH reimagined.2). My project's name is "RH reimagined" (without a dot). In such cases, everything works fine most of the time. However, if you try to rename any topic or image file via the context menu (right mouse click - rename), the file is not provided with the name you enter there, but with the name of the project (i.e. RH reimagined.htm or RH reimagined.png). Also, the file is moved out of its original location into the top most level (e.g., if you are working in C:/documents/MyRHProjects/RH Reimagined/Folder1, the file will be moved to C:/documents/MyRHProjects). After this has happened once, you will not be able to rename any other file, as RH always returns the error, that the file with the name "RH reimagined" already exists.

It is possible to rename the files via the edit properties of the topic in any cases.

Maybe this helps someone.

Regards
Karin

[Peter Grainge]

I would never have a dot in a folder or file name, even though in theory it is OK these days.

That said I just renamed a project folder and put a dot in the name. RoboHelp still works fine. Is this the project that had all the broken links after moving folders and files around. If it is, then i am more inclined to think that is the root of this problem.

Try the same thing with the sample projects or any other project you have. Do they break to?

---

See www.grainge.org for free RoboHelp and Authoring information.

@petergrainge

[Karin Albrecht]

Funny that it works fine for you. I tried it with different projects (e.g. Robohelp Reimagined and Robohelp Reimagined.2) and on different locations, everytime the same error

However, the broken links occured in a fresh sample project without any dots or anything else funny.

[Peter Grainge]

I can explain the different behaviour you are both seeing. The links break when both source topic and target topic are in the same move. Adobe are aware of this problem and it will be fixed as a priority issue.

---

See www.grainge.org for free RoboHelp and Authoring information.

@petergrainge