Problems with using the style repository

[mariya_savina]

Good afternoon, we have encountered a problem that after connecting the style repository, the html build does not display the last changes that were applied in the hm project. Including variables like Major Version and Minor Version are not pulled up.
What could be the reason for this behavior and how to solve it?

[Tim Green]

Hi Mariya,

I'm guessing that you are only seeing these issues with variables, not with the snippets or styles linked from the repository. Currently, variables in the repository are not dynamic. They will be copied from the repository the first time you link it, but changes in the values of the variables in the repository are not updated in your linked projects. See here for details on this:

https://www.helpandmanual.com/help/hm_a ... _vars.html

[mariya_savina]

No, the problem is not that variable values are not copied from the style repository.
The problem is that when the style repository is connected (copied), the variable values that are set in the hm-project itself are not applied during html publishing. In addition, the changes in the text are also not applied at publish time.
I think it is the repository styles that are the problem. Because when we disabled them and applied the styles we used before, the problem went away.

[mariya_savina]

We were able to solve the problem. Thank you!

[Tim Green]

The problem is that when the style repository is connected (copied), the variable values that are set in the hm-project itself are not applied during html publishing. In addition, the changes in the text are also not applied at publish time.

That must be a different problem, possibly associated with the skin you are using. The simple connection of a repository cannot cause this. And even if you have the same variable defined in the repository and the project, the value of the version in the project is used at publish time. This also applies if you are using a topic from the repository as a snippet with the variable used inside the snippet. The project version is used.

One possibility is that you are editing your projects in a managed cloud folder like OneDrive or Google Drive or DropBox. Doing this will cause you to lose data, overwrite other users' data, lose TOC entries and get all kinds of other strange errors, including multiple copies of topic files, each with a different editing status. This all happens silently, without any error messages or warnings. Editing in managed cloud folders is only possible with the programs from the companies themselves, like Microsoft Office programs in OneDrive and Google's programs in Google drive.

This gets even worse if you try to put a project managed in version control inside a managed cloud folder. That is a recipe for even more serious problems and data loss. It is also possible that what you are experiencing may be a problem with version control configuration, even without combination with a cloud folder.

Text changes not turning up definitely cannot be caused by a repository. That could be a cache issue in the browser, problems with include options configuration, a proxy server on your web server and a number of other issues. But not the repository.

I think it is the repository styles that are the problem. Because when we disabled them and applied the styles we used before, the problem went away.

You said that you "copied" the styles, i.e. you chose the option to copy the styles from the repository instead of linking them. When you do this there is no active link between the repository styles and the styles in your project. This means that the styles in the repository are not updated in the project when you edit them in the repository. However, in both cases the styles are copied to the project and the style versions used are always those in the project. So if you disconnected the repository and left the styles in the project, nothing actually changed.

If you continue to have issues we may have to have a look at your entire setup. You would need to send both the repository and a demo project to support AT ec-software.com (replace the AT with @) so that we can test it out directly.