Hi Peter,
EM User here too. MultiSite can be tricky/confusing a bit 🙂
Do you suggest that I edit them on my Sub-site to reflect that they are for the sub site?
That is for the part after your sub blog home url. It has no real effect, other than that you can specify it per blog, making the url clearer/prettier.
I organise walking tours, not events. So my slug is “tours”, for example.
Because WP gets the permalinks by Post ID, the slugs can be anything you want.
The whole idea of
Global Table Mode = yes
, is that the main blog will also show the events of the subsites. It also allows for several cross-blog options. The rest of the settings decide how (mainly) the main blog acts.
Display global events on main – yes
This means the main site will show all events of all blogs by default. Note: subsites will not show events from other blogs, unless you are using the shortcode [events_list blog=”all”], for example.
Link sub-site events directly to sub-site – yes
When a visitor clicks on a sub-site event on the main site, they will be redirected to the single event on the subsite, using that sub blog’s theme, etc.
Locations on main blog – no
Display global locations on main blog – yes
Link sub-site locations directly to sub-site – no
Now you are saving locations per blog. If two blogs have the same location, you would have to manually duplicate it per blog. Because of that, the other two options don’t really have a significant meaning anymore.
Sharing locations across blogs, will let the #_LOCATIONNEXTEVENTS placeholder list all events from all blogs – because they are all using the same location ID on the main blog.
Btw, all sub-events only show up in the front-end of the main site. The actual events are maintained per blog.
Event Categories always reside on the main blog. The sub blogs can “only” use/select them. Editing needs to be done on the main blog.
Event Tags are stored per blog and do not work cross-blog.
