Pau Capó

Thanks @otto42 for this bit of sense in all this.

I understand all that, but I don’t think this is allowed in the www.ads-software.com plugins directory. Right now you have a plugin here and when you install the plugin redirects you to a payed plugin giving the sense of “needed” for it to work.

If this is not solved by today (Europe time) I will try to contact www.ads-software.com staff and inform of it, because this is just… BS

It seems like this is not really important for this company, so here we go with a simple fix that will block any “update” outside www.ads-software.com.

Edit: vendor/otgs/installer/includes/class-wp-installer.php
Add a return; at the start of the __construct() method.

Problem solved.

• This reply was modified 6 years, 9 months ago by Pau Capó.
• This reply was modified 6 years, 9 months ago by Pau Capó.

I’m using last version of WordPress, the last version of InfiniteWP (requieres the client) and version 2.3.1 of your plugin.

I’m not going to clone or anything like this because is a problem caused by your poor decisions.

@bedas
Can you please confirm me that if I dont upgrade to 3.0 I will keep getting the update request?
I just need to know to search for a hack and avoid it, I’m managing a lot of sites and I don’t want to be warned of an update that is not really an update…

I can keep using Types free version with a constant message of needs updating?! Is that true? I will need to see this “needs update” message all the time even after the shutdown of the free version?

No, Types 2.3.1 dont solve this:

View post on imgur.com

Same here, asking to update to 3.0 and pay for it…
Is this allowed by www.ads-software.com plugins rules? :/

I’m waiting too… Thank’s

I just comment with // the die() function.

They are looking to fix it:

https://github.com/Yoast/google-analytics-dashboard/commit/7d740a64273ade41941e5fd467447747dc5bf4f0

Deactivate or edit the file:

wp-content/plugins/google-analytics-dashboard/gad-admin-options.php

line 34, just comment it.

That is solved on version 0.4.3

Facebook add a new expiration entry for all the tokens…!

With new version still this problem?

That is solved on version 0.4.3

Facebook add a new expiration entry for all the tokens…!