On 06/30/11 11:16, Stephan Beal wrote:
What's the proper way for me to fix/work around that (i don't mind rebuilding if needed).
I think this is the same issue as the bug I reported[1] a while ago, except I was using the same version in two locations so it didn't give such error messages.
Frank's workaround should do the trick until it gets fixed. Or go into the older version and de-active all the plugins, then go into the newer version (or vice versa) and re-activate them.
[1] https://sourceforge.net/tracker/?func=detail&aid=3314501&group_id=15...
Cheers, Matthew Brush