Weave Code
Filament Social Media Links Laravel Package
codedor/filament-social-media-links
A Filament plugin that adds a social media links field and repeater to your forms, letting you manage and display social profiles with configurable platforms and icons.
Package to manage social media links in Flament and display them in your front-end
Frequently asked questions about Filament Social Media Links
- How do I install codedor/filament-social-media-links in a Laravel application?
- Install it with Composer using composer require codedor/filament-social-media-links, then register the plugin on the Filament panel where you want the social links management UI to appear. Because the package adds its own settings and migrations, you should run your migrations after installing. Check the repository README for the exact plugin registration snippet, since the available release notes do not document the install steps in detail.
- Which Filament and Laravel versions does this package support?
- The v2.2.0 changelog gives no signal about supported Filament majors or the Laravel and PHP floors, so treat compatibility as unverified. Check the composer.json constraints in the repository and compare them against the Filament version used by your panel before committing. Filament version compatibility is the dominant long-term risk for any panel plugin, so confirm it during a short technical spike.
- What changed in v2.2.0 of filament-social-media-links?
- The single functional change resolves the structured data logo through the configured model, so the JSON-LD logo value is now derived from that configuration instead of the previous fallback. The other two changes are Dependabot bumps to actions/checkout and dependabot/fetch-metadata, which are CI-only and have no runtime impact. It is a minor version bump, but the logo change alters rendered output on public pages.
- What happens if no logo is configured for the JSON-LD output?
- This is the highest-value unknown from the changelog: it is not documented whether the package omits the logo key, emits an empty string, or fails when the configured model has no logo. An empty or invalid logo in Organization structured data can trigger validation warnings in Google Search Console, which is low severity but still a real SEO surface. Verify the fallback behavior in a staging environment and run the affected pages through the Rich Results Test.
- Does this package create its own database tables or store domain data?
- It does not own domain data. The package introduces persistence only for its own settings and migrations, and it does not add queues, jobs, or request-critical processing beyond view rendering. That makes it an additive, low-coupling dependency that sits in the presentation and configuration layer of a Laravel app.
- Can I render the social media links in my front-end Blade views?
- Yes. The package includes a Blade render path that outputs markup and schema.org data, so the links you manage in Filament can be displayed on public pages. Because the output is public-facing, treat changes to that markup as an output contract and check it after upgrades. Snapshot tests or SEO regression baselines are a practical way to catch unintended diffs.
- Is it safe to upgrade to v2.2.0 from an earlier release?
- The minor version bump signals no breaking API changes under semantic versioning, so most consumers should see the logo resolution change as a fix. However, the rendered JSON-LD differs, so anyone with snapshot tests, cached HTML, or hardcoded expectations against the prior markup will see a diff. There is also no documented upgrade step for existing installs that never set the configured logo model.
- What is the configured model for the logo and how do I set it?
- The changelog refers to resolving the logo through the configured model, which implies a config value pointing at an Eloquent model plus an attribute or accessor for the logo. It is unclear from the release notes alone whether this is a config key, a settings record, or a panel-level argument. Confirm the mechanism and the upgrade path for existing installs before adopting the package.
- Does this plugin affect application performance or reliability?
- The blast radius is limited: it sits in the presentation and configuration layer and does not sit on a request-critical path beyond view rendering. If it misbehaves, the likely symptom is incorrect or missing structured data on public pages rather than failed transactions. It does not add queues, jobs, or new persistence beyond its own settings and migrations.
- Is codedor/filament-social-media-links actively maintained, and are there alternatives?
- The changelog shows active Dependabot dependency hygiene, which is a positive signal, but the functional change came from a single external contributor PR, so bus factor and release cadence are unverified. The review recommends completing a short technical spike before committing to the package. If maintainer concentration is a concern for your team, compare it against alternatives that document their Filament version support and logo fallback behavior.
Weaver
How can I help you explore Laravel packages today?