Revigniter v2 "Unable to load the requested stack" error
Posted: Tue Nov 23, 2021 1:13 pm
Hi all,
Revigniter upgrade path - v1.10.3 to 2.3.1
Just tested some more features after doing an upgrade from Revigniter v1 to V2 and I have been unable to load my custom stacks using the rigLoadStack function.
stack location: application/stacks
ERROR received from Revigniter "unable to load requested stack "stack name"" (But stack is in location) (My usage code is "rigLoadStack tStack" and tried rigLoadStack "literal stack name")
Remedies tried: Moved stack to location system/stacks - received ERROR "bad target error" see attached
Tried direct Livecode function "start using stack ("full link to stack in application folder") - THIS WORKS AS EXPECTED
In my log I did get this error "Auth OTP: OTP table missing!". Saying that I don't use the OTP lib and have disabled it in my config file. So not sure if it is relevant.
Would love to know your thoughts if it is a bug or maybe something I missed during the upgrade?
Commenting on the forums so maybe this can help someone else doing the same process.
Maybe my revigniter "rigLoadStack" is grabbing an incorrect path? I have looked at the global gRigA and the path looks good.
Revigniter upgrade path - v1.10.3 to 2.3.1
Just tested some more features after doing an upgrade from Revigniter v1 to V2 and I have been unable to load my custom stacks using the rigLoadStack function.
stack location: application/stacks
ERROR received from Revigniter "unable to load requested stack "stack name"" (But stack is in location) (My usage code is "rigLoadStack tStack" and tried rigLoadStack "literal stack name")
Remedies tried: Moved stack to location system/stacks - received ERROR "bad target error" see attached
Tried direct Livecode function "start using stack ("full link to stack in application folder") - THIS WORKS AS EXPECTED
In my log I did get this error "Auth OTP: OTP table missing!". Saying that I don't use the OTP lib and have disabled it in my config file. So not sure if it is relevant.
Would love to know your thoughts if it is a bug or maybe something I missed during the upgrade?
Commenting on the forums so maybe this can help someone else doing the same process.
Maybe my revigniter "rigLoadStack" is grabbing an incorrect path? I have looked at the global gRigA and the path looks good.