Installed version 3.0, now all the groups have now the slug name.
Thanks

thank you, did some altering and now testing it.

https://github.com/compie67/ossn-GroupSlugRouter/tree/main

which checks for isset($group->guid) before redirecting.

No, all you check is the returned value of your own function (object or false)

Just by naming it $group doesn't mean you're accessing a true instance of a group object
Rename it like $eric = groupslugrouter_get_group_by_slug($slug);
and do your check on $eric: no difference ;)

You may additionally add a error_log($group->title); which would return the name of the group if your theory is correct, but it won't.

You're right — returning just the owner_guid from groupslugrouter_get_group_by_slug() would simplify the logic, and I agree it’s more elegant in theory. However, during development we encountered a subtle issue with some existing groups (e.g. group 291), where slugs weren’t being recognized properly if only the owner_guid was returned.

By wrapping the result in a minimal object ((object) ['guid' => $entity->owner_guid]), we ensured compatibility with the existing vanity handler logic, which checks for isset($group->guid) before redirecting. This helped maintain consistent behavior, especially in fallback cases where slugs were missing or needed regeneration.

So yes — your suggestion is correct, and would work perfectly if we also refactor the handler to drop the isset($group->guid) check and directly redirect("group/{$group}"). But to keep things robust across edge cases and backwards-compatible, we kept the object structure for now.

Appreciate the insight though — this might be a great simplification for a future version.

just had a look into 3.0:
and wondering why you still continue passing the result of groupslugrouter_get_group_by_slug() as an object?

All we want is just a simple integer (the owner_guid of the entity) - no reason to do that extra wrapping.

Thus, it could be simplified like

$entities = ossn_get_entities($params);
if ($entities) {
    error_log("[SLUG] ✅ Slug '{$slug}' gevonden met owner_guid: {$entities[0]->owner_guid}");
    return $entities[0]->owner_guid; // Direct redirect gebruiken
}

and the adapted groupslugrouter_vanity_handler()

$group = groupslugrouter_get_group_by_slug($slug);
if ($group) {
    return redirect("group/{$group}");
}

Working on update. Myself got fast server. But for smaller ones the limit kicks in.

I have download and installed it, then create a new groep, but I see only /group/512 for now.
I will look tomorrow in the database if there is changed something.

What I did with that feedback
✅ I changed the redirect: it now only uses owner_guid, without ossn_get_group_by_guid(), exactly as advised.

✅ I now rely on OSSN's automatic entity cleanup when deleting a group. So there is no separate check anymore.

⚠️ I did consciously choose to delete old slug entities when a group title changes. That way I know for sure that there is only one active slug per group, and I avoid confusion or double references.

I will keep the credits neutral

Sorry Eric,
but I'm not feeling really comfortable being mentioned for 'optimization ideas' because you just ignored what I tried to explain in your thread https://www.opensource-socialnetwork.org/discussion/view/7521/fancy-url-instead-of-86