Thread

I have a similar, if not the same problem that these two good people had : http://ellislab.com/forums/viewthread/135616/P0/
and
http://ellislab.com/forums/viewthread/101234/
.
Can you tell me more about thread#135616 - specifically - assuming the issue is the certificates are in a directory that ee can’t see, even if I’ve provided the full path through the simple commerce control panel .. How do I (where do I) put the certificates such that ee can find them?  I suppose I’m on my own on this one.  It’s easy to say “specific to your environment, therefore we can do nothing.”  If anything, I can report back and let you know what I did to solve this problem for the benefit of others.

Environment disclosure: Expression Engine v1.7.1; Linode vps; CentOS 5.6; upgrading an existing Expression Engine site (v1.6.6) in a staging environment (i.e. a second server).  So .. I know the set up works somewhere else, although parts have broken getting from v1.6.6 to v1.7.1.

The challenge (for me) is getting Simple Commerce to work. 

When Expression Engine was directed to ‘serve-up’ the Simple Commerce area, the original error displayed was:

Could not sign encrypted data: error:0906D06C:PEM routines:PEM_read_bio:no start line

My Simple Commerce certificate files were originally located beyond the scope of the ‘root’ of the site (the level/subdir where the index.php and ./system/ reside). 

I had to RTFM and follow these instructions: Configure Simple Commerce. The instructions included getting into PayPal and generating their PayPal Certificate.

When I put these newly generated files onto the server, I updated the paths in Simple Commerce. 

The solution to the “Could not sign ..” error was correctly generating the (a) public certificate; (b) private key; and (c) paypal certificate AND entering the path to these generated files on the my server.  My error was simply copying these three files over from the other production server.  Big mistake.  .. problem solved ..

However ..

When I clicked on ‘Submit’ - I got another (different) error:

File Does Not Exist for ‘Public Certificate Path’. Make sure to use a full server path.

I created a subdir within the equivalent of ./system/, put that path in the different fields within Simple Commerce, and it took it. 

The solution to this error is to place the three certificates (mentioned earlier) within the scope of the ./system/ directory.  I’m sure there’s a way to let Expression Engine (v1.7.1 in this case) know of certificates outside of the Expression Engine based site directory .. I just don’t know how to do that today.

Now I have a new problem: When Expression Engine serves up the Simple Commerce part of the [staging] site, I see polar bears lost in a blizzard (nothing but whitespace).  .. That’ll be another post I suppose ..

Hi Paul,

I’m sorry you are experiencing this. Let me make sure I’ve got everything clear. You are all set on your first issue regarding the path to your cert, correct?

On your second post, you are seeing a white screen when you bring up Simple Commerce in the Control Panel? That’s generally indicative of a PHP error behind the scenes. Can you open up /system/index.php and set:

error_reporting(E_ALL);

That will let us see any errors that might be causing this white page.

Cheers,

I added error_reporting(E_ALL); to the ./system/index.php file. 

I’ve set

error_reporting = E_ALL & ~E_NOTICE | E_STRICT and
display_errors = On

in the /etc/php.ini file. 

No errors are reported at all.  All error logs show an old date.

What I will do is completely tear-down simple commerce and see if I can put it back together, one piece at a time.

I’ll post what happens here for those that follow.  Hopefully everyone’s on v2.x of EE and this is irrelevant.

My plan is to selectively build up simple commerce, one piece at a time, and see where it breaks.  Then I’ll for sure see what is the problem.

The beauty of this solution is that I’m working on a staging server.  A server is out there that works.

Hi Paul,

Good thing having this on a staging server! Keep me posted how the build-up goes. Do you have a moment to post the template code that is causing the white scree, or have you moved past that point?

Cheers,

The browser was serving up a white screen because a plug-in Image Sizer (a.k.a. pi.imgsizer.php) had a user:group owner of ‘root’ instead of the user:group that belongs to the mySQL user used for this instance of Exp Engine.  Doing a chown on the plug-in solved the problem.  I’ll need to turn off all the detailed error reporting I turned on in my php.ini file.  I’m guessing that due to root ownership of the file, HTTP hung - it couldn’t report an error. 

The version of Image Sizer used was v2.1.  I installed the latest version (v2.5.6).

I also installed a second similar plug-in: ED Image Resizer (a.k.a. pi.ed_imageresizer.php).

I no longer get the white screen.  This problem is solved.

Of course, now I have a new problem (related to these image plug-ins): I can’t get the images to show. 

That’ll be another post.

Paul,

Thank you so much for your thoroughness and for posting your resolution. For image needs, you might also look at CE Image. Very robust and well supported.

For any problems you encounter with third-party add-ons, your best path is to seek support from the author. We’re pretty limited in our ability to support third-party products, as you can imagine. However, if you ever need technical assistance with ExpressionEngine in the future, please feel free to start a new thread.

Cheers!