Jump to content

IPS Community Suite 4.0.0 Release Candidate Available


Charles
 Share

Recommended Posts

  • Management

Upgrading IP.Content to Pages

When upgrading from IP.Content to Pages, it is worth noting that because the underlying code has changed, custom templates and custom blocks are not upgradable. Custom templates are removed from the system after the upgrade, and any custom blocks are retained, but left disabled as a reference point for recreating manually.

This release of Pages does not have external blocks (this feature allows you use IP.Content blocks on another website or page) and neither does it have relational database field functionality. Both these features will be available in a near-future release.

 

Link to comment
Share on other sites

  • Management

Upgrading from a previous 4.0.0 beta to RC 1 with custom CSS
If you have created a custom theme that makes use of Font-Awesome, or you've created a theme with Designer's Mode, then please check your CSS to ensure that you now only use a single backslash whereas previously it would have used two.

For example, in previous betas you might have used this:
content: "\\f1022";

As of RC 1, you'll need to use:
content: "\f1022";

Link to comment
Share on other sites

Theme Hooks

RC1 changes the structure of theme hooks slightly. If you created a theme hook on a plugin or application prior to RC1, open the hook file and change:

public static $hookData = array (
    ...
);

To:

public static function hookData() {
return array_merge_recursive( array (
    ...
), parent::hookData() );
}
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...