Token %listing% is not displayed correctly in title

[tschianlu]

Dear Support Team,

I would like to submit a bug report regarding an issue I have encountered in your product. For the past few days, I have been unable to correctly execute the option in the settings labeled “Listings > Title (optional) > %Listing%”. After saving, the title only displays “%listing%” instead of the category. I have been unable to find any setting to resolve this problem.

1. Navigate to the HivePress settings.
2. Select the “Listings” option.
3. Choose the “Title (optional)” option.
4. Enter “%Listing%” into the corresponding field.
5. Click on “Save”.
6. Check the title of an existing list item.

Expected behavior:
The title of the list item should include the corresponding category, based on the “%Listing%” option in the settings.

Actual behavior:
The title of the list item displays only “%listing%” instead of correctly inserting the category.

I hope that these details will assist you in identifying and resolving the bug. If any other users have encountered the same issue and have potentially found a solution, I would appreciate it if they could share their experiences.

Thank you in advance for your assistance in addressing this problem.

Best regards,
Gianluca

[andrii]

Hi,

This is an object token, so you need to specify it differently. If you need a category name, please specify it as %listing.categories%.

​I hope this is helpful to you.

[tschianlu]

Great, thank you very much for the hint.
However, it seems that the instruction in the InfoBox is not correct.

[ihor]

This may be confusing because the token itself also requires the field name after a dot, we’ll try to make it more clear that it’s an object-like token. Please let me know if adding the field name worked for you, for example:

%listing.attribute_name_here%

[tschianlu]

@andrii

categories

What about the requests? Same problem! Nowhere is there an adequate listing of the tokens!
Only the token “%request%” is unusable.

[andrii]

Hi,

We plan to add the display of all tokens for each email event in the next updates. You need to use a request token, just like with a listing.