Weave Code
Sulu Form Landing Page Bundle Laravel Package
innomedio/sulu-form-landing-page-bundle
A Sulu CMS bundle for building form-enabled landing pages. It lets editors integrate and manage forms directly within landing pages, simplifying form setup and rendering for lead-generation and marketing pages.
Innomedio Sulu Form Landing Page Bundle adds ready-made form landing pages to your Sulu CMS installation. Instead of wiring up a custom template and controller for every campaign or contact form, you get a reusable content type that combines a Sulu form with a configurable page layout—so editors can build and publish landing pages directly from the admin interface.
The bundle follows Sulu's standard bundle conventions and integrates with the built-in form bundle for rendering and submitting forms.
- Provides a dedicated form landing page template and content type
- Renders Sulu forms with configurable fields and layout sections
- Fully editable through the Sulu admin UI—no developer involvement per page
- Installs as a standard Symfony bundle via Composer
- Keeps templates overridable to match your project's design system
Frequently asked questions about Sulu Form Landing Page Bundle
- Can I install innomedio/sulu-form-landing-page-bundle in a Laravel application?
- No. This is a Sulu CMS bundle built on Symfony, not a Laravel package, and it will not install into a Laravel application. If you are a Laravel shop, build the equivalent redirect field and post-submit handler in-house instead of attempting an adapter.
- Does this package work with Sulu 2.x and SuluFormBundle?
- It is intended for Sulu 2.x projects that already use SuluFormBundle, and the evaluation treats those as hard prerequisites. The exact Sulu, Symfony, and PHP version constraints are not verified in the provided assessment, so check composer.json and test a clean install on your stack. If you do not run Sulu 2.x with SuluFormBundle, the assessment ends there.
- What does this Sulu bundle actually add to forms?
- It adds form landing pages to Sulu by letting editors choose a redirect target per form, so a successful submission routes to a conversion-focused page instead of the default success flash. The pages are managed in the Sulu admin and rendered through the bundle's templates. The scope is intentionally narrow: it is about post-submit routing, not a full form builder replacement.
- How do I install and register the bundle in Sulu?
- Install with Composer, register the bundle in config/bundles.php, and typically add a template or configuration override so the redirect field appears in the form editor. If the redirect target is persisted on the form entity, expect a schema migration and plan the rollback before deploying. Audit the handful of classes end to end rather than treating it as a black box.
- Where is the redirect target stored: on the form entity or in a separate table?
- The assessment does not confirm whether the redirect target is stored on the form entity or in a separate table. Expect a schema touch if it is persisted on the form, and verify the migration and rollback story before installing. This is one of the first things to audit in the source.
- How do I prevent open redirects from editor-selected form landing pages?
- Constrain editor selection to internal Sulu content by validating the target against published, accessible pages for the correct website and locale. Reject free-form external URLs unless you explicitly allowlist them. If target selection is unconstrained, you inherit an open-redirect vector on a public form endpoint. Test unpublished, deleted, and permission-restricted targets before rollout.
- What HTTP status does the post-submit redirect use, and does it affect SEO?
- The provided assessment does not state whether the bundle issues a 301 or 302 redirect. Verify the submit-success branch in code and test with curl or browser dev tools, because permanent and temporary redirects have different SEO and analytics implications. If the status is hard-coded, decide whether that fits your campaign and tracking requirements.
- Does the redirect happen after form data is saved and notification emails are sent?
- That ordering is not verified in the assessment and must be checked in the submit-success branch. Ensure the bundle does not replace form-data persistence or notification emails when it performs the redirect. Add a test that confirms the submission is saved, notifications fire, and the redirect occurs in the expected order.
- Is innomedio/sulu-form-landing-page-bundle maintained and tested?
- Treat it as effectively unmaintained by default: the assessment cites a single maintainer, 1 star, 0 dependents, and a 2024-08 release. With that adoption level, assume no meaningful CI and plan to be the QA. Audit the code, add coverage for the submit-success path, and decide who owns a fork when upstream goes quiet.
- What are the alternatives to this bundle for Sulu form redirects?
- For Sulu, the main alternatives are a small in-house event listener or controller override that adds a redirect field and post-submit handler, or maintaining a fork of this bundle. Sulu's default success message does not provide per-form routing, so a bespoke handler is a reasonable one-to-two-day task. For Laravel, do not use this package; implement the equivalent redirect field and post-submit handler in your application.
Weaver
How can I help you explore Laravel packages today?