Guest
11 Jul 2013 13:38

I am using an Image field I get the following error when I try to upload an image.

This is only happening when Select Images Source field is set to 'Upload'. When I set it to Joomla Media Manager or Initial Directory this doesn't happen.

Please advise, I would really like to use the 'Upload' feature.

Last Modified: 02 Mar 2014


stblink VIP
Total posts: 501
11 Jul 2013 14:27

Go to system -> system information -> tab directory permissions

see if the logs folder is writable


Guest
11 Jul 2013 15:22

Yep, everything is green including the logs folder.


stblink VIP
Total posts: 501
11 Jul 2013 15:48

It appears that the error is Joomla related and not Cobalt.

Have a look at this:

http://forum.joomla.org/viewtopic.php?f=706& ;t=797904

http://forum.joomla.org/viewtopic.php?f=708& ;t=797205

http://forum.joomla.org/viewtopic.php?f=707& ;t=790865


Guest
11 Jul 2013 15:52

Thanks for the info I will try some of these solutions out. :)


stblink VIP
Total posts: 501
11 Jul 2013 16:13

Although for the related links they have in common when installing extensions.

But for the error they all are linked to permissions.

Just a though, is the upload directory writable?

Working on localhost or online server?


Guest
12 Jul 2013 09:42

Current permissions are 775 on the image upload directory. That seems like it should be enough. Server is online.


Guest
12 Jul 2013 09:57

I also noticed some strange. Intially I was trying to upload files to the folder images/DirectoryImages when I got my initial error.

Just now I switched the upload directory to images. It still didnt work but I got the much simpler error of "Warning: Failed to move file!"

The permission on both folder are 775, any ideas?


stblink VIP
Total posts: 501
12 Jul 2013 09:59

create a file called index2.php and insert:

$dir = dirname(__FILE__); > echo "

Full path to this dir: " . $dir . "

"; > ?>

upload and visit:

www.ursite.com/index2.php

check configuration.php to see if the logs path correspond the path that index2.php shows + /logs


Guest
12 Jul 2013 10:12

Yep, everything checks out the same.


stblink VIP
Total posts: 501
12 Jul 2013 10:23

Exactly the same? i mean... an uppercase letter is enough for it not to be correct. Have u tried copy/paste the result path and just add /logs to it on configuration.php ?

1 - On system -> directory permissions, which directory/files show up as unwritable?

2 - Assuming that ur image field saves images on ursite.com/uploads , see if ursite.com/uploads/image folder is writable (755)


Guest
12 Jul 2013 10:53

Fixed! Thanks for your help, I would not have thought of the solution without it.

I noticed there was a /log folder and /logs folder. My Joomla install was set to the /log folder. I switched it to the /logs folder and the images are now uploading correctly.

I'm not really sure why this worked, but it did. Thanks again.


Guest
12 Jul 2013 10:55

Another piece of info. Just after writing this my sys admin informed me that he gave permissions on the uploads/ folder to give apache write and inherit permissions.

My guess is that is what fixed it. Anyways, hope this helps someone someday.


stblink VIP
Total posts: 501
12 Jul 2013 10:56

No problem.


stblink VIP
Total posts: 501
12 Jul 2013 11:06

I already had a problem with for example BT Login module.

If a user inserted bad credentials it would give a 500 error blank page.

On localhost everything was fine, it was only happenning when using a cpanel account online.

The problem was that configuration.php had log path set to:

"/logs"

changing it to:

"/home/username/public_html/logs"

Solved the problem.

What i want to say is that even though the logs folder is just for log writing, it can issue errors a little bit hard to diagnoss, if not correctly set.

I also use single image upload and never got that error, neither localhost or online.


Sergey
Total posts: 13,748
15 Jul 2013 02:53

You ned to turn on error reporting to maximum and turn on debug mode in global Joomla settings. then you will see more on error. Perhaps you will see error stack and we will see what files chain is runner to produce this error.

Powered by Cobalt