Actually, I believe there was something about plugins we have been using, and also some concern about what would happen to some of the customizations JBrinley did for us.
But I think the biggest reason was that no one wanted / had the time to do the upgrading. Maybe we could persuade our new Technical Editor, Tom Keays?
Carol Bean
bean...@gmail.com
Ok, but we probably don't want to do it when we are on the eve of
publishing a new issue :-)
> Actually, I believe there was something about plugins we have been using, and also some concern about what would happen to some of the customizations JBrinley did for us.
Is jbrinley no longer active in the c4lj effort? If his plugins are
preventing us from keeping current I would vote for jettisoning his
customizations.
> But I think the biggest reason was that no one wanted / had the time to do the upgrading. Maybe we could persuade our new Technical Editor, Tom Keays?
I would be happy to help out. I think it's pretty important we stay
current because there are security vulnerabilities aplenty in previous
versions of WordPress. I've been bitten before by not keeping my
WordPress up to date, and would hate to see c4lj suffer a similar
fate.
//Ed
Is jbrinley no longer active in the c4lj effort? If his plugins are
preventing us from keeping current I would vote for jettisoning his
customizations.
On Tue, Jan 17, 2012 at 9:44 PM, Carol Bean <bean...@gmail.com> wrote:Ok, but we probably don't want to do it when we are on the eve of
> I nominate Ed to upgrade us.
publishing a new issue :-)
Tom (and everyone) are you going to be at code4lib in Seattle? It
seems we could have a little c4lj breakout session where we could chat
about this and other stuff. If not perhaps we could have a phone call?
You shouldn't feel like this is completely your responsibility to fix,
since the plugin situation makes it a bit more complicated. So having
a plan that we can all help you with would probably help get it done.
//Ed
> --
> You received this message because you are subscribed to the Google Groups
> "Code4Lib Journal-discuss" group.
> To post to this group, send email to c4lj-d...@googlegroups.com.
> To unsubscribe from this group, send email to
> c4lj-discuss...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/c4lj-discuss?hl=en.
-Tod
//Ed