• Home
  • Categories
  • Recent
  • Popular
  • Top
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
v3.5.2 Latest
Buy Hosting

Using Auto 301 Redirect after Renaming/ Updating the Existing Topic to New

Scheduled Pinned Locked Moved Feature Requests
4 Posts 3 Posters 2.0k Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    ankitpr89
    wrote on last edited by ankitpr89
    #1

    Let me explain the case:
    User already created a topic and the moderator/ admin updates it; then the topic url is updated to new one.
    And when we go to old url topic, it lands in 404 error, but, ideally old url should automatically get redirected to new url.
    Need feedback on this...

    A 1 Reply Last reply
    0
  • A Offline
    A Offline
    ankitpr89
    replied to ankitpr89 on last edited by
    #2

    Well due to this issue, when first url is not redirected, it gets indexed in search engine and after that old one results on 404 error page [ that is quite bad for any user ].

    V 1 Reply Last reply
    0
  • V Offline
    V Offline
    vatsal
    replied to ankitpr89 on last edited by
    #3

    @ankitpr89 I understand this is a big issue for our forum but I am not sure if this issue is specific to us, lets first try resolve this by ourselves and then will take some help from NodeBB guys.

    1 Reply Last reply
    0
  • julianJ Offline
    julianJ Offline
    julian GNU/Linux
    wrote on last edited by
    #4

    This is related to an issue resolved earlier.

    We found that if a topic's posts contained images pointing to a relative path (e.g. ![test](1.jpg), NodeBB would attempt to load them, causing them to load the entire topic again (since the url is site.com/topic/123/1.jpg).

    To combat this, @baris restricted the URL so that the slug must be correct, otherwise the user is sent to 404.

    For lack of a better solution, this was the approach we took, so this seems to be the reason why you're running into this issue now.

    1 Reply Last reply
    0

Copyright © 2023 NodeBB | Contributors
  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Home
  • Categories
  • Recent
  • Popular
  • Top
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development