stuffdone posted at 12:28PM Thu, 22 November 2018 - #4340450

**I have found a solution **that works for me on all this content management issue.

I uninstalled the database entirely. Don't miss it.

and...

1. never use installers, I use manual install only.
2. set up separate content folder on a different drive ( in my case I have SSD for C: and it is space limited )
3. add this as a base directory under content pane.
4. change the folder names in un-zipped content to names I choose and were I want it to reside, eliminating vanity folder names.
5. copy those assets to the active content directory.

Other than the necessity of dismissing the start up warning from DS that it cannot find a database, I just get to work.

There are three benefits to this scheme.

1. I can organize and categorize as I see fit to suit my needs so I can find stuff in folders that make sense to me.
2. I can easily keep a backup of all assets for easy reinstall should it become necessary simply by re-adding as a base directory.
3. Since I have two other machines on network for rendering, I just map the drive with the assets to those machines add those assets to content pane on the main machine.
   This means all machines when loading a scene to render find all the necessary assets...no missing file issues.

And this is how you break content so if you have an issue, support cannot solve your issue until you install it properly. Don't do this ever.

Again, if you break your content doing something like this, you are on your own support-wise.