[wp-hackers] Alternative or reactivation for get_blog_info()
frank at bueltge.de
Wed Jul 24 10:24:55 UTC 2013
I have create the default functions with site transients, there is a bid
Maybe this helps other users, there search for a function to get all blogs.
On Wed, Jul 24, 2013 at 11:18 AM, Malte Witt <m.witt at ia-sh.de> wrote:
> I stumbled upon this a few days ago, too.
> In my opinion get_blog_list() is perfectly fine. The Codex and the source
> is just saying: "For performance reasons this function is not recommended."
> That's true for installations with thousands of blogs. But I think most
> multisite installations out there in the real world have 3 to 100 sites and
> they have a perfect valid usecase for get_blog_list().
> If there is a no other reason why the function is deprecated (and I can't
> see any) I would say just reactivate it and place a big warning sign in the
> Codex, that this function shouldn't be used in super-large multisite
> In short: +1 for reactivation of get_blog_list().
> Am 24.07.2013 10:57, schrieb Frank Bueltge:
>> Hello at all,
>> since WP 3.0 ist Multisite more and more popular.
>> Very often on development is it important, that you get all blogs on
>> network. Before WP 3.0 give it the function get_blog_list() for this job.
>> Since 3.0 is this function deprecated. But if you will search via www for
>> alternative solution, you find many code snippets, but all with a sql
>> select. I think it is important, that we have a core function for this
>> topic, maybe the function get_blog_list().
>> What do you think, it is a enhancement, change for the trac that we
>> reactivate the function in core?
>> I have search on trac for topics to this functions, but only one result
>> with other content.
>> Thanks a lot for your time.
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.**com <wp-hackers at lists.automattic.com>
> wp-hackers mailing list
> wp-hackers at lists.automattic.**com <wp-hackers at lists.automattic.com>
More information about the wp-hackers