Looking at http://drupal.org/project/usage/uc_signup, I'd like to copy and paste this data into a spreadsheet and sort by date, but I can't do that because there's no year information exposed.

Looking at http://drupalcode.org/project/project.git/blob/HEAD:/usage/includes/page... , this can be changed by doing something like:

variable_set('project_usage_date_short', 'F jS, Y');

for something like "January 1st, 2011"

This would make it easier for me to play with this data.

Thanks!

Comments

ezra-g’s picture

ezra-g commented

Specifically, I'm looking at this line of code 'data' => format_date($week, 'custom', variable_get('project_usage_date_short', PROJECT_USAGE_DATE_SHORT), 0),

ezra-g’s picture

ezra-g commented

I marked #1242968: Show year in usage statistics next to month and day as a duplicate.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Needs work

I did this via drush @do vset project_usage_date_short 'F jS, Y'

but it hasn't changed anything. Maybe those tables are cached?

dww’s picture

dww
we/he/they
commented

Those tables are heavily cached in {cache_project_usage}, which in turn lives in memcache on d.o...

This code already exists:

function project_usage_flush_caches() {
  return array('cache_project_usage');
}

so in theory drush knows how to flush this cache...

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

I assumed the cache would get flushed as the report was rebuilt this weekend.

It seems that this affects the header rows in http://drupal.org/project/usage/ but not the leading row on http://drupal.org/project/usage/uc_signup

I think we should probably revert this change and someone will need to work on a patch that adds what Ezra wanted and then we can do any appropriate vsets after that patch has been deployed.

dww’s picture

dww
we/he/they
commented
Project: Drupal.org infrastructure » Project
Version: » 6.x-1.x-dev
Component: Drupal.org module » Usage statistics
Category: feature » bug
Status: Needs work » Active

Whoops, yeah. Lame. Seems like a project_usage display bug that that variable isn't consistently used. I don't have time to investigate now, but moving to a more appropriate queue.

ezra-g’s picture

ezra-g commented

I filed #1401736: Requesting drupal.org dev site for project usage so that I can help work on this issue.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

For the record, Bdragon is the one who fixed this by "messing with project_usage_date_long as well as project_usage_date_short, IIRC"

bdragon’s picture

bdragon commented
Status: Active » Closed (works as designed)

There are two variables. I say this is working as designed.

bdragon’s picture

bdragon commented
Issue summary: View changes

fixing typo