Anyone get this server error?

Parse error: syntax error, unexpected ',' in /sites/all/modules/emfield/contrib/emaudio/providers/podomatic.inc on line 84

I started getting this when I made a bunch of updates today for Drupal 6.5 and other related modules that need security fixes. The site won't even load with this error.

Comments

ica’s picture

yes.. i can confirm exactly the same error is exist as a bug on the
Parse error: syntax error, unexpected ',' in ..../providers/podomatic.inc on line 84 needs to be fixed
---------------------
~spiffyd
"The site won't even load with this error"
for now you can just delete the buggy podomatic.inc on your site
/sites/all/modules/emfield/contrib/emaudio/providers/podomatic.inc
than you should have your site 'back'

Aibehn’s picture

i have the same error on the alpha3.

I have to upload to my site the 6.x-1.0-alpha2 version and all was fine now.

redram’s picture

Yep. Me too. Removing that podomatic.inc file from alpha3 release works for me (I didn't need that audio provider).

alex ua’s picture

Status: Active » Fixed

I got rid of the parsing error in the dev version, but emaudio still does not work.

reikiman’s picture

The current tarball available for download has this parsing error... as a temporary workaround I'm restoring the alpha2 version of this file. I suppose you're saying that the HEAD emaudio doesn't work and you can't mark a new alpha4 tag?

Marat’s picture

I got the same Parse error: syntax error, unexpected ',' in drupal\sites\all\modules\emfield\contrib\emaudio\providers\podomatic.inc on line 84 I just deleted podomatic.inc!

neocary’s picture

I can concur that it is the 'podomatic.inc' file found in /sites/all/modules/emfield/contrib/emaudio/providers/podomatic.inc
as I am doing a mod by mod install and php upgrade on each to target trouble mods.

greggles’s picture

I think it would be worth doing a new alpha release of emfield just to fix this. An official release should really never a parse error...

With a big module like emfield it can be hard to make sure all files pass the syntax check. One trick I use in this situation is a little bit of command line magic:

find ./ -type f -exec php -l {} \;

Run that at the command line in your module's directory and it will find all files in the subdirectory and then run the php "lint" checker on the files to confirm that they are syntactically correct.

Some IDEs will provide syntax checking and show problems in the code navigation tree (Eclipse, for example) which also makes this easier to manage.

alex ua’s picture

Hey greggles- thanks for the tip! I'll give it a shot.

The weird thing here is that I set the compatibility for emaudio to 5.x, in an attempt to prevent people from even using the module, which isn't working at the moment anyway.

Either way, I'll try and roll an update later today or early tomorrow.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.