![]() |
Can't use "Additional Fields" I have a problem using one of the features of photopost. The software is finally working great. So, I tried to use the "Additional Fields" to add some "Extra Text Fields". But, when I do that, I can no longer upload to any category, that has these "Extra Text Fields" I get this error, if a category has additional fields. This ONLY happens on categories that have these "Additional Fields". I have removed them and the upload problem goes away. I have added them to different categories, and the problem follows the category that has these additional fields. Any clues why using "Additional Fields" causes the "Upload Photos" function to fail? Update: I am specifically referring to the "Extra Text Field #1*:" items and NOT "Add new field types". When I enter "Extra Field Names", I can no longer upload photos to those categories, until I remove those "Extra Text Field" labels. Update #2 (further debugging) Ok, two situations. 1) When I upload, without any "Extra Text Field" info, the sequence is this, on the location bar.
Another update (clue) There is another situation that causes exactly the same symptom. If I try to upload 2 photos, using the multiple upload capability, I get the exact same error when the "bulkupload.php" can't complete. I believe it's supposed to put up an intermediate screen, that shows each of the photos, with filelds that are to be filled in, before actually completing the upload. That doesn't work and I get the error shown above. The exactly same thing as what happens when I use 1 file, with "Extra Text Fields". That "bulkupload.php" apparently can't put up the screen that has these "Extra Fields". There is a folder /uploads/userID/ that holds these photos prior to putting in the category. I have verified that the files actually make it to this folder. But the bulkupload.php program fails at sending back the form, with the "Extra Text Fields". Any ideas now, as to what could be the problem? |
Hello what type of data are you inputing in the extra fields? You can email me admin login to test this out as on my install this works. I would suggest off right to upload clean uploadphoto bulkupload scripts and templates |
Yes, I can email you an admin login and password. Maybe I'm using it wrong. I assume the fields are for Extra Text Labels (the prompt) that are shown on an intermediate screen. So, for example, I have two extra fields: Name: Origin: That I enter into those "Extra Field Labels". Then, I would expect the intermediate screen to present me with a form, where I can complete the form and fill in these labels, with the actual data. See my latest update above. I have the same problem, with multiple files (with or without these extra text fields). The same problem. The bulkupload.php does not seem to be able to put up this form. |
Okay yes please email me with your response above I think your using something incorrectly but lets wait and see ;) |
:D Setting up the Admin account for you, led me to the source of the problem. I created the admin account but wanted to test it before I sent the details. Odd thing was, the problem didn't show up with the account I setup for you. So, what was the difference. My upload folder is at /uploads/MyUserID/ Your upload folder was at /uploads/YourUserID/ My folder had 7 or 8 large image files (for some reason). I think they were residual files that were left in that folder, for some reason I'm not sure about. Anyway, I assume that is a temporary folder for the initial upload, before moving to the category folder. When the bulkupload.php script executes, it thinks all those images are to be uploaded and the program crashes, for some reason (probably my upload limit or something); although my admin account has no limits. AND, the files are already uploaded (from previous uploads using FTP) so it can't be a PHP upload limit. :confused: Anyway, I cleared out all those images from the /uploads/MyUserID/ folder and my problems went away. Is the /uploads/MyUserID/ folder supposed to be cleared out after each upload? What can cause the images to remain? OH Wait! I just realized that I might have used that to upload some images by FTPing them to that folder and using a URL for the upload. I had that feature to leave the files in the folder. OOPS! I probably should not have checked the "do not delete" files from the upload folder. But that folder seems to be a default. Should one normally use a different folder for FTP uploads? Have I sized up this problem correctly? Anyway, it seems to have worked. I just need to understand the usage of the /uploads/MyUserID/ folder. |
Yep describing your issue as a problem with extra fields was a bit weird hense why I asked to see what you mean ;). Your having an issue with php cutting out cause your uploading large files and it is stopping. Bet your using GD2 which consumes php memory. Let's do this in uploadphoto.php and bulkupload.php require "pp-inc.php"; above that add this ini_set("memory_limit", "32M"); |
Ok Chuck, I guess I spoke a little too soon about the problem being completly fixed. I still have the same problem, with some conditions. I have tried your fix above and it didn't help. I'm sure there is some limits that are being exceeded but they don't seem to be with my server. My file upload limit is 2M (and 30 secon CPU time). Neither are being exceeded. But I can't upload a 1.1 meg file but if I resize it to 800K, it uploads. I have setup the admin account that you requested and will email you (to the address above) the particulars, if you want to take a look. |
If you try to upload a 1.1 meg file what error do you get? What you are experiencing is php server setting issues. If that 1.1meg upload takes longer than 30 seconds your toast. If you email me a url and admin login I can look at things and make suggestions based on your php setup Also your host may also be limiting your LimitBodyRequest variable to a certain size in php.conf or apache setup but based on you recieving the page you say I suspect it is a PHP timeout or PHP memory consumption issue. Try in pp-inc.php to add this code in bold and test with the 1.1 meg file Code: Content visible to verified customers only. |
Quote:
Like I said, the upload takes less than 15 seconds AND actually makes it to the upload folder. So, it's getting to my server OK. UPDATE: Oh wait, I didn't tell you the 15 seconds here. I sent that info in the email I sent, with the admin info. And I did enter that change into pp-inc.php but it made no difference. The upload script returned the error above however the file actually made it to the upload folder. It just didn't get any further. Info you requested has been emailed to both addresses. |
I would seriously suggest you ask your host about this LimitBodyRequest Your server is definately not allowing the processing of any file this big. If they will not change this setting then you will need to set your max filesize variable to 800 |
I will ask about this LimitBodyRequest. I have already explained the problem and the first response didn't look like I was violating anything. But the thing that is very puzzling is the file actually makes it to the server. I can see it in the /photopost/uploads/MyUserID/ folder. So how could a filesize limit be the problem? :confused: BTW, you changed something that put my stats on the right of the index page instead of the left. What did you change? Thanks for the help. PS: Where is the max file size? I see max photo width but nothing for max file size. |
Yes PHP's maxfileupload variable lets it go to the uploads directory However LimitBodyRequest is not allowing it to be processed. ;) Max filesize is settable in edit usergroup settings in admin you should always set this to match php's setting which is 2048 or of course lower |
Ok Chuck, I have checked with my web host and the LimitBodyRequest isn't the problem. That directive is set to "unlimited". They have also verified that it's NOT an upload limit that is being exceeded. They looked through the log files for this and said that there is a memory exhaustion error from the 'image-inc.php' file. Their memory limit for PHP is 32Meg, which is what you had me add to the upload.php and bulkupload.php files. Quote:
|
well yes we go back to memory limit and GD stealing memory which is what the ini_set thing is trying to get around that I suggested Your fine using Imagemagick your files process |
Quote:
I wasn't aware I had Imagemagick. When I installed Photopost, there was an image displayed for GD but none for Imagemagick. I assumed that meant I had only GD installed on the server. Is there any disadvantage to using Imagemagick? Any features lost? Clearly, there are advantages. :D Thanks, |
| All times are GMT -5. The time now is 05:41 PM. |
Powered by vBulletin® Version 3.8.1
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0