Shapediver uploading failed - Plug in Aggregations by KADAK

Does anybody have an idea what is this plug in that failing the upload?

Plugins sometimes make use of non-standard behaviours, such as including invisible components which stay in your document even if you have deleted all visible components belonging to it.

It often works to copy and paste the visible components of your definition to a new one and save it as a new file. If the problem persists, here is a definition with a couple of handy scripts: one that lists the components of your definition along with the plugins they belong to, and a second which allows you to specify the name of a plugin and click on a button to delete all components that belong to it.

Let me know if that helps.

230928_DeletePluginComponents.gh (7.3 KB)

Thanks for the quick response.

I tried to copy and paste it to a new document - but it didn’t work out
I also tried both (SUPER) handy scripts - but didn’t find any of the problematic scripts,

What else can I try?

Please save a minimal file as .ghx and post it here so I can review its contents.

Uploading 2 files
And crossing my fingers.

Thank you so much
Shapediver Upload Prep1_F.ghx (1.1 MB)
Shapediver Upload Prep1_A.ghx (1.3 MB)

Hey,
is there a newer version?
it seems like doesn’t work now

The scripts show the “OLD” label because they were created in Rhino 7 and you are likely attempting to open them with Rhino 8. After some tests, I could run the scripts without issues in Rhino 8, despite the OLD labels, could you confirm whether they are working on your side as well?
Ideally, one would update the scripts to make use of the new Rhino 8 script component. I made a brief attempt just now and it seems that some changes are needed. I will investigate whenever possible and post update versions of those scripts. In the meanwhile, the old ones should still work as far as I can see.

i see.
so regardless the version thing for some reason it wont delete that Aggregations plug in and still cannot upload the definitions - is there any other way to trace the problematic component?

Thanks

Could you share a minimal definition (as a .ghx) which you cannot upload? Maybe just one or two regular components. I would then try to adapt the script to make it work for your case.