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.
Library Web Developer
Drexel University Libraries
3300 Market Street
W. W. Hagerty Library
Philadelphia, PA 19104
Tel: 215.895.1344 | Fax: 215.895.2070
On 12/4/12 10:41 AM, "Shaun Ellis" <[log in to unmask]> wrote:
>Tom, can you post the plugin to Code4Lib's github so we can have a crack
>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.
>On 12/4/12 10:27 AM, Tom Keays wrote:
>> On Tue, Dec 4, 2012 at 9:53 AM, Ross Singer <[log in to unmask]>
>>> 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
>> 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.
>> time, one of the board members offered his technical expertise to build
>> 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
>> model, with all the issues published at one time and arranged in the
>> is a specific order. We could (and have done) all this manually, but
>> 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
>> 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
>> would break the plugins. We have now tested, and it did. I won't bore
>> with the details, but if we want to continue using the plugin to manage
>> workflow, we need help.
>> Is there anybody out there with experience writing WordPress plugins
>> 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
>> how to prevent this from happening again with future releases?
>> Tom Keays / [log in to unmask]
>Shaun D. Ellis
>Digital Library Interface Developer
>Firestone Library, Princeton University
>voice: 609.258.1698 | [log in to unmask]