Download the PHP package hypejunction/notifications_editor without Composer

On this page you can find all versions of the php package hypejunction/notifications_editor. 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?

Example code of hypejunction/notifications_editor

Informations about the package notifications_editor

Notification Editor for Elgg

Elgg 2.0

Features

Interface

Subscription Notifications

The plugin will automatically hijack notifications for all registered notifications events (events that send out subscription notifications). The plugin will first try to locate a view that corresponds to the subject, summary and body of the notification, and use the template view, if it's found. Administrators have the ability to edit the templates, in which case a new template object is created and stored in the database.

Notification views are stored in: /views/default/notifications/$action/$object_type/$object_subtype/$part.$language.html, where $action is an action triggering the notification event, $object_type is object, group, user, site, annotation or relationship $object_subtype is an entity subtype, or annotation name, or relationship name $part is either subject, summary or body $language is the language of the recipient

Custom (Instant) Notifications

For this to work, your delivery method handlers need to trigger 'format','notification' hook and pass the notification object as return. For email delivery method, enable notifications_html_handler plugin.

You can send instant notifications using templates by passing a template name with the notification parameters:

You can then edit your templates, and reference your params as so:

To make templates editable by admin, register them:

Below you can see how to send a notification using a custom template.

Let's say we want to notify a user that their account has been created:

Properties

Properties available in templates:

See mustache reference for information on ternaries and loops

Available in all notifications

**{{sender.name}}** Name of the sender
**{{sender.getURL}}** URL of the sender's profile
**{{sender.XXX}}** Any metadata or method attached to the sender object (e.g. {{sender.language}})
**{{recipient.name}}** Name of the recipient
**{{recipient.getURL}}** URL of the recipients's profile
**{{recipient.XXX}}** Any metadata or method attached to the recipient object (e.g. {{recipient.first_name}})
**{{language}}** Language of the recipient
**{{site.name}}** Name of the site
**{{site.getURL}}** URL of the site (with the trailing slash)
**{{params.XXX}}** Additional params passed to the notification object. The actual available values depend on the notification

Available in subscription notifications

**{{action}}** Action name that triggered the subscription notification event
**{{actor.name}}** Name of the actor (a user performing an action)
**{{actor.getURL}}** URL of the actor's profile
**{{actor.XXX}}** Any metadata or method attached to the actor object (e.g. {{actor.language}})
**{{object.XXX}}** Depending on the event, an object is either an entity, or an annotation, or a relationship. Available properties may vary depending on that.
**{{target.XXX}}** Target of the event: For events that involve Elgg entities, the target is the container entity, e.g. if object is a blog, the target is either a user or group For events that involve annotations, the target is an entity that that annotation is made on For events that involve relationships, the target is an object with subject and object properties, where subject represents the subject of the relationship and object represents the object of the relationship

All versions of notifications_editor with dependencies

PHP Build Version
Package Version
Requires php Version >=5.5
composer/installers Version 1.*
hypejunction/mustache Version ~1.0
hypejunction/forms_api Version ~1.0
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 hypejunction/notifications_editor contains the following files

Loading the files please wait ....