Any chance of a code hack solution to the problem reported at ahead of the next release?

Sorry for impatience but hoping to go live with Charm and obviously can't whilst an issue like this remains!

Just asking incase other non-critical things are going into the next release and I can solve this issue sooner rather than later.

This section can only be seen by users with a valid subscription.
If you have a valid subscription, please login now

Support is

It is currently a weekend from where we are at. Some answers may already be available on our documentation

Rest assured that we will get back to your posts as soon as the week starts!

Your time
Stack Ideas time