The VirtualNamespace primitive isn't accessible on production / beta because the restrictions files there don't have a line like:
call VirtualNamespace allow
There are several solutions that spring immediately to mind.
1) Since this syntax is becoming obsolete with the advent of security layers, we could perhaps disable checking of function restrictions. This would be easy to implement and take little effort.
2) We could have the next update add the VirtualNamespace calls to the restrictions file. This will not be trivial to add, but is the most backward compatible way.
The VirtualNamespace primitive isn't accessible on production / beta because the restrictions files there don't have a line like:
call VirtualNamespace allow
There are several solutions that spring immediately to mind.
1) Since this syntax is becoming obsolete with the advent of security layers, we could perhaps disable checking of function restrictions. This would be easy to implement and take little effort.
2) We could have the next update add the VirtualNamespace calls to the restrictions file. This will not be trivial to add, but is the most backward compatible way.