 |
 |
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 <[log in to unmask]> 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 <[log in to unmask]> wrote: > >> On Tue, Dec 4, 2012 at 9:53 AM, Ross Singer <[log in to unmask]> 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 / [log in to unmask] >>