Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
this shows only during "install from URL" with no Uploadprogress or APC.
An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: .../authorize.php?batch=1&render=overlay&id=4&op=do StatusText: Internal Server Error ResponseText: UpdaterException: Unable to parse info file. in Updater::getProjectTitle() (line 183 of .../includes/updater.inc).
Comment | File | Size | Author |
---|---|---|---|
#34 | 951172-for-carloslamb.patch | 624 bytes | bfroehle |
#15 | drupal7beta2-SS-after_install_from_URL_1.jpg | 33.08 KB | aarael |
#15 | drupal7beta2-SS-after_install_from_URL_2.jpg | 54.22 KB | aarael |
#14 | drupal7beta2-SS - after install from URL - #1.jpg | 33.08 KB | aarael |
#14 | drupal7beta2-SS - after install from URL - #2.jpg | 54.22 KB | aarael |
Comments
Comment #1
rfayPlease describe this more clearly: What exactly did you do to get the error?
Comment #2
EvanDonovan CreditAttribution: EvanDonovan commented@aarael: What was the name of the module?
"unable to parse .info file" sounds like some kind of corruption or bad syntax in module, but maybe it is an error with Drupal itself....
Comment #3
aarael CreditAttribution: aarael commentedthese are the steps I did:
1. fresh install drupal 7 beta 1 or beta 2
2. enter database settings (note that progress bar shows perfectly here)
3. after install: install from URL any module (eg, pathauto, wysiwyg, bueditor) and any themes (eg. typebased).
then I get the error.
It may be due to the fact that the server has no Pecl Uploadprogress or APC?
Comment #4
rfayComment #5
rfayActually, I'm ignorant of what component that should be assigned to. Sorry.
It's a good thing you're testing this! Thanks.
Comment #6
aarael CreditAttribution: aarael commentedPlease note that this error also shows when using "Upload a module or theme archive to install"
Comment #7
EvanDonovan CreditAttribution: EvanDonovan commented@rfay: The component should be update.module, I think. I don't know what could be the cause, but since it works for me, and lots of other people, I think it's likely it has something to do with PHP settings.
@aarael: Could you post the output of phpinfo()?
Comment #8
aarael CreditAttribution: aarael commentedHi,
I have attached the PHP info of the server.
Cheers!
Comment #9
dmitrig01 CreditAttribution: dmitrig01 commentedaarael: thanks -- what method are you using to download (ssh/ftp)? Also, can you describe this in more detail: "3. after install: install from URL any module (eg, pathauto, wysiwyg, bueditor) and any themes (eg. typebased)." after you get to the modules page, walk me through exactly what you click on and where you type something in.
You indicate that it shows when installing from URL. Do you get this same error when uploading a file?
Also, this seems like an odd bug -- thanks for reporting and responding.
Comment #10
bfroehle CreditAttribution: bfroehle commentedI'm not sure we have enough to go off of to solve this bug until we get more information from aarael. However, we might want to consider adding more descriptive error messages --- currently the "Unable to parse info" error gets thrown if either we cannot find a .info or cannot parse the .info.
Comment #11
bfroehle CreditAttribution: bfroehle commentedI'm not sure we have enough to go off of to solve this bug until we get more information from aarael. However, we might want to consider adding more descriptive error messages --- currently the "Unable to parse info" error gets thrown if either we cannot find a .info or cannot parse the .info.
Also the patch in #10 is doomed due to a missing $. Fixed here.
Comment #12
dwwThe test bot will ignore #11 unless the status is needs review. Certainly a more specific error message is a step in the right direction, although none of these error messages are particularly helpful for end users. WTF are they supposed to do if they hit one of these cases? The messages give no indication of if/how to recover from the error...
Comment #13
bfroehle CreditAttribution: bfroehle commentedSetting to needs work since we need to flesh out some proper error messages and help for the user.
Comment #14
aarael CreditAttribution: aarael commentedHi,
Sorry for late reply, as I was on holiday. I tested the file upload and its working fine.
As for installing a module / theme through URL, here are the steps that I am doing in detail:
1. fresh install drupal 7 beta 1 or beta 2
2. enter database settings (note that progress bar shows perfectly here)
3. modules > Install New Module
4. in "Install from a URL", paste the following URL: http://ftp.drupal.org/files/projects/date-7.x-1.x-dev.tar.gz
5. click "install" button
6. ** screen will briefly show this (attached) : http://drupal.org/files/drupal7beta2-SS - after install from URL - #1.jpg
7. ** then screen will show this error (attached) : http://drupal.org/files/drupal7beta2-SS - after install from URL - #2.jpg
Please advise if I should upgrade to beta 3 to check whether this has been resolved?
cheers
Comment #15
aarael CreditAttribution: aarael commentedsorry file attachments seems to break.
reattaching...
Comment #16
bfroehle CreditAttribution: bfroehle commentedThe links to the attachments messed up a bit due to presence of the pound sign in the filename. Here are some working links:
Comment #17
bfroehle CreditAttribution: bfroehle commented@aarael: I'm still not sure what is causing this... can you try a few things for me?
1. Apply the patch in #11 and try again. The error message may (or may not) change.
2. See if you can find the downloaded (and extracted) files. The install (or upgrade) procedure works by downloading the file, extracting to a temporary directory, and then moving (or uploading via ftp / ssh) to the Drupal installation. Check for the downloaded files in /tmp or maybe a tmp directory in your home directory.
I have a directory called 'update-cache' that contains the downloaded date-7.x-1.x-dev.tar.gz file, and a directory 'update-extraction' that contains the extracted date module. Does it look like it has extracted the module correctly into the update-extraction folder?
Thanks!
Comment #18
aarael CreditAttribution: aarael commentedHi,
patch applied. New error shows:
An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: http://nulljournal.net/authorize.php?batch=1&render=overlay&id=24&op=do StatusText: Internal Server Error ResponseText: UpdaterException: Unable to find info file. in Updater::getProjectTitle() (line 182 of ...../includes/updater.inc).
I did not see any "update-cache" or "update-extraction" directories in the tmp directory ( upload_tmp_dir PHP.ini ). Does drupal create these directories automatically?
cheers
Comment #19
aarael CreditAttribution: aarael commentedJust updated the test site to Drupal 7 RC2.and the issue still exists.
I have few questions to clarify:
1. Does drupal 7 use upload_tmp_dir in php.ini?
2. Does drupal 7 create the folders in upload_tmp_dir when uploading themes/modules?
I'd be willing to provide a user access just to help resolve this issue in Drupal 7 before the final release.
Regards
Comment #20
aspilicious CreditAttribution: aspilicious commentedInternal Server Error ResponseText: UpdaterException: Unable to find info file. in Updater::getProjectTitle() (line 182 of ...../includes/updater.inc).
- This means the module doesn't have readable information in the .info file. Or that the .info is missing from the module.
- Could you add in this function (includes/updater.inc) after
$info=...
the following linesdebug($info_file);
debug($info);
- try to install afterwards and print here the debug output
-My extratected folders are located in the C:\xampp\tmp\update-extraction folder (windows)
Comment #21
vj_pdx CreditAttribution: vj_pdx commentedI believe I found a similar but not the same error.
On local MAMP/drupal 7 beta 3 installation, tried to install a module using the download url. I was trying to install Weather (http://drupal.org/project/weather), particularly http://ftp.drupal.org/files/projects/weather-7.x-1.0.zip
My URL is http://d7b3.localhost:8082/#overlay=admin/modules/install
My error reads: UpdaterException: Unable to determine the type of the source directory. in Updater::factory() (line 100 of /Users/vj/Sites/drupal-7.0-beta3/includes/updater.inc).
The website encountered an unexpected error. Please try again later.
The error is not fatal, but does not provide any graceful way of exiting the error.
(Please be kind -- this is my first issue to report. I'm happy to move this if I've put it in the wrong forum. Thanks.)
Comment #22
vj_pdx CreditAttribution: vj_pdx commentedAnd, I got the same error
UpdaterException: Unable to determine the type of the source directory. in Updater::factory() (line 100 of /Users/vj/Sites/drupal-7.0-beta3/includes/updater.inc).
The website encountered an unexpected error. Please try again later.
when trying to install from the "Upload a module or theme archive to install" input.
Thanks.
Comment #23
aspilicious CreditAttribution: aspilicious commentedThis is fixed in latest dev version, zip wasn't fully supported until last week.
Comment #24
vj_pdx CreditAttribution: vj_pdx commentedExcellent, thank you!
Comment #25
dwwThis might have been cleared up via #936490: Update module should verify downloaded tarballs and propagate errors correctly and/or #997802: Update manager doesn't allow you to install a project if it finds a single "broken" module in it. Certainly the error reporting is going to be better thanks to #1012822: If anything throws an Exception while downloading/verifying a tarball, you're in a dead end.
@aarael: Can you try again with the very latest D7 code from CVS HEAD (and potentially also with the latest patch from #997802 if that still hasn't been committed by the time you see this)? Then report back your findings. We could still probably commit #11 just in case, but I think there's probably something else going wrong here...
Comment #26
rack88 CreditAttribution: rack88 commentedSo am I reading this right that the automated updates within Drupal should not yet work (wait for 7.1?)? I've been having the error mentioned above on my site where I did a Drupal 6->7 upgrade recently.
Comment #27
bfroehle CreditAttribution: bfroehle commentedrack88: Can you be more specific about "the error mentioned above" ? Also, this issue is primarily for installing or upgrading modules, not a core Drupal 6 to Drupal 7 update. Your problem might be better dealt with by filing a new issue (or searching for another similar issue).
Comment #28
aarael CreditAttribution: aarael commentedHi guys,
This issues for me seems to be solved in Drupal 7 final release. However, I seem to be getting the issue related to this http://drupal.org/node/935036
Thanks guys!
Cheers!
Comment #29
carloslamb CreditAttribution: carloslamb commentedAs part of our ongoing system maintenance, we sometimes add new devices to help improve the performance of customer websites. As a result of the new hardware, customer CGI scripts (Perl, PHP) and databases that use "real" directory paths may cease to work.
If you are using real directory paths (paths that start with "/hermes/webxx/"), you need to replace them with the correct symbolic paths ("/home/users/web/"), which are fully compatible with our shared hosting architecture.
******** Pulled this from the iPage CGI FAQ. I notice in the error below I receive a reference to the "real directory paths" ********
Does this make any sense?
This is the error I get...
An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: http://stepuptechnology.com/authorize.php?batch=1&render=overlay&id=16&o... StatusText: Internal Server Error ResponseText: UpdaterException: Unable to parse info file: . in Updater::getProjectTitle() (line 183 of /hermes/bosweb/web239/b2392/ipg.stepuptechnologycom/stepup/includes/updater.inc).
Comment #30
carloslamb CreditAttribution: carloslamb commentedI entered the previous post but did not change the status. Please let me know if anybody will take a look at this post. Thanks! Carlos
Comment #31
bfroehle CreditAttribution: bfroehle commentedHi carloslamb. Can you give me the steps you took to get the error? Did you upload a file or paste in a URL? Which URL did you use? [I'm looking for some basic steps to reproduce the issue.]
Comment #32
carloslamb CreditAttribution: carloslamb commentedhosting with ipage.com and using their Drupal 7 install provided by smartscripts
Drupal 7 seems to install fine and the status report looks good
1. From management toolbar select Modules
2. Select Install new module
3. Browse to http://drupal.org/project/cck
4. Right-click on download to copy link address = http://ftp.drupal.org/files/projects/cck-7.x-2.x-dev.tar.gz
5. Paste address into "Install from a URL" field
6. Click on Install
"Upload a module or theme archive to install" yields the same error...
An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: http://stepuptechnology.com/authorize.php?batch=1&render=overlay&id=12&o... StatusText: Internal Server Error ResponseText: UpdaterException: Unable to parse info file: . in Updater::getProjectTitle() (line 183 of /hermes/bosweb/web239/b2392/ipg.stepuptechnologycom/stepup/includes/updater.inc)
Comment #33
carloslamb CreditAttribution: carloslamb commentedYou can use the account we have at ipage.com as a test if that helps. Development has not begun at this point.
Comment #34
bfroehle CreditAttribution: bfroehle commentedcarloslamb: Can you apply the attached patch, try again, and let me know the result.
Comment #35
Pancho3 CreditAttribution: Pancho3 commentedI am having the same problem
The specified file temporary://filegDGtrP could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
http://ftp.drupal.org/files/projects/pathauto-7.x-1.0-beta1.tar.gz could not be saved to temporary://update-cache/pathauto-7.x-1.0-beta1.tar.gz.
Unable to retrieve Drupal project from http://ftp.drupal.org/files/projects/pathauto-7.x-1.0-beta1.tar.gz.
Comment #36
rack88 CreditAttribution: rack88 commentedSorry, to specify better, I was having the same issue as aarael and carloslamb. I'm trying to use the nice updater function built into D7 with a brand new D7 install and recently updated modules. For example, I just tried to update Google Analytics from 1.0 to 1.1 via the on-site updater at /admin/reports/updates/update and I end up getting this error:
An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: http://www.rickhanton.com/test/authorize.php?batch=1&id=15&op=do StatusText: Internal Server Error ResponseText: UpdaterException: Unable to find info file in /tmp/update-extraction/google_analytics. in Updater::getProjectTitle() (line 182 of /hermes/web06/b1967/moo.rickhantoncom/test/includes/updater.inc). 500 Internal Server Error Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, cgiadmin@yourhostingaccount.com and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log.
I also tried the patch for carloslamb, which didn't help. Any ideas of what's going on? I can't locate any log files on the server that can be of use.
Comment #37
bfroehle CreditAttribution: bfroehle commentedrack88: Is safe mode or open basedir enabled? (You can look these up in your php info). Without being able to see if any log messages are generated it's tough to diagnose.
One idea would be to change the /tmp directory you are using. That's under config -> media -> file system.
Comment #38
bfroehle CreditAttribution: bfroehle commentedSetting this back to "Active" since while there are patches, all of them are purely diagnostic in nature (and most won't even apply to HEAD).
Comment #39
bfroehle CreditAttribution: bfroehle commentedComment #40
itspriyank CreditAttribution: itspriyank commentedHi when I tried to install a colorbox module using its url copied from drupal module's page I got following error. Please help me out.
An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: http://www.itspriyank.com/authorize.php?batch=1&render=overlay&id=3&op=do StatusText: Internal Server Error ResponseText: UpdaterException: Unable to parse info file: . in Updater::getProjectTitle() (line 183 of /hermes/bosweb/web231/b2315/ipg.digitalbustercom/itspriyank/includes/updater.inc). 500 Internal Server Error Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, cgiadmin@yourhostingaccount.com and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log.
It jst starts installation and then shows this error.
You can check my phpinfo() at http://digitalbuster.com/phpinfo.php
Comment #41
Pancho3 CreditAttribution: Pancho3 commentedI think the problem is PHP-5.2.17
This is the same version that is running on my server with HostGator and I have the same problem.
My test server on my computer uses PHP-5.3.4 and everything is ok.
I tried to change the /tmp directory nothing.
Comment #42
itspriyank CreditAttribution: itspriyank commentedYes I too think so, as I am using XAMPP on my system with php 5.3.1 and all works perfect. No problem at all. Now at ipage I have latest version 5.2.17, and root cause of problem.
Comment #43
deenseth CreditAttribution: deenseth commentedThe site that I have with ipower.com has the same problem. The php version is also 5.2.17. Is there any work around for installing module? Can I copy the module manually to the server?
Comment #44
itspriyank CreditAttribution: itspriyank commentedYes ther are lot of ways you can install a module.
You can copy the module to your server at drupal/modules then login as admin and go to module and click "check manually" at for updating the list. Now you will be able to see the newly copied module at end of list.
Similar to themes (paste it in drupal/themes)
Remember to paste unzipped or extrated folder and not zip ot tar.bz file.
You can also use Drush (http://drupal.org/project/drush).
Comment #45
John_B CreditAttribution: John_B commentedI was getting the same error (on a Lunux Apache server with php 5.3.4) and found a solution.
I did a full install of the current 7 (not dev) about four days ago. The Install new module feature worked fine on that site site. I did another install in a different directory with different URL on the same server today, and I got the error.
The first site on the server had created folders 'update-cache' and 'update extraction' in the Linux server's top level /tmp directory. When the second site tried to write folders of the the same names, using a different Linux unsername, permission was denied. I went in as root and deleted the folders created by the first site, and the Install new module started working for the second site.
Comment #46
Christopher James Francis Rodgers CreditAttribution: Christopher James Francis Rodgers commented=============================================
Solution to "..specified file %file could not be copied.."
===================================
The solution for me was simply..
Go to 'Configuration' > 'Media' > 'File System'
[*root*]/admin/config/media/file-system
and change the 'Temporary directory' from
/tmp to /tmp3
.
===
Error:
"The specified file temporary://file****** could not be copied,
because the destination directory is not properly configured..."
===
2011.03.26 - I updated this post to refine the work-around solution.
See http://drupal.org/node/1106492 for all the details.
Comment #47
flock CreditAttribution: flock commentedThis worked for me.
Switched /tmp to /tmp/justhost
Thanks.
Comment #48
Christopher James Francis Rodgers CreditAttribution: Christopher James Francis Rodgers commented@Flock:
I am happy for you. :o)
Please Note: I recently learned... 2011.04.05
Your easiest route to eliminate the Errors
that I was trying to address with my original Issue post
is for you to install Drupal 7 or 6 via your WebHost's "SimpleScripts"
or other automated-script-installation free service.
See this Drupal.org node (page) for my beginner's Tutorial.
http://drupal.org/node/1105616
[Install Drupal 7 in one-minute (or Drupal 6)]
I had not suspected that SimpleScripts would be D7 ready;
and I am now the happiest boy I know on Earth.
All the best. -chris. :o)
.
.
.
### D8 is gonna be great: The Dream.
Comment #49
dynamicdan CreditAttribution: dynamicdan commentedThis issue needs a kick!
First few installed no probs, the rest fail consistently...
Pathauto worked,
this failed: (http://drupal.org/project/admin_menu)
http://ftp.drupal.org/files/projects/admin_menu-7.x-3.x-dev.tar.gz (7.x-3.x-dev)
but this worked: http://ftp.drupal.org/files/projects/admin_menu-7.x-3.0-rc1.tar.gz (rc1, not dev version)
Should be enough to go on?
Could this issue be related to this btw?..
"Installation failed" errors when installing modules from Update Manager w/ Overlay
http://drupal.org/node/936686
Comment #50
ghalenir CreditAttribution: ghalenir commentedI also had the same problem with ipage.com but once I renamed and changed the temp file path it worked for me so if anyone has same problem make sure that the /tmp folder inside media/files is writable and really exist.
Comment #51
Christopher James Francis Rodgers CreditAttribution: Christopher James Francis Rodgers commentedFYI: I am not sure to what extent my work-around solution at http://drupal.org/node/1106492#comment-4562780 might be related to this issue, but I post this here in case my notes there are of any possible use to you.
All the best.
-chris
Comment #52
sunSorry, but I fail to see why this is major.
Comment #53
Christopher James Francis Rodgers CreditAttribution: Christopher James Francis Rodgers commented.. additionally, my solution relates to my former problems
with Drupal 7 only..
.. and Not Drupal 8.
Comment #54
Alajjana CreditAttribution: Alajjana commentedI have this same problem, several times with several installs...
My PHP version is 5.2.17
modules > install new module has been working for a while with about 15 installs. Today it failed.
I tried the suggestion of changing the /tmp to /tmp3, but it would not allow me to make changes. tried /tmp/justhost. It would allow me to make the change but the install would still fail.
So, i changed the /tmp to /drupal/sites/[mysite].com/tmp, created the directory tmp and now install is working as it had before it failed.
when i explore the ../tmp directory it has the the *.gz and *.tmp files, directories that were made with the file name format [modulename]-da8c3eaf.
All files are present. IE after install none of the the files have been removed after they are no longer needed.
Comment #55
Christopher James Francis Rodgers CreditAttribution: Christopher James Francis Rodgers commentedArchive? Today is D7.12
I marked this "closed (fixed)"
If this problem is in fact 'ongoing',
please "Add new comment" with location of
Newer-Discussion-URL at drupal.org
Comment #56
campbjp CreditAttribution: campbjp commentedThis sound like the same error I'm getting. Here is the link for 7.15 install: http://drupal.org/node/1748226