Great work 2.5.2. ! I discovered one strange thing.

It isn't a very important bug (if it is one), but my default 2.5.2. admin theme doesn't switch to silver. In 2.5.1a it worked perfectly !

When I click om "Silver", the fonts get black, but the header and the background remain dark. When I click, thereafter, on "Dark", the fonts return to light gray: the background (header) doesn't switch.

I did these tests both with Chrome and IE9. The same results. Erasing xoops-caches and Chrome caches doesn't change anything.

Any idea ?

SME Drieben

The login problem doesn't occur with my test system (xampplite 1.71) using the same Google Chrome browser. It only occurs with my production site. It doesn't occur with IE 8/9.

It seems that the logout-procedure isn't correct: the message of logging out isn't given either. I considered the possibility of a corrupt php-file. That is not plausible, because it works fine with IE 8/9.

Other differences:

Test: php 5.2.9
Production: php 5.2.13

Test MySql: 5.0.51a
Production: 5.1.46

Test Apache: 2.2.11
Production Apache: unknown

SMEDrieben

I have a strange experience with Xoops 2.5.1a and Google Chrome 11.0.696.60:

First experience
The first time I login: no problem.

Then I logout (user menu, or admin "Control Panel Home>Logout", or the Logout icon in the admin section): no system message on logging out appears, but the user menu disappear. When I tryhttp://www.mysite.country/admin.php, a system message apperas that I am not allowed to access this page.

Then I try to login again: a system message appears: "Than you for logging out"; the user menu doesn't appear.

After a second login attempt, the login succeeds.

Any idea ? Any solution ?

Second
Sometimes when I login and access the admin section, the menus don't unfold. I can solve this problem by emptying the browser cache. Nevertheless, last time the problem returned after one day.

Any idea ? Any solution ?

I didn't experience these problems with IE 9 or Mozilla 4. However, using these browser my fonts get very very unsharp. There are sharp in Chrome and IE 8.

SMEDrieben

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

I've sent a mail to Mamba:

Quote:

Mamba answered on March 7th, 2011:

Quote:

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

Removal of the .htaccess file doesn't help. I didn't expect that it would help: my images are stored in the database and not in the uploads folder.

However, I tried, but without success !

Any other suggestion ?

I've added a screenshot of the problem on Sourceforge:

https://sourceforge.net/tracker/download.php?group_id=41586&atid=430840&file_id=398208&aid=3154588

SMEDrieben

In 2.4.5, my images are stored in the database. After the upgrade to 2.5.0, I can use them in modules, using the Image Manager button in my texteditor (dhtmltextarea).

However, in the Image Manager of the Admin section, the images are not shown. After selecting a category, and clicking "View" the images appear, i.e. their names. At the place where the image or a thumb should be given, there is a purple rectangle with the text "Error messages disabled".

In the inline php-debug, no errors are given.

Is this a bug ?
Should the preferences be configured otherwise ?

SMEDrieben

Ghia wrote:

Quote:

When I create a new image category in 2.5.0 I don't have anymore the option of 2.4.5 and before to store images in the database. New categories are automatically stored in teh uploads folder.

Is this new in 2.5.0 ? I mean, can new image categories in 2.5.0 only store images in the uplaod folder ??

SMEDrieben

I think there are two ways for the upcoming 2.5.x releases to handle the cloned template set problem:

1) Stopping support of database template sets (suggestion of Trabis). In that case, the option in the preferences menu (where you can select a database template set) should be removed. Furtheremore, the upgrade instructions should be adjusted. Instructions on saving database template sets to files in the theme directory should be added.

2) Continuing support of database templates (2.5.0 functions in this way). In that case, the database templates should be made accessible for editing in the administration menu.

The Xoops-2.5-developers have to make a choice !

Thanks !

SMEDrieben