Solid link hub plugin, but rewrite conflict and JS workarounds hold it back
-
I’m running WP myLinks on WordPress 6.8.1 and here’s my experience:
Pros
- Styling flexibility: The plugin lets you inject custom CSS directly in its settings, so you can tweak fonts, colors, and layout without editing theme files.
- Customizable link hub base URL: You get a dedicated hub page under a base slug of your choice (e.g.
/links/), where all your saved links are listed with thumbnails and descriptions—no coding required.
Cons
- Font integration is awkward. There’s no built-in field for Google Fonts or other webfonts—you have to enqueue them via custom JS, which feels like overkill for a links plugin.
- GTM / click tracking hacks. If you want to send click events to Google Tag Manager, you need your own JavaScript to detect button clicks and push data. A native hook or setting here would save a lot of work.
- Rewrite-rule conflict. By default WP myLinks registers a very broad regex (
[^/]+/([^/]+)/?$) that hijacks every two-segment URL on the site, causing unexpected 404s for pages, products, and custom post types. It requires a customregister_post_type_argsfilter to scope its CPT slug properly and avoid breaking other URLs.
Verdict
Great styling control and an easy-to-set-up link hub, but the need for “JS magic” around fonts and tracking and the critical rewrite-rule bug hold it back. Three stars until these integrations and URL handling are made more robust.
The topic ‘Solid link hub plugin, but rewrite conflict and JS workarounds hold it back’ is closed to new replies.