Inspiring

Answered

After update project RH 2019->2022: edit is no longer possible

Forum|Forum|3 years ago
July 18, 2022
2 replies
738 views

Hi all!

After updating RH 2019 -> RH 2020, I can't edit project-css (see attachment) in RH GUI. There is an error message (see attached png, in English: stylesheet could not be parsed).
What can I do? I have only created new projects in 2020 so far, but have not migrated any old projects from 2019.
In 2019 the css worked and could be edited. The css was created in RH11.
What can I do? I have no experience editing CSS in html original format. I don't feel confident about that.
Can anyone give me a tip on how to clean/update/renew a RH11 css? I am working with RH 2020.8.34.

assyst-manual.zip

New UI

This topic has been closed for replies.

Correct answer Peter Grainge

2020 is strictly HTML5 and CSS3 compliant. Whilst there are some scenarios where valid CSS will falsely report the CSS cannot be parsed, they are rare and it will almost certainly be that some of your old CSS that was valid in Classic does not meet the 2020 requirements.

In the source view there are numbers in the left column. Scroll down those looking for red circles with a cross. That should highlight what needs fixing.

If there are only a few, post images of them here. Please use the photo icon to insert images within the post. Seeing an image inline with the text makes it easier for anyone answering or viewing the post.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

A

Amebr

Community Expert

It could be the second half of this bug I logged (if the style in the @media statement exists in the main body of the stylesheet, the stylesheet will fail to parse)

https://tracker.adobe.com/#/view/RH-9864

A

Amebr

Community Expert

Feel free to vote on it if this turns out to be the case, in the hope it gets fixed eventually. 🙂

Peter Grainge

Correct answer

Community Expert

2020 is strictly HTML5 and CSS3 compliant. Whilst there are some scenarios where valid CSS will falsely report the CSS cannot be parsed, they are rare and it will almost certainly be that some of your old CSS that was valid in Classic does not meet the 2020 requirements.

In the source view there are numbers in the left column. Scroll down those looking for red circles with a cross. That should highlight what needs fixing.

If there are only a few, post images of them here. Please use the photo icon to insert images within the post. Seeing an image inline with the text makes it easier for anyone answering or viewing the post.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.

A

A-BelAuthor

Inspiring

Thanks for the quick reply, Peter!

At first I got stuck with your tip because there were no marked line numbers to give clues to errors.
Then I created a new, empty css and copied all format definitions of my old css into it bit by bit. What can I say? Exactly one error location existed:

I don't know what sense this formatting had in old versions. I just deleted it and after that the error was fixed 🙂

Thanks a lot!

Peter Grainge

Community Expert

Glad it's sorted. One of your first screenshots of the code showed numbers as well.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded