I am trying to get a copy of ps_cleaner to clear the dummy data from my 1.7 version of Prestashop and I can't download straight to my prestashop version so I have gone to the Git location to take a copy and upload it but that doesn't work. Is there something I have to do to take it from Git to install on Prestashop 1.7
You should better download the zip and install directly via the system, git are not always perfectly fitting last refactoring.
Download module as zip file then unpack first then rename the folder name with the module name "ps_cleaner".
I mean just remove the branch Name (_master) from your module folder (such as ps_cleaner_master), Then again create a zip and install this.
Related
I am using Laravel Backpack and trying to setup roles and permissions in it.
Command I am using is:
composer require backpack/permissionmanager
It is throwing this error again and again:
Can anyone know why is it so? What else I could do to get it installed?
It looks like your problem is NOT installing backpack/permissionmanager, but in installing backpack/devtools. That is a private package, where you only have access to the dist, not the source.
In short, using Composer you can install things:
(A) from dist - will unzip the package to your vendor directory;
(B) from source - will git clone the package to your vendor directory;
It looks like you're trying to do a git clone for backpack/devtools, but since you do not have access the source, you can't do that.
If you've run the composer command using the --prefer-source flag, don't. Otherwise, check your composer.json file for any mentions of this preference. You should make sure you're downloading from dist, not source.
In recent days, it has become impossible to update the modules. I receive an error such as "this is not a valid module name".
Is it possible to manually update the modules by retrieving the latest files from Github? I tried to replace the files with those of the latest version but, it doesn't change anything at all.
I precise that I try to update official modules that are pre-installed in Prestashop.
Yes you can do this.
Grab the moduble from GitHub, wrap the whole module (the ps_xxxxxx directory) in a zip file then install the module from the admin interface.
Don't replace the files manually by using the filesystem (or at least try not to).
If you replace the modules in the modules directory you won't trigger the module "install" method, so if the new version needs some initialization it won't work properly.
EDIT:
Some modules have dependencies, for example ps_facetedsearch will require you to install composer and run 'composer install --no-dev' before you can pack it into a zip.
Alternatively you can get a json list of native prestashop modules here (replace [VERSION] with the version of prestashop you want, ex 1.7.6.4) :
https://api-addons.prestashop.com/?format=json&iso_lang=en&iso_code=all&version=[VERSION]&method=listing&action=native
Then you can download the module with its id with this URL (replace [VERSION] and [MODULE_ID] :
https://api-addons.prestashop.com/?format=json&iso_lang=en&iso_code=EN&version=[VERSION]&method=module&id_module=[MODULE_ID]
Two computers are working on the SAME repository but first computer detect the library and work well but second computer not detect it and show "Error 'PhpOffice\Phpspreadsheet\Reader\Xlsx' not found".
In vendor, the library also exist.
composer.json and composer.lock also the same on both computer.
One thing is that by git ignore, I use yii's composer mechanism at 1st computer but at sec computer(err computer), I add library manually.
If you want to use a composer package, you absolutely need to install it using composer. This ensures that the autoloader is generated properly and your class can be found through PHP.
Copying library files into vendor directory is not enough to install it. During installation Composer creates autoload script with information how to find all classes installed by Composer. If you just copy library files, Composer will not even know that it exist and will not able load any class from it.
If you cannot use Composer on server/computer A, you should install all dependencies on different computer (B) and copy the entire vendor directory into server/computer A. Autoload definitions are in vendor so it should work if you copy the whole dorectory.
Some modules can be auto-updated in backoffice by clicking the update button. However if the module is from an other source than prestashop itself (e.g. github) the module needs - afaik - to be updated manually.
So how should one handle updates?
Download ZIP and
unzip it over the corresponding modules folder (/modules/acme/)
unzip and rsync it to /modules/acme (rsync -trv /tmp/acme /modules)
Same as 2 but with --delete
Delete the folder completely and unzip the new one in place like rm -rf /modules/acme and cp -a /tmp/acme /modules/acme
Others ...
Side note: what about the config.xml and possibly other generated files?
Same applies for theme updates, how to handle these?
Concerning current version Prestashop 1.7+.
If the module upgrade is made correctly (you can check if module version is updated in main module class constructor and uses upgrade scripts in upgrades folder and files inside the module) you can unzip over it. Then visit the modules list page in backend and module upgrade will run. config.xml is auto (re)generated and used only for optimizing module list loading in the same backend page - it has no effect on module behaviour itself.
For themes you can also just unzip over the last one.
When I am in doubt with any upgrades I make a development copy of the store and do upgrades there first and see if everything is ok then do upgrades on live instance.
You can perform the upgrade automatically with this free module
https://www.prestashop.com/forums/topic/820013-migrate-or-upgrade-prestashop-16-or-other-versions-to-17-%E2%80%93-free-module/
Hope it helps
MercurialEclipse' homepage has links to an update site and, indirectly, to downloadable archives. I can't use the update site since my machine is not connected to the Internet, so I'm downloading the archive on a connected machine and copying it to the target machine.
But now - what do I do?
Putting the JAR file (com.vectrace.MercurialEclipse_2.1.0.201304290948.jar ) in the 'dropins/' folder has no effect.
Putting the JAR file in the 'plugins/' folder also has no effect
Eclipse will not treat the archive as an update site (using Install New Software | Add)
So how do I install this thing?
These steps are untested but they should replicate the update site on your local file system:
Clone this repository: https://code.google.com/a/eclipselabs.org/p/mercurialeclipse.wiki/
Download the stable plugin jar file from the downloads section and place it in update_site/stable/plugins
Edit update_site/stable/site.xml and remove all the <archive ..> elements.