Working Safely with a price TV and PHx Modifiers

It is common to see a custom TV such as render correctly while a PHx-style modifier on another field seems to fail. That usually points to parser context or modifier compatibility, not to the TV itself.

The symptom

In the source case, worked, but expressions like returned nothing in the same template area.

What to check

• whether PHx is enabled and loaded correctly
• whether the tag is being parsed in a context that allows modifiers
• whether another plugin changes parser behavior early in the request
• whether the project mixes old PHx patterns with newer parser assumptions

A safer approach

For business-critical output such as prices, do not rely on parser tricks alone. Normalize or transform the value in a snippet, controller, or prepare method so the template receives exactly the string you want to print.

<?php
$price = trim($modx->documentObject['price'] ?? '');
$title = mb_strtolower($modx->documentObject['pagetitle'] ?? '');
?>

Why this matters

PHx can still be useful in legacy projects, but the more essential the value is, the safer it is to make the transformation explicit in code rather than depend on parser edge cases.