Does anyone have group emails working for users?

💬 General Discussion
43

Its not enabled by default. In admin check visible subpanels. Make sure its visible.

image
image732×846 68.3 KB

44

Aha and duh again!

Thank you so much again for what you did with the email groups fix. I know how much time goes in to researching this stuff. I have spent hundreds of hours on SuiteCRM and still get hung up on the simplest of things sometimes.

Now all I need to do is work out why my logo image has suddenly stopped working in my emails. But that’s another topic.

Cheers
Terry

45

Let me if it’s working for you. I’ve tried on like 3 different installations and it worked great. Just want to make sure.

46

Hi Paul

Somehow I missed this post. Yes it all works great thank you.

I’m now embarking on a mission to get rid of some of the persistent errors in suitecrm.log after sending emails.

Regards
Terry

47

@pstevens did you see this PR?

I thought I’d warn you, in case it overlaps with what you did.

1 Like
48

Seems like I hit this mess of an issue too.

(I’ve mentioned it here:

and here

Group mail only display on system admin users. Not on the regular users. :sob:

Is there a compiled step by step guide over how to fix this available?

All this code spread all over posts in this thread makes it quite messy to figure it out (I don´t mean that in disrespectful way. The job done is really fantastic!), but it for me and other users it might make it bit complicated to apply this fix to the system.

(It seems like a bit a pain also because once you make these changes you will have to re-add them on each update, right?)

Out of sheer my own curiosity
How come the SuiteCRM team/ Sales Agility team has not fixed this in the updates and added the code that fixes this bug/problem? :thinking:

49

Check the link to the Github issue. I have a step by step guide there with a link to every PR required.

1 Like
50

Hi @PowerQuest, what’s the goal you’re looking for?
Do you need to make different Users to use the same email account ie. sales@acme.com?

51

Here’s the complete solution on Github. Hopefully it still all works with the latest version: Folder Selection for Group Inbound email Folders not working in user Profile · Issue #277 · salesagility/SuiteCRM-Core · GitHub

52

Hi Paul, I applied your fixes some months ago with full success. However I have also just noticed that group inboxes aren’t available for users in SCRM 7.14.2

Does this mean your fixes have not been applied to the v7 updates? So the only way to get this working again is to go through the same fixes you kindly posted on github?

Why are these fixes you spent hours on not being implementd by the Suitecrm team?

53

I guess this has not been merged in yet!
If so, would it be possible to combine all PRs into one PR, on the hotfix branch of the 7.x repo? It should be easier for SA to test and merge into 7.x and 8.x.

54

Thanks for the question @LionSolution and your reply.

I just want all of the sales staff employees to:
1.) be able to monitor our main email on our website hello@companyname.com (Group email account) and send from it - plus

2.) I want them to be have their own individual email too (for account managers), so they can mail their prospects.

But as I already mentioned the Group mail refuses to be available for non sys admin users (E.g. regular users).

55

Thanks a bunch @pstevens

So once applied you will have to re-apply it during each new update as it will be overwritten right?

56

Yes unless the changes get merged into the core, they’ll have to be re applied when updates ate done.

57

Its pretty crazy that this has not applied into the bug fix updates/ the core.

I don’t understand why Sales Agility has not done it as it doesn’t make any logical sense to me.

It must be in their interest to a have fully working product. At least one could think so, right?

Anyways…

So how do you do this yourself?
Do you have a template saved with all the code on your pc or do you sit and copy/paste all the changes needed each time you update your CRM system?

58

Hey @PowerQuest because there are so many changes at the moment around email in the last couple of versions, the best way is go follow the instructions and edit the code manually. It really only takes like half an hour to apply all the changes carefully.

It’s quite complex and there are a number of files to change. I found that by fixing one problem, it lead to another, and then fixing that, led to another. It took me a couple of months to fix from start to finish and figure out why all this stuff wasn’t working and fix them. There are still a couple of remaining issues bust basically it works.

Key is to do all the JS repair and rebuild stuff and flush out your cache in your browser well for it to work.

1 Like
59

Makes me think if it is worth it? :thinking:

I mean having a group inbox is very nice. But employees could also just use their own email. Just too bad because having a group inbox which allows your sales reps/management monitor your company’s general email address just makes sense.

At least in my way of thinking.

60

@pstevens Any reason not to make these so many changes around email into one PR on github?

61

@chris001 just kind of limited by my Github skills. Not really sure how to make all the changes a single PR. There are quite a lot. All changes kind of have to be done together because one breaks something else and then that fix breaks something else. It took me a couple of months of investigation and testing to root most of it out. I’ll try and do some investigation into how to accomplish that.

62

@pstevens This is an easy one to solve. In order to get all your many changes (across multiple code files) into one PR, you simply modify all the files that need modifying, in your own fork (copy) and in your branch associated with the PR. Github will tell you (or already told you) the name of your branch relating to your PR. Step by step example:

  1. Go to the first file you want to modify, on the SA repo for v7, in the hotfix branch.
  2. Click the pencil icon to start modifying the FIRST file of this all-in-one PR.
  3. Modify the file.
  4. Make note of the name of YOUR fork’s branch name (something like pstevens-029) this is located at the top of the page.
  5. Click Save to save this modified file to your fork/branch.
  6. Create the PR, title it “Fix #xxxxx (that’s the issue number) Group Email not working (exact title of the issue number)” .
  7. Go to YOUR fork (github dot come user pstevens, your copy of the Suite 7 forked repo, go to YOUR branch name pstevens-029 from step 4 above).
  8. Edit and Save ALL the OTHER files that need fixing, to solve this Group Emails Not Working issue.
  9. Go to your PR, in the SA repo, from step 6 above. Verify that ALL of these fixed files automatically have shown up as part of your one PR.
  10. Any further mods or updates to these files, super easy. Go to your github account, edit go to YOUR fork of Suite v7, go to YOUR branch pstevens-029, edit the files, and they automatically appear in your PR in SA’s repo. Awesome!
2 Likes