Conflict between plugin and Organic Purpose theme

Hello, I have the same issue and I dont know what to do .Have you found the solution ?

The solution is for the Organic Themes team to rename the function tgmpa() in either the plugin or theme, since they reused that name in each, which is a PHP no-no. You can try renaming it yourself until a fix comes in but unless you know code you could just further break things, so I don’t recommend it. Hopefully they’ll issue an update soon.

@jr00ck Actually no, though the problem is in the Organic Purpose theme

The problem is that the theme author clearly has done a manual search & replace in the TGMPA code – probably for the text domain – and done this incorrectly.

The simplest way to get round this, is to replace the TGMPA file in your theme.

1. Download the current version of the library from https://tgmpluginactivation.com/download/ (for your purposes, just click on the “Zipball” link below the form)
2. Unzip the file and
3. Copy/upload (via FTP) just the class-tgm-plugin-activation.php file to the location indicated by the error message, i.e. the wp-content/themes/organic-purpose/includes/ directory, replacing the existing class-tgm-plugin-activation.php file.

Once you’ve done that, all should be fine again.

All the same, please contact the Theme author and ask them to update the TGMPA file they include with their theme. They should download a fresh copy of TGMPA using the Custom TGMPA Generator, which will serve them with a customized download of TGMPA which will automagically have done the search & replace the correct way.
https://tgmpluginactivation.com/download/

Hope this helps.

Hi All,

We apologize for this inconvenience.

As Juliette and Jeremy mentioned, this error was occurring if your theme already declared support for the TGM plugin activation script. We recently pushed a plugin update to resolve this issue.

Updating to version 1.4.15 of the Builder Widgets plugin should fix the error.

I hope this helps.

Thanks!

Thanks for the fix! It’s working for us w/ version 1.4.15 of the plugin. Marking this issue resolved.