Edit History

welcome to community tested looool  ps_checkout has been a nightmare, I made a lot of money with client intakes of broken checkout...we just removed it...you  should consider the same unless ps has no other option for the payment gateway you use....

Yep—this is a real bug in the latest ps_checkout update (rolled out around Aug 22–25, 2025). Multiple shop owners are reporting the exact same crash on the Back-Office/FO with this stack trace pointing at the module’s English XLIFF file:
modules/ps_checkout/translations/en-US/ModulesCheckoutPscheckout.en-US.xlf (XLIFF parser: “source element not expected”, Error 1871). prestashop.com+1

Here’s the quickest way to get the site back up and keep ps_checkout usable:

• Restore access (if you’re locked out): via FTP/SSH, temporarily rename the module folder: modules/ps_checkout → modules/ps_checkout.off (site comes back). prestashop.com
• Target the bad file only: put the module folder name back to ps_checkout, then delete this file:
• modules/ps_checkout/translations/en-US/ModulesCheckoutPscheckout.en-US.xlf.
• Several users confirm the module will run without that file. prestashop.com
• Clear cache: delete var/cache/prod (and var/cache/dev if present).
• Reload Back-Office and test checkout.

Why it breaks (short version)

The shipped en-US XLIFF is not schema-valid for what Symfony’s XliffFileLoader expects in PS 8/9—hence the “[ERROR 1871] … source element not expected” crash during cache warm-up. Removing or replacing that one file avoids the fatal. prestashop.com

let us know how that works for you!

welcome to community tested looool  ps_checkout has been a nightmare, I made a lot of money with client intakes of broken checkout...we just removed it...you  should consider the same unless ps has no other option for the payment gateway you use....

Yep—this is a real bug in the latest ps_checkout update (rolled out around Aug 22–25, 2025). Multiple shop owners are reporting the exact same crash on the Back-Office/FO with this stack trace pointing at the module’s English XLIFF file:
modules/ps_checkout/translations/en-US/ModulesCheckoutPscheckout.en-US.xlf (XLIFF parser: “source element not expected”, Error 1871). prestashop.com+1

Here’s the quickest way to get the site back up and keep ps_checkout usable:

• Restore access (if you’re locked out): via FTP/SSH, temporarily rename the module folder: modules/ps_checkout → modules/ps_checkout.off (site comes back). prestashop.com
• Target the bad file only: put the module folder name back to ps_checkout, then delete this file:
• modules/ps_checkout/translations/en-US/ModulesCheckoutPscheckout.en-US.xlf.
• Several users confirm the module will run without that file. prestashop.com
• Clear cache: delete var/cache/prod (and var/cache/dev if present).
• Reload Back-Office and test checkout.

let us know how that works for you!

welcome to community tested looool

Yep—this is a real bug in the latest ps_checkout update (rolled out around Aug 22–25, 2025). Multiple shop owners are reporting the exact same crash on the Back-Office/FO with this stack trace pointing at the module’s English XLIFF file:
modules/ps_checkout/translations/en-US/ModulesCheckoutPscheckout.en-US.xlf (XLIFF parser: “source element not expected”, Error 1871). prestashop.com+1

Here’s the quickest way to get the site back up and keep ps_checkout usable:

• Restore access (if you’re locked out): via FTP/SSH, temporarily rename the module folder:
• modules/ps_checkout → modules/ps_checkout.off (site comes back). prestashop.com
• Target the bad file only: put the module folder name back to ps_checkout, then delete this file:
• modules/ps_checkout/translations/en-US/ModulesCheckoutPscheckout.en-US.xlf.
• Several users confirm the module will run without that file. prestashop.com
• Clear cache: delete var/cache/prod (and var/cache/dev if present).
• Reload Back-Office and test checkout.

let us know how that works for you!