Yes the error log comes up with the following

PHP Fatal error: main() [function.require]: Failed opening required 'uc_order_order_pane.inc' (include_path='.:') in /var/www/vhosts/eddiewalker.co.uk/httpdocs/modules/ubercart/uc_order/uc_order.module on line 16

I've experienced the same issue, and I've resolved it by adjusting the memory limit in php.ini

You can check your memory limit with phpinfo()

create a node and enter

Then adjust the input format all php code, and save it

It should give you a bunch of info, just do a search for memory_limit
and it will tell you how much memory your allowed.

fyi, make sure you delete the node that outputs the phpinfo...you don't want mischievous eyes viewing it.

I have messed with ini_set('memory_limit','(a range of valuesM');

the default at my host is 8M and I took it up to 13M while suffering the same error: Allowed memory size of xxxxxx bytes exhausted... etc.

as soon as I raize the memory limit to 16M I stop getting this error and get the white screen of death instead.

Anyone know why it goes from managing the error to just wandering away, never to return?

Additionally, no additional increase in memory_limit over 16M has any effect... I took it up to 256M and it was consistant about the white screen
Steve

Contacted my the host and the web development support came back with this

The blank page is because PHP is set up not to output any warnings or
errors, you can get around this by either looking in the error log for
the problem or putting error_reporting(E_ALL); at the beginning of the
page.

The first error "PHP Fatal error: main() [function.require]: Failed opening required
uc_order_order_pane.inc' (include_path='.:') in
var/www/vhosts/*******.co.uk/httpdocs/modules/ubercart/uc_order/uc_o
rder.module on line 16"

This simply means the code cannot find the page its trying to include,
which is usually down to the code not being entered correctly i.e.
require('uc_order.module') should be
require('/var/www/vhosts/********.co.uk/httpdocs/
modules/ubercart/uc_order/uc_order.module');
or even require('./uc_order.module');

I haven't seen the code so this is an assumption and should be the first
thing to look at.

Mod_rewrite has been disabled on this server for security reasons and
cannot be enable - you maybe able to get around this problem by putting
the following code within the .htaccess file in the root of your
environment

SecFilterEngine Off
SecFilterScanPOST Off

Please note that if the website causes any security risk to the server
of any other websites I it will be disabled.

The php info file lists memory at 32Mb, I will try the aboove suggestions and update post when done,
thanks for the help so far.

I tryed many times to get past the "white screen of death" on install and wasn't having any luck. I got desperate because ecommerce was being unbelievably problematic for me so I kept trying.

Eventually all I did was reinstall everything and carefully enable modules slowly making sure to always enable the required modules first. And that's all, it installed with no problems.

I'm glad I did because so far it's been really easy to use.

I had a similar problem, Ubercart was working fine in my local development environment, but when I uploaded it to a web server I got a white screen of death. The error log had entries similar to those mentioned above, so I changed the include statements to be similar to the structure mentioned here, and now all is well.

From what I can tell, this is how most Drupal modules structure their include statements, so I would suggest that ubercart core be changed to follow best practices of typical Drupal development. Plus, it seems to address a critical point of failure that has been a problem for a number of users. Also, I would think it could only improve performance, since the server interprets the current script to be at the base of the Drupal directory, and the include statements without the path force the server to do a bit of searching to find the script.

Just upgraded to Beta 3, and had to apply this fix in several places, which was time consuming, and will presumably need to be done with every version, until a true fix is found.

Plus, the fact that even this workaround doesn't work if caching is needed seems alarming.

Could someone who is NOT experiencing this issue share what values they have for include_path and openbasedir? Are there any users out there using Plesk hosted sites that are NOT experiencing this issue?

Yeah. Plesk 8.1.1 to be exact, our host recommends only updating to 8.2 after doing a clean install, which I'm not even considering right now. Other specs: Apache2, PHP 5.2.5, MySQL 4.2. Memory limit right now is set to 48mb (going higher soon) but I've never encountered a memory limit problem, even at 32M, and that includes enabling dozens of modules.

I'm still using Beta2 on the test site, same box, and haven't had to implement any fix of this kind. The one thing I keep recommending to people in the case of a blank page, is to add this bit of code to the very top of your Drupal site's index.php:

Since Drupal chokes on Fatal errors, you will only see why once you've added this code in (or set E_REPORTING options in php.ini).

There is another similar discussion here: http://www.ubercart.org/forum/support/2808/installation_blank_screen_ube... but it hasn't been resolved yet.

Welcome aboard, BlindWolf. Regarding changing the includes, I had done that in core a while back. However, if you turn on caching, Drupal chokes because of the differences in core inclusions for cached pages. The file that has the function drupal_get_path() doesn't get loaded before the module files are loaded, so it breaks any page request. I'm open to any alternatives, but right now I have to keep them as is in core. Perhaps the answer in the future is to just get rid of the .inc files, but they make keeping track of the code so much easier.

Regarding your second question, I'd always recommend the latest release. People have been using Ubercart on live sites since the early alphas, but it definitely behooves you to stay up to date since so much has been changing. The pace has slowed a bit, but now most of the new release material is bug fixes which you'll want on your site anyways.

Yeah, I'm with you. I was referring to the problem making your changes in core makes with caching. For some folks, Plesk isn't resolving the paths relative to the module directory, which is the source of the problem. But if you were to turn caching on on your site, my hunch is it would no longer work.

Here's Drupal's Info:

It's not my server, so I dunno if we can upgrade to PHP 5 or not. I'll have to talk to the guy I'm working for to see if we can, based on other stuff that's running on it.

Just as a note, I believe the error I was getting was about the include path, and I think it said either .:/crm or .:crm

I can test it on my shared hosting account shortly.