Every thing is right on the repository… try to download it again… I just cant say much…
apparently, it only happens when you run on local with wamp and other…
I did not succeed to resolve it…
Have you tried to change the end of line in order to be the Windows way ?
Similar problem on a LAMP box:
Parse error: syntax error, unexpected $end in /srv/www/htdocs/cisweb/wordpress/wp-content/plugins/frontpage-slideshow/frontpage-slideshow.php on line 662
on lamp ??? u sure ?? on linux ? hum… maybe some trouble with php ? dont thing so but who knows ?
I just committed a new release : try this one and let me know if the problems are still there…
Just used WordPress’ automatic plug-in installation to delete then re-install Frontpage-Slideshow version .6. When I tried to activate it, I still received the following:
Plugin could not be activated because it triggered a fatal error.
Parse error: syntax error, unexpected $end in /srv/www/htdocs/cisweb/wordpress/wp-content/plugins/frontpage-slideshow/frontpage-slideshow.php on line 767
My system is:
WordPress 2.8.4
SUSE Linux
Apache/2.2.10
MySQL 5.0.67
PHP Version 5.2.6
I suspect there is a problem with all the PHP short tags used in your code. I’m checking with an administrator of my system to check it out.
Tried enabling short tags in php.ini with
short_open_tag = on
but I got the same error message. Incidentally, in php.ini it states:
; Using short tags is discouraged when developing code meant for redistribution
; since short tags may not be supported on the target server.
So you may want to convert your short tags to regular ones.
Hold on! I did not properly enable short tags before. When I checked a second time and then enabled them properly, Frontpage-Slideshow DID activate!
Mystery solved.
Okay thanks : its just a bad habit… will be corrected on next release
Note : the short tag IS the regular one… le full tag has been added in order to clean some doubts when using multiple languages… but who is using multiple languages into the same script (and which server is supporting that)… in my opignon : its is ont of the most stupid thing about php… anyway…
This bad behavior is corrected by now (since version 0.6.1)
Could you please change the topic status to “resolved” ?
