I have install fresh versions of Prestashop 1.7.5.2 and 1.7.6.1 on my Linux computer and I can't install themes on any them. I have tried with these free themes Apparel and ST002 and I always get some error with a module of the type:
"Cannot install module XXXX. The module is invalid and cannot be loaded."
I think it has to do with something in my Prestashop installation, not with the themes themselves. But I don't have any idea where to start looking, could you please help me? This is getting me mad.
Thank you!
I had a similar problem. I was trying to install the theme by putting the theme's directory into the "themes" directory of my prestashop.
But the proper way to install a theme is by providing a zip file to the administration interface.
If you put the directory manually in "theme" you will also have to manually copy the modules inside the dependency directory of your theme to the "modules" directory of your prestashop.
Manually copying modules might not be enough since it won't call the "install" method on the modules.
Did you check the specs/requirements of the theme? Maybe the theme you want to install is not compatible with the current Prestashop version you using. Especially the version 1.7.6, there's alot of changes/update made.
After much try and error I have found a solution. I have taken each module folder under the dependencies directory of the theme and make a zip file with it. Then I have installed each module with the zip from the administration module dashboard. After installing all the modules, I'm able to install the theme without errors and everything works fine.
Check if those modules(which give errors) exist in a theme dependencies directory and remove them one by one from the directory and all dependencies from theme.yml file in a config directory. It just may be that themes are outdated and contain outdated modules
Related
When editing javascript files in Sublime Text Editor 3.x, I get the error:
Oops! Something went wrong! :(
ESLint: 6.0.1.
ESLint couldn't find the plugin "eslint-plugin-chai-expect".
(The package "eslint-plugin-chai-expect" was not found when loaded as a Node module from the directory "C:\workspace\flltools".)
It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
npm install eslint-plugin-chai-expect#latest --save-dev
The plugin "eslint-plugin-chai-expect" was referenced from the config file in "modules\scoring\.eslintrc.yml".
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.
I tried multiple solutions I found online, including removing global ESLint/moving all ESLint related packages to be global, to altering the SublimeLinter.settings file. The problem only occours when running lint through Sublime. When I run eslint command, it works perfectly.
If anyone has any idea why this is happenning please help me!
Thank you
As far as I can tell this is indeed a problem with migrating to ESLint v6. But it's not a global installation problem.
The problem is now that ESLint looks in the working directory where the eslint command is run from. As you say in your comment:
It seems to be looking in a parent folder (as you can see in the error it's looking in c:/workspace/flltools, whereas my project is in c:/workspace/flltools/modules/scoring
So your editor is running eslint in the parent directory rather than in the directory where the package.json file is. I'm guessing your editor has the project root one level higher than where the package.json file is.
It does look like this has now been patched in the SublimeLinter plugin via github issue #1626: Wrong working directory on nested local eslint installs (breaks eslint#6)
Note that I have similar issues with both VSCode and Vim, so it's not a specifically a Sublime Text thing, more just an ESLint thing.
In the ESLint v6 migration doc, it has a section on "Plugins and shareable configs are no longer affected by ESLint’s location". It suggests:
If you use a config file located outside of a local project (with the --config flag), consider installing the plugins as dependencies of that config file, and setting the --resolve-plugins-relative-to flag to the location of the config file.
This --resolve-plugins-relative-to will fix the problem in that you can specify the path to where the package.json is inside there.
Most probably you have updated your ESLint to v6.
As per Migrating to 6.0 Docs
If you use a global installation of ESLint (e.g. installed with npm install eslint --global) along with plugins.
Then you should install those plugins locally in the projects where you run ESLint.
In your case, Install eslint-plugin-chai-expect and other plugins(if used) as devDependencies locally to your project.
npm install --save-dev eslint-plugin-chai-expect
If your config file extends shareable configs and/or parsers, you should ensure that those packages are installed as dependencies of the project containing the config file.
I have never used Composer, but I want to use PHPSpreadsheet package, and it is recommended that Composer is used.
I am on a MAC using XAMPP and Netbeans.
I have installed Composer, and I have run the following command to get and install the PHPSpreadsheet package.
php ../../Composer/composer.phar require phpoffice/phpspreadsheet
I am running this in my project folder, (hence the ../../ to where Composer.phar is located.
This downloads the files into a vendor folder in my project folder.
What should I do then? Do I need to keep it in the Vendor folder, or can I move into a folder of my choice?
Netbeans has Composer options in the menus, but as far as I can see, this is for creating dependencies rather than installing packages.
I know I am totally missing the point of Composer somewhere, but have spent hours just trying to get this work.
Many thanks
You should really start with the docs -> https://getcomposer.org/doc/01-basic-usage.md
You have to keep the vendor directory - this is where all dependencies are kept. If you require more packages - then they will be installed in that directory.
After requring the package you have to load it so the PHP will know all the classes. Composer comes with great autolader. It is located by default in vendor/autoload.php. So what you have to do now is to require this file in your project. After that all classes from composer packages will be loaded automaticaly each time you use them in the code :)
I hope this will help you with this great tool. Cheers.
I installed a Joomla 3.6.5 and now I cannot install any packages.
And this is the error I've got :
Unable to find install package
This happens when I click on 'Add "Install from Web" tab' button too!
I tried reinstalling and upgrading to 3.8.5 but nothing changed! I can install nothing!
Update:
Folder permissions:
Anything related to installation error, you should check
Your temp file location is correct or not
Your temp folder has appropriate permission or not.
You can attach screenshot of your folder permissions here.
I have two suggestions.
(1) The problem may be because upload_tmp_dir isn't set in your PHP config.
Look in SYSTEM > SYSTEM INFORMATION > PHP INFORMATION and check if upload_tmp_dir has been set. If not, you need to edit php.ini
On our servers (which use open base dir), the setting is:
upload_tmp_dir=/tmp
Depending on your server configuration, this value could be different for you.
(2) The other place to check is the value in SYSTEM > GLOBAL CONFIGURATION > SERVER
If you haven't already done so, try using the full server path to the tmp directory, rather than say a path relative to your home directory.
Good luck!
The temp folder is not where you have told Joomla it is.
I know this is an old topic, but maybe my solution might be helpful for someone...
Error: Unable to find install package (and other errors like that)
is nothing more than permissions error check... So, you have to give right permissions to yourself for:
/var/www/html/nameofyoursite/languages,
/var/www/html/nameofyoursite/tmp,
/var/www/html/nameofyoursite/administrator/languages,
/var/www/html/nameofyoursite/administrator/manifest/everythinginmanifestfolder,
/var/www/html/nameofyoursite/administrator/modules,
/var/www/html/nameofyoursite/administrator/logs.
That's it! Now you can install languages and everything else...
(I found this solution yesterday, and cp my answer from joomla's forum)
I install extension Instant Search by Magestore.after that i see this error.(http://www.magentocommerce.com/magento-connect/product-instant-search.html)
Fatal error: Class ‘Mage_Magenotification_Helper_Data’ not found in /home/****/public_html/app/Mage.php on line 546
I am facing this problem. I have installed Product Instant Search .
http://www.magestore.com/product-instant-search.html
Please help me.
Thanks
If you still get this error-message, you have to install the Magenotification Extension from Magestore.
To install the extension, checkout the extension from google code:
svn checkout http://my-wholesale.googlecode.com/svn/trunk/ my-wholesale-read-only
then copy the directory my-wholesale-read-only/app/code/local/Magestore/Magenotification to your /app/code/local/Magestore/ directory and create a Magestore_Magenotification.xml under app/etc/modules/.
Double check all the module files have been uploaded properly, refresh all the caches and ensure the compiler is off (or recompile). It is most likely the XML cache needs refreshed or the compiler needs recompiled.
There are some Magento Connect extensions that I find myself installing every time I create a new project, such as Fontis_Recaptcha, Mass_Product_Relater, HM_DeveloperToolbar, ModuleCreator, Alanstormdotcom_Layoutviewer, etc. What's on your list?
Does anyone know of a capability to automate the installation of a base set of modules? In the same way that Mage itself installs all its modules. I guess a bash or phing script to automate PEAR? Thoughts?
I would take another approach. Install a clean installation and add all your extension. When your done export the DB and zip all the files. Then you should be able to use the files and the DB as a base for all your magento installations...
I do the same with Joomla, have not tried that with magento yet, but it should work.
Cant you just use the auto installer script as provided and maintained here:
http://www.magentocommerce.com/wiki/groups/227/magento_bash_script_installer
and edit it to install your desired extensions
ie just add ./pear install xxxxxxx at the end of the script.