In Xoops 2.5.0, the image manager works differently from 2.4.5:
1) For new categories, there is no choice for storage in the database or the uploads folder (only storage in the uploads folder is possible)
2) Images already stored in the database (2.4.5. an earlier) are not previewed correctly in the admin Image Manager. I reported this earlier:

https://xoops.org/modules/newbb/viewtopic.php?topic_id=73081&forum=74&post_id=335374#forumpost335374

I also reported these two issues in the Sourceforge bug tracker. Trabis answered that "Images stored in the database are deprecated in Xoops 2.5.0". Is it true ? If it is, then:

1) It is not stated in the release notes of 2.5.0 !
2) There is no script to convert categories stored in the database to categories storing images in the uploads folder.
3) Images from "Categories stored in the Uploads folder" are inserted in in modules, e.g. News, in a very unfriendly way.

Let my explain issue 3):
- If you insert an image using the Image Manager button of the tex editor from a category stored in the database, it looks like:



This code always works, on your test site, after moving your site to another domain.

- If you insert an image from a category that is stored in de uploads folder, using the Image Manager Insert button of the text editor, this image is inserted as:



This is a full URL !! If you move your website to another domain (e.g. a testdomain) the links don't work any more. I think it should be:


or


or



However, these (smarty) codes don't work in e.g. news issues.

In summary, 4 issues:
- The deprecation of "images stored in the database" should be added to the release notes of 2.5.0
- Categories storing images in the uploads folder generate user-unfriendly urls in modules such as "News"
- There is no conversion script to convert image categories storing in the database to categories storing in het uploads folder.
- Not converting is an option, but then the "database-images" cannot be previewed in the image-manager

Wouldn't it be better to continue support for images stored in the database in Xoops 2.5 ?

SMEDrieben

I've sent a mail to Mamba:

Quote:

Mamba answered on March 7th, 2011:

Quote:

Dear Mamba,

This issue is different from the templates overriding issue: the latter could easily be converted.

I think that the conversion from "database images" to "uploads-folder-images" cannot be done manually. We need a conversion script. This script has to execute three steps:

1) store the database images in the uploads folder. The easiest way is to use image_name from the image-table in the database for the file name.

2) remove the imagebody table from the database. The image table must be left intact.

3) adapt the script of image.php or /class/textsanitizer/image/image.php or related scipts in such a way that xoopscodes like



keep functioning. When you were using database images, you will have hundreds of these codes in your module's databases. They cannot be changed in the codes that are regulare for uploads-folder-images. Therefore, the new textsanitizer should - using information from the image table in the database- convert the above given xoopscode to:



I think this issue cannot be solved manually in 2.5.0. I think we need a 2.5.1-patch that executes this conversion.

Kind regards,

SMEDrieben