Prevent markdown rendering in post title and topic fields #51

New Issue
Closed
opened 2026-06-22 17:06:37 +02:00 by retoor · 4 comments
retoor commented 2026-06-22 17:06:37 +02:00
Owner
Copy Link

Summary

When creating a post, the title and topic fields currently accept and render markdown (e.g., bold via asterisks). This should be disallowed to maintain a consistent visual style across all posts.

Steps to Reproduce

  1. Create a new post.
  2. In the title field, enter text containing markdown syntax, such as **bold text**.
  3. In the topic field, enter similar markdown syntax.
  4. Submit the post.
  5. View the post; observe that the markdown is rendered (e.g., bold text appears bold).

Expected Behaviour

Markdown syntax in the title and topic fields should not be rendered. The fields should display plain text only, ensuring a uniform appearance for all posts.

Actual Behaviour

Markdown syntax in the title and topic fields is rendered (e.g., **bold text** appears as bold text), breaking the intended consistent style.

Environment

Not provided.

Reported by Lensflare via DevPlace.

## Summary When creating a post, the title and topic fields currently accept and render markdown (e.g., bold via asterisks). This should be disallowed to maintain a consistent visual style across all posts. ## Steps to Reproduce 1. Create a new post. 2. In the title field, enter text containing markdown syntax, such as `**bold text**`. 3. In the topic field, enter similar markdown syntax. 4. Submit the post. 5. View the post; observe that the markdown is rendered (e.g., bold text appears bold). ## Expected Behaviour Markdown syntax in the title and topic fields should not be rendered. The fields should display plain text only, ensuring a uniform appearance for all posts. ## Actual Behaviour Markdown syntax in the title and topic fields is rendered (e.g., `**bold text**` appears as bold text), breaking the intended consistent style. ## Environment Not provided. --- *Reported by **Lensflare** via DevPlace.*
retoor commented 2026-06-28 00:29:56 +02:00
Author
Owner
Copy Link

@Lensflare this is all allowed by me. The only thing i will change is strip it from the bredcrumbs

Posted by retoor via DevPlace.

@Lensflare this is all allowed by me. The only thing i will change is strip it from the bredcrumbs --- *Posted by **retoor** via DevPlace.*
retoor commented 2026-06-28 13:11:12 +02:00
Author
Owner
Copy Link

So, i did this only for breadcrumbs.

Posted by retoor via DevPlace.

So, i did this only for breadcrumbs. --- *Posted by **retoor** via DevPlace.*
retoor commented 2026-06-28 13:44:17 +02:00
Author
Owner
Copy Link

why do you want to allow it for titles? it's inconsistent.

Posted by Lensflare via DevPlace.

why do you want to allow it for titles? it's inconsistent. --- *Posted by **Lensflare** via DevPlace.*
retoor commented 2026-06-28 13:56:03 +02:00
Author
Owner
Copy Link

I don`t see it happnening @Lensflare

Posted by retoor via DevPlace.

I don`t see it happnening @Lensflare --- *Posted by **retoor** via DevPlace.*
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: retoor/devplacepy#51
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?