https://sourceforge.net/p/postfixadmin/wiki/Custom_fields/Recent changes to Custom_fieldsenSat, 03 Jan 2015 22:02:15 -0000https://sourceforge.net/p/postfixadmin/wiki/Custom_fields/<div class="markdown_content"><pre>--- v1 +++ v2 @@ -19,6 +19,7 @@ * use a table name starting with "x_" * within that table, you can use any field and index names you want +* you might want to have the fields "created", "modified" and "active" (which exist in most PostfixAdmin tables) * you may also create unique keys inside your tables * if you use PostgreSQL, names for indexes and unique keys must start with "x_" (better: "x_tablename_") * avoid foreign keys to PostfixAdmin's default tables if possible. @@ -26,8 +27,15 @@ Integrating the additional fields in PostfixAdmin --- -After you have added your fields and/or tables to the database, -* create the additional fields or tables in your database. +### PostfixAdmin &gt;= 3.0 ### + +* create the additional fields or tables in your database +* write a *_struct_hook() function (see the x_struct_admin_modify() example in config.inc.php) to integrate your custom fields in PostfixAdmin +* enable that function in $CONF\[*_struct_hook] + +You can also use a *_struct_hook() function to change or remove existing fields. + +### PostfixAdmin 2.3.x and older ### + +* create the additional fields or tables in your database * edit the PHP scripts and the templates to add your custom fields - -Future versions of PostfixAdmin (3.0) will provide an easier way to integrate custom fields, however it will take some time until we have that code ready. </pre> </div>Christian BoltzSat, 03 Jan 2015 22:02:15 -0000https://sourceforge.net66bf9bef0191631e279f3e26a472a61e4db12073https://sourceforge.net/p/postfixadmin/wiki/Custom_fields/<div class="markdown_content"><p>From time to time we get requests for adding some fields in PostfixAdmin. Many of them are specific for one user and therefore don't end up in the official code. </p> <p>This page describes what you can do yourself.</p> <h2 id="policy-for-database-changes">Policy for database changes</h2> <p>This policy is important to avoid that your custom fields conflict with any fields, tables or indexes we might add in future versions of PostfixAdmin.</p> <h2 id="additional-fields-in-existing-tables">Additional fields in existing tables</h2> <ul> <li>you can use any fieldname starting with "x_"</li> <li>you can create indexes if needed - also prefix them with x_ (or tablename_x_ for PostgreSQL)</li> <li>avoid creating unique indexes and foreign keys if possible (they could make scheme changes difficult)</li> </ul> <h2 id="additional-tables">Additional tables</h2> <ul> <li>use a table name starting with "x_"</li> <li>within that table, you can use any field and index names you want</li> <li>you may also create unique keys inside your tables</li> <li>if you use PostgreSQL, names for indexes and unique keys must start with "x_" (better: "x_tablename_")</li> <li>avoid foreign keys to PostfixAdmin's default tables if possible.</li> </ul> <h2 id="integrating-the-additional-fields-in-postfixadmin">Integrating the additional fields in PostfixAdmin</h2> <p>After you have added your fields and/or tables to the database,<br /> <em> create the additional fields or tables in your database.<br /> </em> edit the PHP scripts and the templates to add your custom fields</p> <p>Future versions of PostfixAdmin (3.0) will provide an easier way to integrate custom fields, however it will take some time until we have that code ready.</p></div>Christian BoltzSat, 25 Oct 2014 20:49:24 -0000https://sourceforge.neta39444229d3a7652c044a7a86f524934c812d535