Mage Enabler is now available for download in the Official WordPress Plugin repository!

May 12

Richard FeraroTechie Daw , , , 4 Comments

I’m soooo happy to see my very first plugin to be released for everyone to use. I hope it will help a lot of Magento and WordPress users!

Click! click! click!

4 Comments (+add yours?)

  1. Ryan
    May 26, 2010 @ 17:26:01

    Hi Richard,

    Tried using your plugin, however some strange behaviour followed.

    I have wordpress set up as the main part of my site ( in the root directory ) and magento in a sub folder powering just the ecommerce side. I wanted to use this plugin to pull the products of one category onto the homepage of my wordpress site.

    Installing the plugin gave me a white screen, setting the errors to show all in php.ini also provided a white screen which was rather odd. However the plugin worked perfectly once I’d visited my store first website.com/shop then went back to the homepage. Which implies to me that it seems to have trouble creating a new session. I made sure that:


    'frontend'));
    }
    ?>

    Was placed at the top of the php template file before the header also, to the same results. Any chance you could share your thoughts on how we could fix this?

    Reply

    • Richard Feraro
      May 26, 2010 @ 17:59:43

      Hello Ryan,

      Is it possible to see the file and how you implemented it? Your code in the post is incomplete or has been truncated. What is your Magento and WordPress version?

      Reply

  2. Ryan
    May 27, 2010 @ 16:08:07

    Hi Richard, sorry wasn’t anticipating such a swift reply :)

    The code that was cut off there was


    if(class_exists('Mage')){
    Mage::getSingleton('core/session', array('name' => 'frontend'));
    }

    The path to mage.php is correct and declared so in the admin, so its rather odd. I’m not too familiar with Magento’s methods, I assume thats trying to create a session?

    I tried getting errors to display in my php.ini file and it still returned a blank screen, which is rather unhelpful for the both of us I’d imagine :(

    Reply

    • Richard Feraro
      May 27, 2010 @ 17:37:57

      Add at the top of your script the code below:

      error_reporting(E_ALL);

      Is it possible to see the file where the error occurs?

      Reply

Leave a Reply