Tom,
Kudos! I think this is a great example of enabling (and asking for!)
collaboration within the community. Thank you for maintaining it and
integrating Mark's fix!
-Shaun
On 1/14/13 6:36 PM, Tom Keays wrote:
I spent the past week teaching myself how to properly use Git and have
finally
After some discussion on the Code4Lib Journal editors' back-channel, we
decided to move the various WordPress plugins and themes to the Code4Lib
organization site on GitHub. Besides making our process a little more
transparent, we also hope to encourage participation in maintaining and
improving
Woot! Will see you on github.
//MS
-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Tom
Keays
Sent: Tuesday, January 15, 2013 2:39 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
After some
I spent the past week teaching myself how to properly use Git and have
finally updated the repository with Mark's contribution to the Code4Lib
Journal Issue Manager plugin.
https://github.com/tomkeays/issue-manager
Thanks again for the help.
Tom
On Thu, Jan 3, 2013 at 9:48 AM, Tom Keays
After a bit of dithering on this, I'm pretty sure that Mark's revision of
the plugin is working under the current version of WordPress I'm testing on
(3.4.2). I have a few other things I'm going to need to do before I declare
this solved, upgrade the Journal's instance of WordPress and upload the
Yes, that's a good place to start. Once you have git installed and link
it up to your github account, you can follow the same Contribute steps
that are on the README of the anti-harassment policy:
1.) Fork the codebase e.g. to https://github.com/your-username/issue-manager
2.) Clone your fork
Jonathan/Shaun,
Thanks for the direction. I've followed the steps suggested, I think.
Please let me know if you have any questions or don't see anything.
Thanks,
Mark
On Wed, Dec 5, 2012 at 6:51 AM, Shaun Ellis sha...@princeton.edu wrote:
Yes, that's a good place to start. Once you have git
Instead of maintaining a custom codebase to try and force WP to do what you
want, why not just use a tool purpose-built for this kind of job? The
open-source, Open Journal Systems from PKP might be a good fit:
http://pkp.sfu.ca/?q=ojs
Ed Sperr, M.L.I.S.
Copyright and Electronic Resources
We've looked at OJS in the past and not been happy with it, we're pretty
happy with WordPress, and not really looking to migrate all our
operations to different software.
But thanks for the suggestion.
(I do think there are probably ways we could keep using WP without a
custom codebase,
On Tue, Dec 4, 2012 at 9:53 AM, Ross Singer rossfsin...@gmail.com wrote:
Seriously, folks, if we can't even figure out how to upgrade our Drupal
instance to a version that was released this decade, we shouldn't be
discussing *new* implementations of *anything* that we have to host
ourselves.
Tom,
What version of WP are you currently on?
Is the source of the plugin available anywhere?
Chad
On Tue, Dec 4, 2012 at 10:27 AM, Tom Keays tomke...@gmail.com wrote:
On Tue, Dec 4, 2012 at 9:53 AM, Ross Singer rossfsin...@gmail.com wrote:
Seriously, folks, if we can't even figure out
If I recall correctly, there were some noticeable differences in the
way Wordpress would be willing to work with jQuery ajax requests,
even as recently as 3.1 to it's current state 3.4.2.
I do quite a bit with Wordpress professionally. I'd be willing to
help/work on either upgrading the plugin
Tom and Ross,
I'm very familiar with writing and upgrading custom plugins and modules
for Wordpress and Drupal respectively. I'd like to officially offer my
services to help on the back-end diagnosing/coding/etc.
In the mean time, some source to review on GitHub would be great.
Sincerely,
Shaun, I think you missed my point.
Our Drupal (and per Tom's reply, Wordpress -- ...and I'm going to take a stab
in the dark and throw MediaWiki instance into the pile) is, for all intents and
purposes, unmaintained because we have no in charge of maintaining it. Oregon
State hosts it, but
As I mentioned in the other thread, I will get with Ryan on updating
our Drupal instance.
Cary
On Tue, Dec 4, 2012 at 8:08 AM, Ross Singer rossfsin...@gmail.com wrote:
Shaun, I think you missed my point.
Our Drupal (and per Tom's reply, Wordpress -- ...and I'm going to take a stab
in the
While I agree with ross in general about suggesting technical solutions
without suggesting how they are going to be maintained -- agree very
strongly -- and would further re-emphasize that it's improtant to
remember that ALL software installations are living organisms
(Ranganthan represent!),
From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of Tom Keays
[tomke...@gmail.com]
Sent: Tuesday, December 04, 2012 9:27 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: [CODE4LIB] Help with WordPress for Code4Lib Journal
On Tue, Dec 4, 2012 at 9:53 AM, Ross Singer rossfsin...@gmail.com wrote
The problem is that the listserv is not good for brainstorming.
Expecting any one person to have a fully baked solution (with hosting)
before posting to the list is not going to happen. That's why I
suggested an alternative discussion tool with the vote2promote feature.
I also suggested the
On Dec 4, 2012, at 11:38 AM, Jonathan Rochkind rochk...@jhu.edu wrote:
While I agree with ross in general about suggesting technical solutions
without suggesting how they are going to be maintained -- agree very strongly
-- and would further re-emphasize that it's improtant to remember that
Hijacking my thread back. To answer all the questions in one go:
From Chad Nelson:
What version of WP are you currently on?
Embarrassed, but you just have to do a view source of the Journal to learn
the dirty truth: WordPress 3.0.4
As you can see from the wiki, upgrading is something we want
On 12/4/12 12:42 PM, Tom Keays wrote:
From Shaun Ellis (echoed by Katherine Lynch):
Tom, can you post the plugin to Code4Lib's github so we can have a crack
at it
I can't, since I do not have a login to that Github account (I didn't even
know about it until last week). I'm not sure what the
Tom,
Yes, I can confirm that I'm willing to work on this issue. However,
if a solution works better through Shaun's github solution would work
better for the group, I say go that routewhatever is best.
Thanks,
Mark
On Tue, Dec 4, 2012 at 10:01 AM, Shaun Ellis sha...@princeton.edu wrote:
On Tue, Dec 4, 2012 at 1:01 PM, Shaun Ellis sha...@princeton.edu wrote:
You can upload it to your account and then someone with admin rights to
Code4Lib can fork it if they think our Code4Lib Journal custom code should
be a repo there. Doesn't really matter if they do actually. I think for
Beat me by one minute Tom!
And here it is in code4lib github
https://github.com/code4lib/IssueManager
On Tue, Dec 4, 2012 at 1:47 PM, Tom Keays tomke...@gmail.com wrote:
On Tue, Dec 4, 2012 at 1:01 PM, Shaun Ellis sha...@princeton.edu wrote:
You can upload it to your account and then
So, I have a solution - well, at least to what I think is the problem.
It looks like the im_admin_main.php file made a reference to a
depricated 'categories.php' file in the admin section. There were a
couple other query string parameters that weren't quite correct.
I'd love if someone else
Let's have mine be the canonical version for now. It will be too confusing
to have two versions that don't have an explicit fork relationship.
https://github.com/tomkeays/issue-manager
Tom
On Tue, Dec 4, 2012 at 1:56 PM, Chad Nelson chadbnel...@gmail.com wrote:
Beat me by one minute Tom!
As I'm clearly not well-versed in the goings-on of GitHub, I've
'forked' a response, but am not sure it worked correctly.
I've zipped up and sent updates to Tom. If anyone could point me in
the direction of a good GitHub tutorial (for contributing to projects
such as these - the 'creating an
I'd check out the links under Bootcamp here:
https://help.github.com/
On 12/4/2012 5:18 PM, Mark Pernotto wrote:
As I'm clearly not well-versed in the goings-on of GitHub, I've
'forked' a response, but am not sure it worked correctly.
I've zipped up and sent updates to Tom. If anyone could
28 matches
Mail list logo
