Pinterest Board and Title Not Displayed in Calendar and Settings Panel

[jamesdunnington]

📜 Description

When scheduling or viewing Pinterest posts in the Postiz calendar panel, the board ID and title fields are frequently not displayed in the UI, even though they are present and used for publishing. This leads to confusion for users who expect to see which board a scheduled Pinterest post will be published to. In some cases, clicking into the settings panel also fails to show the board, despite successful publishing to the correct board on Pinterest.

👟 Reproduction steps

1. Schedule a Pinterest post via the Postiz webapp and select a board and enter a title.
2. Go to the calendar panel and locate the scheduled Pinterest post.
3. Observe that the board and title are not visible in the calendar view.
4. Click into the settings panel for the scheduled post.
5. In some cases, the board and/or title are still missing from the settings panel, even though the post publishes successfully on Pinterest.

👍 Expected behavior

The board ID and title for all scheduled Pinterest posts should always be displayed in the calendar panel and in the settings panel, so users can confirm which board and title will be used when the post is published.

👎 Actual Behavior with Screenshots

Board ID and title are inconsistently shown in the calendar and settings panel for scheduled Pinterest posts. However, when the post is published, the pin always appears on Pinterest under the correct board, indicating the data is present in the backend but not surfaced in the UI.

💻 Operating system

Linux

🤖 Node Version

18.x

📃 Provide any additional context for the Bug.

This appears to be a frontend serialization or display issue, rather than a backend data persistence problem. All published pins have the correct board on Pinterest, but the user experience is affected by the missing UI data. Please ensure the board and title fields in the Pinterest post settings are always surfaced in all relevant UI views.

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find similar issue

Are you willing to submit PR?

No response