FanPress CM 5.3.0-b2 released

The second beta of FPCM 5.3.0 comes in short order. The next version includes a number of bug fixes.

Fixed

• reminders did not show up due to false reminder type usage
• update dialog did not open in system settings
• fix fpcm\model\files\mediaFile::getMediaFileType(): Implicitly marking parameter $type as nullable is deprecate notice
• fatal error in showsingle public controller from old cron call

Changes

• added settings dialog to IP address manager
• refactored date string conversion from strtotime to DateTime objects, new helper in \fpcm\classes\dateTimeHelper class
• added delete button for comment in editor view from comment manager

Addendum

The change log for the first beta did not include the information that the API registration for modules has been refactored as well.

Before FPCM 5.3, modules could provide an apiCallFunction event. Their methods were available through the VendorKey_ModuleKey_MethodName schema. This event has been removed completely. Static and non-static calls to fpcmAPI objects will trigger a deprecation notice.

The function has been replaced by a new FPCM API method getModuleApi which awaits a module key. The event looks for an event class in fpcm\modules\VendorKey\ModuleKey\events\api which must be an instance of \fpcm\module\api. All public function of can be access directly.

Calls to undefined methods will result in an exception. Therefore, I recommend to use try ... catch statements as of FPCM 5.3 for any API calls.

SHA256 hashes:

f2cd4e65cfb0295d0ed268d0fd06d2d9b77d09eac61d7f25842751fac4ed1936 fanpress_update_version5.3.0-b2.zip
66a222f0ca94c5c14514c3bec047db5f09c88c6fcc4eb4d7cf3f212c6ec6d2de fanpress5.3.0-b2_full.zip

Full Changelog: v5.3.0-b1...v5.3.0-b2