ACF Format_number integrated in bricks?

Feature Requests / Improvements
1

Hi,
I have a terrible problem with the acf format number… I can’t format my acf numbers.
for me who is not a big fan of code, it’s the descent into hell of codes and snippets
to understand,
I put you an image of what I could do in a few clicks with jetengine concerning the formatting of numbers

image
image373×854 26.1 KB

it’s simple, fast, easy, almost natural
now that i have acf pro 6.1.3 and chatgpt… i asked for help and he tried but it doesn’t work…

add_filter(‘acf/format_value/name=property_price’, ‘fix_number’, 20, 3);
function fix_number($value, $post_id, $field) {
if(empty($value)){
return ‘please contact us’;
}
$value = ‘$’ . number_format((float) $value, 2, ‘,’, ‘,’);
return $value;
}

I hope bricks will give an appropriate answer and a real alternative to this very intimidating problem of not being able to format acf numbers directly with the interface and display fallback messages if empty value.
and welcome users like me who are trying to leave solutions like jetengine behind. for performance and simplicity reasons.

I don’t know for how many days or months I’m going to have to adapt to this painful return to codes that don’t work. and even if it does, it doesn’t reassure me, it’s still diy/troubleshooting for normal users like me.

Thanks for reading

2

The code looks correct. How did you use it? Are you using a child theme and added it to its functions.php file? Or are you using some kind of code snippet plugin?

3

image
image1078×713 26.8 KB

I use a snippet plugin as is the standard and advised method and practice these days.

but ACF number fields doesn’t seem to want to listen or cooperate with bricks
Can you visually confirm that it works and show the code? in snippet please

in any case if it doesn’t work I will have to continue with jetengine while waiting for a response from bricks for number format support and fallback for dynamic data

4

The snippet is active (I can’t see that on your screenshot) and property_price is the name of your custom field? Works fine for me with the exact same snippet. See screencast.

5

THANKS to @aslotta
the code works well I was able to test in another clean installation
it seems that jetengine and acf installed in the same instance do not like each other too much…
especially when I redid exactly the same fields and the data is magically copied from jet to acf,
so bricks had a hard time understanding who does what

I hope that the demonstration of this short misadventure will initiate (hopefully) another logic and alternative to make things less dependent on plugins, snippets or codes to paste and not remain at the mercy of elements not controlled by bricks :slight_smile: