WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

How is plugin network activate different from normal activation by implementation? What is done/not done in network activation that is done/not done in activation?

share|improve this question
up vote 7 down vote accepted

Network activation will activate a plug-in for every site in a network whereas regular activation will only activate a plug-in for the site you're currently on. As far as implementation goes, there is one other important difference:

If your plug-in is built to do something when it's activated (via register_activation_hook()), this will fire automatically when you activate a plug-in normally, but it will not fire for a network-activated plug-in until you visit the admin screen for each blog.

So if major database updates are tied in to register_activation_hook() they won't occur until you log in to the other sites.

share|improve this answer
The super-admin or the admin should visit the site.com/subblog/wp-admin URL for plugins' activation hooks to be executed? Or do you mean that they must go to the plugin page of the sub blog and then click on the "activate" link? – rsman Nov 17 '10 at 2:06
They must visit the wp-admin url for the plug-ins' activation hooks to be executed. – EAMann Nov 17 '10 at 2:09
@EAMann is there a programmatic way to do the same thing? I have hundreds of blogs. – Tyler Collier May 10 '15 at 5:24
Not easily. I'd recommend storing a version string in the DB for each site and checking to see if things are installed upon first use. – EAMann Aug 23 '15 at 13:02

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.