Multisite

Network-activate it and every site is set up, including sites added later. The activation sets up as many sites as it can in about three seconds, and each of the others is set up the first time WordPress runs on it, before anything there is recorded (see Caching, and other plugins). Each site has its own settings, its own list of what to hold back, and its own record.

Each site also keeps its own visitors' answers. On a network set up with sub-directories, whose sites share one address, each in a folder of its own (example.com/shop/, example.com/blog/), a visitor's browser sends every site the cookies any of them set. So on such a network each site keeps its answer in a cookie named for that site and kept in its own folder, a site given a domain of its own included, and an answer given on one site does not count on another. A site whose translated pages are in language folders of their own (example.com/shop/es/, as TranslatePress or WPML can put them) keeps one answer for all its languages, so an answer changed on a Spanish page holds on the English ones too. Version 1.3.2 kept a separate copy of the answer for each language folder. A visitor who still has such copies has them folded into one, the answer they gave last, the first time they open a page in that folder; until then, pages outside the folder follow the copy they can see, which is the answer given there. WP Consent API's cookies are named for each site the same way, and whether a visitor is asked where they are (Who is asked) is kept for each site too. Pages cached before the update still use the answer the sites shared, so the first time anybody opens wp-admin on any site of the network after the update, or at the first daily check, the plugin empties the page cache of every site it runs on, as far as the caches switched on for the whole network go. It does that for about three seconds at a time: on a large network each wp-admin screen or daily check that follows, on any site, goes on from where the last one stopped, until every site has been reached. It goes on from the next site by its number, so deleting sites in the meantime makes it miss none. A page cache switched on for one site only is not running then, so it is emptied the first time that site's own wp-admin is opened, or at that site's own next daily check. A cache it cannot empty (see Caching, and other plugins) keeps such pages until they expire. Visitors who answered on such a network before this was so are asked once more on each site. On a single site, and on a network set up with sub-domains (shop.example.com), the cookie is the one it always was, and nobody is asked again. A site deleted from the network takes its record of answers with it. If a site was deleted while the plugin was switched on for that site alone, WordPress could not ask the plugin for its table at the time; deleting the plugin clears those away too.