Thanks for the 7.9.1 upgrade. We really do appreciate all the work. There are still a number of bugs that still leave me dead in the water here. I’ve registered most of them as bug reports in the GIT.
After the upgrade (went without incident) I did a quick repair, synced emails and repaired inbound email account)
Issues so far:
When you go to Activities->Compose Email: there are multiple instances of tinyMCE displayed (See attachment)
There is no “plain text” checkbox in any email compose screen
Checking “Send plain text” in the create/edit email template screen still results in the receiver receiving a html formatted email message
Email template: Insert a variable (Lead > Lead first name) the receivers email will display “$contact_first_name” where the first name should be
No way to select signatures in email compose box
All of the above worked perfectly in 7.8.4. I guess there is no way you guys would consider putting back in the email component from 7.8.4 and leave this new fangled approach to 8.0? It’s pretty buggy.
Add these problems to the email client in our install of 7.9.1
When sending an email based on an email template, the attached FILE that is part of the template is NOT sent
When sending an email based on an email template, the attached DOCUMENT that is part of the template is NOT sent
When attempting to use the Add Document button whilst editing an email the email is SENT on pressing the button
When an email is sent with an attached FILE, 2 COPIES of the file are sent
As the previous poster intimated, this is a HUGE issue for us, is there any way that we can get back to a previously functioning version?
@mpeet normally you would be seeing these problems on a test server, and so you would just delay your decision to upgrade on your production server.
If you are on your production server, the “way back” is the same as for every other server: go back to your backups (or VM snapshot) from before the upgrade.
This is the message you got when you upgraded:
No, I’m honestly sorry if you didn’t do that, like Phil, but face it: you’re in a very complicated situation.
You can forget about “going back” downgrade scripts, they would be a lot of work, extremely hard to test for all the diverse real-world situations, and the (very small and overworked) team obviously needs to spend their time going forward, fixing the bugs, not covering for the accidents leading to lack of backups on some people’s systems.
@philemery: let me try and give you some additional ways of dealing with your current predicament:
Restoring from your least-bad full backup: What is the most recent full database backup that you DO have? Is it a week old, a month old, many months? Sometimes it’s easier to patch the database going forward, than going back. For example, something like this:
make a full backup of your current situation, with your newest data
restore from your old backup. The trick is to restore the database onto a SuiteCRM system at the exact same version that corresponds to the backup
assess exactly what critical data you need to restore from your current data. This is the decisive thing: is it a LOT of diverse stuff, you need, or can you make it with just a few tables?
restore data from those tables one by one, taking care to match the table structure first
Can you use an external mail client? You know, you can use SuiteCRM with Outlook or Gmail, or whatever webmail client you prefer. The only thing you lose by not using the integrated Email, is the ability to link Emails to Accounts, contacts, etc. Can you work around that, at least for a while?
Sticking it out with 7.9.1: many of these bugs will be fixed in a week’s time. Some of them are more critical for work than others. If you keep an eye on Github, you can apply the fixes immediately as they are released. All you need to do is pull them from GitHub, or if that sounds complicated, apply them by hand by changing the changed files. Often it’s just a one-line change. I can help you with this.
Hire a developer to fix the bugs, instead of hiring one to work on MySQL and go back to 7.8.5. If you can get someone smart enough to beat Daniel Samson’s (SalesAgility’s developer) fixing these bugs, or simply to focus on your critical bugs while Daniel has to work on many other things, then you might gain some time here.
A big issue for me (and perhaps some others here) is that 7.9 doesn’t seem to do anything better than 7.8. To be honest, it kinda feels like a step back - as the new theme, although attractive, is not quite as usable.
On 7.8, after I got all the permissions things figured out - it worked perfectly. I’ve looked at so many other CRM’s and this one worked exactly the way I needed it to. I was so friggin productive for a bit there.
I’m not quite sure what benefits this new approach gives the user. It just all seems so much harder to use, and largely broken as far as I can tell.
I really just want to get back to work the way it did in 7.8
This is like when your friend starts going out with that beautiful girl, but he doesn’t’ realize that she’s actually not very nice, perhaps totally bat-crap crazy and just totally bad news all around but just wont see it. The developer seems in love with this new approach even though it doesn’t seem to work very well (at least from this side of the screen). Keep in mind I don’t see the big picture that you’re going for, just as speaking as a user.
Thanks for all the suggestions I do have backups and will/can go back to a previous version, however I will lose some business information that has been added to the CRM since the upgrade and this will need to be manually migrated. I was hoping there may be some type of roll-back script. Apols for my original email being not as exact as it could have been.
I’m with Phil on this one… I think we all live with buggy software on a day to day basis, and we generally accept that. It’s a very difficult task to create and update software that runs on multiple platforms with no problems/bugs. That being the case, I really didn’t expect an update to the email component to be SO broken. The words themselves, update/upgrade, have connotations of moving on to something better…
I, (along with most if not all users) of the software are extremely appreciative of the hard work put in by all contributors/coders, and it being open source, we don’t really have any right to complain. However, the functionality that makes the email client in Suite an attractive, and usable, business solution is/was pretty much ALL broken with this upgrade, it has been rendered pretty much useless for my business. I don’t believe the platform that I’m using is that unique, (Bitnami LAMP stack on Amazon LightSail) and so the number of bugs in a component that was working extremely well for me prior to the upgrade has come as quite a surprise.
I shall obviously have to be far more vigilant with ANY future updates for SuiteCRM and ensure that all of them are run over a devel site prior to implementation on our live site, something I should have done for this update, Starting to feel a bit like the Microsoft update paradigm… I too don’t see the big picture as I am just an end user, however, this experience of an upgrade has not been a good one and can only taint ALL end users views of the usability and stability of open source software