Posted 1 year ago #
My host (Joyent) seems to have issues with this plugin after I moved over to their new servers running PHP5. At issue appears to be the differing use of the full <?php versus <?. For whatever reason (I'm a programmer, but do not keep up with such things), not using <?php causes the plugin to load as plain text and therefore is not parsed.
Simply replacing all <? with <?php fixed the issue. Hope this helps anyone who comes across it.
Posted 1 year ago #
This gives me a chance to link to the WordPress coding standards (and best practices), for those who might need to read up on them:
Posted 1 year ago #
Here's the reference to short tags and why it's causing mine to fail.
http://www.php.net/manual/en/ini.core.php#ini.short-open-tag
Posted 1 year ago #
Version 1.3.2 fixed this -- it has been uploaded to the Plugin Directory.
@yearginsm: I hope this works for you now.
@Kafkaesqui: thanks for pointing me to the solution. I didn't know about the Wordpress coding standards and will try and apply them to all my plugins.
This topic has been closed to new replies.
