OK I think I understand the problem with saving, and why it went wrong
- although I may not explain it well.
As a newbie I was attracted to the "live test" shortcode ability of the plugin
Also as a newbie, I need to experiment.
So I created a test shortcode based on the "age" example from the support site.
Here is the seed of the problem.
The age example requires a parameter so I happily test and save what I think works - because indeed in the test page it does.
However, by the time the shortcode name(s) are saved in the database the shortcode with parameter [age birthdate="Mar 20, 2010"] becomes "age birthdate="
I have looked at the database entries and indeed there is an "age" and an "age birthdate="
Of course I tried to delete them from the plugin test page - but no luck.
Perhaps understandably the presence of the 2 similarly named shortcodes may explain why they did not work?
Also, since the plugin source code is encrypted, I have no idea what may be the problem - but it could be an easy fix....?
Hopefully this is somewhat enlightening.