HTML Component Bug in V1.5.5

Elements
1

As a few components are still not available in Elements, I have been using the HTML Component. I had a few issues changing the HTML code after initial use. This behaviour seems to be worse in v1.5.5. Now I have to close the project and reopen it to change the HTML code. I understand that this is a known bug. @dan Is there a workaround for this, especially as we wait for more components to be added. Or a bug fix in the pipeline?

Custom Componet PROBLEM
2

Ok - being nosey - don’t have to answer…

What kind of html component?

My side html note ‘Sign Up for Newsletter’ slide in is working…

3

It is a breadcrumb html component. It is rather long.

4

Not sure if making it a global component may have changed the behaviour.

5

it drives me around the bend I use the editor all the time, still not fixed

https://forums.realmacsoftware.com/t/issue-in-html-editor/51793?u=upssjw

1 Like
6

This is one of the reasons I put my custom components in a DevPack, then I can edit the code in Nova, which works a lot better for me. There is no problem updating, as the minute you do a save, the component gets updated. I also find it easier to work on the properties in Nova, although I do also use a JSON editor occasionally.

1 Like
7

Yes that is an option, I rarely write more than 20 lines of code plus the json etc, just expect things to work that once worked, a few outstanding things that should work after all this time

8

To work around the error, you don’t have to restart the project, just close and reopen the inspector for the HTML code. Then the code can be edited. I also use Nova to use my own code in Elements. This saves me the time-consuming process of publishing via Elements. My HTML code only contains the PHP call require, and then I do the rest via Nova and also use AI for code development with JavaScript and PHP.

9

see above link, just click on styles js hooks to properties then you can re edit

10

Thanks. That is very interesting. I’ll have to work out how to integrate Nova into my workflow. Currently, I use Visual Studio.

11

Thanks for all the feedback on this.

As far as we’re aware it’s a bug that only affects users on Tahoe, the current workaround is to show the sidebar in the component editor.

I’ve created a ticket for this issue here and we will get it fixed.

1 Like