YAK For WordPress CheckOut Error

I’d say test the latest version (3.4.9) because there was a similar bug to this reported recently. If it’s still a problem, then it could be an incompatibility with another plugin.

Hi,

I just installed the plugin today and I’m having some trouble, too, including the above error. I’ve got the latest version of the plugin and I disabled all other plugins.

Version 3.4.9? And is the error the same line number?

Not sure about the number now, but I’m not getting it anymore. I think I had the wrong checkout page selected. I had another plugin before that used a checkout page and I think I had that selected as the page to go to after buying. I since changed that to the automatically created checkout page for YAK and it’s working.

Well, it WAS working. I’ve been trying to add product options (which resulted in a “Cart empty” message at checkout (although I had selected a product) so when I deleted the multiselect option and went to checkout again, it DID go to the COnfirm Order page, but under Order Details I see this:

Fatal error: main() [function.main]: The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "YakItem" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition in /home/content/43/8283643/html/encino/wp-content/plugins/yak-for-wordpress/yak-view-confirm.php on line 102

Also getting the same on clicking add to cart:

Fatal error: main() [function.main]: The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "YakItem" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition in /home/content/43/8283643/html/encino/wp-content/plugins/yak-for-wordpress/yak-view-cart.php on line 81

Okay, it must be a plugin conflict. I did have all plugins except YAK and Yak for Auth.net deactivated. I forgot that I reactivated them. I guess I need to go through them one by one to eliminate the offender(s).

That error message is usually because another plugin is starting up an HTTP session in the wrong way. The “right” way is to start the session in WordPress’s init action. One of the plugins (if I’m correct about the cause, of course), is doing it outside of that action.

Ok, so we found the offending plugin, All-In-One Event by Timely. Any suggestions on what steps to take on hopefully getting this corrected?

Thank You

I tried downloading that plugin, but it doesn’t seem to install properly in my test site, so I’m unable to reproduce the problem. I took a quick look at the code, but I can’t see any calls to start a session. Unless it has some associated add-ons or themes which do start sessions, I’m not sure how it can be causing your particular problem.

We have been working with the developer, and have an update to the plug-in that has corrected the initial issue.

We now can get the CHECKOUT page to work, we were able to enter CC information 1 time, when we processed (Authorize.net – TestMode) the confirmation page never completed comming up.

Upon subsequent attempts the CC information was never asked for. We would go through the checkout process, confirm the shipping address, we could see that the payment type is set to VISA, but there is no way to see any details or enter a new card number. If we close the window and go back to check out, we get the same results and no way to edit CC info.

I have tried to change from TEST MODE, and CC Processing from Authorize.net TEST to Live and still no changes.

When you say the confirmation page never completed coming up, do you mean the browser hung (the page never loaded), or the page failed to load properly?

It does still sound like some kind of incompatibility problem. My suggestion would be disable all other plugins (switch to the default theme), then test it. If it works you know either theme or another plugin is causing the problem. If it still doesn’t work, then it might be something odd about your PHP setup (which will be, unfortunately, more difficult to track down).