Error 301?

Cindy Coutts · October 2nd, 2010, 11:05 AM

Hi Chuck. I was hoping to give you a break this weekend, but I have a lot of members still reporting an error 301. I can upload just fine and some other members can too, but a lot of them are getting the 301 message.

I've told everybody the usual log-off, clear your cache and cookies, and then reboot.

Any ideas? Thanks!

Chuck S · October 2nd, 2010, 11:39 AM

what are they getting a white page? Thats usually a error 500. what are the actual links of where they are getting a 301?

An error 301 is basically saying whatever link they are trying to access is permanently moved so I think I would need more specifics here on what your trying to report.

HTTP Error 301 Moved permanently Explained

Cindy Coutts · October 2nd, 2010, 12:52 PM

Chuck, here's what Natalie sent me:

Login - Gallery
IMG_4544_edited.jpg
Upload Error: 301

First time it tried it was IO error (it was so fast I couldn't copy it, it disappeared) this second time is the above info.

Chuck S · October 2nd, 2010, 02:03 PM

are you referring to the flash uploader?

Try turning it off in upload options and use the regular uploader.

Cindy Coutts · October 2nd, 2010, 09:59 PM

Turned off flash uploader and thank you. Haven't heard back from Natalie yet. Another member sent me this and we've never had a problem with this before. I think the default upload size may be too small? I'm not sure. I know her upload que is jammed now and I need to unjam that somehow. It's my guess that the upload size parameters changed somewhere and that's why some people are having problems? I'm not sure if we had the default before, but you are more than welcome to take a look to make sure all is well.

"I know you know about the upload issue but I thought I would send over what I've observed, including the error message ID.

I wasn't originally having this problem, but knew that others were. I typically resize my photos before uploading and tried in the midst of all the troubles and things were working just fine.

But then I tried uploading a large (unresized) image and it returned an error message:
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 3152 bytes) in /home/couttsc/public_html/gallery/image-inc.php on line 116

I tried uploading a smaller image and no success. What it seems is that the large files jam the que and aren't being processed through the system. This seems to be a per user issue as I wasn't having any trouble. I was able to upload the resized images, but when I tried uploading a large file and it loaded it to the que, but no further and is preventing any further completed uploads. It will allow me to add to the que, but it returns the error message when attempting to process.

It shows there are images in the que, but fails to process them."

Chuck S · October 3rd, 2010, 07:57 AM

http://www.photopost.com/forum/1266523-post2.html

I think this should help you out

Cindy Coutts · October 3rd, 2010, 03:16 PM

This tells me nothing. The links tell me nothing. Should my host upload Imagemagick to my server so that it's available to me? This crap has gone on for so long now that I don't remember if the new host ever had it on there for me or not. So I've got a ticket into them to find out. I am only one person and just need the gallery to work without jumping through a bunch of hoops for some answers.

Chuck S · October 3rd, 2010, 08:36 PM

what do you mean it tells you nothing?

If your host will install Imagemagick thats better than GD2 as mogrify is not partial to memory issues like GD2 is

The link I showed you has a tweak that allows you to increase your PHP memory since GD2 is part of PHP.

Cindy Coutts · October 3rd, 2010, 09:55 PM

Because I'm not a coder that's why it means nothing to me. The host is saying that it's installed and when I switched back to check, I start getting errors and I was fine with GD2. IM has never worked since the host change. So either the host installs IM or I have to change the php is what I'm reading. I did see the links and am just really afraid to do something like that because with my luck lately, I'll mess it up.

PS: Just told host to get on top of their game and install IM because I don't think it is installed, even though it is an option whereas before it wasn't, but something is wrong with how it's installed, if it is installed!

Cindy Coutts · October 4th, 2010, 07:51 AM

Chuck, I received this from the host this morning, so it looks like you're going to have to go back in and reconfigure some stuff since you installed my PP. As a reminder, I have made NO custom mods to my templates and the only mods that were made, you did, i.e., adjusting the slide show. Let me know your thoughts.

