After careful consideration and due to limited usage, we’ve made the decision to discontinue the PaperMC forums. Moving forward, we recommend using Hangar for plugin uploads, and for all other community discussions and support, please join us on Discord.
Is it somehow possible to redirect my old plugin download page which was hosted on forums.velocitypowered.com to the new one hear on paper? Currently if you click the link in google or using a bookmark it just redirects to forums.papermc.io
That does not solve the problem for other users who want to find the content. Also I am not sure on which other sites (wiki and co) I linked my plugins old velocity page.
That does not solve the problem for other users who want to find the content. Also I am not sure on which other sites (wiki and co) I linked my plugins old velocity page.
But you can just create a new one on the papermc.io forums. So, you mean, that the old forum posts are not in the new forum, right?
Or do you mean, that in other wikis there is liked the old post and then you klick it you just come to the forums.papermc.io without the post/article.
Not directly. I reposted my plugin already, but other websites like google and some other forums are still linking to the og plugin page which was deleted. The web standard offers something called a 301 status code, which tells websites like google that the content has moved. Most people are currently unable to find my plugin. It would be a good practise to redirect the old plugin pages to the newly created once. Here is a link to a w3.org article on why not doing this is bad practice.
Not directly. I reposted my plugin already, but other websites like google and some other forums are still linking to the og plugin page which was deleted. The web standard offers something called a 301 status code, which tells websites like google that the content has moved. Most people are currently unable to find my plugin. It would be a good practise to redirect the old plugin pages to the newly created once. Here is a link to a w3.org article on why not doing this is bad practice.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.