1 hour ago1 hr A few days ago, I migrated most of my plugins from "legacy" PG3 to the EISY Plugins. Most worked well with a couple requiring extra steps to get working. Since they were now working in the new EISY plugin, I chose to delete from PG3. Soon thereafter, all of the nodes associated with the various plugins were gone. Ultimately, I was able to restore a recent backup and the PG3 was repopulated with the configuration prior to migration, and all the programs and scenes containing the plugin nodes were restored. Has anyone else experienced this problem? Was this problem associated with my decision to delete the migrated plugins from PG3? Has anyone else deleted migrated plugins from PG3? Other thoughts?
21 minutes ago21 min 1 hour ago, oberkc said:A few days ago, I migrated most of my plugins from "legacy" PG3 to the EISY Plugins. Most worked well with a couple requiring extra steps to get working. Since they were now working in the new EISY plugin, I chose to delete from PG3. Soon thereafter, all of the nodes associated with the various plugins were gone. Ultimately, I was able to restore a recent backup and the PG3 was repopulated with the configuration prior to migration, and all the programs and scenes containing the plugin nodes were restored.Has anyone else experienced this problem? Was this problem associated with my decision to delete the migrated plugins from PG3? Has anyone else deleted migrated plugins from PG3? Other thoughts?Same thing happened here. I have since deleted the eisy-ui plug-ins and re-installed them back in PG3x. Of course all programs involved with these devices had to be updated (with fake edits) and re-saved to make them function again. Edited 19 minutes ago19 min by larryllix
Create an account or sign in to comment