failed to open stream: No such file or directory

the ESHOP_path is not being set checkout.php. i don’t know where it is supposed to be set. i changed the line of code to use

ABSPATH.’wp-content/plugins/eshop/cart-functions.php

which does get rid of the error but might cause other probs. i would like to figure out why eshop_path is not getting a value.

with this dirty “fix” i am able to fill out the mailing info and click the “Proceed to confirmation”. The “Proceed to confirmation” leads me outside of the admin pages though, and to a public shopping-cart page where it says the shopping cart is empty but then can continue on to paypal.

it seems this shopping cart page is automatically created by eshop and its not getting the message of my premium packages setup. i’m puzzled but will keep digging. any help is much appreciated.

what version of eShop are you using?

and either way – try again after the next release please.

using Version 6.3.8. i see you just updated to Version 6.3.9. i’ll give that a shot. thanks.

i upgraded eshop to the latest release. still getting the errors:

Warning: include_once(ESHOP_PATHcart-functions.php) [function.include-once]: failed to open stream: No such file or directory in /home/werpoorg/public_html/wp-content/plugins/eshop/checkout.php on line 402

Warning: include_once() [function.include]: Failed opening ‘ESHOP_PATHcart-functions.php’ for inclusion (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/werpoorg/public_html/wp-content/plugins/eshop/checkout.php on line 402

then when i proceed the cart takes me outside of admin to the auto made shopping cart page. i’m assuming these auto pages were made since the premium packages plugin was updated. is that correct?

There is no eShop premium package, so not sure where you are getting that from.

What happens when you deactivate the plugin-premium-package-manager-for-wp-networks – are you still seeing errors for that include?

and what do you mean by this:

then when i proceed the cart takes me outside of admin to the auto made shopping cart page.

out of admin?

@elfin – the premium package manager uses eShop as a payment gateway & displays the items for purchase on an admin page. I’m taking from the OP that at some point it’s being redirected to the frontend.

The premium package manager does not use the ESHOP_PATH constant so I’m not sure what’s causing the error.

@ron should the “proceed to confirmation” button after i fill out the mailing addy take me outside of admin to a public page?

What happens when you deactivate the plugin-premium-package-manager-for-wp-networks – are you still seeing errors for that include?

I have just checked on one of my dev sites and I cannot replicate the error. If you have tried the above, the next step would be to download a fresh copy of eShop – and then delete all the files on the server and upload this fresh copy.

@elfin no, i don’t get the error when running eshop without the premium packages plugin. thanks for inquiring. its gotta be some trouble with how pp plugin is interacting with eshop.

@wpmuguru i will keep working on this. should the “proceed to confirmation” button after i fill out the mailing addy take me outside of admin to a public page? i did not expect that. any insight is greatly appreciated.

thanks everyone.

No, you should not be redirected to the front end.

@elfin – is the constant missing because the shopping cart is being generated in the admin area?

for some reason eshop_path is not defined in checkout.php. because of that i defined eshop_path at the top of checkout.php by adding the following lines and it then works without the errors.

if(!defined('ESHOP_PATH'))
	define( 'ESHOP_PATH', plugin_dir_path(__FILE__) );

here’s a video of the behavior i get when processing a product. it makes it through but it leaves admin for the checkout. it also indicates an empty cart at one point. i’m wondering if this is the normal/expected behavior for a premium package process.
https://youtu.be/y8Hstu2KJ3E

one other note. i am running wp super cache but i do have super cache disabled for eshop pages.

Ron, possibly – as I define it in eshop.php, so if you are calling checkout.php directly then it could cause an issue.

If that truly fixes it, I can add that to the core eShop plugin for you. But I need you to confirm exactly where you added it, so can you post the code – a few lines before and after – just so I can be sure to add it in in the same place.

if you are calling checkout.php directly then it could cause an issue.

Yes, it does call it directly.

that’s good news in a way – it means the fix should work when I add it – but I still need to confirm where it is added to ensure I replicate things correctly.

rich, is this fix something you will be doing soon? do you have a ballpark timeframe?