Per discussion in #fedora-commops, the Community Blog should be included in the WordPress package that is currently used for the Fedora Magazine for regular updates.
I think this ticket is meant for @puiterwijk, but I'm not sure if the Magazine / CommBlog have been spread across any other infrastructure folks in the past few months. If not, this is probably best left to Patrick. :)
Right now, there's no urgent rush for this, but it will be helpful long-term so that the CommBlog doesn't lag behind on updates, should there ever be a critical security vulnerability that would affect our WordPress install.
cc: @bex
So, you want to move community blog to the same instance/wordpress as magazine?
Or just move it to using the wordpress rpm ?
@kevin I'm not really sure – I've been out of the loop for a month or two, but if I understand right, the way the Magazine receives updates to WordPress core is through an RPM package that's updated regularly. I think the idea was to have the Community Blog follow a similar update mechanism.
Hmm, this might actually need to happen sooner than I realized… as of now, the editor inside of the Community Blog is unusable. When you try writing a new post, the editor window is blank and none of the WYSIWYG buttons appear. @pfrields and @ryanlerch tested this on their end and also had the same result.
I tried reinstalling core WordPress from the admin panel and then deactivating all plugins except the OpenID + Fedora OpenID authenticator plugins, but the issue still resides. I'm wondering if getting the CommBlog to the same set-up as the Magazine might resolve this, since most of the plugins are the same.
The reason why I think this might need to happen sooner is that the elections are coming up, which means candidates will need to log into the CommBlog to add their posts. But with the editor broken, they won't be able to do that. :pensive:
Is there any chance this could happen in this next week?
Sorry for the delay here.
Is some downtime ok? I can try and do this tomorrow morning... backup things, take the old instance down, fire up a new f26 one and reload it.
@kevin No problem, this wasn't originally a time-sensitive ticket. :sweat_smile:
Some downtime would be fine, especially on the weekend (weekends always are lower traffic times anyways). If you could do this any time at all on Saturday, I can jump on and help take a look once it's done and finished. I really appreciate you helping with this!
ok, the instance has been redeployed and moved to the packaged wordpress.
There's a few issues however we need to fix:
authentication doesn't seem to work for me, just gets in a redirect loop.
The theme doesn't seem quite right.
Will leave this open for us to address those.
We got those issues sorted out yesterday, so everything should be done.
Please let us know if there's anything still needing adjustment.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.