Teams support

[cordoval]

back in 2006 someone wrote a module for supporting teams on sugarcrm community edition

wonder if there are solutions that can be plugged in into this community edition latest version 6:4+

thanks

[graphics]

Even though he hasn't updated the forge page or announced anywhere that its updated, the updated version for SecuritySuite for 6.4 is out now.

You can find the download here:
http://www.sugarforge.org/frs/downlo...ySuite_250.zip

and it works amazingly!

[graphics]

This is my second time trying to reply within a two days. (mods wth?)

There was an update to SecurityTeams for 6.4 which can be found on sugarforge.

[rosanamesa84]

This is my second time trying to reply within a two days. (mods wth?)

There was an update to SecurityTeams for 6.4 which can be found on sugarforge.

I tried that version, but when I try to upload the system return "The uploaded file is not compatible with this version of Sugar: 6.4.1"

Any ideas?

[graphics]

I tried that version, but when I try to upload the system return "The uploaded file is not compatible with this version of Sugar: 6.4.1"

Any ideas?

Open up the manifest.php and change 6.4 to 6.4.*

*you shouldn't have a problem then.

[Chris_C]

Open up the manifest.php and change 6.4 to 6.4.x

*you shouldn't have a problem then.

Not sure, but isn't it 6.4.* ?

[graphics]

Not sure, but isn't it 6.4.* ?

you are correct, i must of hit enter then put the asterisk... Mornings.... ughh.....

[eggsurplus]

Thanks graphics for the kind words!

Just a heads up, just changing the manifest.php version is not the way to go which is why there is a warning in that file to not do so. Because of the nature of the beast this module is not upgrade safe and requires numerous core file changes so the version you need is tightly coupled with the version of Sugar you are on. For example, if you just change the manifest of a 6.4 version to 6.4.1 it will overwrite your Sugar install with the 6.4 version of data/SugarBean.php (among many other files). This will mean bug fixes, enhancements, etc from 6.4.1 will be lost and it may cause compatibility issues as you'll have 6.4 version files interacting with 6.4.1 files. Sometimes it works out but it is better to be safe.

-Jason

[graphics]

Thanks graphics for the kind words!

-Jason

No problem, your module is easily the best written ones out there and a personal favorite!

Well put and your absolutely correct. I'm so used to phpBB coding, We can usually get away with making one or two relative changes. I'm learning that Sugar is.... well.... like you put, a BEAST! lol

[Chris_C]

Thanks graphics for the kind words!

Just a heads up, just changing the manifest.php version is not the way to go which is why there is a warning in that file to not do so. Because of the nature of the beast this module is not upgrade safe and requires numerous core file changes so the version you need is tightly coupled with the version of Sugar you are on. For example, if you just change the manifest of a 6.4 version to 6.4.1 it will overwrite your Sugar install with the 6.4 version of data/SugarBean.php (among many other files). This will mean bug fixes, enhancements, etc from 6.4.1 will be lost and it may cause compatibility issues as you'll have 6.4 version files interacting with 6.4.1 files. Sometimes it works out but it is better to be safe.

-Jason

Big question for you Jason - first let me say I like your module and your enthusiasm in developing it - the question is, what additional "hooks" or "attachment points" would need to be added to Sugar, in order to make your module upgrade-safe ?