CE Phoenix Cart Forum

I have a new install of Phoneix 1.1.0.6 and for reasons that are lost on me I can't upload new product images. Setting things up to output error messages gives me this...
The directory permissions images directory are set to 755 which works on my live site that is located on the same server. Can anyone point me in the right direction? The file name does end up in the images directory but the file size is set to 0.

Dan

I think it's saying it can't find the tmp file. This probably means it's not getting uploaded.
- check the values of post_max_size and upload_max_filesize for php running in your test store
- have you got an addon that could be messing with the form in admin > catalog? Losing the enctype would do this

You can test the assertion by checking tmp file existence and logging the result before move_uploaded_file

My immediate thought was along the same lines as John.

The (I assume AI created?) image is too large (in MB) for your PHP version to handle...

IE, your max filesize might be set at 2MB and the image might be bigger.

Thanks for the responses guys. I dug a little deeper based on your input and I don't think file size is an issue....my php.ini file has the post_max_size and upload_max_filesize both set to 500M and the product images I tried to upload (I tried many different ones) were for the most part less than 100KB...there were a few slightly over that but all what I would consider to be very small files.

In answer to the question about whether I had an add-on installed that might interfere with the upload, it is a clean install from the Softaculous c-panel. Thinking that a file might have gotten corrupt during that process I did another completely clean install and unfortunately the issue persists. This leads me to believe that the download itself from Softaculous is to blame or it has something to do with my hosting account. I won't rule out a hosting issue just yet but since both my live site and now older test site both work fine in the same environment, just in different directories, I doubt that is the issue. That leaves me wondering about the Softaculous install. I'm guessing that others have installed 1.1.0.6 from there without problems but I might just pull a copy from github and see how that goes unless anyone can suggest other options before I do so?

Dan

Compare the two configure file paths. The `live` one might have different DI_FS_ and DIR_WS_ paths to the new one. Make the new one match as close as possible..

Thanks Gary....I compared the configuration files side by side (live site vs new 1.1.0.6) and they look the same other than the necessary differences in folder names. I think it might be time to take a run at installing a test site from a direct download here. I'm out of other ideas.

Dan

@burt@BrockleyJohn

I'm still in the weeds here. I found a bit of time to download the latest version of Phoenix from here on the forums and then uploaded it and copied over the configure files but unfortunately I still have the same issue. I'll probably tap my host next but I'd like to define the problem a little better before I do so. In that regard I decided to output some of the variables that seem to be in play when the move_uploaded_file() is called. Here is what I'm seeing at that point.
I don't see anything out of the ordinary here but maybe someone can spot the issue or suggest other variables or output I could try that would produce some sort of clue. Here's hoping.

Dan

/home/aquarsupplies/public_html/phoenix/images/

/home/aquarsupplies/public_html/PH16/images/

I wonder which is correct?

The PH16 is....my first post included the warning messages from the original site before I re-installed Phoenix again. The original install used the directory phoenix and the new install uses PH16 for the directory.

Dan

I thought I would update this thread. I finally got this working. I asked Gemini for help, and we added several error checks and coding changes to the upload class. This ensured that the file names and directories were correct and had the necessary permissions and then it suddenly started to work. I'm not exactly sure what solved it but I now have an updated class that addresses whatever the issue was and improves error checking within that code. Another win for AI. Woot, woot.

Dan