Hello,

my drush installation fails with the following error message:

Parse error: syntax error, unexpected T_STRING in /home/.dash/rvstudio/drush/includes/table.inc on line 1

Any suggestions welcome.

Thanks.

CommentFileSizeAuthor
#6 drush-515568.patch21 bytesMTecknology

Comments

hutch’s picture

just guessing but there might be some junk characters at the very beginning of table.inc

ellis-’s picture

Im having this problem to.
table.inc is an HTML document.

mariogalan’s picture

To solve the problem you have to download Console_Table.

http://download.pear.php.net/package/Console_Table-1.1.3.tgz

Untar the file and replace the original table.inc with Table.php.

It works for me.

giampirm’s picture

replace the first row with:

<?php echo '<?xml version="1.0" encoding="utf-8"?>'; ?>

by

MTecknology’s picture

Comment #3 was able to solve the issue for me.

MTecknology’s picture

StatusFileSize
new21 bytes

Here's a patch for the issue.

Gabriel R.’s picture

Thank you! This fixed it.

Gabriel R.’s picture

Status: Active » Fixed
tarzadon’s picture

Status: Fixed » Active

Thanks perrymanson. That solved the issue for me too.

jbrauer’s picture

Status: Active » Reviewed & tested by the community

The fix in #3 worked for me as well.

jbrauer’s picture

Category: support » bug
Status: Reviewed & tested by the community » Needs work

This is actually a result of the conversion of php.net from CVS to SVN which is currently running and makes the request to the old CVS page instead return http://svn.php.net/?revision=1.28&view=co at the moment. Once the conversion is complete it will likely be necessary to update the module with a new URL.

jbrauer’s picture

Version: All-Versions-2.0 »

update version

greggles’s picture

Title: unexpected T_STRING at runtime » unexpected T_STRING at runtime - Download code from PEAR via SVN

Improved title (and subscribe).

MTecknology’s picture

Status: Needs work » Closed (fixed)

Feel free to reopen if this is still an issue. I'm just closing it because it's been inactive for a long time.
This issue seems to be resolved as well.