[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-多站點模式multiple-site下的worpress，site_id與blog_id的差異":3},{"id":4,"slug":5,"title":6,"description":7,"content":8,"date":9,"image":10,"imageAlt":6,"author":11,"categories":14,"path":18,"minRead":19},3497,"多站點模式multiple-site下的worpress，site_id與blog_id的差異","多站點模式(multiple site)下的WorPress，site_id與blog_id的差異","多站點模式下的WorPress，site_id與blog_id的差異 自從將WorPress開啟多站點模式(m […]","\u003Ch1>多站點模式下的WorPress，site_id與blog_id的差異\u003C\u002Fh1>\n\u003Cp>自從將WorPress開啟多站點模式(multiple site)後，發現進行站點與使用者的管理行為就變得很複雜，當然多站點模式在某些需求下真的很好用，只是得記得它伴隨著管理難度會相對提高一些。這次在撰寫一些小功能時發現site_id在某些判斷上失效了，深入查下去才發現site_id與blog_id的真正意義。\u003C\u002Fp>\n\u003Cp>簡單來說blog_id就是子站點的id，在多站點模式下，子站點是用「blog」來稱呼，而整個系統則是用「site」，當然就是用site_id來代表其id。\u003Cbr \u002F>\n如果使用以下程式碼\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$blog_id = get_current_blog_id(); \u002F\u002F取得子站點blog_id\n$current_site = get_current_site();\n$site_id = $current_site->id;\u002F\u002F取得系統site_id\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>另外如果用get_sites() 取得的所有站點資訊，也會發現這個數值。\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Array(\n    [0] => WP_Site Object(\n        [blog_id] => 1\n        [site_id] => 1\n        [domain] => example.com\n        [path] => \u002F\n        [registered] => 2013-11-08 17:56:46\n        [last_updated] => 2013-11-08 18:57:19\n        [public] => 1\n        [archived] => 0\n        [mature] => 0\n        [spam] => 0\n        [deleted] => 0\n        [lang_id] => 0\n    )\n\n    [1] => WP_Site Object(\n        [blog_id] => 2\n        ...\n    )\n)\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>未來要開發多站點模式的功能時，要記得呼叫正確的id囉\u003C\u002Fp>\n","2023-04-08T20:25:50","\u002Fapi\u002Fproxy-image?url=https%3A%2F%2Fpost.billxu.net%2Fwp-content%2Fuploads%2F2022%2F12%2FWordPress-logotype-alternative.png",{"name":12,"link":13},"Chih Fan","http:\u002F\u002Fpost.billxu.net",[15],{"name":16,"slug":17},"WordPress","wordpress","\u002Fblog\u002F多站點模式multiple-site下的worpress，site_id與blog_id的差異",1]