Parse error: syntax error, unexpected T_FUNCTION

I'm venture that your download has been corrupted. I assure you that 4.7 does not have any parse errors. I would replace it with a freshly-downloaded copy.

That's a good idea. I'm not going to duplicate the requirements from the project page in the readme, but rather reference the project page. That way it will always be updated.

Committed to 7.x-4.x and 8.x.

@drupalstrap -- That line of code is an anonymous function. There are only 2 reasons I know of why PHP choke on an anonymous function.

1) Use of PHP < 5.3, where anonymous functions aren't supported.
2) Use of an opcode cache that doesn't support anonymous function. APC works. Searching the issue queue will reveal another that doesn't, whose name escapes me at the moment.

I'd venture that your other functioning sites either a) aren't displaying components b) are using an older version of webform, c) are using a newer version of PHP or d) aren't using the same op code cache.

I have hit the same issue. Can confirm I'm using PHP 5.5. Only Webform module is breaking the website. Uninstalled the module and then reinstalled most recent version. Same error.

Parse error: syntax error, unexpected T_FUNCTION in ../sites/all/modules/webform/webform.module on line 4606

Thanks Drupalstrap. Going to try an older version. I should note that the most recent version was working just fine on my WAMP. It was only when I migrated to a live server that it broke. My WAMP is using PHP 5.3.1.

It's your installation. Disable or update eAccelerator. See http://php.net/manual/en/functions.anonymous.php#113422

The syntax in Webform is correct for PHP 5.3 and higher.

Call me crazy, but it seems backwards to push out a module update that requires you to turn off default settings on a server. Shouldn't the module adapt to the server, not the other way around?

It's a bug in eAccelerator, which has been (apparently) been fixed. Webform requires PHP 5.3. The affected version of eAccelerator doesn't support all of PHP 5.3 -- specifically anonymous functions.

eAccelerator is not a "default setting" of a server. It is add-on software (presumably added by a host company, and not kept up-to-date).

If you installed an add-on to Microsoft Word and it made Word crash every time you typed "Drupal", would stop writing about Drupal or would you remove or update the add-on?

Adding an update here for anyone who has hit the same problem.

Because my client's website is on shared hosting, I had to disable the eaccelerator module through .htaccess.

Create an .htaccess file and add the following code:

<IfModule eaccelerator>
php_flag eaccelerator.enable 0
php_flag eaccelerator.optimizer 0
</ifModule>

Then upload this to the WEBROOT folder (aka public_html) of your server.

All of the articles I found online did not include the "IfModule" part of the above code. Without that part, it kept crashing the server with a 500 error. Hope this helps someone in the future.

The project page says that the 7.x-4.x requires php >=5.3. Since drush runs from the command line. I would check the php version of your CLI. At the command line where you normally run drush commands, type php -v. If the version is <5.3, that is probably the cause of the issue.

The php version that your website is running on is not necessarily the same version that your SSH or your CLI is running.

A workaround is to disable webforms when you need to perform drush operations that aren't webform specific. You can always re-enable after your drush operations are completed.

There may be another solution, depending on your Web host's setup. For my issue here, the server was running PHP 5.2, hence the error. No GUI method to fix, but adding this to the .htaccess file at the Web root (public_html) fixed it right up:

# Use PHP54CGI as default
        AddHandler fcgid54-script .php

Hope this can help for some.

I also encounter the same problem here. Fortunately, It solved. The problem in my case is differrent php version used by drupal site and drush. After I corrected my drush php version in bash_profile with the same with drupal site php. Drush is working properly.

@arlingtonvoicellc

Thanks very much for this piece on code, we have been down for over 3 days now and your sweet piece of code has returned us back to a visible domain.

#19 worked for me, thanks