Cannot upload related object

Cannot upload related object

Monday 23 November 2009 7:17:12 am - 8 replies

Author Message

Gaetano Giunta

Monday 23 November 2009 10:39:11 am

Might be you do not have rights to create objects in the "media" section, and that's where eZP is set up to create related objects (such as images) in your case.

Either augment editor user rights or set uploaded images to be created as children of edited node.

Principal Consultant International Business
Member of the Community Project Board

Laurent B

Tuesday 24 November 2009 2:56:36 am

Hi Gaetano
Thanks for your quick answer.
However, I am the site administrator, so I do not know how I can further increase users' rights (as I have already obtained all rights).
Where can I configure the uploaded items to be a child of the edited node?

Thx

Gaetano Giunta

Tuesday 24 November 2009 4:40:09 am

If your are connected as admin user in eZP, then the problem is different.

Can you check in the eZP error log if there is anything streange?

Principal Consultant International Business
Member of the Community Project Board

Laurent B

Wednesday 25 November 2009 1:33:13 am

It says :

[ Nov 25 2009 10:27:01 ] [91.163.198.32] index:Undefined module: design

[ Nov 25 2009 10:27:01 ] [91.163.198.32] error/view.php:Error ocurred using URI: /ezlab/design/standard/images/favicon.ico

I really don't know what to do ? Is this due to OE ?

Gaetano Giunta

Wednesday 25 November 2009 6:50:19 am

The error you are seeing is from a missing line in your apache .htaccess file.

In short: in your pagelayout you have a link to the favicon.ico file in /ezlab/design/standard/images/favicon.ico, but this url is not interoretd by Apache as 'serve from filesystem' and sento to eZP instead. eZP thinks its a bad url and logs the error.

The fix is simple - look up the comments in your .htaccess_root file for examples.

Otoh it is weird that you do not have any message about your error.

You should:

- raise the logging level of eZP to include warning, notice, debug levels (change the Alwayslog setting in site.ini)

- check the php error log, too. Maybe the file you're trying to upload is too big wrt. the max allowed size in php.ini

Principal Consultant International Business
Member of the Community Project Board

Laurent B

Thursday 26 November 2009 2:59:26 am

I can't access the php.ini file, because i don't have the whole control of the server. I can't see the php.ini file in my FTP client.

So how do i can raise the logging level of eZP ?

Thx

Gaetano Giunta

Thursday 26 November 2009 3:20:40 am

The contents of php.ini you can see in the admin interface of ezp, in the "setup/system information" page, clicking on the link "details" next to php version. In there you can search for log_errors (it should be on) and error_log. Then you can see if by ftp you have access to the error log; if error_log is empty php will tunnell his errors in the apache error log.

If you cannot read that file, you should imho ask the server admin to be able to access it, read-only. It is often needed for debugging problems.

While looking at the php config, check the values for upload_max_filesize and file_uploads.

To raise the ezp error logging, set in site.ini.append.php:

[DebugSettings]

AlwaysLog[]=warning
AlwaysLog[]=debug
AlwaysLog[]=notice
AlwaysLog[]=strict

Principal Consultant International Business
Member of the Community Project Board

Laurent B

Thursday 26 November 2009 5:54:53 am

I've set the settings, in site.ini.append.php. However, it didn't help.

When i'm trying to access to the "setup/system information" page, there's no link next to php version. The maximum uploaded file size is 8M.

When i'm trying to read the content of .log files, there's no relation between the upload and the .log file's content.

thx

You must be logged in to post messages in this topic!

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.