I think these are overkill, and I may very well add them back later after things calm down and everything is stable with no problems anywhere with anyone. However, for now, this should establish a benchmark.

You might want to mention that if someone has their custom columns organized in Job Spy, they need to change it to show all columns as editable before creating a new library.

Apparently if you leave the restrictions on some columns, it causes an error that appears to still allow the library to be built, but if you try to add books they take about 15 seconds a book to add.

When I saw that happening, I aborted the import and lifted the restrictions. Then they came in like normal. Not sure if I created a new library or if I just changed the settings, but if anyone tries to switch libraries or create new libraries where the columns don't match up, then it crashes.

Long story short, when leaving or creating a new library, make sure all the columns are unprotected. Until all the columns are matching.

If you want I can send you the error report if I make a clone without changing the settings. I was thinking if there was a quick way to disable the plug in rather than going through the hassle of changing the features. If there was a quick pause, or disable, or something to put the plugin on hold until the user gets to the place where there won't be problems.

I assume you are talking about the protect GUI tool. I am going to change the protect GUI tool to automatically set all custom columns to "editable" for libraries for which it has not been manually configured before due to inheritance. So, its "inherited" configuration will be ignored.