Re: [CODE4LIB] replacing deprecated PHP code throughout website

2015-05-01 Thread Ken Irwin
Thanks to all who responded to this - you've given me a lot to think about. In the near term, I'm going to learn to do PDO calls and convert a few small projects over to that system. In the long-term, taking this as an opportunity to switch to a CMS for the main website might make sense, so I'll

Re: [CODE4LIB] replacing deprecated PHP code throughout website

2015-04-30 Thread Jason Bengtson
In terms of your original question, while I've used mysqli in the past I'm personally starting to gravitate more toward PDO, as it does seem like a more effective approach that is becoming a de-facto standard in some areas. I also second Will Martin's comments; figure out your scope right out of th

Re: [CODE4LIB] replacing deprecated PHP code throughout website

2015-04-30 Thread Jason Bengtson
+1 for a CMS for institutional websites. If I had my druthers I'd go with MODX, which is a solid system for PHP. I've never cared much for Drupal. For a library, I think libguides CMS can be leveraged very effectively. It has its own foibles that you have to deal with, but that's the nature of a co

Re: [CODE4LIB] replacing deprecated PHP code throughout website

2015-04-30 Thread Ian Walls
I second Cary's recommendation to go with a CMS. Another one to consider is SilverStripe. It's highly extensible, though model administration is done on the PHP level, so be prepared to open up your favourite text editor and mind your syntax. Ian Walls Web Services & Emerging Technologies L

Re: [CODE4LIB] replacing deprecated PHP code throughout website

2015-04-29 Thread Cary Gordon
My recommendations are: Move to a CMS. Drupal has a large library community, and I have been happily using it for ten years. You might find Joomla more to your liking, or you could worship the claw and go to Wordpress, which is mammoth, but not particularly developer friendly. If a CMS is out of

Re: [CODE4LIB] replacing deprecated PHP code throughout website

2015-04-29 Thread Little, Jamie
University of Miami Libraries From: Code for Libraries on behalf of Will Martin Sent: Wednesday, April 29, 2015 1:50 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] replacing deprecated PHP code throughout website > 1. Is there a general cons

Re: [CODE4LIB] replacing deprecated PHP code throughout website

2015-04-29 Thread Will Martin
1. Is there a general consensus on what the best long-term alternative to the mysql_* functions is? It's my impression that PDO is basically the way to go. 2. Does anyone have advice about how to proceed with an enormous overhaul like this? Define the scope of your project clearl

Re: [CODE4LIB] replacing deprecated PHP code throughout website

2015-04-29 Thread Michael Berkowski
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 29 Apr 2015, Ken Irwin said: > Hello all, > > I've just learned that the PHP mysql_* functions are all deprecated as of PHP > 5.5, and I'm trying to figure out what this means for my life. My library's > website is heavily database-driven,

Re: [CODE4LIB] replacing deprecated PHP code throughout website

2015-04-29 Thread Mark Pernotto
Ken, I've used both PDO as well as mysqli. My preference is mysqli over PDO. Mysqli is almost identical to the mysql in syntax, in terms of how you call the functions, but it is a bit different in other areas. The PHP docs should point you in the right direction. Not to beat a dead horse, but it'

[CODE4LIB] replacing deprecated PHP code throughout website

2015-04-29 Thread Ken Irwin
Hello all, I've just learned that the PHP mysql_* functions are all deprecated as of PHP 5.5, and I'm trying to figure out what this means for my life. My library's website is heavily database-driven, hand-coded, and all written using the mysql_* functions. It's currently running PHP 5.4, so pr