Dashboard > Extend concrete5 > Upload Package
Package magic can 'upload' packages from a range of sources.
Uplods are checked for a range of issues and rejected if any problems are found.
If an upload does not contain a concrete5 package or is incompatible with the concrete5 version, it will be rejected.
Further checks look at whether a package is cleanly built.You have checkbox control over which issues are detected, by ticking to ignore specific checks. Further checks can be added by speifying glob matches.
If you have a good reson for installing a package containing a file that fails one of these validation checks, you have two choices. You could disable the entire class of checks by deselecting the applicable checkbos. Or you can specify a glob match to exclude just that file from checks using "Skip validation for files matching". For example, if you want to allow .htaccess files, a glob pattern of */.htaccess would allow any subdirectory of the package to contain .htaccess files.
You can similarly specify additional validation through "Detect files matching". Here each line comprises a glob match for the check to apply, then text to use as an error message. For example, entering */Gruntfile.js unwanted Grunt will complain if the package contains a Grunfile.js and provide the error message "Unwanted Grunt".
When a new package is successfully uplaoded, the package is immediately shown in the core Extend concrete5 > Add Functionality > Awaiting Installation section, ready for you to do any of Install, Apply Package Build Tools or even download a rebuilt archive without installing.
When an already installed package is uploaded, the default behaviour is to run the upgrade immediately. If that is not possible, the core Extend concrete5 > Update Add-ons page is loaded to run the upgrade.
Any update to a package source is made atomically. After running a Package Magic Upload, the package source will be either all the new source, or should the upload fail, all the old source.
Package Magic can load packages from sources provided by Package Source plugins.
Functionality can be extended by adding plugin classes for additional Package Sources. Package Source plugins are simple classes that provide the functionality to adapt Package Magic to alternative package sources. They should inherit from PackageSourcePluginBase. Details are provided by comments in the code.
Plugins can be added by placing the plugin classes at packages/anyPackageName/src/JtF/PackageMagic/PackageSources/Plugins/PluginName or application/src/JtF/PackageMagic/PackageSources/Plugins/PluginName. Plugins can also be similarly placed beneath the plugin type's namespace declared in a package controller's AutoloaderRegistries.
Load a package zip file from an FTP source.
Load a package arhcive from an FTP or SFTP source. A further dialog manages a list of FTP hosts allowing hosts to be added, removed, edited and selected.
List package archives held in an FTP repository and select to load.
Load a package archive from an FTP or SFTP repository. As with From FTP, a further dialog manages a list of FTP hosts allowing hosts to be added, removed, edited and selected. This source provides a similar capability to From Local Repository, but for an FTP source. Once configured with an FTP or SFTP directory as the root of the repository, package archives will be selectable from the structure beneath that directory.
Choose a package zip file from the File Manager.
Select a package zip archive file that has already been uploaded to the site using the File Manager. Allowed File Types must be configured to include .zip files.
Select a package zip file from the incoming files directory.
When uploading files to a site by FTP, the usual FTP location is application/files/incoming. With this package source, any package archives in the application/files/incoming directory are listed and selectable for upload.
List package archives held in a structured repository directory and select to load.
Once configured with a local system directory as the root of the repository, package archives will be selectable from the structure beneath that directory. The directory path must be directly accessible to the web server.
Select a package zip file from the /packages directory.
Sometimes a package .zip file is uploaded by FTP or SSH directly to the /packages directory. With this package source, any package archives in the /packages directory are listed and selectable for upload.
Get archive from URL or filepath.
Enter the URL or filepath from which a package zip archive file can be copied to the server. If a filepath is entered, it must be directly accessible to the web server.
Upload a package zip file.
Select a package zip archive file to upload to this site from your own computer.
Pick a submission from the PRB.
This source is only relevant to current PRB members. List PRB submissions and install them directly to your PRB test site. You will be required to copy two ConcreteCMS cookies from your browser developer console. These will saved encrypted.