Hi,
I had created some albums using the image/taxonomy modules, and these were functioning with no problem for months.
I have not done anything to do with uploading pictures for a while. A few weeks ago, the free web host over a period of about 3 weeks was making some server updates that disrupted a number of functions on the site, like a memory problem which at times showed that error & at times the site was blank.
That is to be gone, for over 10days. I have no idea if it has anything to do with some residual problems ... In that time, I must say I deleted some modules - as advised in case they were contributing to the memory issue,. although I had dozens before those problems surfaced & there was no problem at all.
I updated the image module to the latest version the other day - it did not help.
Anyway, the thing is I can access the page were the created albums were listed: mysite/image - but there's only the heading & nothing more. I tried to create another album, but it does not appear.
I see nothing in the image module settings pages to do differently as everything looks ok.
I can access the albmu "list" via /admin/content/taxonomy/...
I can submit an image with no problem to the album I choose, but after that, I have to submit the direct link to access it.
Where could the problem be & how do I solve it?
:(
Comments
how did you create the page?
How did you create the page mysite/image ? Is it a view?
doug
Hi, thanks for replying. As
Hi, thanks for replying.
As much as I remember, it was created automatically when I installed the image module & uploaded some photos, via the corresponding link in "create content menu". I think it's around that time that I created more albums using taxonomy. I remember being able to see all the created albums, each represented by a picture on that page and each led to the whole set of pictures in it, when clicked on.
I have certainly never used the views module in connection to pictures.
Could someone help?
Could someone help?
Problem solved by update
Anyway - after having given up, the problem seems to have been solved after I updated to D-5.2, without having to do anything. :)