Skip to main content
A
ariellea6803
March 15, 2023
Question

Plug-In functions not available error

  • March 15, 2023
  • 7 replies
  • 0 views

Summary:

I am running into an error in a lower environment when trying to use validateemailaddress from People Functions plug-in and getcontentbyattribute from Content Tools plug-in. Both functions were working a few days ago and are currently working in the higher environment.

Input: a!validateEmailAddress("test@email.com") validateEmailAddress("test@email.com") 

Output: "Expression evaluation error at function a!validateEmailAddress: The function a!validateEmailAddress is unavailable." ***Same error for getcontentbyattribute "Expression evaluation error at function 'validateEmailAddress': The function 'validateemailaddress' is unavailable." 

Steps Already Taken

1. Update People Functions plug-in in the lower environment

2. Update Content Tools plug-in in the lower environment

3. Use different casing on the function: validateEmailAddress() & validateemailaddress()

4. ADDED: Use prefix on the function: a!validatemailaddress()

Any ideas?

7 replies

mikes0011
mikes0011
Brainy
March 15, 2023
a!validateEmailAddress(

this isn't actually the plug-in function name.  it's just "validateEmailAddress()", no "a!".  I get the same error when I try to run it with the (incorrect) "a!" prefix; but when I remove this, it works fine.

Generally (and maybe always, but don't quote me), plug-in functions don't have the "a!" prefix.

A
ariellea6803Author
March 15, 2023

My mistake, was just trying out different inputs. It also does not work for me without the a! as pictured below:

mikes0011
mikes0011
Brainy
March 15, 2023

Can you confirm that the environment in question definitely has the most recent version of the People Functions plug-in installed?  This function is relatively new to People Functions, so if the version is out-of-date even by a little, it might not actually have it.

Note that I'm not sure why/how that would explain an apparent regression in your case, but i'd at least double check that first.  I have 1.10 (which itself is slightly out-of-date) but is recent enough to have the function - i'm not sure exactly which version it was added in, without checking.

Terms & ConditionsAccessibility statement