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

unknown modifier 'sprintf' #739

Open
bwurst opened this issue Feb 26, 2025 · 7 comments
Open

unknown modifier 'sprintf' #739

bwurst opened this issue Feb 26, 2025 · 7 comments

Comments

@bwurst
Copy link

bwurst commented Feb 26, 2025

I have installed a new CiviCRM with CiviSEPA. After applying the patch from pull request #736 I could set up a sepa mandate.

When I click on "Close and Send" in CiviSEPA dashboard, another smarty error occures: Syntax error in template "file:CRM/Sepa/Page/CloseGroup.tpl" on line 22 "

{$group_text|sprintf:$txgroup.reference}

" unknown modifier 'sprintf'

I modified the specified line to simply replace "sprintf" with "string_format" to fix this issue.
(But there seems to be a bunch of smarty5 errors left...)

@Fabian-SYSTOPIA
Copy link

Could you sepcify the CiviSepa and CiviCRM versions you are using?

@bwurst
Copy link
Author

bwurst commented Feb 26, 2025

Installed a few days ago, CiviCRM 5.82.0 and CiviSEPA 1.11.0

(When I look at the extension details, CiviSEPA is not marked as compatible with 5.82 but there was no complaint when I set thing up. Does CiviCRM no check version compatibility?)

@Fabian-SYSTOPIA
Copy link

Could you try if a more recent pre-release fixes your problem such as 1.12beta1?

If not, maybe @bjendres could have a look?

@bjendres
Copy link
Member

bjendres commented Feb 26, 2025

@bwurst Thanks for reporting!

Just to be sure: can you confirm that changing

<p>{$group_text|sprintf:$txgroup.reference}</p>

to

<p>{$group_text|string_format:$txgroup.reference}</p>

in this line fixes it for you?

@bjendres
Copy link
Member

(updated last comment)

@bwurst
Copy link
Author

bwurst commented Feb 26, 2025

Yes, changing the given line does fix this, as I stated directly in the bug report. :)

Upgrading to beta does not help.

@bjendres
Copy link
Member

Yes, changing the given line does fix this, as I stated directly in the bug report. :)

Just wanted to make sure I'm not forgetting anything.

Should be released with next 1.12 (#740) and next 1.13 (#741)

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

No branches or pull requests

3 participants