Search

In developing 'stuff' for Symphony, I have come across different ways of doing content pages, and I would like some advice on which is considered best practice.

Some extensions do all the work of the pages in one content.{name}.php file while others break them up...

content.index.php
content.edit.php
content.{name}.php

Which is the recommended way to do it all? I also found that the functions in these methods are named differently too.

I ask as I want to get it right for 'future proofing' the extensions I'm developing, and for the upcoming 'best practices' and coding guidelines that are on the table for developing.

Create an account or sign in to comment.

Symphony • Open Source XSLT CMS

Server Requirements

  • PHP 5.3-5.6 or 7.0-7.3
  • PHP's LibXML module, with the XSLT extension enabled (--with-xsl)
  • MySQL 5.5 or above
  • An Apache or Litespeed webserver
  • Apache's mod_rewrite module or equivalent

Compatible Hosts

Sign in

Login details