You are here

Frequently Asked Questions

General Questions

For Regular Users

For Agency Users


How does Evercurrent work?

Evercurrent has two components: a module that you install on your website, and a central dashboard which tracks available updates. When you install the Evercurrent module, it will periodically poll your site's core and modules and compare your version against the most current available version online. If Evercurrent detects that one or more of your modules are not up to date, it will send a message to your dashboard (and optionally an email to you) with information on what site is affected, which module needs to be updated, and to which version. It is then up to you to ensure the updates are applied.

Updates are coded into one of several categories:

  • Security updates
    Urgent updates that affect the security of your site and users.
  • Minor updates
    Updates to functionality that do not affect security.
  • Revoked releases (rare)
  • Unsupported releases (rare)

How can I get support?

You can email our support team at support@projectricochet.com with questions.


How do I start monitoring a new website for updates?

Choose Site Keys → Add New Key from the navigation menu. Then fill out the following fields:

  • Site name
    A human-readable name for the site; i.e. "Joe's Bank"
  • Description
    A description for the site. Optional.
  • Website URL
    The URL of the website to monitor, complete, with protocol (usually "http://" or "https://"). If your site has multiple development/production environments, we recommend using the URL of your production environment.
  • Send update mail
    If checked, your client will receive an email each time a core or module update is detected by Evercurrent.
  • Update types that trigger emails
    You can limit the emails your client will receive by filtering out certain types of updates.
  • Enforce site URL check
    Check this box if you are using a development environment with multiple instances of your site, i.e. dev, stage, and prod. This will eliminate duplicate or conflicting update messages from environments other than the URL you've entered above.

How can I choose the types of updates I want to see on my dashboard?

Click the name of a client on your dashboard. On the screen that follows, you will see all updates available for all of your sites. At the top of the screen, you have several options to filter this list:

  • By website
  • By update type
    You may choose all updates or security updates only.
  • By snooze status
    By default, updates you have snoozed are hidden from this display. You can show them by choosing "Show snoozed".
  • By completed status
    You can view previously completed updates by choosing "Show completed updates" here.

How can I choose the types of updates I want to be notified about via email?

Click "Site Keys" in the main menu. Click "edit" on the site you wish to edit. Look down the page for the section entitled "Update types that triggers emails." There you can choose which types of updates will cause an email notification to be sent (shift-click to select multiple).


How can I assess the urgency and importance of an update?

For more information on the exact content and risk value of any update, click the version number in the "Recommended Update" column to visit the update page on drupal.org.


How can I fix a site that isn't reporting?

There are a number of reasons a site may not be reporting updates. Here are some steps to take to resolve the issue:

Module settings on your site

  • Visit the Evercurrent module settings on your own website at http://<yourwebsite.com>/admin/config/system/ricochet_maintenance_helper.
  • Ensure that "Enable sending update reports" is checked.
  • Verify that your API key has been entered and matches what is configured on your Evercurrent dashboard.
  • Under the "Advanced" section, check the frequency of updates sent from your site. We recommend a setting of "Every hour."
  • You may also manually trigger an update to be sent when you click "Save" on this page by checking "Send update report when saving configuration."

Site URL check and settings.php

We recommend turning on "Enforce site URL check" in your site's settings on app.evercurrent.io if you have multiple environments in your release workflow (dev, stage, prod, etc.). This prevents multiple copies of the same update being reported by each environment. However, this setting can cause problems if your site's base URL is not set correctly in settings.php. To fix this problem, you can either:

  1. Set a base URL for your site.
    • Open the file where your site's base URL is configured, usually at sites/default/settings.php.
    • Search for a line that looks like # $base_url = 'http://www.example.com';. Uncomment the line if necessary and change the value to your site's URL. For example, if your site is accessed at http://www.mysite.com, change the line to $base_url = 'http://www.mysite.com';. Do not use a trailing slash after the site URL.
    • Your base URL settings may be in another file, such as sites/default/local.settings.php. Please consult your site administrator if you are not sure where to look.
  2. Disable "Enforce site URL check" in your site's settings on http://app.evercurrent.io.

PHP version on your server

  • Please note that the Evercurrent module requires PHP 5.3 or higher to run. In addition, using old versions of PHP is in itself a security risk. Consider upgrading to the latest version of PHP to ensure the security of your site.

How do I avoid receiving conflicting updates from multiple environments (dev, stage)?

