Quote:

Thanks for the suggestions. I've looked at the text of the comments in the database and it looks OK - it's just simple text. I don't have access to modsec_audit.log so I will open a support ticket with my hosting company.

Situation
I am working in the Comments Manager on the admin side reviewing comments from Anonymous Users to decide whether a particular comment should be approved or deleted. When I click on any comment to view it I get a blank page (no error messages even with XOOPS debug turned on). When I click on Edit or Delete I am immediately logged out and I get the “Sorry, you don't have the permission to access this area”. I can log on again OK but I cannot view, edit or delete any comments using the Comments Manager, including existing, approved comments. However, I can view, edit or delete comments from the user side (if I can find them).

Actions Taken
I’ve searched these forums very carefully and I’ve tried every possible suggestion but the problem persists. Here is a summary of the things I’ve tried:
1. Check all permissions – I am logged on as Webmaster (UID=1) with all permissions set for everything.
2. Check the web host error log – no messages.
3. Check the PHP error log – no messages.
4. Turn on XOOPS debug – no error messages.
5. Run SQL Repair Table on the sessions table.
6. Delete all rows in the sessions table.
7. Run SQL Repair Table on the online table.
8. Delete all rows in the online table.
9. Clear the cache.
10. Clear the templates-c directory.
11. Test with custom sessions and without custom sessions.
12. Disable IP bans.
13. Deactivate all modules except for admin module (the theory being that there might be a module conflict).
14. Upload all files in admin folder again.
15. Run update module on admin module.
16. Temporarily disable XOOPS protector.

Xoops Environment
• XOOPS version - XOOPS 2.0.16
• Software server - Apache/2.2.10 (Unix) mod_ssl/2.2.10 OpenSSL/0.9.8b DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 mod_jk/1.2.25
• PHP version - 5.2.6
• MySql version - 5.0.67

Browsers
I have tested with:
• Firefox 3.0.5
• IE 7.0
• Safari 3.2.1 for Windows.

PHP INI Settings
The php.ini file has these settings:
• session.use_trans_sid = 0
• session.use_only_cookies = on
• register_globals = off
• allow_url_fopen = on
• post_max_size = 40M
• upload_max_filesize = 32M
• max_execution_time = 1800
• memory_limit = 80M
• log_errors = On
• error_log="phperror.log"

Hypothesis
I am running the same XOOPS software on other hosts and I’m not seeing this problem on the other sites. I am beginning to think that there might be something in the hosting environment which is causing this. However, I don’t know what to look for. Any suggestions?

I am trying to work out how to set the height of a text area used in a smartFAQ form when TinyMCE is used as the editor.

I am using TinyMCE version 0.5.
My XOOPS version is XOOPS 2.0.16.

I now have TinyMCE as the common editor throughout my XOOPS installation. I achieved this by following the advice in this XOOPS News Topic:
https://xoops.org/modules/news/article.php?storyid=4176

The advice in this topic is to modify class/xoopsform/formdhtmltextarea.php by changing this statement:
var $htmlEditor = array();

to:
var $htmlEditor = array( 'XoopsFormTinymce', '/class/xoopseditor/tinymce/formtinymce.php' );

This change has achieved the desired result in that I now have the TinyMCE editor available to me in every text area, i.e. across all modules and all through the admin sections. This is great because I can now offer a user-friendly editor to my users regardless of what module they happen to be using. I am using 5 XOOPS modules where text areas appear:

1. eXtCal version 2.00
2. newbb version 2.02
3. AMS version 2.42
4. smartsection version 2.13
5. smartfaq version 1.08

The question is:
How can I set the height of the text area for the smartFAQ Answer area?

The generated html code as shown in the html source at run time when I run submit.php shows this element as:
<textarea name='answer' id='answer' rows='10' cols='50' style='width: 100%; height: 200px;'></textarea>

The height of 200px is a default value which is set in formtinymce.php in this statement:
var $_height = "200px";

I am happy with this as the default height of a text area but I want to set the height of some text areas to a higher value. In this case I would like to set the height of Answer to 600px.

I have posted a similar question in the forums for these modules:
• Newbb
• AMS
• Smartsection
• SmartFAQ

Thanks, Tom O’Dea

I am using the DMS module (version 1.87) and I find that it's great for managing documents.

I am using the versioning facilities and I’m now up to version 8 on some of my documents. I would like to delete some of the older versions (mainly because of a need to free up disk space) but I can’t find how to do this.

I’ve tried various DMS options, I’ve studied the readme file and I’ve searched these forums but I can’t find anything.

Quote:

I finally figured it out. I found that I needed to add logic to the include file comment_delete.php to check to see if the current user is the owner of the comments.

I added these lines after line 97:

Quote:

Thanks for the tip, particularly about the checkbox. I thought I had set the expiry date by entering a date but it had no effect because I hadn't checked the checkbox.

Quote:

Thanks. I had a closer look at my articles and found that the module is behaving just as you say. Expired articles are no longer displayed on the main page but are available in the Archive. In other words, an article will be "moved" to the Archive when the expiry date is reached.

The AMS module allows you to set the date/time of expiration when you create a new article. However, I have not been able to find out how this date/time gets used.

I have articles where the expiry date has been well and truly reached but I can't see where anything different has happened to any of the articles.

When a registered user creates a comment, the user has 3 buttons available for that comment: Edit, Delete, and Reply. Edit and Reply work just fine. However, when the user presses Delete, the system responds with the "you do not have permission" message.

This is very confusing for the user because we show the Delete button but then when the user tries to use it, we give an error message!

Has anyone else encountered this problem?

Permissions are checked in the include file, comment_delete.php so I need to make a change to this file but it’s difficult to understand where the change should be made or what the change should be.

Any suggestions?

I’ve recently started using the Wordbook module. I am using Version 1.16.

I encountered a problem with letter.php where a request to show all entries had no results.

It seems as though this was corrected in Wordbook v1.17 RC 1. However, I can’t find a download for v1.17 anywhere.

In searching the forums I found references to a replacement module called Lexikon but I can’t find a download for this module anywhere.

So I decided to figure out what was wrong with letter.php.

I’m posting the resolution here in case there are others who are using Wordbook v1.16.

Line 74 in letter.php reads:

$queryA = "SELECT w. * , c.name AS catname FROM ".$xoopsDB -> prefix( 'wbentries' )." w LEFT JOIN ".$xoopsDB -> prefix( 'wbcategories' )."c ON w.categoryID = c.categoryID WHERE w.submit = '0' AND w.offline = '0' ORDER BY w.term ASC";

There is a space missing before “c ON w.categoryID”.

The statement should be:

$queryA = "SELECT w. * , c.name AS catname FROM ".$xoopsDB -> prefix( 'wbentries' )." w LEFT JOIN ".$xoopsDB -> prefix( 'wbcategories' )." c ON w.categoryID = c.categoryID WHERE w.submit = '0' AND w.offline = '0' ORDER BY w.term ASC";