Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Magepal GmailSmtpApp empty configuration #132

Closed
Nicatgenglobal opened this issue Jan 8, 2019 · 5 comments
Closed

Magepal GmailSmtpApp empty configuration #132

Nicatgenglobal opened this issue Jan 8, 2019 · 5 comments

Comments

@Nicatgenglobal
Copy link

Magento version #: 2.3.0

Edition (EE, CE, OS, etc): CE

Expected behavior:

I installed manually Magepal GmailSmtpApp following instructions. all good via composer.
Expected behavior:

  1. to see the configuration in Store --> Configuration --> Magepal --> Smtp Configuration
  2. to see the configuration page in Store --> Configuration -->Advanced --> System

Actual behavior:

Both pages are completely empty

I found a couple of related issues open and closed but no solution.

Please, anyone came across the same issue?
image

Thanks in advance.

Nick

@srenon
Copy link
Contributor

srenon commented Jan 8, 2019

@Nicatgenglobal... Could you check your PHP error log?

@Nicatgenglobal
Copy link
Author

Nicatgenglobal commented Jan 8, 2019

2 exception(s):
Exception #0 (Magento\Framework\Exception\LocalizedException): Invalid block type: MagePal\GmailSmtpApp\Block\Adminhtml\System\Config\Form\Module\Version
Exception #1 (ReflectionException): Class MagePal\GmailSmtpApp\Block\Adminhtml\System\Config\Form\Module\Version does not exist

Exception #0 (Magento\Framework\Exception\LocalizedException): Invalid block type: MagePal\GmailSmtpApp\Block\Adminhtml\System\Config\Form\Module\Version
#0 /home/gengloba/public_html/vendor/magento/framework/View/Layout/Generator/Block.php(249): Magento\Framework\View\Layout\Generator\Block->getBlockInstance('MagePal\GmailSm...', Array)
#1 /home/gengloba/public_html/vendor/magento/framework/View/Layout.php(776): Magento\Framework\View\Layout\Generator\Block->createBlock('MagePal\GmailSm...', 'adminhtml\syste...', Array)
#2 /home/gengloba/public_html/vendor/magento/framework/View/Layout.php(759): Magento\Framework\View\Layout->_createBlock('MagePal\GmailSm...', 'adminhtml\syste...', Array)
#3

@srenon
Copy link
Contributor

srenon commented Jan 8, 2019

I have not seen, could not replicate or have not idea why this issue occurs. No one has reported this issue in over a year. Can you try clearing cache and rerun setup:upgrade and di:compile

@Nicatgenglobal
Copy link
Author

Thanks for your help.
However no solution yet.
Magento 2.3 has been released end of November. the bug history is limited of course.

after di:compile the error differs

Fatal error: Uncaught Error: Class 'MagePal\GmailSmtpApp\Block\Adminhtml\System\Config\Form\Module\Version' not found in /home/gengloba/public_html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php:116 Stack trace: #0 /home/gengloba/public_html/vendor/magento/framework/ObjectManager/Factory/Compiled.php(108): Magento\Framework\ObjectManager\Factory\AbstractFactory->createObject('MagePal\GmailSm...', Array) #1 /home/gengloba/public_html/vendor/magento/framework/ObjectManager/ObjectManager.php(56): Magento\Framework\ObjectManager\Factory\Compiled->create('MagePal\GmailSm...', Array) #2 /home/gengloba/public_html/vendor/magento/framework/View/Element/BlockFactory.php(46): Magento\Framework\ObjectManager\ObjectManager->create('MagePal\GmailSm...', Array) #3 /home/gengloba/public_html/vendor/magento/framework/View/Layout/Generator/Block.php(269): Magento\Framework\View\Element\BlockFactory->createBlock('MagePal\GmailSm...', Array) #4 /home/gengloba/public_html/vendor/magento/framework/View/Layout/Generator in /home/gengloba/public_html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php on line 116

@srenon
Copy link
Contributor

srenon commented Jan 10, 2019

I will not be able to fix it without the ability to replicate it. The only recommendation I can provide is to open a paid support so that I can better review the issue

@srenon srenon closed this as completed Jan 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants