pancakes

MicrostockGroup Sponsors


Author Topic: Need help with image upload and processing images  (Read 8483 times)

0 Members and 1 Guest are viewing this topic.

Microstock Man

  • microstockman.com

« Reply #75 on: May 21, 2013, 03:38 »
0
In general I find it crashes around 5-6 minutes I think.

10 minutes - you actually did well! I don't think it's actually run that long before without crashing.

Uploaded the file again, though I highly doubt that is it.

It doesn't always crash when doing 15 images or so but it takes SO LONG. Then randomly it will decide to white screen me. It also white screens me occassionaly when on the image edit page to process them to live.

Any way to have 2 scripts - one for bluehost that works like it used to, one for godaddy people (that is until they change hosts  ;) )


Leo Blanchette

« Reply #76 on: May 21, 2013, 03:42 »
0
I rather liked that greedy stack of pancakes version too. This one gives you little thin pancakes one at a time...as slowly as you can digest them.

A toggle button...to switch to greedy mode? That might be possible. Let me think about it. This actually writes tmp files and everything...very slow. The other one juggled large amounts of data in mid-air, whch is why it performed so well.

But the constant crash reports from godaddy users demanded some sort of compromise.

« Reply #77 on: May 21, 2013, 09:17 »
0
Hi Leo,
I too have an issue when processing several photos. Sometimes it processes only the first photo of the batch. One time it did 20 and I had more than 200 selected.
Also, the search don't find my photos but it searches the network ones (clipartillustrations) ok. Is there another step that I missed?

I sent you a user admin credentials if you would like to verify.

http://michaelpettigrew.com/symbiotest/

Thanks!
Michael

« Reply #78 on: May 21, 2013, 12:09 »
0
The only error I get when processing images is when my JPEG images are more than 5000 pixels (at least one side).

Leo Blanchette

« Reply #79 on: May 21, 2013, 17:27 »
0
Hey guys, at this point I'd say we might be ok when 2.0+ is out. So it might just be best to wait for that. We're making fast and good progress.

Jeffery - does it say "imagemagick" or "gd library" on the image processor? 5000 width is probably around your cut-off length for that environment.

@blackvx I'll try to check that today and see where its failing. And if I may ask, what is your hosting? Did you set up your server memory properly?  What you are saying sounds like random crashes due to memory.

« Reply #80 on: May 21, 2013, 21:37 »
0
Hey guys, at this point I'd say we might be ok when 2.0+ is out. So it might just be best to wait for that. We're making fast and good progress.

Jeffery - does it say "imagemagick" or "gd library" on the image processor? 5000 width is probably around your cut-off length for that environment.

@blackvx I'll try to check that today and see where its failing. And if I may ask, what is your hosting? Did you set up your server memory properly?  What you are saying sounds like random crashes due to memory.

still have GD -- added the ini line  but imagemagick doesn't show up - any suggestion s?

« Reply #81 on: May 25, 2013, 16:39 »
0
still have GD -- added the ini line  but imagemagick doesn't show up - any suggestion s?


@cascoly Bluehost has some great help documentation for installing PHP extensions (http://my.bluehost.com/cgi/help/534 and posted the page itself further down just in case it is not visible).  Is there a line in your php.ini for extension_dir?

Quote
Viewing Currently Installed PECL Packages
To view the PECL Packages currently installed, you will need ssh access. To learn how to get SSH access, Click Here. Once you have logged in via SSH, enter the following command:

Code: [Select]
/usr/bin/pecl list       

Installing New PECL Packa
In the past we have done manual installations of packages as our customers needed them, but actually now we just have a pre-installed library, and if you wish to have another PECL package installed, these are the directions for doing so: You can download and install PECL packages locally to your account. You'll need SSH access. Once you're logged in, these are steps for installation:

    Create a folder in your home directory to download and compile the packages in.

   
Code: [Select]
mkdir ~/pecl
    Create a directory for you php extensions to be located in. Something like ~/php/extensions.

   
Code: [Select]
$ mkdir ~/php )

    $ mkdir ~/php/extensions

    Change directories to that created pecl directory and run the following command:

   
Code: [Select]
cd ~/pecl

    pecl download <packagename>

    ********************** For multiple PECL packages, repeat steps 4-9 and then step 12 *****************
    That will download the package which you'll then need to untar with:

   
Code: [Select]
tar -xvzf
    Change directories to the extracted directory and run the phpize command

   
Code: [Select]
cd ~/pecl/<packagedirectory>

    phpize
           

    When that's done, run the following command from inside the module folder ./configure --prefix=$HOME/pecl/<packagedirectory> ( you can find the directory to use by typing pwd inside the package directory)

   
Code: [Select]
cd ~/pecl/<packagedirectory>

    ./configure --prefix=$HOME/pecl/<packagedirectory>

    If that runs without error, then the package should be compatible with our environment. If it completes successfully, run the following command from individual module directory make

   
Code: [Select]
make
    That will create the module file that you'll need to put in your php.ini. It'll be located in the modules directory and will be named <packagename>.so

   
Code: [Select]
cd modules
    Copy the .so file to your ~/php/extensions directory that you created.

   
Code: [Select]
cp <packagename>.so ~/php/extensions
    Copy the existing server-installed extensions from /usr/lib64/php/modules/ to the ~/php/extensions directory:

   
Code: [Select]
cp -rf /usr/lib64/php/modules/* ~/php/extensions/
    Edit your php.ini file in public_html (assuming you're on single php.ini mode from the php config icon in the cpanel) and change the extension_dir setting to the full path to your ~/php/extensions directory

       extension_dir = "/home<#>/<username>/php/extensions"

    Add the extension to your php.ini file. It'll look like:

    extension=<filename>.so



 

Related Topics

  Subject / Started by Replies Last post
6 Replies
2858 Views
Last post June 24, 2007, 14:37
by hatman12
23 Replies
6820 Views
Last post January 24, 2016, 12:11
by Sean Locke Photography
26 Replies
12432 Views
Last post July 25, 2010, 15:05
by trek
2 Replies
3170 Views
Last post September 22, 2012, 09:36
by Will
7 Replies
2327 Views
Last post March 06, 2013, 13:01
by Pilens

Sponsors

Microstock Poll Results