Class conflict between OAuth libraries when PECL OAuth extension installed on server

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. Install PECL OAuth extension on server.
2. Download and configure Simple-LinkedIn library, along with required OAuth 
class.
3. Run demo script, and OAuth libraries will cause fatal conflict.

At this time, I am trying to plot out the best course of action here.  The 
whole point of this 'simple' library is that by using a third-party stand-alone 
OAuth class, you don't need root access on the server to install the OAuth 
extension, etc.  Possible solutions include rolling our own OAuth library, or 
fully integrating all OAuth-specific functionality into the LinkedIn library, 
thus preserving the OAuth class namespace for any pre-existing extensions.

Original issue reported on code.google.com by pmmenneg@gmail.com on 23 Oct 2010 at 1:57

GoogleCodeExporter commented 8 years ago

Version 2.1.0 of the Simple-LinkedIn library now performs a simple check to see 
if the PECL OAuth library is installed.  If it is, Simple-LinkedIn will fire an 
Exception and will not instatiate.

Original comment by pmmenneg@gmail.com on 27 Oct 2010 at 3:46

GoogleCodeExporter commented 8 years ago

Original comment by pmmenneg@gmail.com on 22 Apr 2011 at 4:32

Changed state: Fixed

GoogleCodeExporter commented 8 years ago

Original comment by p...@fiftymission.net on 11 Nov 2011 at 5:14

GoogleCodeExporter commented 8 years ago

I renamed the OAuthException class in the 3third party Oath library to 
OAuthException_sec is this a good idea ? i did this because i dont have the 
rights to adjust the php libs on the server.

So is this a good workaround? it works....but?

Thanks in advance,
Jacob

Original comment by jacobni...@gmail.com on 29 Aug 2012 at 8:04

dnzengou / simple-linkedinphp

Class conflict between OAuth libraries when PECL OAuth extension installed on server #1