Hi,

I installed inline without using image cache. It is not a problem to upload a file and to use the inline tag to insert it. My problem occur when you want to read the long version of the node in the frontend. Following error appers:

------------------------
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster and inform them of the time the error occurred, and anything you might have done that may have caused the error.
------------------------

Any idea to solve this matter?

Thanx
Jan

Comments

sun’s picture

Status: Active » Postponed (maintainer needs more info)

Please add some more information about your configuration, e.g. file storage method, enabled modules, web server, php version, and of course, if you encounter this error with any node, content-type, and file/file-type.

highmarket’s picture

Hi Sun,

I just tried to insert a small jpeg for testing reasons in a normal node. As requested more technical details:

Drupal 5.5
Configuration file Protected
Database schema Up to date
File system Writable (public download method)
MySQL database 5.0.18
PHP 4.4.7
Unicode library PHP Mbstring Extension
Web server Apache/1.3.37 (Unix) FrontPage/5.0.2.2623 mod_ssl/2.8.28 OpenSSL/0.9.8a

Moduels:
Core optional
Comment -enabled
Help -enabled
Menu -enabled
Poll -enabled
Search -enabled
Statistics -enabled
Taxonomy -enabled
Upload -enabled

Input filters
Inline -enabled

Other
Autolocale -enabled

Voting
jRating -enabled
Voting API -enabled

sun’s picture

Component: User interface » Code
Assigned: highmarket » sun
Category: support » bug
Priority: Normal » Critical
Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new2.38 KB

Please test attached patch.

havran’s picture

I think this is web hosting configuration problem. Drupal create in `files` (where are uploaded files saved) .htaccess file with some settings for Apache web server. You may try delete all lines in .htaccess file (but you must keep this file here) or make them to notes (with #).

#SetHandler Drupal_Security_Do_Not_Remove_See_SA_2006_006
#Options None
#Options +FollowSymLinks

This help me and many others people with restrictive web hosting.

sun’s picture

Please test the patch in front of havran's approach. Removing exactly that .htaccess file can lead to serious security vulnerabilities.
It is possible that this bug is just Apache 1.3.37/PHP 4.4.7-related.

highmarket’s picture

StatusFileSize
new14.78 KB

Hi,

After implenting the patch, I am receiving just the inline tag, neither a picture nor an error. Enclosed my new inline.module, you can doublecheck if I did the changes right.

If I change the .htaccess as havran mentioned and use the original inline.module it is working correctly.

sun’s picture

Priority: Critical » Normal

@highmarket: See http://drupal.org/patch/apply for information about how to apply patches. Please report back if the patch worked for you then, but also, if you will not try the patch anymore.

highmarket’s picture

I received following error while appling the patch:

patching file inline.module
Hunk #1 succeeded at 184 with fuzz 1 (offset -42 lines).
Hunk #2 succeeded at 196 (offset -42 lines).
Hunk #3 FAILED at 205.
Hunk #4 FAILED at 418.
Hunk #5 succeeded at 376 with fuzz 2 (offset -99 lines).
Hunk #6 succeeded at 402 (offset -99 lines).
2 out of 6 hunks FAILED -- saving rejects to file inline.module.rej

sun’s picture

This is most likely because other improvements have been committed since the release of 5.x-1.1, and the patch in #3 is against the latest development snapshot of Inline 5.x. You can download the latest development snapshot from the project page.

sun’s picture

@highmarket: Is this still relevant?

sun’s picture

Status: Needs review » Closed (won't fix)

Without further information I'm obliged to mark this won't fix, because I am not able to replicate this bug.