Repository navigation
Update Slug for Alumni Board members #115
Description
Description
Partner noticed the slug for the Alumni shows https://opensource.org/blog/status/alumni and would like to update to https://opensource.org/about/board-of-directors/alumni or https://opensource.org/about/alumni.
The changes should be made on the staging site for partners review before merging to production.
We can use the /about/alumni URL path to add the Alumni Board members and create a link on the About page as well
Once that is done, we can create a redirect from https://opensource.org/blog/status/alumni to https://opensource.org/about/alumni.
Note: The partner also noticed https://opensource.org/status/alumni was gone and instead it found it at https://opensource.org/blog/status/alumni and wants to know why that happened.
In addition:
CPTs and their taxonomies should not use /blog slugs in their URLs. Here’s a list of all CPTs which highlights where the issue is:
- Board Member CPT:
(Correct) Board members: https://opensource.org/board-member/chris-aniszczyk
Status: https://opensource.org/blog/status/alumni
Seat type: https://opensource.org/blog/seat-type/affiliate - License CPT:
(Correct) License: https://opensource.org/license/blue-oak-model-license
License Steward: https://opensource.org/blog/steward/apache-software-foundation
Category: https://opensource.org/blog/license-category/international - Press Mentions CPT:
(Correct) Press mentions: https://opensource.org/press-mentions/meta-is-accused-of-bullying-the-open-source-community
Publications: https://opensource.org/blog/publication/adda-24-7
The /blog slug should only apply to blog post types.
A few related PRs:
- Blog post migration: Merge/blog import to main #56
- “removing blog path from author page: remove blog path from author page #58
- Omitting /blog/ from CPTs: Add rewrite slug to custom post types #59
Related: Fix rewrite URL for press mentions #61
Activity
webmink commentedon Aug 26, 2024
We probably need to do some thinking on the design of the Alumni page. It could use some dates for everyone not just the recent ones, and the list is very much incomplete. Also, for the OCD among us, "alumni" is the plural so would not be expected under an individual image!
nickpagz commentedon Sep 20, 2024
I've pushed a fix to the staging site for this, for testing. I've also re-published an old "about" page and created a child page of it with slug "board-of-directors". This was done to check for page loading conflicts as the desired permalink for the "status" taxonomy has the same general structure as the existing page/child
/about/board-of-directors/on production. All seems to be working fine.I've also added the redirects for testing.
I did not address @webmink's comment above. I'll let our TAM's coordinate what this should look like and decide if a new dev request should be made for that or let live in the current one.
EDIT:
This happened when the blog was migrated over and the custom permalink format
/blog/%postname%was added. The theme/osi plugin's settings didn't account for a custom permalink structure. As a result all CPT taxonomies ended up getting/blog/prepended to the permalink.xpurichan commentedon Sep 26, 2024
Thanks for the updates and RCA @nickpagz. I've tested the updates and informed Ariel of the changes via email, currently awaiting feedback.
We will work this into a new request once this permalink update has been completed and pushed to production. (cc @webmink, we'll communicate with you more about this at that time)
webmink commentedon Sep 28, 2024
lovestulip commentedon Oct 28, 2024
Hello, we have reached out to Ariel multiple times; however, there has been no response on this issue. We will pause this on our end.
ajolo2ky commentedon Apr 2, 2025
Hi, sorry this got buried.
Going back to the original request, I'm building a new alumni page with the right slug: https://opensource.org/wp-admin/post.php?post=125037&action=edit
What we'd need is https://opensource.org/blog/status/alumni (and other statuses) not be public nor accesible via search engines.
nickpagz commentedon Apr 2, 2025
Ok. I'll add this to my list.
nickpagz commentedon Apr 12, 2025
@ajolo2ky It sounds like we're changing direction a little here, so just trying to understanding what we need.
On both production and staging, the statuses get rendered automatically using the archive template - with the staging site having been adjusted to remove the
/blog/and instead use/about/board-of-directors/{status}.It sounds like we now want to use a custom/dedicated page for the "alumni", and not show the archive page for the different statuses at all. If this is the case, we can probably just redirect the status pages accordingly. Does that sound about right?
ajolo2ky commentedon Apr 14, 2025
Hi @nickpagz, you are right. Changing direction here. We'd like /status/ not to be publicly available. We'll build proper templated pages using query loops.
So https://opensource.org/blog/status/alumni, https://opensource.org/blog/status/past-candidate and other status pages shouldn't be public facing.
nickpagz commentedon Apr 15, 2025
Sounds good. I'll modify the taxonomy terms so they're not public, and it's probably best to setup some redirections for those in wp-admin when the new pages are ready. At the moment I can see a couple of the statuses are already indexed.
I'll get this up on the staging site.
nickpagz commentedon Apr 16, 2025
@ajolo2ky I've updated the staging site with these changes. I've found that to be able to see the "status" as a filter in the query loop block I had to keep one of the parameters public. Specifically,
publicly_queryablehad to betrue, thoughpublicis false. This means you need to construct a query to view it, iehttps://open-source-initiative-development.mystagingwebsite.com/?taxonomy-status=board-member. For this particular status I setup a redirect in the Redirection plugin so it goes to the Board of Directors page. We would do the same for the alumni and other statuses when ready.As an aside, if we want to change
publicly_queryabletofalse, we can still do this, but you'll need to add the filter via the code editor, as described here. This is not ideal, and the redirect more or less keeps it "private" in this regard.Lastly, I've adjusted the still open PR for the main branch for changing the slug of all taxonomies to remove the change for the
statustaxonomy, and have another PR with this particular change as a separate but dependent change for the main branch when ready to deploy. When we're ready, I can merge both of those and help setup the redirects as needed.