Page 1 of 1

Album mobule broke after upgrade to 1.1

Posted: Wed Jul 25, 2007 6:57 am
by jd
Hi,
I upgrade one of the websites to ver. 1.1 and the album module that was installed on it and it broke.
The images in the albums were displayed as their Alt texts. When I tried to re-create the albums again, I can't see the thumbnails of the images from the Image Manager.

The website has current mask of 002. I tried to switch to 022, but still doesn't work.

Any ideas?

(btw - if this does matters, I'm using FCKEditor as WYSIWYG editor)

Re: Album mobule broke after upgrade to 1.1

Posted: Mon Aug 06, 2007 11:51 am
by jd
???

anyone?

Re: Album mobule broke after upgrade to 1.1

Posted: Mon Aug 06, 2007 7:34 pm
by Dr.CSS
Had the same problem with no reply...

Re: Album mobule broke after upgrade to 1.1

Posted: Wed Aug 08, 2007 4:22 pm
by Michal
Hello,
which browser are you using? Maybe I have the same problem with IE, but in all others browser it's correct.

See my post - http://forum.cmsmadesimple.org/index.php/topic,14125.new.html#new



Michal

Re: Album mobule broke after upgrade to 1.1

Posted: Thu Aug 09, 2007 7:21 am
by jd
I had the problem regardless of the browser I used (I'm using FF 2.0.x anyways).

I managed to fix it (somehow) by tweaking again the site mask (switched again to 002), edited the config.php so that the server path in the images section of the config says

Code: Select all

/path/to/the/root/image/folder
insted of the default

Code: Select all

http:///path/to/the/root/image/folder
and it worked. I don't know whether this should be the correct "hacking" so that it works for the default installation, maybe it will be fixed in the next release of the Album module.

Re: Album mobule broke after upgrade to 1.1

Posted: Fri Sep 07, 2007 7:06 am
by SimonSchaufi
if anybody want to continue in the project: do it, because Elijah has not time and the others are also doing nothing (i think)

Re: Album mobule broke after upgrade to 1.1

Posted: Thu Oct 11, 2007 8:47 am
by jd
it's a great module, but now with the upgrade of the cms to 1.1.4.1 had the same problem and the same solution worked.