Search the Community
Showing results for tags 'mvc frameworks'.
Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you. The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system. You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire Documentation The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update 16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
Hi, I'm new to ProcessWire after using general purpose MVC frameworks such as Laravel/Rails/Django, due to the fact I cannot find any CMS built on those platforms feels as stable, well supported, and easy to use (for clients) as ProcessWire does. I'm trying to replicate the MVC benefits of the above frameworks in ProcessWire, so I'm abstracting my templates into Controllers and Views as described in this thread, however, I am really missing the ORM API's in these frameworks. Being able to define models and them to store relational data i.e. social data, form data, and whatever else without dropping down to raw SQL.... and then retrieving and outputting this data in my templates. Does anybody have any advice of achieving this kind of behaviour in ProcessWire? Would it be a case of integrating a third-party ORM, or is there some whole part of ProcessWire that I've missed?