Prior to Simple:Press version 5.5.7 the only way to protect against custom changes to any part of a standard supplied Simple:Press theme being lost due to future updates was to develop a Child Theme starting with a Child Theme Framework or a Custom Theme to hold the customizations. This was true even if only minor custom changes utilizing a filter or an action were wanted because the standard theme’s spFunction.php file would have to be modified with the changes.
With Simple:Press version 5.5.7 the standard theme’s spFunction.php need not change so Child or Custom Themes are not required for minor changes utilizing a filter or an action. Instead a completely new file with the name ‘sp-user-functions.php’ can be made to accommodate the minor custom filter(s) or action(s). Having a place to put implementations that tie into the filters and actions available in Display Template Functions is the main purpose of this ‘.php’ file.
The new file is to be placed in the “wp-content” file where it will not be affected by Simple:Press updates.
This new functions file always runs before the active theme’s ‘spFunction.php’ file. It will affect any Simple:Press theme that is active.
The development rules for the file are simple.
As always, it is suggested a descriptive header be included in the file along with clear and descriptive comments regarding the changes being implemented.
Once developed, this new file is to be placed in in the ‘wp-content’ folder for the website.
Since Simple:Press version 5.5.7.
Codex page sync’d to code version 5.5.7.