magefan / module-blog-m22 Goto Github PK

I installed the module with composer, after successfully installing the blog module.

• Installed with composer
• ran 'setup:upgrade'
• Cleared the cache
• I see module with version 2.0.0 in 'setup_module' - table

But when I open the website in the browser, I get the error:

1 exception(s):
Exception #0 (UnexpectedValueException): Setup version for module 'Magefan_BlogM22' is not specified

Exception #0 (UnexpectedValueException): Setup version for module 'Magefan_BlogM22' is not specified
#0 /var/www/vendor/magento/framework/Module/DbVersionInfo.php(54): Magento\Framework\Module\DbVersionInfo->isModuleVersionEqual('Magefan_BlogM22', '2.0.0')
#1 /var/www/vendor/magento/framework/Module/DbVersionInfo.php(77): Magento\Framework\Module\DbVersionInfo->isSchemaUpToDate('Magefan_BlogM22')
#2 /var/www/vendor/magento/framework/Module/Plugin/DbStatusValidator.php(120): Magento\Framework\Module\DbVersionInfo->getDbVersionErrors()

Can you check this?

I see there is a comment with a suggested fix in the readme file bundled with the Novetty theme from Cleversoft regarding this bug. The suggestion in the readme file was a work-around involving using the html mode of the editor to replace a double-quote with a single quote. The work-around does work for my tests, but it doesn't actually show a double-quote in the HTML mode, it shows a url encoded " instead. You can replace the pair of " with either a pair of either single or double quotes and it fixes the link. But it should be noted that the html-encoding is breaking the template field itself as the {{ }} block is actually appearing until you remove the " and replace it. (once replaced, if you go back to the html view, you see an actual relative path)

Also, upon finding the xml fix in this branch, I noted that there was already a commented out section in the app/code/Magefan/Blog/view/adminhtml/ui_component/blog_post_form.xml which is a match for the file in this branch. I tried uncommenting the section as per the suggestion in the first line of the comment but it did nothing as far as solving the issue.