@kikib – This has been patched and tested in v1.4.7 going out tomorrow, all of those parse errors were caused by a very obscure PHP setting called asp_tags which lets PHP process <% the same as <?php. This was an issue because we use a lot of javascript templates that used <%. We have converted them to another safe format that won’t cause any issues, same format WP core uses so should be good from here on out.
Glad you found a stable version to go back to. Sorry for the issue, with 2 months in public beta this bug never showed up.
@dave_s, @kikib, @probyn – This should be fully resolved now. If you are still having issues please open a new ticket.
Please take a moment to rate and review the plugin and or support once you have updated to the latest version.
