No worries. Might have been a Medium API glitch, or a sever glitch on my end that resolved it self. If it happens again, feel free to report it.
Thanks for the report. I'm able to see the article on Scribe. Are you still seeing a 404?
Thanks, and I agree. That would be nice. If someone wants to take this on, I'd likely accept it pending a look at the code. 🙂
I do understand having to uninstall more extensions. That's annoying.
Unfortunately, maintaining the config has been one piece of Scribe that has needed a lot of maintenance and attention compared to the app itself. I had custom infrastructure in Scribe itself to facilitate the config, which had nothing to do with reading articles. Other bugs and this issue which broke web browsers was too much. So I decided to outsource the problem to an extension for people who want this optional behavior.
It's still possible to use Redirector of course, and if someone wanted to maintain a Redirector config for Scribe, I would link to it.
Thanks! I did some tests and LibRedirect performs much better, so I'll switch to that.
Thank you for the report. Do you have a sample redirect I could test with? I'm considering abandoning Redirector and suggesting people use LibRedirect instead. It think it's possible for it to be smarter. As a bonus, it supports multiple instances. But I'd like to try it on a link that is a known problem before I suggest it.
Hi kaki87. No news. I have a bunch of other tasks taking priority (migrating websites off of Heroku, starting a new job) so this is still on the back burner for now. If anyone is reading this and would like to take a run at it, I do have time to steer you in a direction. Feel free to post here and I'll offer what guidance I can.
Hello and thanks for the suggestion. I think this is a good idea, however it's not on my list of priorities at the moment. If you or anyone else reading this wants to give it a shot, it would probably go in the
Articles::Showaction, or in the
ArticleIdParser. In either case, it probably makes sense to break it out into a separate object as those classes already are doing enough.
This is now fixed!