Just wanted to follow-up: Mujahed/ModulesBakery was able to help me with #2 and did a great job all around. Would definitely recommend ModulesBakery if you are looking for a developer.
Maybe it would be ideal to have a setting in the Plugin that would allow you to enable/disable each independently.
[x] Ticket System
[x] Knowledge Base
The passwords are lost either way, as the encryption key in each of your /config/blesta.php config files is likely different. Copying them from phpMyAdmin will not work.
I'm aware of this design limitation for plugins. It's something we'll need to discuss internally. In the meantime, I'm going to move this to the Feature Requests forum.
Unless you can confirm that the email address belongs to a valid domain when you encountered that error, I would chalk this one up to normal behavior. As Paul already mentioned, an email address must both be in a valid format, and pass a DNS lookup.
There usually are updates to view files with upgrades. Only you know what modifications you've made, so you need to do file comparisons to check and merge any necessary changes.
http://www.blesta.com/forums/index.php?/topic/3820-knowledgebase-not-shown-after-upgrade-from-33/?p=28110
He means the the Blesta cache. In your installation go to the cache folder remove the 1 folder.
If you prefer you can re-save your staff group if you can access that page.
Or you can use a plugin if you have one installed like admin tools.
Try clearing the cache. Go to Settings > System > Staff > Staff Groups. Edit your staff group and simply save it.
Extensions are upgraded automatically in most cases when running an /admin/upgrade
i believe domain manager refactor is more important than the Mass mailer. because the mass mailer can be done witb a plugin and a good dev can do it , but domain refactor , need core files to be changed and this is the priority to do .
Did you add it to the portal? Did you enable permissions for your staff group?
{% if plugins.support_manager.enabled %}<div class="col-md-4 col-sm-6 portal-box">
<a href="{client_url}plugin/support_manager/client_tickets/add/">
<div class="well">
<i class="fa fa-ticket fa-4x"></i>
<h4>Support</h4>
<p>Looking for help? You can open a trouble ticket here.</p>
</div>
</a>
</div>
<div class="col-md-4 col-sm-6 portal-box">
<a href="{client_url}plugin/support_manager/knowledgebase/">
<div class="well">
<i class="fa fa-info fa-4x"></i>
<h4>Knowledge Base</h4>
<p>Have a question? Search the knowledge base for an answer.</p>
</div>
</a>
</div>{% endif %}
Client/Contact 2FA will use the QR code method. We recommend using the Google Authenticator app for Android/IOS. This keeps it simple for clients, it's free TOTP, easy to set up, difficult to get locked out. The 2FA requests a token before it will be saved.