In the \Mbx\System namespace you may find useful: This value is always available in the API as $data[‘uid’]. Recursively removes dir and contents Sends an HTML email. $recipients can be a string if single or an array of addresses. Any valid address format. Creates a settings system table for your module.$setting is your FeatureModule name. Continue Reading
In order to give your FeatureModule an admin page(s) you need a Page.php file that looks something like this: Each page must have a function named the same as the feature in the admin link. Your apage is always your FeatureModule name. Currently the only menu choices are crm, map and help.
A FeatureModule can handle a hook by implementing a function named the same as the hook with the signature matching the data returned. In this case we are handling the AfterRetsUpdate event. Note that this method reuses an API method. In order to do that MBX_CODE_API is defined to 1. The class must implement \Mbx\Entity\IMbxHooks. Implementing Continue Reading
Implementing your API is a simple matter. The required file is frontend.php. Simply change SiteMap to your FeatureModule name and SiteMapApi to YourModuleNameApi and thats it. Calling from the client can be
So what is a FeatureModule? A FeatureModule is a fast and simple way to extend RetsPro without hacking into core code. Again, extend RetsPro without any manual edits to make the next update work. The mbx system incorporated in RetsPro is, itself, an extension of our AppMagic for WordPress plugin. Enough with the history lesson. Continue Reading