Unsubscribing users from forum causes 404s

[Nateowami]

It appears that forem has started using POST for unsubscribing users, so emails with a link to unsubscribe no longer work. As this appears to be a bug with forem, I was going to post there, but then realized that Memverse uses a forked version of forem. I'm not quite sure why that is, and maybe this needs to be fixed downstream in alexcwatt/forem, which doesn't have issue tracking. Oddly, alexcwatt/forem doesn't appear to be any commits ahead of radar/forem, so perhaps the fork was used only to keep the codebase static? Should I open this as an issue on radar/forem?

[avitus]

I would check with @alexcwatt on this. I would recommend getting back onto the Forem master branch if possible.

[alexcwatt]

@Nateowami I should have moved us a good while ago. For a time, I had a patch that had not been merged into forem, and so had pointed us to my branch, but now it is quite behind the times. If you can move us back, that'd be great; otherwise, I would hope to this weekend...

[alexcwatt]

I spent some quality time with my VM getting different versions of Ruby
installed for different projects and getting the bundle of gems to install,
etc. It seems like I'm pretty close to having Memverse running on it again
for development, but not quite... It's amazing how long it can take to get
set up sometimes but once it's there, the sailing is a bit smoother.

On Mon, Mar 30, 2015 at 1:53 PM, Andy [email protected] wrote:

I would check with @alexcwatt https://github.com/alexcwatt on this. I
would recommend getting back onto the Forem master branch if possible.

—
Reply to this email directly or view it on GitHub
#318 (comment).

[alexcwatt]

I have completed the forem updates locally but only committed and pushed the db migrations, as these must be done on the server first before the code is updated.

@avitus Are your recent changes deploy-ready? I just saw that the version in production is from April 1.

I will try to address that Jasmine spec soon. The trouble with breaks is that everyone has plans for what I will do with all the time :) I am going to work outside now...

[alexcwatt]

I copied the migrations to the server and ran them, then pushed the updated gem to master. So now if you deploy the updated gem, there is no need to worry about the db migrations they require, as those have already been run. I am not sure if this will take care of it, but I expect it will, since we'll be using the latest forem...

[avitus]

@alexcwatt I would never push changes to Master that aren't deploy-ready :)

I will deploy later today.

[avitus]

@Nateowami Do you know whether this issue is resolved?

[Nateowami]

@avitus It is not resolved. Just checked with an email I got yesterday. See rubysherpas/forem#522 and rubysherpas/forem#662. But @alexcwatt indicated he had made updates, and the gem just needed to be updated (not sure where the updates are though).

[avitus]

No longer using Forem.