Right now, the defaults are hard-coded in dashboard.defaults.inc. This is bad, but not too high priority.

Comments

agentrickard’s picture

This is where the 'presets' or 'defaults' implementation of hook_dashboard() comes in, I think.

drumm’s picture

Every dashboard instance will want defaults. We shouldn't require two dashboards to be defined for every dashboard, the defaults should come for free.

agentrickard’s picture

Hm. In the MySite world I did this by storing defaults under user 0.

But here, I think we can use Presets or defaults in this manner, as the defaults UI would have a secondary argument to specify "for which dashboard this is the default."

Otherwise, we need a default dashboard path in the menu.

devoncrouse’s picture

Any more thought to this? As a user, I'm trying to set a static dashboard page for all authenticated users and am running into problems. Please let me know if a solution exists - I'm not finding one so far. Thanks!

Anonymous’s picture

Defaults have been moved out of a hard coded set into an administrative page.

Anonymous’s picture

Right now, by default, the comments block should be showing for users. I will be adding back in the admin page for defaults soon.

M

snorkers’s picture

Version: 6.x-2.0 » 6.x-1.x-dev
Priority: Normal » Minor

Deleted comment

Michelle’s picture

Seems like this should have more than minor priority. I'm new to trying out dashboard so forgive me if I'm missing something but isn't this pretty key functionality? Every site that uses Dashboard is going to want to have their own defaults set, including drupal.org. I'd be surprised if anyone wants to start their users out with a (nearly) empty dashboard. In my case, starting out with the comments block is actually worse since I use Node Comments.

Michelle

snorkers’s picture

Assigned: » Unassigned
Priority: Minor » Normal

Deleted this comment

Anonymous’s picture

Version: 6.x-1.x-dev » 6.x-2.0
Assigned: Unassigned »

How about we don't change the priorities on this issue. I am trying to reserve higher priorities for things are are broken or do not already exist.

The code for default dashboards is already in the module and just needs to be turned back on. This does not warrant a higher priority.

M

Michelle’s picture

@techsoldaten: If it just needs to be turned on, could you give us a hint where to turn it on? I'm excited about using Dashboard but presenting my users with a blank page and saying, "Here you go, customize it" is an exercise in futility. Without a default dashboard, there's no point in me even installing this on my production site. I suspect this is the case for many people, hence my suggestion that this is more than a minor issue but I won't mess with the priority you've decided on.

Michelle

snorkers’s picture

Priority: Normal » Minor

Edit

Deleted entire comment after being contacted by @techsoldaten off forum

Anonymous’s picture

Priority: Minor » Normal

@snorkers, I have a dim view of complaints about perceived values in arbitrary priority systems, and object to wasting time going back and forth on qualitative rankings possessing little meaning in the real world.

Since you feel so strongly about it, bumping this up to normal at your insistance. Be advised that I am addressing minor issues before getting back into the normal and critical queues.

@michelle, we removed the callback from admin/settings/dashboard/default for one reason or another. I will add that back in after I get back into it and will want some help testing. There is likely to be some minor issue with the way defaults work, I just can't remember exactly what it is (but probably already fixed it). This should happen tonight, I am getting a 2.0-dev release ready.

Hugs,
M

Michelle’s picture

@techsoldaten: That sounds good. To be honest, I couldn't care less what the priority is set to; my only concern was that this wasn't relegated to a "get to it some day" list. Not that I have any right to tell you where to prioritize it since I'm not doing the programming. :) But knowing where you stand on this issue helps me form my own long term plans on whether or not this module will be usable by non geek site members.

I'm going to be out of town this weekend but intend to dive into revamping the whole log in / home page / dashboard aspect of my site next week so will likely have feedback for you then. I think this module has great potential for social networking sites and can't wait to really dig into it beyond the quick look I had on my dev site.

Michelle

Anonymous’s picture

Version: 6.x-1.x-dev » 6.x-2.0
Assigned: Unassigned »
Priority: Minor » Normal

Just a heads up - next week's release of dashboard will support this feature.

M

Michelle’s picture

techsoldaten++ :)

Michelle

drumm’s picture

Where is development of this happening? I'd like to see CVS commits and issues updated on Drupal.org as things happen.

Anonymous’s picture

It's all in Trellon's svn repository right now.

There are reasons for this, ping me in IRC to discuss.

M

rickvug’s picture

I'm curious about how this will be implemented. It would be really nice to have the configuration saved in an exportable format via cTools for integration with Features module.

ManyNancy’s picture

Can you post the link to the svn repo?

ChrisMiller627’s picture

There is an implementation of default dashboards released to the dev branch. You can now easily create default widgets from blocks in a new admin screen, and set the preset in the general screen. take a look!

fatfish’s picture

Dev version was not workin right for me (but maybe I did not upgrade carefully)
Anyhow, I found up we can use real default deshboard settings from dashboard_default by rewriting dashboard.default.inc

function dashboard_defaults($uid) {
    $page = array(
        'uid' => $uid,
        'path' => 'dashboard',
        'weight' => 0,
        'title' => 'Dashboard',
    );
    drupal_write_record('dashboard_page', $page);
    $result = db_query("SELECT id, widget_type, subtype, conf FROM {dashboard_default}");
    while ($item = db_fetch_object($result)) {
        $widget =
                array(
                    'widget_id' => $item->id,
                    'page_id' => $page['page_id'],
                    'type' => $item->widget_type,
                    'subtype' => $item->subtype,
                    'col' => $item->id % 2,
                    'weight' => $item->id,
                    'conf' => $item->conf,
        );
        drupal_write_record('dashboard_widget', $widget);
    }
}

Sorry for not providing a patch but that's a quick one

plopesc’s picture

Assigned: » agentrickard
Issue summary: View changes
Status: Active » Closed (won't fix)