Skip to content

EP Attribution

EP Attribution adds a small credit line to the footer of every page on your site:

Built on PageMotor. Designed by ElmsPark.

It is one toggle, it styles itself to suit your theme, and it works whether your site uses a standard PageMotor footer or a bespoke design with no footer at all.

Published by ElmsPark Studio.

  • One setting. A single checkbox turns the credit line on or off sitewide.
  • Theme-agnostic placement. Appends into your site’s own footer where there is one, or renders a slim strip at the foot of the page where there is not.
  • Adapts to your design. The stylesheet inherits your theme’s text colour and sits at low opacity, so it reads correctly on light and dark backgrounds without configuration.
  • On by default. Ticked once on first activation so the credit appears immediately. Unticking it is respected permanently.
  • No tracking. The plugin renders two links and nothing else. No cookies, no analytics, no external requests.
  • PageMotor 0.7 or later
  • EP Suite base class (bundled)
  1. Download ep-attribution.zip from the EP Suite downloads page.
  2. Upload via Plugins → Manage Plugins. Activate.
  3. Load any page on your site and scroll to the bottom. The credit line should be there.

The credit is switched on the moment you activate the plugin, so there is no third step.

Everything lives under Footer Credit:

  • Show the credit line. Tick to display the credit sitewide, untick to hide it. That is the whole plugin.

The settings screen also shows a small status panel telling you whether the credit is currently showing or hidden, and which two sites it links to.

The box is ticked once, automatically, the first time the plugin activates. After that your choice wins: if you untick it, it stays unticked. Deactivating or reactivating the plugin will not silently switch it back on.

PageMotor has no server-side “sitewide footer” hook, because footers are theme instances rather than a single global template. EP Attribution therefore places the credit in the browser, just before the end of the page, which is what lets one toggle cover every site regardless of theme.

It looks for your site’s footer and picks the last visible one on the page. That matters on sites where individual articles have their own <footer> element: the credit lands in the site footer at the bottom, not inside the last article.

  • Standard themes render a footer, so the credit is appended inside it and inherits its spacing and colour.
  • Bespoke designs often hide or omit the footer entirely. When no visible footer is found, the credit renders instead as a standalone strip at the foot of the page.

Because the credit is added in the browser, it will not appear in the page’s initial HTML source, and it will not appear at all for visitors browsing with JavaScript disabled.

Check the box is ticked under Footer Credit first. If it is, open your browser’s developer console and look for a JavaScript error from another plugin or theme script. The credit is injected by a small script at the end of the page, so an unrelated script that throws earlier can stop it running.

Also confirm you are looking at a normal page rather than the admin, and that you are not viewing a cached copy.

”It appears inside an article instead of at the bottom of the page”

Section titled “”It appears inside an article instead of at the bottom of the page””

The plugin targets the last visible footer or #footer on the page. If an article footer is rendering after the site footer, or the site footer is hidden, the article footer becomes the last visible one. Either make the site footer visible, or hide the trailing article footer.

Section titled “”It appears as a strip rather than inside my footer””

That is the fallback, and it means no visible footer was found. Usually the theme hides #footer with display: none or does not render one. This is expected on bespoke designs and needs no fix unless you would rather place it yourself.

”I unticked it but it is still showing”

Section titled “”I unticked it but it is still showing””

The setting takes effect on the next page load, so refresh. If it persists, you are almost certainly seeing a cached page: clear your browser cache, and any server-side or CDN cache in front of the site.

Section titled “”The text is hard to read against my footer””

The stylesheet deliberately inherits the surrounding text colour at reduced opacity rather than hardcoding a colour. If your footer sets an unusual colour, or sets none at all, add a rule for #ep-attribution in your theme CSS to override it.

Nothing to reconfigure. The placement is decided per page load, so a new theme simply changes whether the credit lands inside a footer or as a standalone strip. If it vanished entirely, check the plugin is still active on the new theme.

For a quick question about this plugin, EP Support inside your admin is the fastest option. The chat widget sits on every EP plugin settings page and knows which one you’re on, with starter questions and links preloaded for that exact screen.

For anything bigger — a bug report, a feature request, or a “how do I…” that needs a real reply — open a ticket at help.elmspark.com. A real person, helped by AI, writes the reply. Usually within a few hours. Tickets don’t disappear into the void.

  • Settings language menu. The language menu in this plugin’s settings now lists only the languages it is actually translated into, plus English, so you can no longer pick a language that changes nothing.
  • Section status. Each settings section shows whether that feature is switched on. On a site that also runs an older EP plugin, the section shows its plain title instead.
  • Fixes a doubled cache-busting tag on its stylesheet. On PageMotor 0.11 and later the page asked for the attribution stylesheet with two version tags on the end of its address (?v=…?v=…), because the core had started adding its own tag and the plugin was still adding one too. The file loaded correctly, so nothing was visibly broken; the address was just malformed. The plugin now leaves the tag to the core on 0.11 and later, and still adds its own on older cores, where nothing else would.
  • The same check now reads beta and release-candidate cores (such as 0.11b or 0.11rc1) correctly, which it previously mistook for versions older than 0.11.
  • No change to what the stylesheet does.
  • Fixes “Your session has expired. Please reload to ensure your security.” on PageMotor 0.11. The message appeared on this plugin’s admin screens even though you were signed in perfectly normally, and whatever you were doing failed to save.
  • Nothing was wrong with your session. PageMotor 0.11 started handling part of the security check that this plugin was already handling itself, and the two together made every save look invalid. The plugin now checks whether PageMotor has already done it.
  • Visitors who were not signed in were never affected, on any version.
  • There is nothing to reconfigure, and nothing else changed.