Dumb quick question about module backward compatibility

halftone

Joined: 2005-09-29
Posts: 22

Posted: Sat, 2006-05-20 11:03

Probably the stupidest question posted here, but I don't know the answer. Something recently ate my database through making assumptions, so I thought I'd better ask this time...

Specifically the module I am asking about is the Checkout module, but it's really a general question.

I am using Gallery 2.0.2.

1. Do I download the latest module version, designed to work with Gallery 2.1 - ie is backward G2 compatability retained in later module versions?

2. Or must I download an earlier version of the module which worked with G2 v 2.0.2, but avoid module versions for later G2 because Things Will Break?

3. Or is it a case of 'maybe, maybe not - it depends what has changed'.

A simple 1,2 or 3 response would educate me iwth least embarassment.

Regards
Tony Sleep

Termitenshort

Joined: 2005-10-09
Posts: 1894

Posted: Sat, 2006-05-20 13:29

A gallery module designed for G2.1 has 99.5% chance NOT to work on gallery 2.0.x (and vice versa ....)

So I guess the answer to your question is 2

-------------------------
The Termite

halftone

Joined: 2005-09-29
Posts: 22

Posted: Sat, 2006-05-20 16:25

Thanks. I meanwhile went away and determined this empirically, and indeed, you appear to be correct, +/- 0.5%

At least some modules appear to check for Gallery code compatability, but not all. IWBNI like the Drupal Modules page, it was possible to filter modules by the version they work with. Drupal seems to have a module packaging convention which maybe makes things easier, eg 'MyDrupalModule-x.xx.tar.gz' - where x.xx is the Drupal version it's designed for. If Gallery modules have any naming convention, I'm too dim to have understood it yet.

Regards
Tony Sleep

floridave

Joined: 2003-12-22
Posts: 25965

Posted: Sat, 2006-05-20 17:23

Third party modules don't have any naming convention but some third party modules have some sort of naming convention. It is up to the developer / supporter of the module in question.

I guess you could try to enforce some naming convention but I doubt you would be successful as some modules are not even actively developed anymore.

Dave

mindless

Joined: 2004-01-04
Posts: 8601

Posted: Sat, 2006-05-20 18:24

the user contributions page has a checkmark and download link for each G2 version they work with..

halftone Joined: 2005-09-29 Posts: 22	Posted: Sat, 2006-05-20 11:03
	Probably the stupidest question posted here, but I don't know the answer. Something recently ate my database through making assumptions, so I thought I'd better ask this time... Specifically the module I am asking about is the Checkout module, but it's really a general question. I am using Gallery 2.0.2. 1. Do I download the latest module version, designed to work with Gallery 2.1 - ie is backward G2 compatability retained in later module versions? 2. Or must I download an earlier version of the module which worked with G2 v 2.0.2, but avoid module versions for later G2 because Things Will Break? 3. Or is it a case of 'maybe, maybe not - it depends what has changed'. A simple 1,2 or 3 response would educate me iwth least embarassment. Regards Tony Sleep
	XUser login Username: * Password: * Create new account Request new password
Termitenshort Joined: 2005-10-09 Posts: 1894	Posted: Sat, 2006-05-20 13:29
	A gallery module designed for G2.1 has 99.5% chance NOT to work on gallery 2.0.x (and vice versa ....) So I guess the answer to your question is 2 ------------------------- The Termite

halftone Joined: 2005-09-29 Posts: 22	Posted: Sat, 2006-05-20 16:25
	Thanks. I meanwhile went away and determined this empirically, and indeed, you appear to be correct, +/- 0.5% At least some modules appear to check for Gallery code compatability, but not all. IWBNI like the Drupal Modules page, it was possible to filter modules by the version they work with. Drupal seems to have a module packaging convention which maybe makes things easier, eg 'MyDrupalModule-x.xx.tar.gz' - where x.xx is the Drupal version it's designed for. If Gallery modules have any naming convention, I'm too dim to have understood it yet. Regards Tony Sleep

floridave Joined: 2003-12-22 Posts: 25965	Posted: Sat, 2006-05-20 17:23
	Third party modules don't have any naming convention but some third party modules have some sort of naming convention. It is up to the developer / supporter of the module in question. I guess you could try to enforce some naming convention but I doubt you would be successful as some modules are not even actively developed anymore. Dave

mindless Joined: 2004-01-04 Posts: 8601	Posted: Sat, 2006-05-20 18:24
	the user contributions page has a checkmark and download link for each G2 version they work with..

Dumb quick question about module backward compatibility

XUser login