@wplab: Test the version I posted about, and it should work. Worked for me. Also already have all my themes approved with it.
Just wanted to be a little bit helpful. In my case, it worked just fine with the version from the Dev branch. That is: https://raw.githubusercontent.com/thomasgriffin/TGM-Plugin-Activation/develop/class-tgm-plugin-activation.php
Have a great day! Paul
For me, it doesn’t work at all. I click on one of the fields, nothing happens. No pop-up, no slide in, no anything.
Reference: OS X 10.10, Chrome 42.
It’s easy. As a WordPress Theme Designer I definitely know where to look. In about 5 seconds I know what’s from where
No, it’s not Avada.
It’s a theme called Startuply. You can find it here on the market.
Consult a Steuerberater.
I’ve read this thread entirely. I didn’t want to post anything, but it’s definitely clear what happened.
I’ll just leave this here: http://jamigibbs.com/premium-themes-are-dead-as-we-know-it/
That sums up my thoughts.
Server usually. It has to have set allow_url_fopen.
4 years later, a man walks into a bar… a bit late to the party don’t you think?
As long as you respect the license under which the plugins are distributed, and if you assign all functionality to a plugin, you should be fine. If we’re talking about WordPress.org plugins, those are released under the GPL. Make sure you respect that license in your theme/plugins and it’s okay
As outlined by the WordPress mantra: Themes are for Presentation, Plugins are for functionality.