Brandon Dove

Thanks for the review @finomeno! I think you’re right, we could add some embed methods here. A shortcode and a block would be an awesome addition. Thanks for the idea!

• This reply was modified 9 months, 1 week ago by Brandon Dove.

@bogames16 We’re looking into this to see what the issue is.

@tsteur I removed that file and cleared the cache again (just for good measure). That seems to have fixed the issue! Thanks for your wonderful and prompt support, you saved the day!

@tsteur, thanks for the fast feedback, it’s truly appreciated. All three of those files were present in the folder in the production environment, but not in my local dev environment.

We’re hosted on WP Engine and use git deployments there. Because I had a similar problem with files not clearing previously, I deleted the entire Matomo plugin folder in my local dev environment and committed that change. I then added a fresh plugin folder from www.ads-software.com locally and committed that change. I then deployed the site to our production environment. I can’t explain why the files still existed in production.

I have removed the three files you indicated and then cleared the cache.

I’m now getting a different error in the POST matomo.php.

——-
An error occurred

[1054] Unknown column ‘interaction_position’ in ‘field list’
Backtrace:

#0 /nas/content/live/sitename/wp-content/plugins/matomo/classes/WpMatomo/Db/WordPressTracker.php(176): Piwik\Tracker\Db\WordPress->after_execute_query(Object(wpdb))
#1 /nas/content/live/sitename/wp-content/plugins/matomo/app/core/Tracker/Model.php(31): Piwik\Tracker\Db\WordPress->query(‘INSERT INTO wp_…’, Array)
#2 /nas/content/live/sitename/wp-content/plugins/matomo/app/core/Tracker/Action.php(426): Piwik\Tracker\Model->createAction(Array)
#3 /nas/content/live/sitename/wp-content/plugins/matomo/app/plugins/Actions/Tracker/ActionsRequestProcessor.php(91): Piwik\Tracker\Action->record(Object(Piwik\Tracker\Visitor), ’22’, ’21’)
#4 /nas/content/live/sitename/wp-content/plugins/matomo/app/core/Tracker/Visit.php(218): Piwik\Plugins\Actions\Tracker\ActionsRequestProcessor->recordLogs(Object(Piwik\Tracker\Visit\VisitProperties), Object(Piwik\Tracker\Request))
#5 /nas/content/live/sitename/wp-content/plugins/matomo/app/core/Tracker.php(160): Piwik\Tracker\Visit->handle()
#6 /nas/content/live/sitename/wp-content/plugins/matomo/app/core/Tracker/Handler.php(55): Piwik\Tracker->trackRequest(Object(Piwik\Tracker\Request))
#7 /nas/content/live/sitename/wp-content/plugins/matomo/app/core/Tracker.php(140): Piwik\Tracker\Handler->process(Object(Piwik\Tracker), Object(Piwik\Tracker\RequestSet))
#8 /nas/content/live/sitename/wp-content/plugins/matomo/app/core/Tracker.php(115): Piwik\Tracker->track(Object(Piwik\Tracker\Handler), Object(Piwik\Tracker\RequestSet))
#9 /nas/content/live/sitename/wp-content/plugins/matomo/app/piwik.php(73): Piwik\Tracker->main(Object(Piwik\Tracker\Handler), Object(Piwik\Tracker\RequestSet))
#10 /nas/content/live/sitename/wp-content/plugins/matomo/app/matomo.php(13): include(‘/nas/content/li…’)
#11 {main}
——-

@alexandernst, that’s an interesting idea. It is already possible to achieve this functionality with a bit of CSS.

For example, if you have a page with an ID ‘1234’ that you wanted to show the widget on and a widget with ID ‘rssiconwidget-1’ you could hide it on all pages and show it on a specific page with something like the following:

#rssiconwidget-1 { display: none; }
#postid-1241 #rssiconwidget-1 { display: block; }

Would you be comfortable with doing that?

@aerendir, thanks for the detailed feedback. We’ll definitely keep this in mind for future updates.

Next time I see you, I’ll buy you a coffee. Seriously. This plugin is SO helpful.

Great.

@sudhir600, that is correct. The slug is an internal identifier for the gdpr plug-in and has no bearing on the actual cookie name.

@sudhir600 an example for a slug for Google Analytics for your site might be cm-googleanalytics.

@sudhir600 thanks for your valuable feedback. We didn’t do automatic detection of cookies for a number of reasons, but the top two reasons are:

• In preparation for the GDPR, it is advised to do a full audit of the data that you’re collecting. This will ensure that all of the cookies that you’re still tracking are valid and required. Because you should be taking stock of these scripts, the process of setting the plugin up should be easy, even if it takes a while to set up.
• There are infinite purposes for using cookies and detection of all those cookies would be complicated, unmaintainable, and inexact. This type of setup is more accurately handled by a human.

Is there a reason you’re not using cookieboat or Complianz GDPR plugins? It seems like they’re able to do a lot of what you’re looking for already.

In this current version, what i am facing issue is how to set slug (its under script (slug (do not edit after creation)

What trouble are you having with setting up a slug? You just need to use only lowercase letters and dashes.

I want that, at start of page, no GA, Google adsense and others cookies will set and adsense will not show ads, GA not start tracking, only wordpress necessary cookie wills set. even i group this but i found that GA still accessing and adsense still showing ads, even i decline the cookies.

If you place your GA scripts and adsense scripts into the code fields provided by the plugin, they won’t fire until the user accepts them. If they’re placed somewhere else, you’ll have to use the developer API outlined in the plugin’s description to block the scripts from firing until the user accepts those cookies.

Unfortunately, we can’t provide personalized support for your specific installation. If you’d like to hire my company to set this up for you, you can fill out a project request form at https://www.pixeljar.com.

@sudhir600, we’ve just released version 1.1.1 which should address the problem that you’re experiencing.

@sudhir600, we are working on a release to fix this bug. It should be available shortly. Thank you for reporting this bug and sorry for the inconvenience.

@tiogaplanet, you’ve been given commit access.

We’re glad you like it!