You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I created a post with the title "meta" and published it to a blog. It redirects to xxxxx.com/blogname/meta and says
This page is missing.
Are you sure it was ever here?
But the post is displayed properly in the blog's post list. Then I tried pinning it. It was pinned successfully, only that the link directs me to the same missing page. I tried to unpin the page through xxxxx.com/blogname/meta/unpin. This attempt failed also. Fortunately, I was able to use the link xxxxx.com/blogname/meta/edit and editted the post's metadata, changing its slug to something else.
Steps to reproduce (if necessary)
Steps to reproduce the behavior:
Go to 'New Post'
Type # meta
Click on 'Publish'
Expected behavior
Not sure. I think either it's a bug, or the user is not supposed to create a post named "meta".
Application configuration
Single mode or Multi-user mode? Multi-user mode
Database? sqlite
Open registration? no
Federation enabled? yes
Version or last commit: 0.11.2
The text was updated successfully, but these errors were encountered:
I was able to replicate this too. My understanding is that /meta is reserved for editing the metadata of posts. So if you were editing the metadata on a post, the route on your instance would be example.com/post/edit/meta. This is why I think it's pulling up an error - so more in line with the "user is not supposed to create a post named 'meta'" explanation.
I think one solution would be moving these under the /d/ path, just like we already do for single-user instances. Ideally we'd also make it consistent with our collection editing paths -- so /d/{action}/edit/meta instead of /{action}/meta.
Describe the bug
I created a post with the title "meta" and published it to a blog. It redirects to
xxxxx.com/blogname/meta
and saysBut the post is displayed properly in the blog's post list. Then I tried pinning it. It was pinned successfully, only that the link directs me to the same missing page. I tried to unpin the page through
xxxxx.com/blogname/meta/unpin
. This attempt failed also. Fortunately, I was able to use the linkxxxxx.com/blogname/meta/edit
and editted the post's metadata, changing its slug to something else.Steps to reproduce (if necessary)
Steps to reproduce the behavior:
# meta
Expected behavior
Not sure. I think either it's a bug, or the user is not supposed to create a post named "meta".
Application configuration
Version or last commit: 0.11.2
The text was updated successfully, but these errors were encountered: