Title: AlertWire
Author: AlertWire
Published: <strong>December 16, 2014</strong>
Last modified: January 5, 2017

---

Search plugins

This plugin **hasn’t been tested with the latest 3 major releases of WordPress**.
It may no longer be maintained or supported and may have compatibility issues when
used with more recent versions of WordPress.

![](https://s.w.org/plugins/geopattern-icon/alertwire.svg)

# AlertWire

 By [AlertWire](https://profiles.wordpress.org/alertwire/)

[Download](https://downloads.wordpress.org/plugin/alertwire.zip)

 * [Details](https://wordpress.org/plugins/alertwire/#description)
 * [Reviews](https://wordpress.org/plugins/alertwire/#reviews)
 *  [Installation](https://wordpress.org/plugins/alertwire/#installation)
 * [Development](https://wordpress.org/plugins/alertwire/#developers)

 [Support](https://wordpress.org/support/plugin/alertwire/)

## Description

**AlertWire** is a system for centralized administration of alert/messaging for 
multiple sites.

Once your site has been configured in the AlertWire system, you can add this plug-
in and set the data-token to enabled the checking of alerts. When the
 page is rendered,
a `<script>` tag will be inserted into the document being rendered.

_How AlertWire Works_

 1. The page is generated with the correct API server and `data-token` configured, 
    typically added to the bottom of the page `body` tag.
 2. An async script tag is executed (late as possible) which loads a small (<4K) javascript
    plug-in. This plug-in has no dependancies and will
     not interfere with any existing
    frameworks like jQuery
 3. A cross-domain JSON request is made to the AlertWire API service to determine if
    there are any active alerts for the `data-token` specified.
 4. If there are one or more alerts to view, a CSS style-sheet will also be loaded 
    from the API server.
 5. The alerts are then generated dynamically into the document and styled automatically.
    There are several formats that are rendered
     differently (e.g. page-top, lightbox,
    etc.).
 6. Tracking pixels are generated to record when a check-in for alerts cccurs and when
    a view or close or click-through of an alert occurs.

_Notes_

 * The javascript plug-in and CSS style-sheet are publically cached from a CDN and
   are very small, the impact on load times should be tiny.
 * The CSS file is only loaded if there are alerts to be rendered.
 * The javascript plug-in only introduces one symbol into the global scope, the 
   _AlertWire_ module. All other functionality is behind that scope.
 * The plug-in will set a cookie when a user closes an alert to ensure it isn’t 
   displayed again. Depending on the alert type, this cookie may be a
    session cookie
   or a durable cookie with a 1 year expiration.
 * A very small font file will be downloaded for the alert icons the first time 
   an alert is displayed to an end user.

## Screenshots

 * [[
 * The plug-in settings screen, where you enter the `data-token` and select into
   what pages the script is injected.
 * [[
 * The script that is injected at the bottom of the page.

## Installation

#### Automatic Installation

 1.  Log into your WordPress admin
 2.  Click ‘Plugins’
 3.  Click ‘Add New’
 4.  Search for _AlertWire_
 5.  Click ‘Install Now’ under _AlertWire_
 6.  Activate the plugin through the _Plugins_ menu in WordPress.
 7.  Navigate to the _Settings/AlertWire_ page
 8.  Enter the `data-token` value provided on the site-setup page from the _AlertWire_
     system.
 9.  Optionally enter the ID (or other valid CSS selector) for the container element
     alerts should be inserted into.
 10. Select if alerts should be shown on the Home/Front Page and/or the Single Post
     pages.

#### Manual Installation

 1. Download from [here](https://www.alertwire.com/plugin/WordPress/AlertWire.zip) 
    and unzip the plugin.
 2. Upload the entire _AlertWire_ directory to `/wp-content/plugins/`.
 3. Activate the plugin through the _Plugins_ menu in WordPress.
 4. Navigate to the _Settings/AlertWire_ page
 5. Enter the `data-token` value provided on the site-setup page from the _AlertWire_
    system.
 6. Optionally enter the ID (or other valid CSS selector) for the container element
    alerts should be inserted into.
 7. Select if alerts should be shown on the Home/Front Page and/or the Single Post 
    pages.

## FAQ

  Will this slow down my pages?

 * The javascript plug-in is very small, is loaded from a global CDN (content delivery
   network) and is publically cacheable for years. Once a
    end-user has visited 
   your site it will be in their cache.
 * The javascript snippet does a very fast JSON call that is publically cachable
   for 5 minutes (default), so even if your site is very heavily loaded it will 
   be
    available long before any images are finished loading.
 * The CSS file is only loaded _if_ there are alerts to be rendered (not normally
   the case) and is also served from a CDN as a public long-cacheable file.
    This
   CSS file is under 2K and will only be downloaded one per end-user.
 * The font file for the alert icons is downloaded only if there are alerts to be
   rendered and is also served from a CDN as a public long-cacheable file.
    This
   font file is under 10K and will only be downloaded once per end-user.
 * The actual script execution is very fast and will not block on any downloads.

  Will this break my pages?

 * All alerts are injected into the page in a `div` tag and the CSS generated is
   scoped via a nonce-based id. It should never interact with any styling on your
   page
    but you might need to provide a placement anchor-element to ensure your
   site CSS doesn’t hide the alert. The script snippet allows you to specify a container`
   div` to act as the parent for the injected alerts in case you need to adjust 
   them around header or navigation elements.
 * The alerts are deleted from the page DOM when closed so nothing remains on screen
   if the end-user closes the alert. The lightbox-style alert acts as a complete
   
   page take-over and thus might have z-index issues, by default the alerts will
   be z-index of at least 10000.
 * If the javascript snippet has an error, nothing will be displayed so nothing 
   will need to be hidden.

  What about updates?

Since the _AlertWire_ javascript client-side plug-in is long-cached, it has built-
in ability to update itself to a new version. This is triggered by a
 version-requirement
declared in the JSON response and is completely automatic.

  How much does this cost?

The plug-in is free and use is included in the cost of an _AlertWire_ system. For
[more information about AlertWire](https://www.alertwire.com).

  What if I stop using AlertWire?

Since the script does essentially nothing if there are no alerts configured for 
the site, your script will just silently keep working and display nothing.

  Is this secure?

 * Yes, everything is _only_ loaded over HTTPS with OSCP stapling, Strict Transport
   Security (HSTS) required and preloaded in all browsers.
 * No admin defined assets other than _pure text_ are ever served to the end-user’s
   browser.
 * No CSS, JS, HTML or image assets are available for hacking/injecting.
 * All _AlertWire_-supplied content is served via the [CloudFlare CDN](https://www.cloudflare.com)
   with
    Qualsys SSL Labs [A+ SSL rating](https://www.ssllabs.com/ssltest/analyze.html?d=alertwire.com).
 * The administration application is fully tested against the OWASP best-practice
   criteria.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“AlertWire” is open source software. The following people have contributed to this
plugin.

Contributors

 *   [ AlertWire ](https://profiles.wordpress.org/alertwire/)

[Translate “AlertWire” into your language.](https://translate.wordpress.org/projects/wp-plugins/alertwire)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/alertwire/), check 
out the [SVN repository](https://plugins.svn.wordpress.org/alertwire/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/alertwire/) by [RSS](https://plugins.trac.wordpress.org/log/alertwire/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.2.2

Resaved all files in UTF8 _without_ BOM so we don’t bust headers

#### 1.2.1

Removed unneeded markup in setting page.

#### 1.2

Change default endpoint to https and note version compatibility to 4.7 and update
notes.

#### 1.1.1

Bump revision in the plug-in itself.

#### 1.1

Cleanup now that we’re in the WordPress plug-in repo.

#### 1.0

 * Initial release.

## Meta

 *  Version **1.2.2**
 *  Last updated **9 years ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 3.0 or higher **
 *  Tested up to **4.7.33**
 * Tags
 * [alert](https://wordpress.org/plugins/tags/alert/)[messaging](https://wordpress.org/plugins/tags/messaging/)
   [notice](https://wordpress.org/plugins/tags/notice/)[notification](https://wordpress.org/plugins/tags/notification/)
   [recall](https://wordpress.org/plugins/tags/recall/)
 *  [Advanced View](https://wordpress.org/plugins/alertwire/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/alertwire/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/alertwire/reviews/)

## Contributors

 *   [ AlertWire ](https://profiles.wordpress.org/alertwire/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/alertwire/)

## Donate

Would you like to support the advancement of this plugin?

 [ Donate to this plugin ](https://www.alertwire.com)