- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Payment Methods configuration broken on default and website store scope
Hi,
I am updating a customized shop from 1.6 to 1.9.
Going to 1.8, system/configuration for the "payment methods" is broken.
The page would simply not load, but just leave a white page, without any error message anywhere.
The URL is well defined ..index.php/admin/system_config/edit/section/payment/key/...
Changing the shop scope to a specific shop (here it is just language versions), the panel works.
(with the reduced configuration values for paypal)
Settings from the old shop, as far as seen, are correct.
Switching back to scope Default or Website again just brings a white page.
Server is still running with php 5.3
Any Idea what makes this panel broken?
Any settings that are not compatible from the old paypal implementation in 1.7 to the changed implementation in 1.8?
Regards,
david
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Payment Methods configuration broken on default and website store scope
Hello,
See if this fix addresses your issue:
http://www.tjcafferkey.me/blank-system-configuration-page-magento-1-9-0-1-upgrade/
It is more for the entire configuration screen, but it may be related.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Payment Methods configuration broken on default and website store scope
Hi Rob,
thanks for the hint.
Finally it was some custom code copied over from the old version not working in 1.8
(app/code/local/Mage/Paypal/Model/Config.php)
Removing the modified file, made the configuration page work again.
Now I know that everything changed and I have to rework all code modifications.
Regards,
david
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Payment Methods configuration broken on default and website store scope
Hallo,
ich habe das Problem bei der Version 1.9.2.3 auch nach der PHP Umstellung bei 7.2.
So eben habe ich umgestellt auf PHP 7.1 und es läuft wieder.