FileField and ImageField 3.0 have just been released and bring with them the ability to display an upload progress meter in the FileField widget while a file is being uploaded. As ImageField uses the FileField widget this works for ImageFields too.
The original article FileField and ImageField 3.0 for Drupal 6 Released points out:
Probably the most exciting improvement is the addition of upload progress indication. This enhancement requires the PECL uploadprogress PHP extension, but adds a real asset to sites that use FileField for podcasts, videos, or other large files.
It took me a while to figure out how to install this extension so I thought I'd do a quick post about it. These instructions are probably valid for other PECL extensions but since this is the only one I have installed I wouldn't like to say for sure.
Installation on Unix/Mac
$ pecl install uploadprogress.Download the PECL uploadprogress extension
Extract the uploadprogress-1.x.x.tgz archive, cd into the extracted folder and run these commands in Terminal:
$ phpize # prepares the PHP extension for compiling
$ ./configure
$ make
$ sudo make installCheck that the directory for the extensions is correct. The last line of the output returned from the
$ make installcommand (on my system) is:Installing shared extensions: /usr/lib/php/extensions/no-debug-non-zts-20060613/.Open php.ini and edit the
extension_dirdirective, replacing it with this path.Add the extension to php.ini by adding this line
extension=uploadprogress.so- Restart apache
You should now have the PECL uploadprogress extension installed.
Installation on Windows
It's very simple to install on Windows:
- Copy the uploadprogress.dll file from pecl4win into the path set for
extension_dirin php.ini. - Add
extension=uploadprogress.dllto php.ini. - Restart apache.
The pecl4win site was down for maintenance at time of writing so you could try here in the meantime (thanks to chriscohen for the link).
If you're using using WampServer 2 then it already comes with php_uploadprogress.dll installed (thanks again to chriscohen for pointing this out and testing that both methods work).
Increasing Maximum Filesize
To increase the maximum filesize you need to set 2 directives:
- upload_max_filesize - Maximum allowed size for uploaded files.
- post_max_size - Maximum size of POST data that PHP will accept.
Generally you should set post_max_size to double what you set upload_max_filesize to. This means you can upload 2 files of your maximum limit for each POST and seems like a good middle ground.
The memory_limit directive should also be set above the value of post_max_size so your server can handle the uploads.
There are 2 ways you can set this directive:
php.ini
Edit php.ini and modify these directives:
post_max_size = 256M
.htaccess
Edit .htaccess and add:
php_value post_max_size 256M
Adjust 128M and 256M with the sizes you require.
Increasing PHP's Memory Limit
You could edit the memory_limit directive in php.ini but I personally like to set that directive on a site-by-site basis. This helps to keep sites that don't need such a large memory_limit nice and efficient.
Instead you can set the directive in settings.php by adding this line just below the other ini_set lines:
pecl install EXTENSION_NAME
Or just type "pecl install uploadprogress" which accomplishes the same thing on at least Linux. You'll still need to add the line to php.ini.
Hadn't realized though you needed to install uploadprogress to get the bar. It looks nice.
ERROR: `phpize' failed
@Kyle Mathews: Thanks for pointing that out, I forget to write about it in the original post. When I tried to run it I got this error:
Password:
downloading uploadprogress-1.0.0.tgz ...
Starting to download uploadprogress-1.0.0.tgz (7,761 bytes)
.....done: 7,761 bytes
3 source files, building
running: phpize
Configuring for:
PHP Api Version: 20041225
Zend Module Api No: 20060613
Zend Extension Api No: 220060519
ERROR: `phpize' failed
This is why I had to go the manual route. If
pecl install uploadprogressworks then that's obviously much easier!Added to DrupalSightings.com
Added to DrupalSightings.com
How to install it on MAMP under OS X
Thank you for sharing. I have created a how to about this issue if you need to do it on OS X and with MAMP for your dev. env.
http://smbjorklund.no/how-enable-pecl-uploadprogress-extention-mamp
Cheers
Steinmb
On Debian and Ubuntu
There is a package called dh-make-php that allows you to turn PECL (and PEAR) extensions into .deb packages, so you can manage 'em through the package system.
pecl download uploadprogress
dh-make-pecl uploadprogress-1.0.0.tgz
cd php-uploadprogress-1.0.0
# The next step may require depends, it will tell you. Just install them.
fakeroot dpkg-buildpackage -b
# The source is configured and the package is created. You should see something like:
dpkg-deb: building package `php5-uploadprogress' in `../php5-uploadprogress_1.0.0-1_amd64.deb'.
You now have a .deb that you can install (and also install elsewhere, as long as distro and arch match).
Good hint using
Good hint using dh-make-pecl!
At Ubuntu 8.04 I had to use:
Also setting the maintainer information was necessary before running dh-make-pecl:
export DEBFULLNAME='Your Name'
Cannot find autoconf.
I got this error when installing on Debian:
environment variable is set correctly and then rerun this script.
I had to install php4-dev to get it to work:
Thanks
You are the only persons that could explain how to installed.
shared hosting install?
Is it possible to install the upload progress on a godaddy shared hosting account?
Possibly
Hi adam, Not sure about godaddy, I have not used them before. You could try emailing their support to see if they will install it for you.
php5-dev on debian 4
There's a similar comment above, but just in case you get something like:
Starting to download uploadprogress-1.0.0.tgz (7,761 bytes)
.....done: 7,761 bytes
3 source files, building
running: phpize
sh: phpize: command not found
ERROR: `phpize' failed
If you are using Debian 4 with PHP5, you'll need to have php5-dev installed. So:
and then you can run
Thanks for the help!
Can't Make with Tiger
No errors with phpize or ./configure
When I try and make it, I get the errors below.
gcc -I. -I/Users/v4/Desktop/uploadprogress-1.0.0 -DPHP_ATOM_INC -Iinclude -Imain -I/Users/v4/Desktop/uploadprogress-1.0.0 -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM -I/usr/include/php/Zend -DHAVE_CONFIG_H -g -O2 -c uploadprogress.c -fno-common -DPIC -o uploadprogress.lo
uploadprogress.c: In function 'uploadprogress_php_rfc1867_file':
uploadprogress.c:75: error: 'MULTIPART_EVENT_START' undeclared (first use in this function)
uploadprogress.c:75: error: (Each undeclared identifier is reported only once
uploadprogress.c:75: error: for each function it appears in.)
uploadprogress.c:76: error: 'multipart_event_start' undeclared (first use in this function)
uploadprogress.c:76: error: 'e_data' undeclared (first use in this function)
uploadprogress.c:77: error: parse error before ')' token
uploadprogress.c:87: error: 'MULTIPART_EVENT_FORMDATA' undeclared (first use in this function)
uploadprogress.c:89: error: 'multipart_event_formdata' undeclared (first use in this function)
uploadprogress.c:90: error: parse error before ')' token
uploadprogress.c:124: error: 'MULTIPART_EVENT_FILE_START' undeclared (first use in this function)
uploadprogress.c:127: error: 'multipart_event_file_start' undeclared (first use in this function)
uploadprogress.c:129: error: parse error before ')' token
uploadprogress.c:146: error: 'MULTIPART_EVENT_FILE_DATA' undeclared (first use in this function)
uploadprogress.c:147: error: 'multipart_event_file_data' undeclared (first use in this function)
uploadprogress.c:149: error: parse error before ')' token
uploadprogress.c:163: error: 'MULTIPART_EVENT_FILE_END' undeclared (first use in this function)
uploadprogress.c:164: error: 'multipart_event_file_end' undeclared (first use in this function)
uploadprogress.c:166: error: parse error before ')' token
uploadprogress.c:176: error: 'MULTIPART_EVENT_END' undeclared (first use in this function)
make: *** [uploadprogress.lo] Error 1
Dependences of php4-dev
How i use sid, haven't php4-dev package, so when i tried to resolve the depends, returned the error. I found a bug (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449025) and the solution (into bug), where say to use the '--only 5' option in the dh-make-pecl command. Using the example above:
same error
I am getting the same error with LarryO. Any suggestion?
worked grate thanks!
worked grate thanks!
I get to pecl download uploadprogress....
and then I get the phpize failed error. I tried doing it manual but it says that ./configure does not exist. Now what?
Thank you! Saved me a great
Thank you! Saved me a great load of time!
Hello, I am completely new to
Hello,
I am completely new to configuring web servers but I'd like to install this library in order to use it with drupal. I tried to follow the first option and I got this error:
parsePackageName(): invalid package name "uploadprogress." in "uploadprogress."
invalid package name/package file "uploadprogress."
Cannot initialize 'uploadprogress.', invalid or missing package file
Package "uploadprogress." is not valid
install failed
So I decided to follow the second part of the instructions but as far as I can understand (which is not much, I can assure it to you) those instructions are to be used in case of managing my own server, which is not my case since I am on a shared hosting by dreamhost. I assume I can install those libraries since their support team have provided me the link to this website, but I don't know how to proceed. Could someone give me an answer, please?
Thank you
Got the .db made, now what
Thanks for the directions to create a .deb file on my Ubuntu system, they were great. But now what do I do with the .deb file?
Ahhh. got it
cd ..
sudo dpkg -i ./php*.deb
And then did phpize + install but no joy
Following appeared to work:
$ ./configure
$ make
$ sudo make install
But my Drupal report claims it isn't installed yet.
What's left to do???
to pete
3.Check that the directory for the extensions is correct. The last line of the output returned from the $ make install command (on my system) is:
Installing shared extensions: /usr/lib/php/extensions/no-debug-non-zts-20060613/.
Open php.ini and edit the extension_dir directive, replacing it with this path.
4.Add the extension to php.ini by adding this line extension=uploadprogress.so
5. Restart apache
You should now have the PECL uploadprogress extension installed.
Just a tiny detail, but for
Just a tiny detail, but for windows installation I think it should say:
Add extension= php_uploadprogress.dll to php.ini.
instead of:
Add extension=uploadprogress.dll to php.ini.
You just needed to drop the
You just needed to drop the trailing fullstop from your command. It should be "pecl install uploadprogress" not "pecl install uploadprogress." You can see the fullstop still in each occasion the package name is listed in quotes, and it tells you also invalid package name on both the second and third lines... :)
uploadprogress-1.x.x.tgz archive, cd into the extracted folder
I can do everything else in terminal and such but this easy part i dont get, errrrrrr, i'm all hung up, any help is appreciated
Installing it in Bluehost / Linux
Is it also possible to install it without the shell console? thanks a lot!
Unable to install on ubuntu jaunty
I am very new to linux and this is above my head.
I am unable to install pecl upload progress through the terminal on Ubuntu desktop 9.04.
I tried:
sudo aptitude install php-pear
sudo pecl install uploadprogress
But after downloading the gz file it says a directory .build/m4 doesn't exist and the installation fails.
Is there another way?
Download the package manually and extract to ... ? ...
Chmod or chown or create a directory to allow for installation?
Also if i add an extension to php.ini, should i not also add an extension directory?
Other issues to note
Apparently when I added some gd extras with dotdeb.org sources a while back, it switched my php5-dev to the dotdeb version when I ran apt-get update, which pretty much ruins pecl because its got different directories for several files that throw errors when the pecl install command is run. What a pain in the but! lol ... so if ur getting the following errors thats whats going on.
downloading uploadprogress-1.0.1.tgz ...
Starting to download uploadprogress-1.0.1.tgz (8,536 bytes)
.....done: 8,536 bytes
4 source files, building
running: phpize
Configuring for:
PHP Api Version: 20041225
Zend Module Api No: 20060613
Zend Extension Api No: 220060519
cp: cannot stat `libtool.m4': No such file or directory
cp: cannot stat `ltmain.sh': No such file or directory
cat: ./build/libtool.m4: No such file or directory
configure.in:8: warning: LT_AC_PROG_SED is m4_require'd but not m4_defun'd
aclocal.m4:2628: PHP_CONFIG_NICE is expanded from...
configure.in:8: the top level
configure.in:137: error: possibly undefined macro: AC_PROG_LIBTOOL
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure:1849: error: possibly undefined macro: LT_AC_PROG_SED
ERROR: `phpize' failed
When googling I saw several drupalers with the same problem cause I used dotdeb as per some instructions on adding the extra gd support to ubuntu/debian. Wish I could remember where that was so I could let them know...
Cannot find autoconf.
[...]
"Cannot find autoconf. Please check your autoconf installation and the $PHP_AUTOCONF
environment variable is set correctly and then rerun this script."
I've searched far and wide, and I can't seem to find a solution to this.
I'm running CentOS with php 5.
I've tried mounting /tmp as exec, setting $PHP_AUTOCONF as an environment variable to point to the correct binary, and just about every other tip I could find on the net.
Any help you could give would be greatly appreciated.
cancel upload
Does anybody know if anybody has implemented a cancel upload button? or how would you guys implement such feature?
php_uploadprogress not present in WampServer 2.0i
I just installed WampServer 2.0i and php_uploadpregress is not present in the list of extensions :)
How could I do? Couse I think that the version that i can donwload of php_uploadprogress is different from the php
UploadProgress Not Accessible from Drupal Directories
Thanks for the article, psynaptic.
My shared hosting provider installed the uploadprogress extension and I am able to confirm this with phpinfo(). However, none of my Drupal installation directories can access the extension.
Running phpinfo() from any directory inside /public_html shows that the uploadprogress has been installed except when I run phpinfo() from any directories where Drupal is installed in.
Any ideas what could be causing this? Do I need to change something in the .htaccess file created by Drupal?
Linux / Apache / PHP 5.2.9 / Drupal 6.14
Thanks
php.ini Conflict
Removing php.ini file from Drupal directories fixed the problem.
Will have to use .htaccess and/or settings.php to make changes to php settings.
Increasing Maximum Filesize
I was able to Increase PHP's Memory Limit using the directive in settings.php. However, adding
php_value post_max_size 256M
Is it possible to use settings.php to increase the maximum file size and what would be the syntax?
extension_dir directive
I've followed your unix/mac directions on a current version of debian.
I'm a n00b so I didn't know that downloading and extracting uploadprogress with ssh is done with these commands:
wget http://pecl.php.net/get/uploadprogress-1.0.1.tgztar zxvf uploadprogress-1.0.1.tgzrm uploadprogress-1.0.1.tgzAnyway, after following through with the commands in step 2 i am stuck at step 3.
You say that I should change php.ini's
extension_dirdirective with the path mentioned afterInstalling shared extensions:.But extension_dir is already pointed at
./Would redirecting
extension_dirnot break any other extensions?Shouldn't i rather point to
uploadpgrogress.sowith a symlink from./or move it to the default extension_dir location./?specific extension_dir directive is correct
The originial instruction udner Max/Unix is correct.
I tested symlinking the extension and placing it at
php.ini's original location. This did not work. Apparentlyuploadprogress.soeither contains specific paths after installation or needs a specific path inphp.inito get at necessary resources.thanks a lot it worked.
thanks a lot it worked.
Hi, i have a problem
Hi, i have a problem installing this package on gentoo 2010..
could you help meplease ?
command : pecl install uploadprogress
error :
Starting to download uploadprogress-1.0.1.tgz (8,536 bytes)
.....done: 8,536 bytes
4 source files, building
running: phpize
Configuring for:
PHP Api Version: 20041225
Zend Module Api No: 20060613
Zend Extension Api No: 220060519
configure.in:158: warning: AC_CACHE_VAL(lt_prog_compiler_static_works, ...): suspicious cache-id, must contain _cv_ to be cached
../../lib/autoconf/general.m4:1974: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:1994: AC_CACHE_CHECK is expanded from...
aclocal.m4:3549: AC_LIBTOOL_LINKER_OPTION is expanded from...
aclocal.m4:5487: _LT_AC_LANG_C_CONFIG is expanded from...
aclocal.m4:5486: AC_LIBTOOL_LANG_C_CONFIG is expanded from...
aclocal.m4:2966: AC_LIBTOOL_SETUP is expanded from...
aclocal.m4:2946: _AC_PROG_LIBTOOL is expanded from...
aclocal.m4:2909: AC_PROG_LIBTOOL is expanded from...
configure.in:158: the top level
configure.in:158: warning: AC_CACHE_VAL(lt_prog_compiler_pic_works, ...): suspicious cache-id, must contain _cv_ to be cached
aclocal.m4:3504: AC_LIBTOOL_COMPILER_OPTION is expanded from...
aclocal.m4:7614: AC_LIBTOOL_PROG_COMPILER_PIC is expanded from...
configure.in:158: warning: AC_CACHE_VAL(lt_prog_compiler_pic_works_CXX, ...): suspicious cache-id, must contain _cv_ to be cached
aclocal.m4:5600: _LT_AC_LANG_CXX_CONFIG is expanded from...
aclocal.m4:5599: AC_LIBTOOL_LANG_CXX_CONFIG is expanded from...
aclocal.m4:4635: _LT_AC_TAGCONFIG is expanded from...
configure.in:158: warning: AC_CACHE_VAL(lt_prog_compiler_static_works, ...): suspicious cache-id, must contain _cv_ to be cached
../../lib/autoconf/general.m4:1974: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:1994: AC_CACHE_CHECK is expanded from...
aclocal.m4:3549: AC_LIBTOOL_LINKER_OPTION is expanded from...
aclocal.m4:5487: _LT_AC_LANG_C_CONFIG is expanded from...
aclocal.m4:5486: AC_LIBTOOL_LANG_C_CONFIG is expanded from...
aclocal.m4:2966: AC_LIBTOOL_SETUP is expanded from...
aclocal.m4:2946: _AC_PROG_LIBTOOL is expanded from...
aclocal.m4:2909: AC_PROG_LIBTOOL is expanded from...
configure.in:158: the top level
configure.in:158: warning: AC_CACHE_VAL(lt_prog_compiler_pic_works, ...): suspicious cache-id, must contain _cv_ to be cached
aclocal.m4:3504: AC_LIBTOOL_COMPILER_OPTION is expanded from...
aclocal.m4:7614: AC_LIBTOOL_PROG_COMPILER_PIC is expanded from...
configure.in:158: warning: AC_CACHE_VAL(lt_prog_compiler_pic_works_CXX, ...): suspicious cache-id, must contain _cv_ to be cached
aclocal.m4:5600: _LT_AC_LANG_CXX_CONFIG is expanded from...
aclocal.m4:5599: AC_LIBTOOL_LANG_CXX_CONFIG is expanded from...
aclocal.m4:4635: _LT_AC_TAGCONFIG is expanded from...
building in /var/tmp/pear-build-root/uploadprogress-1.0.1
running: /tmp/pear/download/uploadprogress-1.0.1/configure
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for a sed that does not truncate output... /bin/sed
checking for cc... cc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... none needed
checking how to run the C preprocessor... cc -E
checking for icc... no
checking for suncc... no
checking whether cc understands -c and -o together... yes
checking for system library directory... lib
checking if compiler supports -R... no
checking if compiler supports -Wl,-rpath,... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for PHP prefix... /usr/lib64/php5
checking for PHP includes... -I/usr/lib64/php5/include/php -I/usr/lib64/php5/include/php/main -I/usr/lib64/php5/include/php/TSRM -I/usr/lib64/php5/include/php/Zend -I/usr/lib64/php5/include/php/ext -I/usr/lib64/php5/include/php/ext/date/lib
checking for PHP extension directory... /usr/lib64/php5/lib/php/extensions/no-debug-non-zts-20060613
checking for PHP installed headers prefix... /usr/lib64/php5/include/php
checking if debug is enabled... no
checking if zts is enabled... no
checking for re2c... no
configure: WARNING: You will need re2c 0.13.4 or later if you want to regenerate PHP parsers.
checking for gawk... gawk
checking whether to enable uploadprogress functions... yes, shared
checking for ld used by cc... /usr/x86_64-pc-linux-gnu/bin/ld
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from cc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if cc static flag works... yes
checking if cc supports -fno-rtti -fno-exceptions... no
checking for cc option to produce PIC... -fPIC
checking if cc PIC flag -fPIC works... yes
checking if cc supports -c -o file.o... yes
checking whether the cc linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
creating libtool
^[[Aappending configuration tag "CXX" to libtool
configure: creating ./config.status
config.status: creating config.h
running: make
/bin/sh /var/tmp/pear-build-root/uploadprogress-1.0.1/libtool --mode=compile cc -I. -I/tmp/pear/download/uploadprogress-1.0.1 -DPHP_ATOM_INC -I/var/tmp/pear-build-root/uploadprogress-1.0.1/include -I/var/tmp/pear-build-root/uploadprogress-1.0.1/main -I/tmp/pear/download/uploadprogress-1.0.1 -I/usr/lib64/php5/include/php -I/usr/lib64/php5/include/php/main -I/usr/lib64/php5/include/php/TSRM -I/usr/lib64/php5/include/php/Zend -I/usr/lib64/php5/include/php/ext -I/usr/lib64/php5/include/php/ext/date/lib -DHAVE_CONFIG_H -g -O2 -c /tmp/pear/download/uploadprogress-1.0.1/uploadprogress.c -o uploadprogress.lo
/var/tmp/pear-build-root/uploadprogress-1.0.1/libtool: line 460: CDPATH: command not found
/var/tmp/pear-build-root/uploadprogress-1.0.1/libtool: line 1145: func_opt_split: command not found
libtool: Version mismatch error. This is libtool 2.2.6, but the
libtool: definition of this LT_INIT comes from an older release.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6
libtool: and run autoconf again.
make: *** [uploadprogress.lo] Error 63
ERROR: `make' failed
Build the extension manually
I used dotdeb.org repositories with debian/lenny too and ran into exactly the same problem. A workaround solution is to build the extension manually. This is what worked for me:
tar xvzf uploadprogress-1.0.1.tgz
cd uploadprogress-1.0.1
export PHP_PREFIX="/usr"
$PHP_PREFIX/bin/phpize
./configure --with-php-config=$PHP_PREFIX/bin/php-config
make
make install
Then I added .INI file with
nano /etc/php5/conf.d/uploadprogress.iniwith content:And finally restarted Apache:
I used jelenex's instructions
I used jelenex's instructions and got it to work. I am using Media Temple (dv) 3.5. I could not figure out how to edit php.ini with vi (but did not try nano, did not figure out if I had that) and added extension=uploadprogress.so after the line extension_dir = "/usr/lib/php/modules" restarted apache, and it worked.
I meant to mention I edited
I meant to mention I edited php.ini with TextWranger through ftp.
uploadprogress on GoDaddy
Did you ever get an answer to this question?
I'm trying the same thing but GoDaddy Tech support is next to useless if you're asking for anything more complicated than having a password reset. . .