You are here
GregoryLMartin - Wed, 2013/02/27 - 18:11
In the Password Management section, there are pulldowns to choose Email templates for Sending Initial Password to new users and for sending a user a Reset Password Email.
Both of these are blank to begin with, but some "canned" choices are available via the pulldown.
However, choosing those Templates and then clicking the Save button has no effect. When returning to this configuration page, both pulldowns are again showing the "None" choice that was there originally.
As a result, we are unable to add users and unable to retrieve lost passwords.
Please help.
Forum:
SugarCRM Community Edition (Version 6.5.2 - Build 8410)
We built the server using the Turnkey Linux AMI from the Amazon Marketplace in AWS. I call that "self hosted", but not sure how you would classify it.
So this seems like a bug in SugarCRM 6.5.2?
Is that right? If so then perhaps we need to get the TKL guys to consider upgrading the SugarCRM version included in the SugarCRM appliance!?
Generally versions of software are not updated in TKL versions but they may make an exception?
We'll need to get in quick though because I know the TKL guys are currently working on a final 12.1 bugfix/update release (prior to moving development to v13).
SugarCE Admin Settings Won't Stick
I can confirm the same behavior (SugarCE 6.5.3 Build 8410). Neither the Enable System-Generated Passwords check box will stay uncheck nor will the email template choice stay selected from the dropdown menu.
As for the log suggestion - same problem occurs when trying to set the logging level to something other than fatal. That is, when you re-open the page, the log level has automagically been reset to fatal.
UPDATE
This is a permission problem but I hit it with a large hammer so I have no refined suggestions.
Since it seemed to me to be acting like a write-forbidden problem, I chown -R on /var/www/sugarcrm from root:root to www-data:www-data. Then reloaded apache2 for good measure.
Now the change in password enable and email link stays when changed, so too does the logging level.
btw - thanks to all for your efforts
SugarCRM Password Management
Its upto the software of sugarCRM which is defintly based upon the log server that drive the information, that create valuable data
Cloudways provide you a platform for managed hosting services with wordpress, Alfresco cloud hosting,joomla and other hosting service
Great post
Thanks for contributing. It might actually be a good idea to add this to the appliance.
Yes I agree, it is not ideal
However, the appliances are generally configured for maximum security (ideal). Unfortunately in some cases this messes with functionality (not ideal). So it is always a trade-off between security and usability.
When an appliance is developed, often the TKL core devs are not totally familiar with the software, so they use installation documents provided by upstream and then on top of that use a 'best practice' security model. Sometimes 'best practice' security means that the webserver account doesn't have write privileges to areas that it might need to provide maximum usability/functionality. So whilst in a perfect world each upstream software would clearly document 'best balance' between security and usability/full functionality, that isn't always the case. Sometimes, even when upstream does document this (as it seems SugarCRM do - as linked to by Nate) the devs don't see it...
So this leaves TKL to take a 'best guess'. All the appliances are tested prior to release, but not always all possible functionality (as you could imagine testing every possible option in every single appliance would take forever...). So if there is ever any doubt, we always err on the side of caution.
This approach sometimes means that permissions (or other minor factors) are not always quite perfect. But we figure that rather than spending heaps of time researching each piece of software (too time consuming for our available resources) and testing each release totally exhaustively (pragmatically impossible), we rely on end users like yourself to assist in this regard.
Once we know what needs to be tweaked, we can ponder that and decide the best course of action. Generally that will result in the next release of the appliance containing said fix...
FWIW though I'm really glad you posted, because I had forgotten about it and have only added it to the TKL Issue tracker!
Still a continued problem
I just downloaded the VMWARE version of SugarCRM and it continues to have this exact problem.
Thanks for reporting
This has actually been fixed in the source code (see here) but the new appliance has not yet been released. Soon hopefully...
Add new comment