Use the Outliner.
You can then expanded the 'tree' and select the nested Container, and double-click it in the Outliner to edit it that way.

It's not published, buy you could try contacting its author and offer to buy it ?
See the first post in the thread...

So at the moment you have SketchUcation toolset v5.0.3 OK, the SCF licensing OK and most of Fredo's extensions OK.
BUT Fredo'sTools must be disabled for this to get everything else working.
So the issue lies with FredoTools.
Have you tried reinstalling FredoTools from a newly downloaded RBZ ?

@slbaumgartner

I meant the SUp version.
I suspect that most users will have newer SUp versions ?
The reason I cited @fredo6 is that he is instrumental in the licensing coding, and I am inviting his input...

The licensing code hasn't changed in several versions but that seems to now be causing at issue - way back to the lat v4 ?? @fredo6 ??
Other MAC users haven't reported anything... Are you still running v2019

So to clarify. Please confirm...
You now have no SketchUcation.rb or SketchUcation subfolder in your Plugins folder having temporarily moved them.
You have temporarily moved the SCFLicense subfolder and SCFLicense.rb [usually in your SketchUcation folder] back into your Plugins folder.
You have restarted SketchUp.
Does the licensing set up load ?
It seems not !
If you add the SketchUcation subfolder and its RB file back into Plugins, AND temporarily remove the SCFLicense.rb and subfolder from the SketchUcation subfolder, AND also remove those you moved into Plugins: after a restart of SketchUp does SketchUcation toolbar/submenu load OK ? If so the issue appears to lie with our licensing set up... [@fredo6 ?]

Incidentally, our test is...
[Assume a valid path to load the RB files]

require('zlib') unless defined?(Zlib)
require('zip')  unless defined?(Zip)

SketchUcation tools only loads the ZIP gem stuff if it hasn't been already loaded [required].
I suggest you adjust your code to do the same.
It doesn't break things. it just warns about it already being installed ?

Compatible with v2017 and newer [better].
You can try an older version, but no guarantees...

@jackybe67

This has been reported before.
It's probably because you have one of Chuck Vali's extensions loading.
He omitted giving it a Version [check in your Extension Manager for that omission...],.
This means that when we try to find its version so we look for updates it trips us up with a fault.
Our v5.0.3 sidesteps this very problem [amongst others] and should be published very soon...

@Macho3001
The > on the right end of the extension details, if you click it it expands the entry and shows the Version, or in the case of Instant Architecture == nothing !
The 'unsigned' message appears if an extension hasn't been processed by Trimble/SketchUp, if the extensions is older it's probably not been updated in the last few years, that's OK if it's from a trusted source and your Extension Manager's > Loading Policy is set to Unrestricted, otherwise it's loading is blocked.

I'm preparing an update to the SketchUcation tools to robustly trap for this kind of unexpected problem from poorly structure code by others...

@Macho3001

I'll look into it further...

Meanwhile:
It looks like you have an Extension loaded which doesn't report a Version in the Extension Manager - if it returns '' it ought to be OK, but with a nil it cause the trip hazard.
A known cause is some of Chuck Vali's stuff.
But the nil return was trapped for this very reason.

Can you check your Extensions and unload any without a Version set, and see it SketchUcation then loads on a restart. And let me know what Extension[s] are the culprits...

@gullfo
So this file/folder copying was an error with the v2026 extension-migration tool by SketchUp, not copying all DM's files over and causing an error ??
It has nothing to do with the SketchUcation extension - except in so far that it breaks it and stops it loading !!

@Edson

Can you please cause the error dialog again, this time click the bottom-left button to 'Copy All Errors' to your clipboard.
Then paste the full error report into a reply here.
It should tell us if DM's code is somehow messing up our files' loading...

There is no calls to a "DMLanguageHandler" directly associated with SketchUcation, so that's a mystery.
I'm wondering if it's part of the compiled @fredo6 licensing files ?
Or something else might be causing an issue which then clashes ?
I fact I can find nothing in any Plugins I use needing this [PC].
You are on a MAC running which SUp version ?
Under investigation....

It works just fine in v2026.
I just tried it, have you ?
The PluginStore listing might say compatibility up to v2025 but that's because I haven't updated the page yet. [EDIT: just added it]
Until a few days ago there was no v2026 or v2025 checkbox on the PluginStore !

@i5963c
The reason the toolbar appears is, because there are updates available - hence the red marker on the first button - not present otherwise.
If you open the ExtensionStore dialog and choose to install the updates, then close the toolbar, when you restart SketchUp the toolbar stays off, until you next activate it.
If you don't want the updates simply dock the toolbar in the side bar with others, it's unobtrusive...

v5.0.2 should be out very soon...

@gullfo

I was think of that...
Since very few have reported an issue it must be a rare RB file you have that's causing this issue.
BUT can we get v5.0.2 out first.
Then I'll PM you something later this week.
Thanks for your help.

The other report was from a French member, however, worries about oddly encoded Windows user-names in file paths have been without foundation, and we force_encode them to UTF-8 text just in case. User-names that do not follow the Windows recommendations - e.g. with accented characters - might occasionally cause issues, but they are very rare.
The various extensions' RB files themselves are also get their lines of text force_encoded as UTF-8 text in case they are improperly encoded too [but again that's rare].
However, in the cases of these rare reported error messages, a line from the RB file that's being read in fails to force_encode because it's not encoded at all in any known format ! This is very weird. To avoid the error our code now uses a line.encoding_valid? test, and if that is false it skips it rather than trying to encode it - because force_encoding only works if the text is already encoded in some other format - so there was an error.