Skip to content

Conversation

@ezio416
Copy link

@ezio416 ezio416 commented Jul 9, 2025

No description provided.

@codecat
Copy link
Member

codecat commented Jul 10, 2025

What's the motivation behind the export? Ah, I see this fixes #34.

I also think the error needs to be more explained, "permissions" isn't very clear by itself. This information is already available on the website too, so I'd rather just somehow link to that instead of inviting people to discord.

Maybe you want to make a separate PR for these two things? It's better to keep them apart instead of mixing things up.

@ezio416
Copy link
Author

ezio416 commented Jul 11, 2025

Ok, I added a button that shows up on the plugin page when it fails to install that will take the user to the troubleshooting page and I will move the export to another PR

@ezio416 ezio416 changed the title verify plugin installations and add uninstall export verify plugin installations Jul 11, 2025
@codecat
Copy link
Member

codecat commented Jul 11, 2025

Thanks! Hmm, just showing a button might not be the best UX. Perhaps we should make this a modal dialog instead?

We may also want to have some different error handling: a file being 0 bytes is probably not the only failure state that exists. Maybe the engine should throw a script exception if Meta::LoadPlugin fails, and then we handle that and display that error specifically more prominently.

@ezio416
Copy link
Author

ezio416 commented Jul 11, 2025

It might not be the only error but it's certainly the most common that we have to help people troubleshoot in the discord server frequently. A file size of 0 also includes a missing file.

As for a dialog, I'm not sure of a good way to do that.

@ezio416
Copy link
Author

ezio416 commented Aug 14, 2025

bump, though I haven't given much thought to a dialog since pushing this

@codecat
Copy link
Member

codecat commented Aug 16, 2025

This is less important as the permissions thing should be mostly solved in coming updates. Without a dialog or anything more specific I don't think I am ready to merge this as-is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants