Moving some rules over to the new global variable connectors and experienced an error.
I don't know exactly what I did, so this might be tough. Best I have is I was creating several new global variables. And I think I started typing a new one before the last one had finished updating. I had managed to type in a "V" before the page switched back to the main global variable page. I went back in to create a new variable, the "V" was still there, and I finished creating it. No issues. After finishing creating the variables, I started creating connectors. When I hit this one "VolumeTTS Bathroom Night" (which may or may not have been the one I initially incorrectly entered as just "V") the error occurred.
I'm on a slightly older version, but I don't see that the new versions corrected this error. I am on 2.1.4.126
OR, just thought of another thing I did that might have caused it:
I started creating a global variable, lets say it was "Volume TTS Bathroom Night", then the page updated to choosing the type. I noticed it wasn't the name I wanted, and I deleted the space between "Volume" and "TTS" and continued on. It appeared OK, but maybe it didn't like that it had already moved on once with the wrong name, then I went back and changed it.
I'd test if that causes it, but I'll have to restore a backup as I can't see how to get past the "Unexpected Error" into the GV page.
Thanks for the quick response! I had just gotten started, so no big deal. Will restore from backup and apply the latest hotfixes. And I won't do that again!
@bravenel
I'm back up and running again! Thank you.
But, I wanted to point this out. I don't know if it is an issue or not (I'm afraid to try it)...
But it generally seems you have to go through the steps and finish completing a global variable in order - name, type, then initial value. All 3 need to be completed. However, there is a done button as well:
It may be completely fine to hit the done button... like I said, just don't want to mess anything up by trying. Sorry for wasting your time if it is there on purpose!
Thanks for pointing it out. These are the subtle nuances of the UI that need a little love. Throughout the UI I'm trying to not present inappropriate choices, depending on context. That's what I meant above about not leaving open the possibility of breaking it. It's all similar, UI options that are present (and available to use) when they shouldn't be.
But I've got my new globals in, and the connectors.
One doesn't have the carrot in the "in use by" field, all the others do. I know of nothing this time that went wrong when I set them up. Everything went smoothly.
Not sure if the carrot is supposed to be there or not, but the difference just stood out. I'm going to assume the one without it is the "bad" one (if it is bad at all) and delete then recreate it.
Interesting. I've seen that also, and I don't know why it misses sometimes. I'd like to know, but I don't yet.
If it doesn't have the asterisk in the In Use column, it will not work. And you already found the fix: remove the connector and then create a new connector.
I don't know if this well help you in your search, but it has happened to me a couple more times tonight. Deleting and recreating the connector doesn't always work. However, refreshing the page then readding the connector seems to get it to stick.
Also very minor UI issue - sorting in the list of variable math:
