Opened 18 months ago

Closed 16 months ago

Last modified 16 months ago

#3440 closed Bug (fixed)

widget error message "The report 'nb_uniq_pageviews' was requested but it is not available"

Reported by: matt Owned by: capedfuzz
Priority: normal Milestone: 1.10 - Piwik 1.10
Component: Core Keywords:
Cc: Sensitive: no

Description

reported in forum

Error: The report 'nb_uniq_pageviews' was requested but it is not available at this stage. You may also disable the related plugin to avoid this error.

Steps to reproduce
1) Add "Visits overview (with graph)" to dashboard
2) Change metrics to plot to 'pageviews'. Graph refreshes.
3) Reload page

Change History (12)

comment:1 Changed 18 months ago by matt (mattab)

  • Owner set to capedfuzz

Could we avoid this error and fail gracefully, or is the error really not expected?

comment:2 Changed 18 months ago by matt (mattab)

  • Priority changed from normal to major

comment:3 Changed 18 months ago by matt (mattab)

  • Priority changed from major to critical

comment:4 Changed 18 months ago by mrjoops

Here is the trace :

#0 /.../core/Archive/Single.php(181): Piwik_ArchiveProcessing::getPluginBeingProcessed('nb_pageviews')
#1 /.../core/Archive/Single.php(266): Piwik_Archive_Single->prepareArchive()
#2 /.../core/Archive/Single.php(462): Piwik_Archive_Single->get('nb_pageviews', 'numeric')
#3 /.../core/Archive/Single.php(505): Piwik_Archive_Single->getNumeric('nb_pageviews')
#4 /.../plugins/VisitsSummary/API.php(88): Piwik_Archive_Single->getDataTableFromNumeric(Array)
#5 [internal function]: Piwik_VisitsSummary_API->get('359', 'day', 'yesterday', false, Array)
#6 /.../core/API/Proxy.php(190): call_user_func_array(Array, Array)
#7 /.../core/API/Request.php(128): Piwik_API_Proxy->call('Piwik_VisitsSum...', 'get', Array)
#8 /.../plugins/VisitsSummary/Controller.php(98): Piwik_API_Request->process()
#9 /.../plugins/VisitsSummary/Controller.php(129): Piwik_VisitsSummary_Controller::getVisitsSummary()
#10 /.../plugins/VisitsSummary/Controller.php(24): Piwik_VisitsSummary_Controller->setSparklinesAndNumbers(Object(Piwik_View))
#11 [internal function]: Piwik_VisitsSummary_Controller->index()
#12 /.../core/FrontController.php(138): call_user_func_array(Array, Array)
#13 /.../index.php(53): Piwik_FrontController->dispatch()
#14 {main}

comment:5 Changed 17 months ago by capedfuzz (diosmosis)

  • Resolution set to fixed
  • Status changed from new to closed

(In [7500]) Fixes #3440, make sure Actions metrics are associated w/ an Actions report in Piwik_Archive_Single::getRequestedReportFor and make sure Piwik_VisitsSummary_Controller::getVisitsSummary can handle case where Piwik_API_Request returns false.

comment:6 Changed 17 months ago by matt (mattab)

  • Resolution fixed deleted
  • Status changed from closed to reopened

There are metrics in the array that do not belong to the Actions plugin, ie.

		'sum_time_spent',
		'exit_nb_uniq_visitors',
		'exit_nb_visits',
		'sum_daily_exit_nb_uniq_visitors',
		'entry_nb_uniq_visitors',
		'sum_daily_entry_nb_uniq_visitors',
		'entry_nb_visits',
		'entry_nb_actions',
		'entry_sum_visit_length',
		'entry_bounce_count',

Were this added for a reason?

Vote for revert

comment:7 follow-up: Changed 17 months ago by capedfuzz (diosmosis)

They are referenced by Archive.php in the $mappingFromIdToName as actions metrics so I guess I put them in w/ the others. I can see they're not actually archived as numeric metrics, though, by the Actions plugin. I guess I can remove them?

comment:8 in reply to: ↑ 7 Changed 16 months ago by matt (mattab)

Replying to capedfuzz:

They are referenced by Archive.php in the $mappingFromIdToName as actions metrics so I guess I put them in w/ the others. I can see they're not actually archived as numeric metrics, though, by the Actions plugin. I guess I can remove them?

Sounds good to remove them and only put the actions metrics, this would prevent further issues.

comment:9 Changed 16 months ago by capedfuzz (diosmosis)

(In [7621]) Refs #3440, remove non-archived metrics from Piwik_Archive::$actionMetrics.

comment:10 Changed 16 months ago by matt (mattab)

To fix it, maybe could have a test case that used to trigger the error? thoughts?

comment:11 Changed 16 months ago by matt (mattab)

  • Resolution set to fixed
  • Status changed from reopened to closed

Ok, fixed.

comment:12 Changed 16 months ago by matt (mattab)

  • Priority changed from critical to normal
Note: See TracTickets for help on using tickets.