The message that is displayed if the library is not detected (curvycorners_status() function in curvycorners.module) is this:

The CurvyCorners javascript is missing. Please download it from <a href="http://curvycorners.googlecode.com/files/curvycorners-2.0.4.zip">CurvyCorners.net</a> and place curvycorners.js inside the root of your %curvycorners_folder folder.

...and it has version 2.0.4 hard-coded in the link. We should either change it to the google code download section: http://code.google.com/p/curvycorners/downloads/list and tell people to download the latest STABLE or link to the download section in the official CurvyCorners site: http://www.curvycorners.net/downloads/

I take it this code was left there from the 5.x branch, when perhaps the files were hosted in google code only and before there was a dedicated downloads section in the official CurvyCorners site. Anyways, if we don't generalize this now, will' have to be keeping track of the latest version of curvyCorners and updating as soon as a new version is out.

Now, I am aware that leading people to download any freshly released version like say the next 2.0.5 might break things. One -having this fact/possibility in mind- might argue that we should keep the latest tested version hard-coded in the link, but I think we should risk it and this way we'll have people reporting issues with newer versions of the library as soon as they occur. That will help us fix them sooner.

Thoughts?

Comments

JStarcher’s picture

JStarcher commented

That was the reason I hard coded it as it was the tested version. I also noticed they changed the filename a little since 1.x and if they decide to do it again that would cause problems.

However, I do agree about the testing new versions. I am going to put a little more thought into this, I may end up just recommending the latest stable but not sure yet.

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

Ok, thanks for considering this one.