Download the PHP package elgg/community_plugins without Composer

On this page you can find all versions of the php package elgg/community_plugins. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package community_plugins

Elgg Community Plugin Repository

Data Model

There are two primary classes: PluginProject and PluginRelease. A PluginProject holds the general information about a plugin such as its description, license, and categories. The PluginRelease holds the release notes and the actual zip file or tarball. A PluginProject serves as the container for one or more PluginReleases.

Views Structure

The repository uses its own layout for many of the pages. This layout has a right sidebar, a main content area, and an optional footer. The other pages use the default sidebar on left with a main content area.

Search

Search uses Elgg's search plugin with its own custom hook: plugins_search_hook(). The hook makes sure that category selection is used and searches over some metadata fields. To support Elgg's search plugin, it also defines some views that are automatically picked up. This can be hard to follow if you do not have experience with the search plugin (or maybe it is just always hard to follow).

Contributions

What to contribute to the plugin repository? The first step is getting a Github account and forking the git repository.

All versions of community_plugins with dependencies

PHP Build Version
Package Version
Requires composer/installers Version >=1.0.8
bower-asset/flot Version ~0.8
bower-asset/chosen Version ~1.6
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package elgg/community_plugins contains the following files

Loading the files please wait ....