Peter Clough Posted November 20 Posted November 20 Since the update today that highlights questions on custom forms with issues, I am seeing these on every single form field with any conditional terms, including some that are known to be working fine, but also some that I can't really fix even if I wanted to, for example: Warning: Referencing a context variable that does not exist - global['pcfglobals']['PortalType'] It would appear this is being perhaps a little over-zealous in what it is flagging? 1
Matt Parker Posted November 20 Posted November 20 Thanks for posting Peter - I was creating a new capture today and couldn't work out what was wrong! Works fine, I didn't have any warnings, then made a change saved and then the Warning appeared:- Warning: Referencing a context variable that does not exist ....I went back to a previous version and that had warnings on. Searched on the forum and saw your post, so checked some other captures that are working and now see Warnings on those. I'll watch this space.
Steve Giller Posted November 20 Posted November 20 I've reported this internally, this appears to be a false flag which vanishes when you validate the Capture. I've not had chance to investigate this fully, but the developers are aware. 2
Adrian Simpkins Posted November 20 Posted November 20 I raised a Support call earlier for the same issue that I am seeing in our instance - thanks for the update Steve will await more information many thanks Adrian
Berto2002 Posted November 20 Posted November 20 Yes, appears to be a flag which disappears on validation.
Ryan Posted November 21 Posted November 21 This should now be fixed - the global parameters (Portal Type, Source etc) should no longer cause incorrect validation warnings. Thanks, Ryan 1
Adrian Simpkins Posted November 21 Posted November 21 Hi Ryan Still seeing this on our instance where the Yellow marker appears after making no changes to an IC node. I have updated my support call just now to show this Many thanks Adrian
Nanette Posted November 25 Posted November 25 @Adrian Simpkins thanks for confirming that all is working ok. Clearing the cache did the trick!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now