Properties.json limit maybe?

Ive a fairly large properties.json 943 lines, If I attempt to add another group it breaks in the UI.

Instead of showing that final group name it gets a random number generated for the title of the group.

I’ve tried adding various types of additional groups to test, and all the same result. Does not even matter where I add one more group in the json structure its the last group I add that gets corrupted, which is definitely really strange.

I’ve thrown it At ChatGPT to error check to no avail. I’ve thrown it at a dozen online checkers and all say the json is valid.

At a bit of a loss.
943 lines, and a weight of 45 KB on disk

Even after adding any more groups everything else still works apart from what ever I add now.

The component as it stands : http://www.garysimpson.co.uk/vault/temp-sharing/shared-components/Icon.elementsdevpack.zip

Put the fire extinguishers away. I’m clearly a tired idiot!

When trying to debug this I’ve been heading to the docs and just grabbing a group example, I want a new group right!.. Errrrr… Wrong!
Neglecting the facts the examples contain the over arching Groups, plural. What a duffuss :sob:

Haha, no problem! I’m just glad you got that one resolved and it wasn’t another bug for us to fix :laughing:

This is an interesting post. :slight_smile:

I think that the JSON property UI is an area that could be improved post Elements Release 1.0. At the moment it is long winded and prone to errors setting up properties, especially with a lot of properties.

If you have an error in the Properties JSON, Elements doesn’t tell you about it, it just seems to ignore it and use what was working before. This can and does get confusing. :confused:

I normally edit my Elements DevPack using the Nova editor. If I have issues, I also open the Elements DevPack using PHPStorm and this highlights any JSON errors. You still have to try and work out what the correction is, which can take time.

As an aside, I also use PHPStorm to view and check the published site, to make sure everything was generated correctly from a PHP perspective.

Going forward, it would be very useful to have some sort of UI (rather like the Page Layout Node browser) where you could define a group or groups and just drop in the Elements UI Property Controls that you want. I am sure that would remove a lot of errors and speed up development.

@logrunner Your describing this sort of thing. Not built in but does keep you structured. I have it installed but not used for years. I just couldn’t gel with it personally. But for some it might be the golden egg.

http://www.smartjsoneditor.com

Not exactly, I have various JSON editors already. What I am suggesting is having a UI that doesn’t even mention / show JSON. :wink:

1 Like

A visual editor for the properties.json file sure would be nice — we actually discussed this internally a while back, and whilst we would all love to have this, I don’t believe this will make it in to the app for a 1.0 release.

@Doobox This is a great little component, very handy.

Is there anyway to add custom icons to the mix. I only ask because a couple of the icons I would need in the BRAND category are missing (Bluesky & Mastodon).

I also found what appears to be a small bug in the color property where the opacity slider is set to “5”, but in fact, the opacity is at 100.

I’m assuming you would eventually add support for setting a LINK on an icon.

No, afraid not. It’s built on Font Awesome 4, the last completely free version of Font Awesome, So brands are a little behind the times..

The version posted above is just work in progress.

I figured that but thought I would ask as this would be a useful component to have in ones toolbox. I have been using Tabler icons lately as they are up to date and there are a lot of them and free as well.

Hope you keep working on the component as I’d like to purchase it when you are ready.