Troubleshooting

Last Updated: 13 September 2026 Hits: 36

Check the most common causes first

If Alamarte Cookie Consent Pro does not behave as expected, use this guide to review the most common problems. Most issues can be identified by checking the plugin status, saved preferences, content configuration and the code generated on the public part of the site.

Perform tests in a private or incognito window.

If the browser already has a saved consent decision, its behaviour may differ from that of a new visitor. A private window makes it easier to check the notice and content blocking from an initial state.

The notice does not appear

First check that Alamarte Cookie Consent Pro is enabled in the Joomla! plugin manager.

Then test in a private window to rule out an existing consent decision saved in the browser.

If the problem occurs only on a specific page, also check whether that page is included in the notice exclusions.

Cookie notice exclusions

The notice appears again

Check whether the previous preferences are still stored and whether the configured consent retention period has expired.

This can also happen when testing in different browsers, profiles or private windows, because each environment may have its own consent state.

Content loads before consent is given

Review the code of the content you want to block. If it is an iframe, the external address should not remain in the src attribute.

For an iframe prepared for Alamarte Cookie Consent Pro, the address should be stored in data-acc-src and the category should be specified using data-acc-category.

If the resource is loaded by another extension, module or independent script, that second integration must also be reviewed.

Blocking content until consent is given

The iframe does not activate after consent is given

Check that the iframe still contains both data-acc-category and data-acc-src.

Also check that the category name is correct and corresponds to the category you are authorising during the test.

If you use a visual editor, reopen the code after saving to check that it has not modified the attributes.

The `data-*` attributes disappear

Some editors may clean or modify certain HTML attributes when saving.

If you use JCE or another editor, check that it allows the custom attributes used by Alamarte Cookie Consent Pro to be preserved.

After saving the content, review the source code again to confirm that the attributes are still present.

YouTube loads before consent is given

Check that the video code does not still contain the URL inside src.

To keep it blocked, use data-acc-src for the video address and data-acc-category for the corresponding category.

Blocking YouTube videos

Google Maps is not blocked

Review the iframe provided by Google Maps and check that the complete URL has been moved from src to data-acc-src.

Do not keep the actual URL in both attributes at the same time.

Google Maps and other external iframes

An external script continues to run

Check every location from which the service may be loaded.

Code may exist in the template, a module, an extension, a tag manager or a manually added integration.

If there is a second independent load, blocking only one of the code fragments will not prevent the service from continuing to work.

Google Analytics and external scripts

The notice does not appear in the expected language

On multilingual sites, review the active language of the page and the corresponding site configuration.

Also check Joomla! associations when using different pages or menu items for each language.

The notice does not display correctly on mobile

Review the specific settings for mobile devices and check the result on a real screen or using the browser's developer tools.

Pay attention to text size, buttons, available space and the ability to scroll when the content is longer.

Desktop and mobile customisation

Quick check

Before looking for a more complex cause, check the following:

Alamarte Cookie Consent Pro is enabled.
The test is performed in a private window or with a known consent state.
The page has not been accidentally excluded from the initial notice.
Blocked iframes use data-acc-src and do not keep the URL in src.
The data-acc-category attribute contains the correct category.
The editor has not removed or modified the data-* attributes.
The same service is not being loaded from another extension or location on the site.

Technical API check

If you are developing a custom integration, you can check from the browser console that the public API is available:

window.AlamarteCookieConsent

You can also check the current consent state:

window.AlamarteCookieConsent.getConsent()

These checks are intended for technical diagnostics and are not required for normal plugin use.

Events and API

If the problem continues: note which page is affected, which category is being used, which action the visitor performs and what result occurs. If blocked content is involved, also keep the HTML code being used. This information makes it easier to identify whether the problem is in the Alamarte Cookie Consent Pro configuration or in the way the external service is integrated.