Daniel F

Invision Community 4.4 has introduced the new AdminCP Notification, which allow you to programmatically send a notification to the admin. To implement this within your custom application, create the new extension via the ACP Application Developer Center, and then you can send it using the following: \IPS\core\AdminNotification::send( 'demo', 'Test'); if you want to remove a notification, you can use following code: \IPS\core\AdminNotification::remove( 'demo', 'Test' ); Similar to the frontend notifications, the send method accepts the following additional parameters /** * Send Notification * * @param string $app Application key * @param string $extension Extension key * @param string|null $extra Any additional information which persists if the notification is resent * @param bool|null $resend If an existing notification exists, it will be bumped / resent * @param mixed $extraForEmail Any additional information specific to this instance which is used for the email but not saved * @param bool|\IPS\Member $bypassEmail If TRUE, no email will be sent, regardless of admin preferences - or if a member object, that admin will be skipped. Should only be used if the action is initiated by an admin making an email unnecessary * @return void */ public static function send( $app, $extension, $extra = NULL, $resend = TRUE, $extraForEmail = NULL, $bypassEmail = FALSE )

Club Navbar IPS 4.4.0 provides a new method /** * Can be used by 3rd parties to add own club navigation tabs before they get sorted * * @param array $tabs Tabs * @param \IPS\Node\Model|NULL $container Container * @return array */ protected function _tabs( array $tabs, \IPS\Node\Model $container = NULL ) : array which allows hooks to add own tabs to club navigation bar. Changes to the queue/task system: We've created 3 new constants 'REBUILD_SLOW' => 50, // Number of items to be rebuit per-cycle for routines that take a while 'REBUILD_NORMAL' => 250, // Number of items to be rebuit per-cycle for most routines 'REBUILD_QUICK' => 500, // Number of items to be rebuit per-cycle for routines that are fast which should be used in your queue extensions depending on the task and the time it takes. Editor Buttons: It's now easier to add or remove buttons to the editor within the \IPS\Helpers\Form\Editor class. Additional plugins are handled via $defaultOptions['ipsPlugins'] New useful methods: Item::lastModificationDate() - The sitemap generation uses this method to get the last modification date. Email Templates Change: If your custom application includes email templates, please create also emailstats__key language strings for each email template. This language strings are used for the email statistics which were introduced in IPS 4.4.0 New Form Helper: Interval/TimeFrame Selector New Traits: Content\ItemTopic - implements the logic to allow content items to create, update and delete their topic ( pages app & downloads app) Core BC Breaks (warnings): Node\Model::canOnAny and Node\Model::can() got a new parameter Node\Model::modPermission 3rd parameter is required, there's no default value anymore Member::moderateNewContent got a new parameter Member::postRegistration got a new parameter Content\Item::followers() & containerFollowers - method signature changed, the last parameter was replaced Content\Item::can() , canComment ,canReview , canCommentReview, moderateNewItems, moderateNewComments, moderateNewReviews- got a new parameter $considerPostBeforeRegistering which is used to determine if the content was created by a guest public static function canOnAny( $permission, $member=NULL, $where = array(), $considerPostBeforeRegistering = TRUE ) Additional Information: ActiveRecord - new property $caches allow you to define datastore keys which will automatically be cleared after save&delete was called. There's no need to implement this logic anymore.. The \IPS\Helpers\Table\Content constructor got a new parameter for a callback function, which is executed at the end of the getRows method. This way you don't need to implement an own Content Table Helper just to prepare the data for the output. Most of the not extensible classes like share services, file storage engines, package types, payment gateways, license key generation methods, server types, converters, and widget types or classes which were required to be placed in a specific directory are extensible now...

To support lazy loading in your content, first of all, the container of the image needs either to utilize the ipsLazyLoad module or if you're using the Lightbox, it's enough to have your content wrapped by an element utilizing the core.front.core.lightboxedImages controller. <div data-ipsLazyLoad> {{if settings.lazy_load_enabled}} <img src='{expression="\IPS\Text\Parser::blankImage()"}' data-src='{$coverPhoto->file->url}' class='ipsCoverPhoto_photo' data-action="toggleCoverPhoto" alt=''> {{else}} <img src='{$coverPhoto->file->url}' class='ipsCoverPhoto_photo' data-action="toggleCoverPhoto" alt=''> {{endif}} </div> If you are loading html content which could contain lazy loaded images via JS, you can call ips.utils.lazyLoad.loadContent( elem ); in your controller to load the elements, or alternatively ips.utils.lazyLoad.observe( elem ); to attach the lazy load observer to the new element. Since IPS 4.4.2 you can also use the richText template to parse your content. {template="richText" group="global" app="core" location="global" params="Content containing the lazy load images", array('ipsType_normal')"}

Invision Community 4.3 introduces a new Reply to a Review feature. To support Review Replies, your Review class needs to define author_response in the column map. namespace IPS\myapp; class _MyClass extends \IPS\Content\Review { public static $databaseColumnMap = array( /* etc */ 'author_response' => 'author_response', ); } Additionally, you must add a Mediumtext column to your content items database table with the defined name from the columnMap. New ReviewReply related methods: /** * Has the author responded to this review? * * @return bool */ public function hasAuthorResponse() /** * Can the specified user respond to the review? * * @note Only the author of the content item can respond by default, but this is abstracted so third parties can override * @param \IPS\Member|NULL $member Member to check or NULL for currently logged in member * @return bool */ public function canRespond( $member=NULL ) /** * Can the specified user edit the response to this review? * * @param \IPS\Member|NULL $member Member to check or NULL for currently logged in member * @return bool */ public function canEditResponse( $member=NULL ) /** * Can the specified user delete the response to this review? * * @param \IPS\Member|NULL $member Member to check or NULL for currently logged in member * @return bool */ public function canDeleteResponse( $member=NULL )