-
Notifications
You must be signed in to change notification settings - Fork 134
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
Can not install #52
Comments
@jonshkreli, are you sure, you uploaded all files from archive? and have no issues with file permissions? |
Hey i tried to delete and try it again. This time i downloaded from "clone or download", not from the zip link provided in installing instructions. But when i try to go into categories pages i get this error: And this one when i try to go to page posts: 2 exception(s): Exception #0 (Zend_Db_Statement_Exception): SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mage1.magefan_blog_post' doesn't exist, query was: SELECT COUNT(*) FROM While import and configuration links works. I have to say that i flushed cache and the result is the same. I were able to save a meta keyword in configuration menu successfully. |
@jonshkreli, it's look like install db data and schema where not runned. Are you sure, that you have runned |
when i try to install it via files download, I followed instructions:
....
when i run the secon command i get this error:
Fatal error: Interface 'Magefan\Blog\Api\ManagementInterface' not found in C:\xampp\htdocs\mage1\app\code\Megafan\Blog\Api\CategoryMana
gementInterface.php on line 11
and if i run the third command and/or try to open admin pages i get this:
Exception #0 (ReflectionException): Class Magefan\Blog\Observer\PredispathAdminActionControllerObserver does not exist
and this in homepage:
Exception #0 (ReflectionException): Class Magefan\Blog\Observer\PageBlockHtmlTopmenuBethtmlBeforeObserver does not exist
PS: i checked many times and files all exist. and they have all permissions from all users.
I am using lastest magento version.
The text was updated successfully, but these errors were encountered: