Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • pleroma pleroma
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 646
    • Issues 646
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 89
    • Merge requests 89
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PleromaPleroma
  • pleromapleroma
  • Issues
  • #2376
Closed
Open
Issue created Dec 22, 2020 by absturztaube@absturztaube

POST /api/v1/statuses strips away hashtag when using markdown

Environment

  • Installation type (OTP or From Source): Source
  • Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): 6bb4f4e1
  • Elixir version (elixir -v for from source installations, N/A for OTP): Elixir 1.10.4 (compiled with Erlang/OTP 22)
  • Operating system: debian 10
  • PostgreSQL version (psql -V): 11.7-3

Bug description

Screenshot_from_2020-12-22_09-34-13

Posting that with Content Type Markdown results into BE striping away all the content of the Post.
Screenshot_from_2020-12-22_09-34-29

Doesn't seem like it is FE since the POST request does contain the text as intended but returns an empty post.

Request Payload POST /api/v1/statuses

-----------------------------141161563019050552811390399381
Content-Disposition: form-data; name="status"

#ThisIsATestPleaseIgnore
-----------------------------141161563019050552811390399381
Content-Disposition: form-data; name="source"

Pleroma FE
-----------------------------141161563019050552811390399381
Content-Disposition: form-data; name="visibility"

public
-----------------------------141161563019050552811390399381
Content-Disposition: form-data; name="content_type"

text/markdown
-----------------------------141161563019050552811390399381--

Response (removed account block)

{
	"account": {
		...
	},
	"application": {
		"name": "Web",
		"website": null
	},
	"bookmarked": false,
	"card": null,
	"content": "<p></p>",
	"created_at": "2020-12-22T08:37:30.000Z",
	"emojis": [],
	"favourited": false,
	"favourites_count": 0,
	"id": "A2SCMwpaDHBWy0RckS",
	"in_reply_to_account_id": null,
	"in_reply_to_id": null,
	"language": null,
	"media_attachments": [],
	"mentions": [],
	"muted": false,
	"pinned": false,
	"pleroma": {
		"content": {
			"text/plain": ""
		},
		"conversation_id": 33335700,
		"direct_conversation_id": null,
		"emoji_reactions": [],
		"expires_at": null,
		"in_reply_to_account_acct": null,
		"local": true,
		"parent_visible": false,
		"spoiler_text": {
			"text/plain": ""
		},
		"thread_muted": false
	},
	"poll": null,
	"reblog": null,
	"reblogged": false,
	"reblogs_count": 0,
	"replies_count": 0,
	"sensitive": false,
	"spoiler_text": "",
	"tags": [
		{
			"name": "thisisatestpleaseignore",
			"url": "/tag/thisisatestpleaseignore"
		}
	],
	"text": null,
	"uri": "https://fedi.absturztau.be/objects/c41bdc42-ab54-43d0-91f9-1341290f2d4e",
	"url": "https://fedi.absturztau.be/notice/A2SCMwpaDHBWy0RckS",
	"visibility": "public"
}

interestingly enough, BE seems to add the tag to the post tho, just removes it from the content / text

Assignee
Assign to
Time tracking