setSite and getSite should indeed be available from a sane place, at least saner than hooks.
That said, setSite should still come with a warning label attached. It's good for tests and some esoteric use cases, but in general, application code shouldn't have to be aware of it (I've seen some bad examples here recently).
setSite and getSite should indeed be available from a sane place, at least saner than hooks.
That said, setSite should still come with a warning label attached. It's good for tests and some esoteric use cases, but in general, application code shouldn't have to be aware of it (I've seen some bad examples here recently).