Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 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 tomke...@gmail.com wrote: The Code4Lib Journal is now running an up-to-date version of WordPress on our server and all of our plugins are similarly updated and operational. I'd especially like to acknowledge the contribution of Mark Pernotto, whose good knowledge of the WordPress codex allowed him to see the problem that I could not, and write a revised Issue Manager plugin. I'll post the revised code to GitHub in the next week or so. Thanks again to the other code4libbers that also offered to help. This group's generousity and expertise is great. For the Code4Lib Journal, many thanks! Tom
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 the Journal's WordPress web experience. The two c4lj repositories that have been ported are: https://github.com/code4lib/c4lj-issue-manager (renamed issue-manager plugin) https://github.com/code4lib/c4lj (Journal's current WordPress theme -- with 1 open issue) Tom On Mon, Jan 14, 2013 at 6:36 PM, Tom Keays tomke...@gmail.com wrote: 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 tomke...@gmail.com wrote: The Code4Lib Journal is now running an up-to-date version of WordPress on our server and all of our plugins are similarly updated and operational. I'd especially like to acknowledge the contribution of Mark Pernotto, whose good knowledge of the WordPress codex allowed him to see the problem that I could not, and write a revised Issue Manager plugin. I'll post the revised code to GitHub in the next week or so. Thanks again to the other code4libbers that also offered to help. This group's generousity and expertise is great. For the Code4Lib Journal, many thanks! Tom
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 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 the Journal's WordPress web experience. The two c4lj repositories that have been ported are: https://github.com/code4lib/c4lj-issue-manager (renamed issue-manager plugin) https://github.com/code4lib/c4lj (Journal's current WordPress theme -- with 1 open issue) Tom On Mon, Jan 14, 2013 at 6:36 PM, Tom Keays tomke...@gmail.com wrote: 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 tomke...@gmail.com wrote: The Code4Lib Journal is now running an up-to-date version of WordPress on our server and all of our plugins are similarly updated and operational. I'd especially like to acknowledge the contribution of Mark Pernotto, whose good knowledge of the WordPress codex allowed him to see the problem that I could not, and write a revised Issue Manager plugin. I'll post the revised code to GitHub in the next week or so. Thanks again to the other code4libbers that also offered to help. This group's generousity and expertise is great. For the Code4Lib Journal, many thanks! Tom
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 tomke...@gmail.com wrote: The Code4Lib Journal is now running an up-to-date version of WordPress on our server and all of our plugins are similarly updated and operational. I'd especially like to acknowledge the contribution of Mark Pernotto, whose good knowledge of the WordPress codex allowed him to see the problem that I could not, and write a revised Issue Manager plugin. I'll post the revised code to GitHub in the next week or so. Thanks again to the other code4libbers that also offered to help. This group's generousity and expertise is great. For the Code4Lib Journal, many thanks! Tom
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 updated plugin to GitHub, but I wanted to say thanks in advance. The Code4Lib community is incredible! Tom
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 locally (git clone g...@github.com:your-username/issue-manager.git my-antiharassment-policy) 3.) Create a branch to hold your changes (git checkout -b my-changes) 4.) Commit the changes you've made (git commit -am Some descriptive text around what you've added) 5.) Push your branch to github (git push origin my-changes) Once you do that, we can test it out for you before merging. -Shaun On 12/4/12 5:45 PM, Jonathan Rochkind wrote: 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 point me in the direction of a good GitHub tutorial (for contributing to projects such as these - the 'creating an account' part I think I have down), I'd appreciate it. Thanks, Mark On Tue, Dec 4, 2012 at 1:43 PM, Tom Keays tomke...@gmail.com wrote: 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! 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 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 debugging, it's best to point folks to the actual code the journal is running, which was forked from the official one on the Codex, right? It was written for the Journal and originally kept in a Google Code repo (this is before Github became the de facto). After the author left the journal, he did a couple of updates which he uploaded to the WP Codex, but nothing for a few years. Anyway, here it is: https://github.com/tomkeays/issue-manager -- Shaun D. Ellis Digital Library Interface Developer Firestone Library, Princeton University voice: 609.258.1698 | sha...@princeton.edu
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 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 locally (git clone g...@github.com:your-username/issue-manager.git my-antiharassment-policy) 3.) Create a branch to hold your changes (git checkout -b my-changes) 4.) Commit the changes you've made (git commit -am Some descriptive text around what you've added) 5.) Push your branch to github (git push origin my-changes) Once you do that, we can test it out for you before merging. -Shaun On 12/4/12 5:45 PM, Jonathan Rochkind wrote: 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 point me in the direction of a good GitHub tutorial (for contributing to projects such as these - the 'creating an account' part I think I have down), I'd appreciate it. Thanks, Mark On Tue, Dec 4, 2012 at 1:43 PM, Tom Keays tomke...@gmail.com wrote: 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! 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 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 debugging, it's best to point folks to the actual code the journal is running, which was forked from the official one on the Codex, right? It was written for the Journal and originally kept in a Google Code repo (this is before Github became the de facto). After the author left the journal, he did a couple of updates which he uploaded to the WP Codex, but nothing for a few years. Anyway, here it is: https://github.com/tomkeays/issue-manager -- Shaun D. Ellis Digital Library Interface Developer Firestone Library, Princeton University voice: 609.258.1698 | sha...@princeton.edu
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 Officer St. George's University esp...@sgu.edu __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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, which I personally would prefer, but it's all tradeoffs.). On 12/5/2012 5:05 PM, Ed Sperr wrote: 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 Officer St. George's University esp...@sgu.edu __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 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. Not being one to waste a perfectly good segue... The Code4Lib Journal runs on WordPress. This was a decision made by the editorial board at the time (2007) and by and large it was a good one. Over time, one of the board members offered his technical expertise to build a few custom plugins that would streamline the workflow for publishing the journal. Out of the box, WordPress is designed to publish a string of individual articles, but we wanted to publish issues in a more traditional model, with all the issues published at one time and arranged in the issue is a specific order. We could (and have done) all this manually, but having the plugin has been a real boon for us. The Issue Manager plugin that he wrote provided the mechanism for: a) preventing articles from being published prematurely, b) identifying and arranging a set of final (pending) articles into an issue, and c) publishing that issue at the desired time. That person is no longer on the Journal editorial board and upkeep of the plugin has not been maintained since he left. We're now several WordPress releases behind, mainly because we delayed upgrading until we could test if doing so would break the plugins. We have now tested, and it did. I won't bore you with the details, but if we want to continue using the plugin to manage our workflow, we need help. Is there anybody out there with experience writing WordPress plugins that would be willing to work with me to diagnose what has changed in the WordPress codex that is causing the problems and maybe help me understand how to prevent this from happening again with future releases? Thanks, Tom Keays / tomke...@gmail.com
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 or help script a new one. By the way, for the specific issues mentioned, there is now a way where you should be able to set publication of articles by future date natively in Wordpress - no plugin required. I remember running into this issue before, where a client desired this feature and we had to write something custom for them, only to revert the custom script with the upgrade of Wordpress. Thanks, Mark On Tue, Dec 4, 2012 at 7:47 AM, Chad Nelson chadbnel...@gmail.com wrote: 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 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. Not being one to waste a perfectly good segue... The Code4Lib Journal runs on WordPress. This was a decision made by the editorial board at the time (2007) and by and large it was a good one. Over time, one of the board members offered his technical expertise to build a few custom plugins that would streamline the workflow for publishing the journal. Out of the box, WordPress is designed to publish a string of individual articles, but we wanted to publish issues in a more traditional model, with all the issues published at one time and arranged in the issue is a specific order. We could (and have done) all this manually, but having the plugin has been a real boon for us. The Issue Manager plugin that he wrote provided the mechanism for: a) preventing articles from being published prematurely, b) identifying and arranging a set of final (pending) articles into an issue, and c) publishing that issue at the desired time. That person is no longer on the Journal editorial board and upkeep of the plugin has not been maintained since he left. We're now several WordPress releases behind, mainly because we delayed upgrading until we could test if doing so would break the plugins. We have now tested, and it did. I won't bore you with the details, but if we want to continue using the plugin to manage our workflow, we need help. Is there anybody out there with experience writing WordPress plugins that would be willing to work with me to diagnose what has changed in the WordPress codex that is causing the problems and maybe help me understand how to prevent this from happening again with future releases? Thanks, Tom Keays / tomke...@gmail.com
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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, Katherine --- Katherine Lynch Library Web Developer Drexel University Libraries Drexel University 3300 Market Street W. W. Hagerty Library Philadelphia, PA 19104 Tel: 215.895.1344 | Fax: 215.895.2070 drexel.edu/library On 12/4/12 10:41 AM, Shaun Ellis sha...@princeton.edu wrote: Tom, can you post the plugin to Code4Lib's github so we can have a crack at it? Ross, I'm not sure how many folks on this list were aware of the Drupal upgrade troubles. Regardless, I don't think it's constructive to put new ideas on halt until it gets done. Not everyone's a Drupal developer, but they could contribute in other ways. -Shaun On 12/4/12 10:27 AM, Tom Keays 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 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. Not being one to waste a perfectly good segue... The Code4Lib Journal runs on WordPress. This was a decision made by the editorial board at the time (2007) and by and large it was a good one. Over time, one of the board members offered his technical expertise to build a few custom plugins that would streamline the workflow for publishing the journal. Out of the box, WordPress is designed to publish a string of individual articles, but we wanted to publish issues in a more traditional model, with all the issues published at one time and arranged in the issue is a specific order. We could (and have done) all this manually, but having the plugin has been a real boon for us. The Issue Manager plugin that he wrote provided the mechanism for: a) preventing articles from being published prematurely, b) identifying and arranging a set of final (pending) articles into an issue, and c) publishing that issue at the desired time. That person is no longer on the Journal editorial board and upkeep of the plugin has not been maintained since he left. We're now several WordPress releases behind, mainly because we delayed upgrading until we could test if doing so would break the plugins. We have now tested, and it did. I won't bore you with the details, but if we want to continue using the plugin to manage our workflow, we need help. Is there anybody out there with experience writing WordPress plugins that would be willing to work with me to diagnose what has changed in the WordPress codex that is causing the problems and maybe help me understand how to prevent this from happening again with future releases? Thanks, Tom Keays / tomke...@gmail.com -- Shaun D. Ellis Digital Library Interface Developer Firestone Library, Princeton University voice: 609.258.1698 | sha...@princeton.edu
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 that's it. Every year, every year, somebody proposes we ditch the diebold-o-tron for something else (Drupal modules, mediawiki plugins, OCS, ... and most recently Easy Chair), yet nobody has ever bothered to do anything besides send an email of what we should use instead. Because that requires work and commitment. What I'm saying is, we don't have any central organization, and thus we have no real sustainable way to implement locally hosted services. The Drupal instance, the diebold-o-tron (and maybe Mediawiki) are legacies from when several of us ran a shared server in a colocation facility. We had skin in the game. And then our server got hacked because Drupal was unpatched (which sucked) and we realized we probably needed to take this a little more seriously. The problem was, though, when we moved to OSU for our hosting, we lost any power to do anything for ourselves and since we no longer had to (nor could) maintain anything, all impetus to do so was lost. To be clear, when we ran all these services on anvil, that wasn't sustainable either! We simply don't have the the organization or resources to effectively run this stuff by ourselves. That's why I'm really not interested in hearing about some x we can run for y if it's not backed up with and my organization which has shown commitment through z will take on the task of doing all the work on this. -Ross. On Dec 4, 2012, at 10:41 AM, Shaun Ellis sha...@princeton.edu wrote: Tom, can you post the plugin to Code4Lib's github so we can have a crack at it? Ross, I'm not sure how many folks on this list were aware of the Drupal upgrade troubles. Regardless, I don't think it's constructive to put new ideas on halt until it gets done. Not everyone's a Drupal developer, but they could contribute in other ways. -Shaun On 12/4/12 10:27 AM, Tom Keays 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 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. Not being one to waste a perfectly good segue... The Code4Lib Journal runs on WordPress. This was a decision made by the editorial board at the time (2007) and by and large it was a good one. Over time, one of the board members offered his technical expertise to build a few custom plugins that would streamline the workflow for publishing the journal. Out of the box, WordPress is designed to publish a string of individual articles, but we wanted to publish issues in a more traditional model, with all the issues published at one time and arranged in the issue is a specific order. We could (and have done) all this manually, but having the plugin has been a real boon for us. The Issue Manager plugin that he wrote provided the mechanism for: a) preventing articles from being published prematurely, b) identifying and arranging a set of final (pending) articles into an issue, and c) publishing that issue at the desired time. That person is no longer on the Journal editorial board and upkeep of the plugin has not been maintained since he left. We're now several WordPress releases behind, mainly because we delayed upgrading until we could test if doing so would break the plugins. We have now tested, and it did. I won't bore you with the details, but if we want to continue using the plugin to manage our workflow, we need help. Is there anybody out there with experience writing WordPress plugins that would be willing to work with me to diagnose what has changed in the WordPress codex that is causing the problems and maybe help me understand how to prevent this from happening again with future releases? Thanks, Tom Keays / tomke...@gmail.com -- Shaun D. Ellis Digital Library Interface Developer Firestone Library, Princeton University voice: 609.258.1698 | sha...@princeton.edu
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 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 that's it. Every year, every year, somebody proposes we ditch the diebold-o-tron for something else (Drupal modules, mediawiki plugins, OCS, ... and most recently Easy Chair), yet nobody has ever bothered to do anything besides send an email of what we should use instead. Because that requires work and commitment. What I'm saying is, we don't have any central organization, and thus we have no real sustainable way to implement locally hosted services. The Drupal instance, the diebold-o-tron (and maybe Mediawiki) are legacies from when several of us ran a shared server in a colocation facility. We had skin in the game. And then our server got hacked because Drupal was unpatched (which sucked) and we realized we probably needed to take this a little more seriously. The problem was, though, when we moved to OSU for our hosting, we lost any power to do anything for ourselves and since we no longer had to (nor could) maintain anything, all impetus to do so was lost. To be clear, when we ran all these services on anvil, that wasn't sustainable either! We simply don't have the the organization or resources to effectively run this stuff by ourselves. That's why I'm really not interested in hearing about some x we can run for y if it's not backed up with and my organization which has shown commitment through z will take on the task of doing all the work on this. -Ross. On Dec 4, 2012, at 10:41 AM, Shaun Ellis sha...@princeton.edu wrote: Tom, can you post the plugin to Code4Lib's github so we can have a crack at it? Ross, I'm not sure how many folks on this list were aware of the Drupal upgrade troubles. Regardless, I don't think it's constructive to put new ideas on halt until it gets done. Not everyone's a Drupal developer, but they could contribute in other ways. -Shaun On 12/4/12 10:27 AM, Tom Keays 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 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. Not being one to waste a perfectly good segue... The Code4Lib Journal runs on WordPress. This was a decision made by the editorial board at the time (2007) and by and large it was a good one. Over time, one of the board members offered his technical expertise to build a few custom plugins that would streamline the workflow for publishing the journal. Out of the box, WordPress is designed to publish a string of individual articles, but we wanted to publish issues in a more traditional model, with all the issues published at one time and arranged in the issue is a specific order. We could (and have done) all this manually, but having the plugin has been a real boon for us. The Issue Manager plugin that he wrote provided the mechanism for: a) preventing articles from being published prematurely, b) identifying and arranging a set of final (pending) articles into an issue, and c) publishing that issue at the desired time. That person is no longer on the Journal editorial board and upkeep of the plugin has not been maintained since he left. We're now several WordPress releases behind, mainly because we delayed upgrading until we could test if doing so would break the plugins. We have now tested, and it did. I won't bore you with the details, but if we want to continue using the plugin to manage our workflow, we need help. Is there anybody out there with experience writing WordPress plugins that would be willing to work with me to diagnose what has changed in the WordPress codex that is causing the problems and maybe help me understand how to prevent this from happening again with future releases? Thanks, Tom Keays / tomke...@gmail.com -- Shaun D. Ellis Digital Library Interface Developer Firestone Library, Princeton University voice: 609.258.1698 | sha...@princeton.edu -- Cary Gordon The Cherry Hill Company http://chillco.com
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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!), and need ongoing labor not just initial install labor I don't agree with the conclusion that the _only_ way to do this is with a central organization or my organization which has shown commitment through z I think it IS possible to run things sustainably with volunteer decentralized not-formal-organization labor. But my experience shows that it _isn't_ likely to work with ONE PERSON volunteering. It IS more likely to work with an actual defined collective, which feels collective responsibility for replacing individual members when they leave and maintaining it's collective persistence. Is that foolproof? No. But it doens't make it foolproof to incorporate and have a 'central organization' (still need labor, paid or unpaid), or to have an existing organization that commits to it (can always change their mind, or not fulfill their commitments even without actually changing their mind). There are plusses and minuses to both. I am a firm believer in code4lib's dentralized volunteer community-not-organization nature. I may be becoming a minority, it seems like everyone else wants code4lib to be Official? There are plusses and minuses to both. But either way, I don't think officiality is EITHER neccesary NOR sufficient to ensure sustainability of tech projects (or anything else). But i fully agree with rsinger that setting up a new tech project _without_ thinking about ongoing sustainability is foolhardy, unless it's just a toy you don't mind if it disappears when the originator loses interest. On 12/4/2012 11:08 AM, Ross Singer 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 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 that's it. Every year, every year, somebody proposes we ditch the diebold-o-tron for something else (Drupal modules, mediawiki plugins, OCS, ... and most recently Easy Chair), yet nobody has ever bothered to do anything besides send an email of what we should use instead. Because that requires work and commitment. What I'm saying is, we don't have any central organization, and thus we have no real sustainable way to implement locally hosted services. The Drupal instance, the diebold-o-tron (and maybe Mediawiki) are legacies from when several of us ran a shared server in a colocation facility. We had skin in the game. And then our server got hacked because Drupal was unpatched (which sucked) and we realized we probably needed to take this a little more seriously. The problem was, though, when we moved to OSU for our hosting, we lost any power to do anything for ourselves and since we no longer had to (nor could) maintain anything, all impetus to do so was lost. To be clear, when we ran all these services on anvil, that wasn't sustainable either! We simply don't have the the organization or resources to effectively run this stuff by ourselves. That's why I'm really not interested in hearing about some x we can run for y if it's not backed up with and my organization which has shown commitment through z will take on the task of doing all the work on this. -Ross. On Dec 4, 2012, at 10:41 AM, Shaun Ellis sha...@princeton.edu wrote: Tom, can you post the plugin to Code4Lib's github so we can have a crack at it? Ross, I'm not sure how many folks on this list were aware of the Drupal upgrade troubles. Regardless, I don't think it's constructive to put new ideas on halt until it gets done. Not everyone's a Drupal developer, but they could contribute in other ways. -Shaun On 12/4/12 10:27 AM, Tom Keays 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 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. Not being one to waste a perfectly good segue... The Code4Lib Journal runs on WordPress. This was a decision made by the editorial board at the time (2007) and by and large it was a good one. Over time, one of the board members offered his technical expertise to build a few custom plugins that would streamline the workflow for publishing the journal. Out of the box, WordPress is designed to publish a string of individual articles, but we wanted to publish issues in a more traditional model, with all the issues published at one time and arranged in the issue is a specific order. We could (and have done) all this manually, but having the plugin has
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
It might be worth considering the Annotum theme for Wordpress, meant to do just that. http://wordpress.org/extend/themes/annotum-base Jason Jason Stirnaman Digital Projects Librarian A.R. Dykes Library University of Kansas Medical Center 913-588-7319 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: 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. Not being one to waste a perfectly good segue... The Code4Lib Journal runs on WordPress. This was a decision made by the editorial board at the time (2007) and by and large it was a good one. Over time, one of the board members offered his technical expertise to build a few custom plugins that would streamline the workflow for publishing the journal. Out of the box, WordPress is designed to publish a string of individual articles, but we wanted to publish issues in a more traditional model, with all the issues published at one time and arranged in the issue is a specific order. We could (and have done) all this manually, but having the plugin has been a real boon for us. The Issue Manager plugin that he wrote provided the mechanism for: a) preventing articles from being published prematurely, b) identifying and arranging a set of final (pending) articles into an issue, and c) publishing that issue at the desired time. That person is no longer on the Journal editorial board and upkeep of the plugin has not been maintained since he left. We're now several WordPress releases behind, mainly because we delayed upgrading until we could test if doing so would break the plugins. We have now tested, and it did. I won't bore you with the details, but if we want to continue using the plugin to manage our workflow, we need help. Is there anybody out there with experience writing WordPress plugins that would be willing to work with me to diagnose what has changed in the WordPress codex that is causing the problems and maybe help me understand how to prevent this from happening again with future releases? Thanks, Tom Keays / tomke...@gmail.com
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 mentorship program as a way to get people to give back a little bit while also getting guidance. It's not going to happen overnight, but if anyone's interested in either being a mentor or mentee, sign up for the RailsBridge pre-conf. Again, it's not fully baked, but those who are interested can discuss it off list to brainstorm. -Shaun On 12/4/12 11:38 AM, Jonathan Rochkind 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 ALL software installations are living organisms (Ranganthan represent!), and need ongoing labor not just initial install labor I don't agree with the conclusion that the _only_ way to do this is with a central organization or my organization which has shown commitment through z I think it IS possible to run things sustainably with volunteer decentralized not-formal-organization labor. But my experience shows that it _isn't_ likely to work with ONE PERSON volunteering. It IS more likely to work with an actual defined collective, which feels collective responsibility for replacing individual members when they leave and maintaining it's collective persistence. Is that foolproof? No. But it doens't make it foolproof to incorporate and have a 'central organization' (still need labor, paid or unpaid), or to have an existing organization that commits to it (can always change their mind, or not fulfill their commitments even without actually changing their mind). There are plusses and minuses to both. I am a firm believer in code4lib's dentralized volunteer community-not-organization nature. I may be becoming a minority, it seems like everyone else wants code4lib to be Official? There are plusses and minuses to both. But either way, I don't think officiality is EITHER neccesary NOR sufficient to ensure sustainability of tech projects (or anything else). But i fully agree with rsinger that setting up a new tech project _without_ thinking about ongoing sustainability is foolhardy, unless it's just a toy you don't mind if it disappears when the originator loses interest. On 12/4/2012 11:08 AM, Ross Singer 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 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 that's it. Every year, every year, somebody proposes we ditch the diebold-o-tron for something else (Drupal modules, mediawiki plugins, OCS, ... and most recently Easy Chair), yet nobody has ever bothered to do anything besides send an email of what we should use instead. Because that requires work and commitment. What I'm saying is, we don't have any central organization, and thus we have no real sustainable way to implement locally hosted services. The Drupal instance, the diebold-o-tron (and maybe Mediawiki) are legacies from when several of us ran a shared server in a colocation facility. We had skin in the game. And then our server got hacked because Drupal was unpatched (which sucked) and we realized we probably needed to take this a little more seriously. The problem was, though, when we moved to OSU for our hosting, we lost any power to do anything for ourselves and since we no longer had to (nor could) maintain anything, all impetus to do so was lost. To be clear, when we ran all these services on anvil, that wasn't sustainable either! We simply don't have the the organization or resources to effectively run this stuff by ourselves. That's why I'm really not interested in hearing about some x we can run for y if it's not backed up with and my organization which has shown commitment through z will take on the task of doing all the work on this. -Ross. On Dec 4, 2012, at 10:41 AM, Shaun Ellis sha...@princeton.edu wrote: Tom, can you post the plugin to Code4Lib's github so we can have a crack at it? Ross, I'm not sure how many folks on this list were aware of the Drupal upgrade troubles. Regardless, I don't think it's constructive to put new ideas on halt until it gets done. Not everyone's a Drupal developer, but they could contribute in other ways. -Shaun On 12/4/12 10:27 AM, Tom Keays 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 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.
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 ALL software installations are living organisms (Ranganthan represent!), and need ongoing labor not just initial install labor I don't agree with the conclusion that the _only_ way to do this is with a central organization or my organization which has shown commitment through z I think it IS possible to run things sustainably with volunteer decentralized not-formal-organization labor. But my experience shows that it _isn't_ likely to work with ONE PERSON volunteering. It IS more likely to work with an actual defined collective, which feels collective responsibility for replacing individual members when they leave and maintaining it's collective persistence. FWIW, this is more what I meant (although stated much better). That is, a clearly defined plan, with a group that is dedicated to the ongoing maintenance of said plan. The journal is a good example of this. On the other hand, a non-distributed approach (see: OSU's commitment with Drupal and Mediawiki) is also fine, as long as the institutional commitment is there. -Ross.
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 to do: http://wiki.code4lib.org/index.php/Code4Lib_Journal_Tech_Wishlist Is the source of the plugin available anywhere? Version 1.4.3 is the most current version I found. There's an older version on a Google Code repo, so don't use that. http://wordpress.org/extend/plugins/issue-manager/ From Jason Stirnaman: It might be worth considering the Annotum theme for Wordpress, meant to do just that. http://wordpress.org/extend/themes/annotum-base Peter Murray suggested Annotum to me last week, but we'd very likely have to change our workflow to use it and work would have to be done to merge our template with Annotum's. I'm not against either, but inertia sets in. Peter also mentioned SemiotiX New Series, which I have yet to suss out http://ideophone.org/semiotix-wordpress-e-journal/ 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 feeling of the current Code4Lib owner(s) is regarding this, but if you can push content to that account, please feel free to start a new plugin repo there. I've had offers of help from Mark Pernotto and Katherine Lynch, for which I am thankful. We'll have to figure out how to go forward with this. First though, Mark and Katherine, can you confirm that you will help? We can probably do the rest of this off the public channel. And to anyone else who feels like it: please take a look at the code in the WordPress Codex and see if anything jumps out at you. All and all, it seemed to me to conform to the WP documentation I've read, but obviously something has changed in the codex that I'm missing. Mark suggested that the way WP handles jQuery ajax requests might be part of it, and I think he's on to something. However, there also seems to be a problem with the way the cat_ID (category ID) search is being executed to build the list of articles in the target issue. Maybe it is tied to the how the jquery-ui-sortable-1.5.2.js module is working, but maybe not. Thanks for the positive response, Tom
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 feeling of the current Code4Lib owner(s) is regarding this, but if you can push content to that account, please feel free to start a new plugin repo there. 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 debugging, it's best to point folks to the actual code the journal is running, which was forked from the official one on the Codex, right? -- Shaun D. Ellis Digital Library Interface Developer Firestone Library, Princeton University voice: 609.258.1698 | sha...@princeton.edu
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 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 feeling of the current Code4Lib owner(s) is regarding this, but if you can push content to that account, please feel free to start a new plugin repo there. 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 debugging, it's best to point folks to the actual code the journal is running, which was forked from the official one on the Codex, right? -- Shaun D. Ellis Digital Library Interface Developer Firestone Library, Princeton University voice: 609.258.1698 | sha...@princeton.edu
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 debugging, it's best to point folks to the actual code the journal is running, which was forked from the official one on the Codex, right? It was written for the Journal and originally kept in a Google Code repo (this is before Github became the de facto). After the author left the journal, he did a couple of updates which he uploaded to the WP Codex, but nothing for a few years. Anyway, here it is: https://github.com/tomkeays/issue-manager
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 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 debugging, it's best to point folks to the actual code the journal is running, which was forked from the official one on the Codex, right? It was written for the Journal and originally kept in a Google Code repo (this is before Github became the de facto). After the author left the journal, he did a couple of updates which he uploaded to the WP Codex, but nothing for a few years. Anyway, here it is: https://github.com/tomkeays/issue-manager
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 would take a look at this, though. Can someone contact me off-list (or even on-list) and instruct me the best way to go about posting the patch? Thanks, Mark On Tue, Dec 4, 2012 at 10:56 AM, Chad Nelson chadbnel...@gmail.com wrote: 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 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 debugging, it's best to point folks to the actual code the journal is running, which was forked from the official one on the Codex, right? It was written for the Journal and originally kept in a Google Code repo (this is before Github became the de facto). After the author left the journal, he did a couple of updates which he uploaded to the WP Codex, but nothing for a few years. Anyway, here it is: https://github.com/tomkeays/issue-manager
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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! 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 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 debugging, it's best to point folks to the actual code the journal is running, which was forked from the official one on the Codex, right? It was written for the Journal and originally kept in a Google Code repo (this is before Github became the de facto). After the author left the journal, he did a couple of updates which he uploaded to the WP Codex, but nothing for a few years. Anyway, here it is: https://github.com/tomkeays/issue-manager
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 account' part I think I have down), I'd appreciate it. Thanks, Mark On Tue, Dec 4, 2012 at 1:43 PM, Tom Keays tomke...@gmail.com wrote: 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! 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 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 debugging, it's best to point folks to the actual code the journal is running, which was forked from the official one on the Codex, right? It was written for the Journal and originally kept in a Google Code repo (this is before Github became the de facto). After the author left the journal, he did a couple of updates which he uploaded to the WP Codex, but nothing for a few years. Anyway, here it is: https://github.com/tomkeays/issue-manager
Re: [CODE4LIB] Help with WordPress for Code4Lib Journal
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 point me in the direction of a good GitHub tutorial (for contributing to projects such as these - the 'creating an account' part I think I have down), I'd appreciate it. Thanks, Mark On Tue, Dec 4, 2012 at 1:43 PM, Tom Keays tomke...@gmail.com wrote: 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! 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 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 debugging, it's best to point folks to the actual code the journal is running, which was forked from the official one on the Codex, right? It was written for the Journal and originally kept in a Google Code repo (this is before Github became the de facto). After the author left the journal, he did a couple of updates which he uploaded to the WP Codex, but nothing for a few years. Anyway, here it is: https://github.com/tomkeays/issue-manager
