Chances are you’re seeing this because you enabled the Parking Lot module but not intending to use it. Disable the module in Module Admin and the message goes away.
That doesn’t make sense. The module is enabled so that it can be used, the message is either a BUG or, there is some setting that is omitted from the default install that it’s expecting. I have this in multiple servers and we are using the feature.
lol for whatever reason i didnt’ see that you had to “tick the box” above the extension number you assign for parking which says “Enable Parking Lot Feature”
i never got around to testing parking lot feature as never use it but i did have to change the extension number and unless you tick this box you well get an error message it makes total sense…but yeh i wish the UI made more sense…
Yes, that checkbox is on. I believe the parking lot won’t work without it and the parking lot does work, I believe its an a bug in the message more so than it not working. After upgrading to the 2.10x branch I have seen that go away.
Sounds like you have not set the Alternate Destination Behavior.
If that’s the case, to the extent it’s a bug, I guess we should probably set it to some default. Problem with that, what default? Better to remind you in such a message so you see you missed something.
I guess we should also complain if we are not when you don’t choose a destination?
Anyhow … check that and for the other people’s sake who chimed in you may want to let them know if that was the case.
Whether or not you set “Return Destination Behavior” to Originator or Alternate Destination, you still have to change the drop down to something other than “== choose one ==” if you are going to enable the parking lot feature. This will remove the bad destination error. Yes, logic would dictate that this should only need to be changed IF Alternate Destination is chosen (ie enabled/activated). But…for the sake of sanity, this should fix it for now.