X-Cart forums

[cflsystems]

Also when you say On_Sale module I assume you are talking about AlteredCart On Sale? There could be a problem with that 3rd party mod and 4.5.2, better contact Bill

[photo]

Originally Posted by cflsystems

Also when you say On_Sale module I assume you are talking about AlteredCart On Sale? There could be a problem with that 3rd party mod and 4.5.2, better contact Bill

Yes indeed, thank you for pointing out the obvious, helped me figure out the issue.

Looks like the upgrade script works fine and dandy. Thanks Qualiteam!

[cflsystems]

Unfortunatelly I still see

Tick here to continue upgrading regardless of the found problems

checked by default and "apply patch" button enabled on the patch/upgrade page. This should be DISABLED, the person doing the upgrade have to "opt-in" not "opt-out". This leads to problems.

[photo]

Originally Posted by cflsystems

Unfortunatelly I still see

Tick here to continue upgrading regardless of the found problems

checked by default and "apply patch" button enabled on the patch/upgrade page. This should be DISABLED, the person doing the upgrade have to "opt-in" not "opt-out". This leads to problems.

Just out of curiosity, if you do continue with the upgrade when there are files that can not be patched, does the database get updated?
Seems to me I remember that if there were file/files that could not be patched and you continued with the upgrade regardless, the database did not get patched (if indeed there was a patch.sql included in the upgrade).

[cflsystems]

Yes, if there are warnings but you continue database does NOT get patched. So you have 2 problems - some needed php files may not get patched causing php errors AND database is not patched. On top of that it is very easy to miss that because the note for the database not being patched is buried in the middle of a long list of files and text. A non-experienced user will easily fall into this trap.

[cherie]

The upgrade process for 4.x needs to be improved even if they are small incremental improvements.

[cflsystems]

Originally Posted by photo

Well I decided to try the upgrade on our server and all went well, but enabling the On_Sale module it still breaks the front end causing it to show a blank white page with a "500 Internal Server Error"

Disabling the On_Sale module fixes the issue and the store front works fine.
Not sure what may be causing the issue but I am guessing it has to do with a javascript conflict.

This problem may be due to code added to 4.5.2 for module with same name. There is this in home_main.tpl

+{elseif $main eq "new_arrivals" && $active_modules.New_Arrivals}
+{include file="modules/New_Arrivals/new_arrivals.tpl"}
+
+{elseif $main eq "on_sale" && $active_modules.On_Sale}
+{include file="modules/On_Sale/on_sale.tpl" navigation="Y"}
+
+{elseif $main eq "quick_reorder" && $active_modules.Quick_Reorder}
+{include file="modules/Quick_Reorder/quick_reorder.tpl"}
+

These modules do not exists in standard XC installation but are part of http://mods.x-cart.com/ yet the above code is included in 4.5.2 and the upgrade packs. I would guess there is more code about these modules in php files causing confussion with AC On Sale? You can try to delete the onsale related lines in home_main.tpl and see if front end works

I have no idea why QT would do this?

[Spechie]

Has anyone been able to modify OPC and have Iframe gateways on OPC without X-Payment.

[spence88mph]

To use Paypal Access do you need Paypal Standard or Standard Pro? We can't use Paypal Standard Pro in Australia...

[cflsystems]

So I tested the new features Lexity and PayPal Access.

Lexity - does not work with out of the box code. Code doesn't match what Lexity gives you when registering. In the Lexity service_head.tpl the src line has to be replaced with the code from Lexity - the one included is for QT as partners

s.src = '//np.lexity.com/embed/{$lexity_partner_code}/{$lexity_embed_hash}?id={$lexity_merchant_id}';

replace with (where XXXXX is yor Lexity code)

s.src = "//np.lexity.com/XXXXX";

There is also Google analytics code in the one provided by Lexity which does not exists in XC file but it works without it

PayPal Access - creating the application on PP is as described but the login popup in XC returns error. Either there is something more on PP to do (I don't see anything else there) or most likely the module in XC backend is not working correctly to allow for API keys to be entered.

These 2 new features do not work ok