Ticket #1765 (closed Bug: invalid)

Opened 10 months ago

Last modified 8 months ago

browsing with filemanager causes error

Reported by: marten1986 Owned by:
Priority: Normal Milestone:
Component: File Browser Version: FCKeditor 2.4.3
Keywords: Pending Cc:

Description

Dear,

I use FCKeditor for a while and implemented in several sites. Today I copied the working version on a other site too the new site. I build my directory structure that way that I can use /templates/images/upload/ in all my site as the user file path. So I don't need to change that. I've uploaded several images with a own upload script which is build in php.

When I browse the images I get the following error:

http://194.123.100.201/test/marten/error.jpg

Can someone help me with this problem?

Change History

Changed 10 months ago by wwalc

  • keywords file browser error xml removed

Hi,

This is not a bug in FCKeditor, you probably have to adjust server settings (IIS?). I have never seen that before, but you could try to google a bit: search for "php has encountered a stack overflow" and perhaps you will find some tips there, e.g try disabling Zend Optimizer etc.

Changed 10 months ago by marten1986

On another site on the same server it is working properly.....

Changed 10 months ago by wwalc

I guess that's the file permissions issue then. Make sure that permissions are set correctly.

Changed 10 months ago by marten1986

Still don't work..... the only thing I can see is the latest line on the error image. url="/templates/images/upload/image/"

It should be templates/images/upload/ But when I create the image directory in the upload map and change the userfilepath global it still doesn't work.

Changed 10 months ago by wwalc

Ok, so we have located the problem, it's invalid path. I suggest upgrading to FCKeditor 2.5. All paths are configuable there.

Changed 10 months ago by marten1986

I will try it.

Changed 10 months ago by w.olchawa

  • keywords Pending added
  • priority changed from High to Normal

Changed 9 months ago by wwalc

Did upgrading to 2.5 solve your problem?

Changed 8 months ago by w.olchawa

  • status changed from new to closed
  • resolution set to invalid

Ticket expired.

Note: See TracTickets for help on using tickets.