Closed (fixed)
Project:
Commerce Reporting
Version:
7.x-4.x-dev
Component:
Tax Reports
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
7 Oct 2015 at 15:54 UTC
Updated:
21 Oct 2016 at 17:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
mglamanMarking to major. The tax module never required main module as dependency, and I kind of liked that (I think more people use that than main reports.) Thanks for identifying this.
Comment #3
xurizaemonRan into this, here's a patch since I'm waiting for a deploy to complete.
This can bite you if you
drush dis commerce_reportsand Commerce Tax Reports starts to have baby fatals a lot.Comment #5
webadpro commentedPatch #3, worked for me also.
Comment #6
dsuess commentedthis update just took down my store. please address!
Comment #7
dylf commentedNot sure if this is the right approach but instead of adding a dependency I added a function that does the same thing in the commerce_reports_tax module.
Comment #8
dylf commentedComment #10
dylf commentedNot sure that the failing test is related to this issue.
Comment #11
mglamanRetested 5.5
Comment #12
splendidles commentedI can report that #3 works, I was able to replicate this one by disabling reports, flushing caches and then viewing the tax report. Provided that the reporter can ensure they did not have commerce_reports at the time, then that looks to be the issue. Patch #3 resolves this. Once commerce_reports is enabled again, the report works and I'm seeing no errors in the logs.
Comment #14
mglamanWorks good enough for me. No idea how to work around it otherwise. People often seem to use the tax submodule more than the normal module anyways.