🚀 Elementor Pro Multisite Automated Activation on Network Sites

[ehong33234]

Prerequisites

• [X] I have searched for similar features requests in both open and closed tickets and cannot find a duplicate.
• [X] The feature is still missing in the latest stable version of Elementor ( Elementor Pro. )

What problem is your feature request going to solve? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Currently, Elementor must be manually activated on each network site in a multisite environment. This is problematic and not an ideal workflow for a multisite network which allows clients to launch their network site instantly without Super Admin help. Especially in an environment where sites are launched and closed frequently, this is definitely not a great workflow. When client launches their site, it will appear that Elementor is broken and causes a lot of frustration with Elementor -- this we know. Not a good experience with Elementor Pro by this manual activation method and also big potential security risk with activation key available to network site admins.

Describe the solution you'd like A clear and concise description of what you want to happen.

Elementor Pro should have a network activation option for your Expert Plan where the Super Admin can activate with key on the main site or the network admin dashboard (plugins > Elementor Pro). This will allow all subsequent network sites to be activated without manual intervention. This is a huge upsell opportunity for Elementor Pro Expert Plan.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

The only current solution is for manual activation on each network site by Super Admin but this is a very bad user experience and tasking for everyone using Elementor Pro on a turnkey multisite environment which allows clients to launch their own site instantly. This creates frustrated End Users who will not be able to use Elementor Pro features until it is manually activated by Super Admin. The only alternative for multisite admins is to use another page builder like Beaver Builder which has this activation feature native.

Additional context Add any other context or screenshots about the feature request here. Wordpress is growing as a WaaS platform and this is a basic activation feature that needs to be implemented. Thank you.

[aabergkvist]

I second this highly!

[ghost]

"The only current solution is for manual activation on each network site by Super Admin"

Have you looked at using a WP CLI script for when you are setting up a subsite automatically. Elementor Pro has a wp-cli command to help you to do this.

wp elementor-pro license activate <YOUR LICENCE KEY>

On multisite, you can then use the --url flag to indicate which site you wish to activate

wp elementor-pro license activate <YOUR LICENCE KEY> --url=subsite.domain.com

[webenadam]

+1

[webdiner]

Will elementor ever have a different licensing option? I hope they provide a different agency type license. That can be a server key or something. It's a pain now having to relicense several plugins when the URL changes.

Regarding the new 1000 site limit... Their use count is probably way higher than it actually is. We have to relicense elementor twice for every site. 1. when we clone our base install on our server. 2. when the site goes live and the url changes again.

[lozzyp]

wp elementor-pro license activate <YOUR LICENCE KEY>

On multisite, you can then use the --url flag to indicate which site you wish to activate

wp elementor-pro license activate <YOUR LICENCE KEY> --url=subsite.domain.com

In this solution, would you need to know what the subsite was called in order for it to work? Or would you be able to replace 'subsite' with a wildcard '*' ???

eg. wp elementor-pro license activate <YOUR LICENCE KEY> --url=*.domain.com

[mredodos]

+1 pls add some function for quickly activation

[webenadam]

+1 again :)

[gene158]

any updates on this?

[grinono]

It would be fantastic to have a wildcard solution for elementor. I can not even mannually enable subdomain as my main domain is www.x.com instead of x.com with subdomainss.

[blogbytes]

To activate the license on all domains via WP CLI in your network use the below;

wp site list --field=url | xargs -n1 -I % wp --url=% elementor-pro license activate <your license key>

[yosefeliezrie]

To activate the license on all domains via WP CLI in your network use the below;

wp site list --field=url | xargs -n1 -I % wp --url=% elementor-pro license activate <your license key>

Will this activate on all sub sites in the network?

[blogbytes]

To activate the license on all domains via WP CLI in your network use the below; wp site list --field=url | xargs -n1 -I % wp --url=% elementor-pro license activate <your license key>

Will this activate on all sub sites in the network?

Yes.

[iugo-robert]

+1

[Hans-101]

To activate the license on all domains via WP CLI in your network use the below;

wp site list --field=url | xargs -n1 -I % wp --url=% elementor-pro license activate <your license key>

Thanks for that. Unfortunately, this has to be run every time a sub-site is created. Would be great if it was triggered automatically.

[Hans-101]

+100

It's a real pain for agencies. Especially, when after certain actions (some cache purging) Elementor Pro gets disconnected, and has to be manually reconnected site-by-site. If you manage 100 sites, it's a real pain. Actually, anything above a few sites is a pain.

It's not about abusing the # of licenses used for each sub-site, we're more than happy to pay even the new pricing ($999 for 1000 sites), as it's $1/site/year. But this should be addressed and fixed by Elementor.

This has been raised years ago, but no solution/workaround whatsoever has been offered. This is why we are phasing out from Elementor to other agency/multisite friendly solution. With WP block editor on the rise and so many new Block Editor solutions with high potential, make them more and more feasible as Elementor Pro alternatives. Especially, when considering speed impact, but that's another story.

[nicholaszein]

Hi there,

thanks for submitting your feature request! 🙏

Please understand that while we do welcome new feature requests, we can't promise they will be considered or added to our roadmap for the time being.

🔖 We will, of course, keep this suggestion in mind and consider adding it if there is significant demand in the future.

📅 This request is scheduled to be Migrated to the new Discussions section.

Please do not duplicate this request.

Once we migrate it, we encourage you to cast your ⬆️ Upvote on the first comment if you feel it should be considered for our roadmap.