WordPress.org

Ready to get started?Download WordPress

Forums

CG-Amazon fix for WP 2.0 (4 posts)

  1. WarAxe
    Member
    Posted 8 years ago #

    I just posted a fix I worked out with David Chait for CG-Amazon.: http://www.negative99.com/archive/79

    As a courtesy I will also post it here:

    1) Go to your WordPress directory and add the following code to WP-config.php…
    '
    // ***** IE-warning fix for CG-Amazon *****
    include_once('wp-content/plugins/cg-plugins/error-handler.php');
    '
    That's it. :-)

  2. davidchait
    Member
    Posted 8 years ago #

    Just to be clear (people won't always follow links around here), this eats the warning messages by activating the CG error-handler.php code -- it installs a custom error handler, that buffers error messages rather than having them echo out to the page. You can call myErrorOutput() in the footer.php file or something, preferably only for admin users!, if you want to see the error messages when/if they show up.

    This does NOT solve the actual warnings being generated, or any issues therein -- it just hides them so you, and your users, don't see them. I'm still working on the proper fixes to eliminate those warnings, but it does still seem that CG-Amazon is completely functional despite the warnings.

    Hope that helps,
    -d

  3. AlanSmithee
    Member
    Posted 8 years ago #

    If you upgrade beyond 2.0 (including 2.1-alpha1) there is a fatal error using the CG-Amazon and CG-WhatTunes plugins. Something about redeclaring wp_get_current_user(). I haven't checked the CG code yet to see what might be the problem.

    EDIT: I just commented this out in cga-config.php

    //if (!isset($user_level))
    //{
    // if (!function_exists('get_currentuserinfo'))
    // require (ABSPATH . WPINC . '/pluggable-functions.php');

    // if (function_exists('get_currentuserinfo'))
    // get_currentuserinfo(); // cache away in case hasn't been yet...
    //}

  4. davidchait
    Member
    Posted 8 years ago #

    yeah, the user_level conversion is trickier than I first thought -- it's requiring me to possibly pull some stuff into separate files, or drop certainly functionality to get a revised version out the door.

    thanks for the post so people have temp workarounds until I get a real new version out! ;)

    -d

Topic Closed

This topic has been closed to new replies.

About this Topic