ImageMagick has to be installed and enabled on the server, then the correct path entered - but this is unavailable on Shared Hosting plans. We do not allow ImageMagick on Shared Hosting plans, since it is too unstable and resource intensive, which is why we give you GD2+. With Photopost Pro all that is required is that ImageMagick is disabled and GD2+ is enabled. The errors you are receiving look like they are related to a misconfiguration in Photopost Pro. We do install Photopost Pro on many servers, and all are setup to use GD2+, we do not have any issues being reported from it being configured to use GD2+.

Chuck S · October 4th, 2010, 08:20 AM

There is nothing for me to reconfigure here. If your host tells you all they are going to allow you is GD2 then you are stuck with that.

I have linked you to a post explaining GD2 issues and possible resolutions.

Basically your issue and you can tell your host this as this is not a photopost issue is your using GD2 to process images and as a result GD2 is part of PHP so its restricted by PHP settings.

The error you get says you do not have enough memory. Therefore when your using GD2 to process images you want to raise your PHP memory to something like 60 or 72M. GD2 is way more server intensive than Imagemagick IMO.

If you host does not want to raise the server's PHP memory limit then your only other direction would be for you to edit our global file pp-inc.php and near the top of the file under the error_reporting line place an ini_set line like this below save that file and reupload it to photopost directory.

Code:

Content visible to verified customers only.

Feel free to pass my thoughts along to your host as this is your resolution if you cant use mogrify.

Cindy Coutts · October 4th, 2010, 09:33 AM

One quick question Chuck, the memory problem is not a global problem. It only affects a few users, so logistically, that doesn't make sense. Any idea as to why?

And one user said that she resized her image and was able to upload and she was also getting the error message before then. In my settings, it's set to auto resize when needed.

I remember when I first got a new camera last year and I had the same problem at Splitcoast Stampers. I adjusted the size and QUALITY from high to normal and then I was able to upload. I don't know if they're GD2 or IM.

Chuck S · October 4th, 2010, 09:52 AM

Its a filesize issue so it is global.

if you upload a 600kb image it may process fine. However try and upload a 1.2M image you will probally see this issue as well.

You can clear all numeric directories under UPLOADS to unclog a users upload directory I believe we have discussed this before but the minute they try and process an image that size again you will see the problem which is why you want to give more PHP memory to GD2. GD2 is part of PHP and constrained by those same settings.

Cindy Coutts · October 4th, 2010, 10:41 AM

Chuck, it's currently set at 64. I asked host to change it to 72. When they do this and people still can't upload, I am going to assume that it's a problem on their end because their files are too big and they need to lower their camera and quality settings?

Chuck S · October 4th, 2010, 11:17 AM

It is set to 32mb from what I see and what your error states.

I would suggest they save the images as normal not fine yes in the camera.

Cindy Coutts · October 4th, 2010, 11:36 AM

Per host:

Hi Cindy,

128M is the amount recommended for vb4.
I can't downgrade it to 72m as there are site on the server using that allocation.
Your php.ini file can be set to a lesser/greater amount. We can change that for you.

Are we all on the same page for here? I'm not running vb4 and told them that and I thought I was asking for more server space, not less!

Cindy Coutts · October 4th, 2010, 11:56 AM

Per host again:

Hmmm...Here's my point of confusion.

The server is set to accept 128M
You want 72M, but you already have access to more than that?

Server space is a totally different thing and your still a long way from your 10gb allocation

Can somebody please straighten this out for me? Aren't you guys supposed to be talking the same language?

Chuck S · October 4th, 2010, 06:06 PM

They upped it to 64M so have you had the user try there upload?

Cindy Coutts · October 4th, 2010, 06:27 PM

Hi Chuck,

Hey this is Greg At UrlJet...

Our servers are set at 128M...the phpini file calls out 64M...

What can be done?

Chuck S · October 4th, 2010, 07:08 PM

Cindy needs to see if her customer's error is corrected since you changed the php settings to 64M. I beleive her customer was getting this error when you had it set to 32M which is not an uncommon thing when trying to process larger images with GD2 as it steals all the php memory. Now that you have changed it to 64M lets see what Cindy says if her customers issue is corrected.