- Is ezsystems/share-buttons-bundle a Laravel package?
- No. It is a Symfony bundle registered manually in AppKernel.php (or EzPublishKernel.php on eZ), and it has no Laravel service provider, facade, publishable config or assets, or package auto-discovery. Its configuration model is built around eZ siteaccess keys, which only make sense inside an eZ-based Symfony application. On a Laravel codebase the architectural fit is effectively zero, so a native reimplementation is the realistic path.
- How do I install ezsystems/share-buttons-bundle with Composer?
- Run composer require ezsystems/share-buttons-bundle from your project root, then add new EzSystems\ShareButtonsBundle\EzSystemsShareButtonsBundle() to your kernel's bundle array. Optionally import the bundle's css/default.css if you use the default template. Installation will only succeed inside a permissive legacy dependency tree that still satisfies its Symfony 2.6-era constraints.
- Which Symfony and PHP versions does this bundle support?
- The README states Symfony 2.6 or later, but the packaging and documentation target the Symfony 2.x/3.x era with PHP 5.x-era constraints. The AppKernel registration entry point was removed in Symfony 4.4, and the Assetic stylesheets tag it documents was removed in Symfony 4.0. Treat it as legacy-only and verify compatibility on a pinned version before considering it.
- Why does the {% stylesheets %} tag fail with this bundle on Symfony 4 or 5?
- The {% stylesheets %} tag is provided by Assetic, which was removed from Symfony core in 4.0. The bundle's default template instructions assume that tag still exists. On newer Symfony versions, reference the bundle's css/default.css with a plain link tag or ship your own stylesheet instead.
- How do I configure share button providers per siteaccess?
- Configure under ez_share_buttons.system with a default block or per-siteaccess keys in config.yml. List the providers you want (facebook_like, facebook_recommend, twitter, linkedin, google_plus, xing), choose the default or a custom template, and set options such as layout, width, show_faces, share, show_username, large_button and language. Only enabled providers are rendered, so you can keep the markup minimal.
- Does this bundle work on eZ Platform and eZ Publish 5.x?
- Yes. It was written for eZ Publish 5.x and eZ Platform and is registered in EzPublishKernel.php there, and the siteaccess-driven configuration matches how eZ scopes settings. That makes it a reasonable fit for a legacy eZ application, subject to the version and licensing caveats. Because the repository is archived, vendor or fork it rather than treating it as a maintained Composer dependency.
- Is ezsystems/share-buttons-bundle still maintained, and what license is it under?
- The repository is archived with a single release dated 2018-02-14, five stars and no dependent repositories, so there is no observable production usage or maintenance path. Its license metadata is NOASSERTION, which is not a usable license; eZ Systems historically shipped under GPL-2.0, which can carry copyleft implications for distribution. Get legal review before any code enters your tree.
- What are the GDPR and privacy concerns with social share buttons?
- Typical share widgets pull third-party JavaScript and, for share counts, make outbound requests that leak the visited URL to Facebook, Twitter, LinkedIn or Xing. That is an ePrivacy and consent-management problem rather than a templating detail. The bundle ships no Subresource Integrity hashes and no CSP guidance, so prefer plain share links without counts and gate any embeds behind consent.
- How do I add social share buttons to Laravel without this bundle?
- Build a Blade component such as <x-share-buttons> or a small view composer, keep a config/share-buttons.php file listing enabled providers and URL templates, and publish a CSS asset. Estimated effort is half a day to one day including tests. This keeps the bundle's only real value, a curated provider list plus URL-encoding logic, while dropping the Symfony packaging, license and abandonment risk.
- What are the alternatives to ezsystems/share-buttons-bundle?
- For Laravel, use a small native implementation or a Blade component; third-party scripts like AddToAny or ShareThis also work but carry the same privacy and third-party JavaScript caveats. On Symfony or eZ, reimplement the markup as a Twig partial with a config array, or fork the bundle into your own tree if you must preserve existing behavior. The functional scope is only a few dozen lines of template and URL-encoding code.