We have a Zapier integration in the works, as of now it can only do basic operations (create contacts, accounts, leads etc). Are there any features in particular you would like the integration to implement?
Please note that you will also need to re-enter your app credentials from manage apps, including your Google integration credentials as the previous cipher used with mcrypt has no analogous cipher in openssl.
You may need to re-generate your encryption.iv and encryption.key files in protected/config. You can do this by deleting these files (the app should then re-create them or you can manually create them by running protected/yiic cryptsetup).
This is strange, I believe we have run into issues with Safari browser users and are currently designing a fix. Would you happen to know which browsers these leads may have been using? Regardless, we are currently testing web forms with different browsers to replicate the issue. I will keep this thread updated with our results.
I would not necessarily use notifications as a critieria for IP ban with fail2ban as the period at which the 'GET /index.php/notifications/get.*' can be configured within the admin panel (you might also inadvertently ban yourself as your browser would be maing the requests). The notification JS is run periodically to retrieve messages such as 'John Doe has opened an email!' etc and display them in the notification box (the box in the upper right corner with blue numbers). However removing them from the apache logs can be a good thing.
On our developer server we use some of the default apache fail2ban jails such as 'apache', 'apache-noscript' and 'apache-overflow'. I don't have any specific filters written out but I would recommend adding a filter for 403 errors on the login page, this should help against bots that are trying to brute force login to your app. The same goes with the API (protect against failed authentications of API).
Regarding the module assignments, we have something in the works to expand user roles such that modules would take these user-created roles into account when determining permissions. Basically there would be more options for module permissions than just 'admin only'.
Regarding the assignments for reports, we have a prototype built already and should have it ready for release early next year.
We apologize for any issues that may have occurred in 7.0 with regards to email and will release a hot-patch very soon. With regard to the XVERP issue, please do the following:
* Whether to use VERP.
* Default is changed to true for bounce handling
* @link http://en.wikipedia.org/wiki/Variable_envelope_return_path
* @link http://www.postfix.org/VERP_README.html Info on VERP
* @var boolean
public $do_verp = false;
as well as in protected/components/phpMailer/class.phpmailer.php:
* Whether to generate VERP addresses on send.
* Default is set to true for bounce handling
* Only applicable when sending via SMTP.
* @link https://en.wikipedia.org/wiki/Variable_envelope_return_path
* @link http://www.postfix.org/VERP_README.html Postfix VERP info
* @var boolean
public $do_verp = false;
We are currently working on the formal roadmap for the product moving forward. We will post a text copy of the roadmap on this forum as well as utilize the Github 'Milestones' feature to convey the upcoming changes.
Thank you for the feedback! We will be releasing a hotfix sometime next week in order to address the 'maxFileSize' issue (thank you Atilla for providing a workaround/fix) as well as the email UI bugs.
The name change from 'Accounts' to 'Company' was added in order to add a proper conversion from a 'Contact' record to an 'Account' record and vice-versa. This change was in the attribute label only so the workflows using the field should still work. However we will address this issue in the hotfix as well in order to keep custom workflows compatible with the changes.
We are currently in the process of updating the Github project. The new changelog will be included in the update.
It appears that this may be a browser issue, we are looking at a few different ways to prevent the auto-fill for unnecessary fields. I will bump this thread with updates as soon as we come to a conclusion.