Hey everyone, first off our sincere apologies for any issues the latest upgrade caused. Shortly after the release, we noticed that the SVN push did not include a file that caused the upgrade error (and indirectly you all did as well). We agree it’s not at all the behavior we want out of the plugin and definitely want to make every effort to make things right.
Within minutes of realizing what had happened a patch was issued and fixed the problem. Again, we’re very sorry for any hassle this has caused. If you’re still having issues, we recommend deleting the existing plugin from your FTP and performing a fresh install. If for any reason you continue to have problems please let us know and we’ll be happy to troubleshoot.
Plus one for this, the latest update (2.1.8) has broken our site.
Hey everyone, first off our sincere apologies for any issues the latest upgrade caused. Shortly after the release, we noticed that the SVN push did not include a file that caused the upgrade error (and indirectly you all did as well). We agree it’s not at all the behavior we want out of the plugin and definitely want to make every effort to make things right.
Within minutes of realizing what had happened a patch was issued and fixed the problem. Again, we’re very sorry for any hassle this has caused. If you’re still having issues, we recommend deleting the existing plugin from your FTP and performing a fresh install. If for any reason you continue to have problems please let us know and we’ll be happy to troubleshoot.
Thank you for fixing it!!
Most welcome @timkeen, again our apologies for any hassle – very unusual for SVN to leave out a file like that. We’ll do everything in our power to make sure that doesn’t happen again in the future.
