Steps to reproduce the issue
Field Creation: Create a Custom Field (e.g., ID 4) with a value (e.g., "1.200").

Article Metadata: Go to an article and navigate to the "Publishing" or "Metadata" tab.

Insertion: In the Meta Description or Meta Title field, insert the field placeholder: Price is {field 4},- kr.

Front-end Check: Save the article and view the page source (Ctrl+U) on the front-end.

Expected result
The metadata in the section should be parsed by the Content Plugins, rendering the output as:

Actual result
The metadata remains unparsed, outputting the raw shortcode string to the browser:

System information (as much as possible)
Joomla Version: 6.0.2

PHP Version: 8.4.16

Database: 10.6.23-MariaDB-ubu2204

Relevant Settings: Content - Fields plugin is enabled.

Additional comments
This limitation violates the "Single Source of Truth" principle. If an administrator uses Custom Fields to manage dynamic data (like prices or dates), they are currently forced to manually hardcode the same values in the Metadata fields to avoid SEO failure.

If Custom Fields are not parsed in Metadata, the feature becomes redundant for commercial applications where SEO integrity is critical. The metadata rendering pipeline should pass through the onContentPrepare trigger (or a similar mechanism) to ensure consistency across the entire document, including the . This is a high-impact issue for data management integrity in Joomla 6.

Regards,
John