Choose "Site Keys" from the main menu and click "edit" on the site in question. Check the "Enforce site URL check" to filter out update reports coming from URLs other than your site's production URL, which you should have entered above in the "Website URL" field.


How can I delete a site I no longer wish to monitor?

Click "Slient Keys" in the nav bar. Then click "Delete" on the site you wish to remove.

This operation cannot be undone.


How do I start monitoring a new website for updates?

The websites you monitor with Evercurrent must be associated with a client. If you don't yet have any clients set up, click on the "Add new customer" link at the top of the screen, fill in a username and email address for the new client, and click "Create Account." You will receive a password that this client may use to log in to Evercurrent at the client level, and you will also be able to manage their sites from within your agency account.

Once you have created a client, click the "Add new site" link at the top of the screen. There are several fields to fill out:

  • Site name
    A human-readable name for the site; i.e. "Joe's Bank"
  • Description
    A description for the site. Optional.
  • Client
    The client to associate the site with (see above). This should already be filled out.
  • Jira project key
    The project key to use when creating Jira tickets from Evercurrent. This is configured in Jira and is used as the prefix of issue tickets in your project. For example, if your project has tickets named "JB-100" and "JB-101," your project key would be "JB". This field can be left blank and edited later if you're not ready to configure Jira integration yet.
  • Website URL
    The URL of the website to monitor, complete, with protocol (usually "http://" or "https://"). If your site has multiple development/production environments, we recommend using the URL of your production environment.
  • Send update mail
    If checked, your client will receive an email each time a core or module update is detected by Evercurrent.
  • Update types that trigger emails
    You can limit the emails your client will receive by filtering out certain types of updates.
  • Jira configuration
    The Jira configuration settings to use for this project. You can leave this blank and configure it later if you are not ready to set up Jira integration yet. Read more about creating Jira configurations here.
  • Enforce site URL check
    Check this box if you are using a development environment with multiple instances of your site, i.e. dev, stage, and prod. This will eliminate duplicate or conflicting update messages from environments other than the URL you've entered above.

How can I choose the types of updates I want to be notified about via email?

From the dashboard, click the client whose website notifications you wish to edit. Then click the "Client Keys" tab in the top right corner and click "edit" on the site you wish to edit. Look down the page for the section entitled "Update types that triggers emails." There you can choose which types of updates will cause an email notification to be sent (shift-click to select multiple).


How do I avoid receiving conflicting updates from multiple environments (dev, stage)?

From your dashboard, click a client and then click the "Client Keys" tab in the upper right. Click "edit" on the site in question. Check the "Enforce site URL check" to filter out update reports coming from URLs other than your site's production URL, which you should have entered above in the "Website URL" field.


How can I delete a client whose sites I no longer wish to monitor?

Currently this operation is not supported. Please contact us at support@projectricochet.com to request a client to be removed from your account.


How can I delete a site I no longer wish to monitor?

Click the client whose website you want to delete and then click "Client Keys" in the upper right corner of the screen. Then click "Delete" on the site you wish to remove.

This operation cannot be undone.


How do I configure automatic creation of tickets in JIRA?

For your convenience, agency accounts have the ability to automatically create Jira tickets to address your sites'updates.

First you need to create a Jira configuration to store your Jira credentials and instance-specific data. To do this, click on the "Edit" tab at the top of your agency overview. Find the section on the page called "Jira Credentials" and click "Add Jira Configuration." Fill in all the requisite fields on this page, and then scroll all the way to the bottom and click "Save" (don't click "Add Jira Configuration" again).

Once this is done, click on "My Account" in the upper left and click on the client whose project(s) you wish to use this Jira configuration for (if you need to first create a client or a site, follow these instructions). Click "Edit" next to the site you wish to use. Near the bottom of the page you will be able to select the Jira configuration you've just created. Click "Save" after selecting it. Now you will be able to take advantage of the Jira integration for your security updates.


Why won't my configuration allow me to create JIRA tickets?

Verify that you have correctly filled out all fields in the Jira Credentials section of your account settings. If everything is correct there, also verify that the user you've specified has permission to file new issues in the Jira project itself.


How can I change the JIRA ticket number for an update I've already sent to JIRA?

On the update screen, click the module name whose ticket number you want to update. Click "Edit" in the top right corner of the screen. You may then enter a new value in the JIRA Ticket ID field and save the update.