Problem Solving

Missing Class errors during install

In addition to their internal functionality, many of my addons make use of facilities provided in others to enhance their own capabilities. The consequence is that occasionally an update to an addon will depend, where another of my addons is installed, on an update to the other addon. 

Hence:

Before installing any of my addons, please make sure any of my addons already installed are up-to-date.

Javascript in another addon doesn't respond correctly when Syntax Anywhere is active on the page

The main way Syntax Anywhere can mess with JavaScript in another block is when you use the [code]...[/code] method of specifying syntax areas. Behind the scenes, Syntax Anywhere does some rewriting of the html to facilitate [code] sections, and doing so can result in other JavaScript event handlers becoming detached.

The simple solution is to not configure Syntax Anywhere to look for [code]..[/code] on any page containing JavaScript heavy blocks. Use any of the other methods of declaring sections to be highlighted such as <pre class="syntax_anywhere">...</pre>.

You can see Syntax Anywhere working on the same page as blocks that involve quite complex JavaScript on this site.

You can also exclude a block from any consideration by Syntax Anywhere by wrapping it with the class "syntax-anywhere-exclude" or specifying an id or class for the block in the Exclude section of thye Syntax Anywhere edit dialog.

Whoops on install

What we mean here is an internal code exception in an addon or the core when you click the install button from the Add Functionality dashboard page or when you visit a page after installing an addon package. 

If you experience such an issue, here are a few things you can check that may resolve the problem.

  1. Php Version. Check your php version is compatible with the addon, For example, check if you are running php5.6 when an addon requires php7+. You can find the php version in the report at /dashboard/system/environment/info. As a general guide, if your site is concrete5 version 8+ then aim to run on at least php7.2. (It will run on lower versions, but less efficiently)
  2. Database Entities. concrete5 uses a database abstraction layer called Doctrine. Doctrine works by creating proxy classes that map between php data and the database and sometimes these get out of step or muddled into a chicken and egg dilemma. The dashboard page at /dashboard/system/environment/entities has a switch to control when the proxy classes are regenerated. Try placing this into Development mode when installing an addon package (but remember to disable development mode to speed up a live site)
  3. Cache. concrete5 makes extensive use of a number of different caching mechanisms to speed up web pages. When installing a package, sometimes outdated cached data causes issues with the install. Try disabling all the caches at /dashboard/system/optimization/cache when installing an addon package (but remember to re-enable the caches for a live site).
  4. Theme. Most marketplace themes are well behaved. Nevertheless, sometimes a theme can interfere with an addon package, so try switching the site theme back to Elemental using /dashboard/pages/themes. You won't loose any content on the front of your site, but some page areas may not be shown until you swap back to your theme.
  5. Middleware. Some addons implement middleware layers that manipulate pages before and/or after the main concrete5 rendering of each page. If such addons are installed, there is a possibly they could interfere with the dashboard and other addon installation. Most such middleware implementations include condition checks to ensure they don't mess with the dashboard, but perhaps you can switch them temporarily off just to be sure.

If you experience a code error on or immediately after install and need assistance, please use the Get Help link from the addon marketplace page to report the problem. On the Whoops report, click the [copy] button immediately below the error message. That will provide a stack trace you can paste into the help request and save time having to request that report later.