Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add warning about APIv4 switch #49

Merged
merged 2 commits into from
Oct 11, 2024
Merged

Add warning about APIv4 switch #49

merged 2 commits into from
Oct 11, 2024

Conversation

bjendres
Copy link
Member

No description provided.

@bjendres bjendres merged commit 8de36cb into master Oct 11, 2024
9 checks passed
public function upgrade_5002() {
CRM_Core_Session::setStatus(
E::ts('MoreGreetings has switched to APIv4, which means that some tokens might not work any more.') . '<br/><br/>' .
E::ts('An example would be the defunct <code>$individual_prefix</code> token, which can be substituted by the <code>prefix_id:label</code>') . '<br/><br/>'.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would be contact.individual_prefix token (without the $), no …?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't configured this in a while, but I think its SMARTY tokens, not regular ones - see the examples

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're probably right. We really should stop calling Smarty variables Tokens, this has always been so confusing …

@bjendres
Copy link
Member Author

this is moot anyway, since the suggested contact.prefix_id:label token cannot be accessed anyway, since smarty cannot process this format.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants