• I am getting an Aweber error in my log even though I don’t have Aweber set up for Leadin. It’s also pretty much non stop. Here is a batch copy from the log.

    [Sat Jan 24 16:50:38.164825 2015] [:error] [pid 18047] [client 74.87.163.55:46724] PHP Warning: Duplicate: Another AWeberAPI client library is already in scope. in /nas/wp/www/cluster-30014/scottwyden/wp-content/plugins/leadin/power-ups/aweber-connect/inc/aweber_api/aweber_api.php on line 4
    [Sat Jan 24 16:50:55.651374 2015] [:error] [pid 11313] [client 178.137.17.49:46743] PHP Warning: Duplicate: Another AWeberAPI client library is already in scope. in /nas/wp/www/cluster-30014/scottwyden/wp-content/plugins/leadin/power-ups/aweber-connect/inc/aweber_api/aweber_api.php on line 4
    [Sat Jan 24 16:51:20.202773 2015] [:error] [pid 16138] [client 54.87.132.150:46783] PHP Warning: Duplicate: Another AWeberAPI client library is already in scope. in /nas/wp/www/cluster-30014/scottwyden/wp-content/plugins/leadin/power-ups/aweber-connect/inc/aweber_api/aweber_api.php on line 4
    [Sat Jan 24 16:51:20.705877 2015] [:error] [pid 18048] [client 104.130.192.82:46786] PHP Warning: Duplicate: Another AWeberAPI client library is already in scope. in /nas/wp/www/cluster-30014/scottwyden/wp-content/plugins/leadin/power-ups/aweber-connect/inc/aweber_api/aweber_api.php on line 4
    [Sat Jan 24 16:51:45.262031 2015] [:error] [pid 18051] [client 157.55.39.85:46812] PHP Warning: Duplicate: Another AWeberAPI client library is already in scope. in /nas/wp/www/cluster-30014/scottwyden/wp-content/plugins/leadin/power-ups/aweber-connect/inc/aweber_api/aweber_api.php on line 4
    [Sat Jan 24 16:52:15.226144 2015] [:error] [pid 30793] [client 195.211.155.157:46836] PHP Warning: Duplicate: Another AWeberAPI client library is already in scope. in /nas/wp/www/cluster-30014/scottwyden/wp-content/plugins/leadin/power-ups/aweber-connect/inc/aweber_api/aweber_api.php on line 4, referer: http://scottwyden.com/8-travel-photography-accessories-forget/?utm_source=rss&utm_medium=rss&utm_campaign=8-travel-photography-accessories-forget
    [Sat Jan 24 16:52:17.418798 2015] [:error] [pid 16138] [client 195.211.155.157:46839] PHP Warning: Duplicate: Another AWeberAPI client library is already in scope. in /nas/wp/www/cluster-30014/scottwyden/wp-content/plugins/leadin/power-ups/aweber-connect/inc/aweber_api/aweber_api.php on line 4, referer: http://scottwyden.com/8-travel-photography-accessories-forget/?utm_source=rss&utm_medium=rss&utm_campaign=8-travel-photography-accessories-forget
    [Sat Jan 24 16:52:36.482931 2015] [:error] [pid 18052] [client 121.205.239.240:46851] PHP Warning: Duplicate: Another AWeberAPI client library is already in scope. in /nas/wp/www/cluster-30014/scottwyden/wp-content/plugins/leadin/power-ups/aweber-connect/inc/aweber_api/aweber_api.php on line 4, referer: http://scottwyden.com/hdr-photography-tip-shadowmapping/

    https://wordpress.org/plugins/leadin/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi Scott –

    Thanks for the printout of the error logs. This is a known bug that I’m hoping to take care of this week. Basically the issue here is that you have two plugins trying to include an AWeber library with the same class name. Typically we’d just be able to namespace our service under the Leadin logic, but because so many of our users run PHP 5.2, we can’t use namespaces. They didn’t exist until PHP 5.3 unfortunately.

    I’ll circle back with you once we have this fixed and launched.

    This issue should be fixed as of Leadin Pro 3.1.3. There is one small glitch where I still need to namespace the oauth files libraries which connect to AWeber, but it should be working now except for a few outlier instances.

    Thread Starter Scott Wyden Kivowitz

    (@scottwyden)

    Awesome!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Aweber error’ is closed to new replies.