Weave Code
Core Framework Laravel Package
uvdesk/core-framework
UVdesk Core Framework is an open-source PHP/Symfony foundation for building helpdesk and ticketing systems, with modular architecture, workflow automation, and customizable agent and customer portals for support teams.
UVDesk Community Helpdesk Core Framework Bundle providing the core essential functionalities and integration tools to easily integrate any other community helpdesk packages.
Frequently asked questions about Core Framework
- Is uvdesk/core-framework compatible with Laravel?
- Treat uvdesk/core-framework as a Symfony bundle, not a Laravel-native package. It can provide helpdesk domain models and services, but its agent and role semantics and UI conventions would need adapters or a separate Symfony service. Run a discovery spike before assuming drop-in Laravel compatibility.
- How do I install uvdesk/core-framework with Composer?
- Install it with Composer and register it as a Symfony bundle in your kernel, then publish its assets and views. Pin the version you validate, such as v1.1.7, and resolve dependencies in a branch first. It is not installed as a typical Laravel package.
- Which PHP and Symfony versions does uvdesk/core-framework support?
- Check the package composer.json for the supported PHP and Symfony matrix before committing. Validate your host application versions against that matrix, because the doctrine-migration dependency bump can cause transitive conflicts. Do not assume compatibility from the README alone.
- What features does uvdesk/core-framework provide?
- It supplies core entities and repositories for tickets, threads, and users, plus service and event architecture for support operations. It includes workflow and automation components, email channels, saved replies, and bundle-based extensibility. Version 1.1.7 adds ticket ratings, webhook notifications, filtered search, coloured notes, and shared saved replies.
- What changed in uvdesk/core-framework v1.1.7?
- v1.1.7 is additive at the feature level: ticket ratings, webhook notifications, filtered search, coloured notes, agent-access details, shared saved replies, Portuguese translations, and remote email images. It also fixes XSS, access-privilege, and saved-replies vulnerabilities. Treat the privilege and saved-replies fixes as behaviour changes for QA.
- Is uvdesk/core-framework safe for production helpdesk deployments?
- Only v1.1.7 or later should be considered for internet-facing deployments because older versions carry fixed XSS, access-privilege, and saved-replies vulnerabilities. Review tightened privilege checks for impact on agent, admin, and super-admin workflows. Plan webhook egress controls and remote-image tracking policies as part of production hardening.
- How do webhook notifications work in uvdesk/core-framework?
- v1.1.7 introduces webhook notifications for helpdesk events, which means outbound HTTP egress becomes part of your integration design. Require admin-gated webhook configuration, signed payloads, retries, timeouts, and a URL allow-list to reduce SSRF and PII exposure. Queue workers and network egress policy should be in scope before enabling them.
- What license does uvdesk/core-framework use?
- The package uses OSL-3.0, so legal review is required before embedding it in a commercial product. Reciprocal obligations may affect your distribution model, especially if you modify and redistribute the code. Confirm licence implications with counsel before committing to the dependency.
- How do I migrate an existing UVdesk installation to core-framework v1.1.7?
- Pin v1.1.7 in a branch, update only that constraint, resolve dependencies, republish assets and views, and run migrations against a production-like staging snapshot. Time the migrations against real ticket volume and keep a database restore point because reversibility is not confirmed. Verify ticket list, ticket view, agent create, dashboard, and saved-replies screens after republishing.
- What should I check before choosing uvdesk/core-framework over a Laravel helpdesk package?
- Confirm whether your stack is genuinely Symfony-compatible, because this is a Symfony bundle with UVdesk-specific agent and role semantics. Review low community adoption, the OSL-3.0 licence, and the commercial support and security-response model. For a Laravel product, compare Laravel-native helpdesk packages or plan a separate Symfony service.
Weaver
How can I help you explore Laravel packages today?