-
-
Notifications
You must be signed in to change notification settings - Fork 10.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No support for legacy Blogger or WP routes #6055
Comments
The problem seems to be in the tools used to convert from Blogger to Ghost. In theory, if the 'slug' attribute of the post is set correctly in Ghost, then those routes could in theory work without the workaround you have set. (See http://support.ghost.org/post-settings-overview/ for info on how to set the post slug.) IMO, supporting something like legacy blogging routes from other blogging systems in Ghost itself rather than in an import tool quickly gets bloated, due to the many different url styling flavors of the various platforms. I would take this issue up with whatever tool you used to convert from Blogger data to data imported by Ghost. |
These redirects can be done by a proxy in front of ghost, like nginx or haproxy, no need to hack the core. @acburdine You can change the slug, but permalinks are fixed to |
@jgillich yeah I get that, but the permalink structure doesn't seem to be the issue here (at least based on the gist) - also, that's technically configurable in the database settings table iirc I agree that an nginx proxy can also be used, but IMO fixing this issue in the blogger-to-ghost conversion tool (if there is one) is the better way to fix this. |
I realized that it isn't possible to set the '.html' endings for a post slug in the post itself, however, you can change the permalinks setting in the database itself. By default it is set to Also, you still would have to go to each post and shorten the slug, as it appears Blogger's slug max length is shorter than Ghost's. |
@acburdine Agree, the conversion tool is the best place for this type of thing if the core supports it but from your comments it doesn't look like it is supported fully. FYI, the tool I used to do the conversion is https://www.npmjs.com/package/blogger2ghost It was pretty easy and worked well. I don't much like the permalinks setting idea as I don't' really want to keep the year/month/post format going forward, it is ugly and arbitrary. @jgillich I hadn't thought of using my proxy for that purpose, I am self hosting behind nginx so that is a viable option for me, most average folks might find that a bit difficult though. |
Hey @mdausmann, I definitely recommend moving those redirects to nginx - it will be much more performant and that is the expected way to do redirects with Ghost. A few notes on what has been said:
What would be nice is if the tools like blogger 2 ghost generated a set of redirection rules for you to plug directly into nginx/apache. That's something to raise against those individual projects, although I believe @cobbspur has worked on blogger2ghost. TLDR; theres not really anything for Ghost to do here. |
I can convert my blog from blogger with the various tools however one it is imported, I can't find any way to support my legacy URL format. e.g.
http://www.michaeldausmann.com/2014/09/how-to-not-learn-coffee-script-in-90.html
I have deployed a ghost instance with a horrible kluge to hard code my legacy routes but this is hardly a great solution.
https://gist.github.com/mdausmann/02c4993d11a8776f6842
Interested in any suggestions or plans for supporting this. I can help with implementation if a clear approach can be agreed.
The text was updated successfully, but these errors were encountered: