It's not possible to override a module template within a child theme. The template files override works fine but the module templates got mixed up. It seems that the smarty cache use the latest version of the theme (Parent or child).
Let's say you have theme A wich is a parent of Theme B . you have an override for module ps_emailsubscription on Theme A (Parent) and you also have an override for the same module template file on theme B (Child) then when you access the frontend for the theme A you can see the override created on theme B.
It might be related to the smarty cache for the template file that is not creating the cache on the child theme folder structure.
The expected behavior is to be able to override the modules on a child theme exactly as the template overrides having two different versions of the module template, one for each theme.
Steps to reproduce the behavior:
Screenshots
If applicable, add screenshots or screen recordings to help explain your problem.
Thanks for opening this issue! We will help you to keep its state consistent
Can you test with PrestaShop 1.7.7 beta?
It should be fixed with https://github.com/PrestaShop/PrestaShop/pull/14727 & https://github.com/PrestaShop/PrestaShop/pull/13804
Can you test with PrestaShop 1.7.7 beta?
It should be fixed with #14727 & #13804
It seems to be working fine on 1.7.7 beta, however I can't use it on production yet.
I have created an override for classes/controller/FrontController.php with the fix https://github.com/PrestaShop/PrestaShop/pull/13804/commits/7a03159ed7b6d3df5e867cdfe44c05ce07bbf3b7#diff-a5aacc71d32391733634cc71652c7bc7 and it's working fine.
Thank you for your help !
Most helpful comment
It seems to be working fine on 1.7.7 beta, however I can't use it on production yet.
I have created an override for classes/controller/FrontController.php with the fix https://github.com/PrestaShop/PrestaShop/pull/13804/commits/7a03159ed7b6d3df5e867cdfe44c05ce07bbf3b7#diff-a5aacc71d32391733634cc71652c7bc7 and it's working fine.
Thank you for your help !