Our local instances are single-site and I expect our initial production instance to be single-site. However, bfn.context.org is multisite and we've been carrying the multisite / multiblog setup along from that.
This PR addresses that through changes in bfc_top_nav_menu_builder() and bfc_top_nav_is_active()
I also needed to rename home.php to homepage.php. home.php turns out to be a reversed name in the WordPress template hierarchy and was forcing dev.bfcom.local/blog/ to use home.php which is meant for the non-blog home page. I got clues to this from Blog Page Redirects To Homepage and from Query Monitor's template listing.
You will need to make some Admin changes to mesh with the coding changes.
Go to Admin Dashboard > Pages and find the page called "BFNet Blog". It should be marked as the "Posts Page"
Hover over it and choose Quick Edit. You will then see something like this:
Change the slug from bfnet-blog to just blog.
This change can be made before merging the new version.
Our local instances are single-site and I expect our initial production instance to be single-site. However, bfn.context.org is multisite and we've been carrying the multisite / multiblog setup along from that.
This PR addresses that through changes in
bfc_top_nav_menu_builder()
andbfc_top_nav_is_active()
I also needed to rename
home.php
tohomepage.php
.home.php
turns out to be a reversed name in the WordPress template hierarchy and was forcingdev.bfcom.local/blog/
to usehome.php
which is meant for the non-blog home page. I got clues to this from Blog Page Redirects To Homepage and from Query Monitor's template listing.You will need to make some Admin changes to mesh with the coding changes.
bfnet-blog
to justblog
.This change can be made before merging the new version.