Recent comments

πŸ‡ΏπŸ‡¦South Africa nravens

I tested it and it worked for me. I created the database table for aggregator_feed and also aggregator_item

This resulted in the modules/uninstall url to load and allowed me to uninstall the aggregator module, this time successfully.

πŸ‡ΏπŸ‡¦South Africa nravens

Can I simply go to phpMyAdmin then open the database that's missing the table for "aggregator_feed"

Then click on Operations and under "Create new table" under "Table Name" add "aggregator_feed" and create?

Then from there, will I be able to uninstall the aggregator module (core version)?

πŸ‡ΏπŸ‡¦South Africa nravens

I'm following the instructions as per the Upgrade Status module page but I am unable to complete the step 2 so my question is whether that step is essential for the module to work?

πŸ‡ΏπŸ‡¦South Africa nravens

nravens β†’ created an issue.

πŸ‡ΏπŸ‡¦South Africa nravens

I have the same issue as in #6 where the images are seen separately most of the time when logged in and occassionally when not logged in.

I've using Drupal 10.2.3 and 2.0.4 of this module.

πŸ‡ΏπŸ‡¦South Africa nravens

I seem to have resolved this by following these steps:
In composer.json I added this
"platform":{
"php":"8.1.25"
}
below - "sort-packages": true,

That solved the PHP version requirement but running composer "drupal/core-*" --with-all-dependencies said there was nothing to install

Then I ran:
composer require drupal/core-recommended:10.1.6 drupal/core-composer-scaffold:10.1.6 drupal/core-project-message:10.1.6 --update-with-all-dependencies

This updated the site to 10.1.6

πŸ‡ΏπŸ‡¦South Africa nravens

Tested and it works, thank you!

πŸ‡ΏπŸ‡¦South Africa nravens

Hi,
Thank you. I will test this. Do I need to uninstall the current version or can I just run?:
composer require 'drupal/easy_google_analytics_counter:3.x-dev@dev'

I assume it will just upgrade to the 3.x branch but it being a dev version, I'm unsure.

πŸ‡ΏπŸ‡¦South Africa nravens

nravens β†’ created an issue.

πŸ‡ΏπŸ‡¦South Africa nravens

I get the same error with Drupal 9.5.9

πŸ‡ΏπŸ‡¦South Africa nravens

Has this patch been applied to the latest release?

Production build 0.71.5 2024