template or templates? #29

Activity

1. timint commented on Jul 11, 2026

   

   timint

   on Jul 11, 2026

   Last edited by timint

   Collaborator

   More actions

   Thank you for pointing this out. LiteCart will go with 'app://frontend/templates/'.settings::get('template').'/partials/notices.inc.php' and LiteCore will do 'app://frontend/template/partials/notices.inc.php'. Inconsistencies comes from side by side comparison and copying of lines from LiteCart v3 to LiteCore.

   PR is welcome
2. s22-tech commented on Jul 11, 2026

   

   s22-tech

   on Jul 11, 2026 via email

   ContributorAuthor

   More actions

   Hmm... I really thought you were going to go with `templates` for both. How is that going to work, with LiteCore being the core of LiteCart, especially with add-ons that populate template folders? How will paths be written so they work with either platform?
3. timint commented on Jul 11, 2026

   

   timint

   on Jul 11, 2026

   Collaborator

   More actions

   LiteCore aims to be the naked core. not an identical copy that includes everything.

   How is that going to work, with LiteCore being the core of LiteCart, especially with add-ons that populate template folders?

   All addons will not be 100% compatible without some minor adjustment. What comes to templates I have been thinking if templates should be moved to vMod overrides rather than template folders in LiteCart. So they work similarily.

   How will paths be written so they work with either platform?

   As of now, do 'app://frontend/templates/'.settings::get('template').'/partials/notices.inc.php' in LiteCart and 'app://frontend/template/partials/notices.inc.php' in LiteCore. It's possible to add a path alias to vMod if this is a big issue.
4. s22-tech commented on Jul 12, 2026

   

   s22-tech

   on Jul 12, 2026 via email

   Last edited by s22-tech

   ContributorAuthor

   More actions

   I don't know about things like add-ons functioning differently across platforms. Maybe it's my ignorance of the under-pinnings of the system, but the 30,000 ft view is that you're probably opening yourself up to headaches down the road when you have to explain to everyone why their paid add-on isn't working. It seems to me that the closer both platforms are together, especially for things that will directly be used by non-technical end-users, the better it will be, not only for you, but for everyone who writes add-ons, as well.