View Issue Details

IDProjectCategoryView StatusLast Update
0007811module Amazon Paymainpublic2025-08-19 14:06
Reporterdigidesk Assigned To 
PriorityimmediateSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version3.1.5 
Fixed in Version3.1.6 
Summary0007811: Missing AmazonExpressButton at checkout with apex-childtheme
DescriptionWe have identified the problem that the block overloads of an apex-childtheme do not work in the basket. We noticed the problem with the AmazonExpressButton in the basket.
Steps To ReproduceTo reproduce the problem, we observe the block overload of vendor/oxid-esales/amazon-pay-module/views/twig/extensions/themes/apex/page/checkout/inc/summary_sidebar.html.twig

This only works if Apex is selected as the theme, i.e. not with a childtheme (apex based). In the module folder vendor/oxid-esales/amazon-pay-module/views/twig/extensions/themes/default the overload for this is also missing.
Additional InformationWe use OXID7.2.0 and a childtheme which has apex as parent.
Tagsamazonpay, missing block at basket, oxid7.2

Activities

QA

2025-07-17 12:27

administrator   ~0018087

- es -

QA

2025-07-17 12:31

administrator   ~0018088

I also use OXID7.2.0 and a childtheme which has apex as parent.

Even when I use a customized page/checkout/inc/summary_sidebar.html.twig in the child theme, the Amazon button is still displayed.
See Screenshots
amazon_pay_0.jpg (101,431 bytes)   
amazon_pay_0.jpg (101,431 bytes)   
amazon_pay.png (322,661 bytes)   
amazon_pay.png (322,661 bytes)   

QA

2025-07-18 09:16

administrator   ~0018089

Last edited: 2025-08-19 14:06

If the theme is not based on APEX (i.e., if it was created as a parent theme), I was able to reproduce the behavior.
I therefore confirm the bug.
-es

mario_lorenz

2025-08-19 10:45

developer   ~0018154

We've moved all templates that explicitly extend a theme named "apex" to the "default" section.

Because the affected templates now apply to all themes (not just explicitly for "apex"), inheritance to the child themes works.

It is solved in v3.1.6-rc.7 It will be part of the final release v3.1.6.