-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Let’s discuss: permalink generation scheme #682
Comments
I'm in the process of migrating a few Meetup groups away from Meetup - as well, I am a WordPress Meetup organizer in Kansas City - I am VERY happy to come across this plugin! I've been a Meetup user for about 14 years and have used it for many different types of groups. I'd love to give input about various use-cases and UX input for ease of use for all types of users. I've helped organize Meetup groups with a vast range of tech savviness among my fellow group organizers and fellow group members. As I started playing around with GatherPress last night, one of the first things that came to mind was the slug. My group that I'm most eager to move away from Meetup is a social club for area dog lovers. Our members range literally from 18 years old to 82 years old. We get together to do any and all things with our dogs and all things dog-related. All of that said, we like to keep event details mostly private except for members (though hiding individual blocks based on login/logout is a different topic). We keep it more private because years ago we went through a weird many-months-long stretch where random guys who didn't own dogs kept showing up to try to "pick up" women in the group. Part of the group's privacy is using simple/generic event titles, such as "3 Mile Hike" or "Dog Park Get-together" with only the date and the title visible to the public. All the details, date/time, location, RSVPs, etc. only viewable by logged in registered club members. Given this this use-case, I'd like to see a global permalink option for GatherPress. We would use either |
@carstingaxion @travispflanz @patriciabt Maybe we consider a |
Take a look at https://github.com/thefuxia/t5-rewrite @mauteri which does a lot of, what GatherPress needs. Unfortunately I was wrong with the buttons for the rewrite tags. But it adds a contextual help-tab with the new rewrite tags. This plugin is more than 10 years old; for sure GatherPress can do better. |
Thank you for your detailed feedback @travispflanz! Even that I’m late responding here, I’ve thought about your words many times since you commented over here. Your use case makes a lot of sense and I was happy to read a different perspective to broaden my view. As long as the GatherPress team is working on a suitable solution for many people (#826), you might make use of WordPress core private & password-protected post stati, which should work the same with events & venues, as they do with posts & pages. (But, unfortunately I haven’t tested this, just guessing) For a more granular control I highly recommend the Block visibility plugin. As the author @ndiego is also a WordPress core contributor you can expect the same smooth integration into the Admin-UI that GatherPress is gaining for, too. |
@carstingaxion is this one still relevant now that we completed #722? |
No, I don't think so @mauteri. While the mentioned #722 changes the post types permalink BASE slug, this issue is about changing the auto-generated |
Is your enhancement related to a problem? Please describe.
I’d like to suggest a change to the current scheme, GatherPress uses to create permalinks for events.
Currently the plugin generates permalinks based on the default
%post_name%
, which can be ok as a default. But maybe is not.One thing I’ve been doing with most of the websites, that use any kind of calendar, was changing the generated links to be more accessible to humans and perform better from a SEO perspective. I’d like to change the generation-scheme to be
%post_name%-on-%event_date%-in-%venue(_city)%
.May it be a setting with UI or just a well-documented filter, both would suit my needs.
Designs
No response
Describe alternatives you've considered
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: