Question about recent changes to layout.inc

lvthunder

Joined: 2003-09-12
Posts: 808

Posted: Thu, 2004-11-11 21:14

I was reading the changelog and found this.


2004-11-08 07:13 bharat

We now support module upgrades.  If you upgrade and a module's version changes,
then the module will become inactive and you'll have to go to the AdminModules
page and click the "upgrade" (or "downgrade" as appropriate!) link and then
reactive the module.

* We now store the module version in the plugin status list so that we can
  get easy access to it and determine whether or not the module's code has
  changed vs. what's in the database

* AdminModules has icons for active, inactive and needs-install/upgrade

* New status code:  ERROR_PLUGIN_VERSION_MISMATCH

* Changed status code: ERROR_BAD_MODULE => ERROR_BAD_PLUGIN

* We now need to check for ERROR_PLUGIN_VERSION_MISMATCH any time that we
  request a module that's not the one we're currently in (except for core).

* Layouts no longer have init() -- we do it in the constructor

* GalleryCoreApi::loadPlugin() no longer takes an initialize parameter

* NetPBM site admin page now handles bad paths a little more gracefully

    * layouts/matrix/layout.inc (1.43)
    * layouts/slider/layout.inc (1.10)
    * layouts/tile/layout.inc (1.8)

Does that mean that I should redo the layout.inc file for my layout? I would like to know before I install another snapshot.

I'm impressed on how responsive the devs are at getting g2 updated with fixes and adding in new stuff. There is quite a bit of new stuff that has been added since Alpha 3.

Thanks,

mindless

Joined: 2004-01-04
Posts: 8601

Posted: Thu, 2004-11-11 23:36

yes, if you update then your custom layout.inc will break.. but, the update you need to make is very easy.. just change the init() method to be the constructor instead. the content is the same (though you can remove the return value I guess)

lvthunder Joined: 2003-09-12 Posts: 808	Posted: Thu, 2004-11-11 21:14
	I was reading the changelog and found this. 2004-11-08 07:13 bharat We now support module upgrades. If you upgrade and a module's version changes, then the module will become inactive and you'll have to go to the AdminModules page and click the "upgrade" (or "downgrade" as appropriate!) link and then reactive the module. * We now store the module version in the plugin status list so that we can get easy access to it and determine whether or not the module's code has changed vs. what's in the database * AdminModules has icons for active, inactive and needs-install/upgrade * New status code: ERROR_PLUGIN_VERSION_MISMATCH * Changed status code: ERROR_BAD_MODULE => ERROR_BAD_PLUGIN * We now need to check for ERROR_PLUGIN_VERSION_MISMATCH any time that we request a module that's not the one we're currently in (except for core). * Layouts no longer have init() -- we do it in the constructor * GalleryCoreApi::loadPlugin() no longer takes an initialize parameter * NetPBM site admin page now handles bad paths a little more gracefully * layouts/matrix/layout.inc (1.43) * layouts/slider/layout.inc (1.10) * layouts/tile/layout.inc (1.8) Does that mean that I should redo the layout.inc file for my layout? I would like to know before I install another snapshot. I'm impressed on how responsive the devs are at getting g2 updated with fixes and adding in new stuff. There is quite a bit of new stuff that has been added since Alpha 3. Thanks,
	XUser login Username: * Password: * Create new account Request new password
mindless Joined: 2004-01-04 Posts: 8601	Posted: Thu, 2004-11-11 23:36
	yes, if you update then your custom layout.inc will break.. but, the update you need to make is very easy.. just change the init() method to be the constructor instead. the content is the same (though you can remove the return value I guess)

Question about recent changes to layout.inc

XUser login