Hey again @RetroMonroe!
Hmm… Did you possibly have multiple variables named the same thing? And are you sure you only did those things?
If the variable you were setting there was for a different Blueprint, you need a better naming scheme. Never, ever, ever let any two variables have the same name unless they’re local or things get confusing.
Now, if the only place a “Control Panel Obj” exists is on this blueprint, there shouldn’t be any reason that removing those should cause an error. But hey, if it’s not working without them, put them back in.
As far as the printstrings, you have to say which one is supposed to say which thing 
they are custom so we don’t know if the 1 or the 2 is the one going off- going to assume only #1 based on context.
So the further matter here is if it IS INDEED ENABLED- what is happening? We need some details. Is it invisible, is it visible but unclickable (if so, show the button code)?
Get back to us with some details and let’s iron this out! 