The old sugarcrm demos on the sugar website

[stevec]

Hi,

A while back, clicking on demo on the sugarcrm website would start an online instance of sugar to play with. However, now, there are only video demos and signups for trials.

The old online demos were really useful for testing for possible bugs we found on our customized instance - if I could replicate it online, then it was a bug in the core code - or an affect of our server installation (caching and compression etc).

Does anyone know if these are still available?

[salesagility]

No ... but there are some online demos at the salesagility site http://salesagility.com/index.php/sugarcrm-demo.html that you are welcome to use

[salesagility]

When I said "No" ... I had actually meant to say that the online demos disappeared some time ago ... they were useful ... but I suppose Marketing knows best

[stevec]

Thanks - I had a look but the advanced search criteria for account list view are the same as the account popup picker criteria - I found a possible bug where when these are different, thy start to overwrite each other.

I guess I might have to install a vanilla copy.

Thanks

[roblaus]

This is actually a bug. But don't ask me where it comes from, we experience this one app. since 5.2. I can't even say when it happens but I suspect after a reorg (quick repair) but not always...

[stevec]

The problem seems to be the 'searchdefs' definition in the various modules' popupdefs.php and listviewdefs.php metadata files overwriting each others' cached templates.

Locally, I got around this by creating custom view.list.php and view.popup.php views that overrode the display function, calling a template cache clear:

        function display(){
        require_once('modules/Administration/QuickRepairAndRebuild.php');
        $selected_actions = Array('clearTpls');
        $modules = Array($this->bean->module_dir);
        $RepairAndClear = new RepairAndClear();
        $RepairAndClear->repairAndClearAll($selected_actions, $modules, $autoexecute = true, $show_output = false);

        parent::display();
        }

However, this is a bit ugly but it's better than running in developer mode.

I'll raise it as a bug again - last time it was resolved as a problem down to customisations.

[roblaus]

Thx for the confirmation. But I am absolutely sure that it has nothing to do with customization (except if they call adding fields or changing searchdefs a customization).

Did you check with 5.5 already? If not I'll have a look these days.

[stevec]

I haven't tried 5.5 - and I'm about to go on vacation for a few days.

I've tried to resurrect the sugar case for it though so fingers crossed.