Yeah, I had the same problem. Here’s the error it gave:
Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in blahblahwordpresssite/wp-content/plugins/secure-wordpress/secure-wordpress.php on line 99
what do you have for an php-version?
My server’s running php version 5.2.14.
I am having the same issue on a number of blog installs…running php v. 5.2.9
Same issue for me – with same error string. ISP had to back-up my site from before the update. Would love to know when its stable so I can reinstall?
Actually, for me, it didn’t crash my sites but it will not activate after install or other activation attempts.
Please can you test the version in the trunk (http://downloads.wordpress.org/plugin/secure-wordpress.zip), i have change from public to var this variable and i hope this works in your php-configuration? Thanks for reply!
@frank — That version appears to be working fine for me!
@wes: thanks! i will upload the update and hope this works also on the other php-version. The new feature from the plugin is nice; remove now also the WP version on scripts- and styles-urls.
If needs test the new version, backup your data first.
@frank — No problem! Thank you for working up a fix so quickly. 🙂
@digtwitter — Good advice, though I don’t think the plugin permanently alters anything. When I initially had problems with it, I just deactivated it and everything was fine.
Ok, so now I’m completely screwed. I’m getting the same message and I have no idea how to recover!
Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in blahblahwordpresssite/wp-content/plugins/secure-wordpress/secure-wordpress.php on line 99
OMFG this is causing me all kinds of stomach ulcers, help please!!
please use 1.0.6 and check, if you have PHP5.
I just asked my ISP to switch to PHP5 (it was indeed on PHP4.x, looks like it defaulted to that when I first set it up a few years ago), but it’ll take up to 24 hours before it’s effective. Not sure what to do before then. I hope it’ll automagically fix it, but if not…can anyone create a step-by-step process where I can go through to fix this issue via FTP (by editing some files)?
Thanks.
you can deactivate the plugin; easy via FTP when you rename or delete the folder of the plugin or the plguin-core-file in the folder secure-wordpress.
