Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error "Accessing static property DoubleClick::$enqueued as non static" #37

Closed
samueldjack opened this issue May 19, 2017 · 4 comments · Fixed by #76
Closed

Error "Accessing static property DoubleClick::$enqueued as non static" #37

samueldjack opened this issue May 19, 2017 · 4 comments · Fixed by #76
Assignees
Labels
Milestone

Comments

@samueldjack
Copy link

samueldjack commented May 19, 2017

We're using the DoubleClick for Wordpress plugin on the same site as the WPLR Sync plugin.

When we invoke the WPLR sync plugin it exposes an error in the DoubleClick-for-Wordpress plugin:

The error is Accessing static property DoubleClick::$enqueued as non static it occurs in this code here.

I think the fix is to change the line in question to if(!self::$enqueued) {.

There's also an identical error two lines below.

@benlk
Copy link
Collaborator

benlk commented May 30, 2017

Hi Samuel,

Thanks for your bug report. Can you answer these questions for me, please?

@benlk benlk self-assigned this May 30, 2017
@benlk benlk added the bug label May 30, 2017
@samueldjack
Copy link
Author

Hi Ben,

Sorry for not getting back to you sooner. To answer your questions:

  1. Yes, that's the one
  2. No, WP_DEBUG is false
  3. PHP 7.1
  4. Wordpress 4.7
  5. I'll have a look to see if that new version helps.

Thanks!

@izzygld
Copy link

izzygld commented Jun 29, 2017

i have the same error
after deactivating all other plugins still get this error!

Notice: Accessing static property DoubleClick::$enqueued as non static in /var/www/vhosts/local.jewishaction.com/public/content/plugins/doubleclick-for-wp/dfw-init.php on line 96

@rclations
Copy link
Contributor

Hey @izzygld & @samueldjack thanks for the reports here. We've got some updates coming out soon that should resolve these issues. Stay tuned

@benlk benlk closed this as completed in #76 Oct 23, 2018
@benlk benlk added this to the 0.3 milestone Oct 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants