Why is CiviReport not showing up as an installed module?

[carpenter]

Is there a beta?

[Donald Lobo]

no

but there is a demo at: http://reportsandbox.civicrm.org/

login as demo/demo

and then goto:

http://reportsandbox.civicrm.org/civicrm/report/template/list?reset=1

if you are a developer you can install from svn, the branch is at:

http://svn.civicrm.org/civicrm/branches/v2.2.report/

lobo

[Tekas]

Hello,

I'd like to install CiviReport from svn but the directory is absent?

I also try to watch the demo but I get an Access denied page.

Can you help?

Thanks

[Tekas]

Sorry, I get to see the CiviReport pages via the menu.

The problem now is the svn directory named v2.2report that I can't see.

Thanks

[Dave Greenberg]

CiviReport has now been merged into the 2.2 branch in svn - so you can get all the code there. We expect to be releasing 2.2.7 (tarballs etc.) sometime next week - which will include CiviReport!

[bsorgi]

Hi Guys- I've upgraded to 2.2.7 and still do not see CiviReport as a component to enable, or as a entry in drupal permissions to enter... any advice?

[Dave Greenberg]

Since CiviReport is part of "core" you don't need to enable it (doesn't show up as a separate component in Enable Components). However, you definitely should see new permissions under Drupal >> Administer >> User >> Permissions:

- access CiviReport (which "turns on" the menu item in our menu block)
- administer CiviReport
- access Report Criteria

If you're not seeing those, make sure you completed the upgrade steps (including running civicrm/upgrade to upgrade your DB):
http://wiki.civicrm.org/confluence/display/CRMDOC/Upgrade+Drupal+Sites+to+2.2

[bsorgi]

Hi Dave, I followed the instructions exactly when upgrading CiviCRM to version 2.2.7 and it is still not showing up.

[Deepak Srivastava]

bsorgi,

1. Do you see those permissions mentioned by dave ?
2. Can you go through your db and see if civicrm_report_instance table is present ?
3. In the db again, whats the value set for version column of civicrm_domain table ?

[bails]

Hi I have this problem as well no civicrm_report_instance table in the database, civicrm_domain version returns NULL and no permissions for reports in the matrix.

I should mention that when i went to domain/civicrm/upgrade?reset=1 and chose to upgrade I was presented with an error message stating I was already running civicrm-2.2.

I was running CiviCRM-2.2.3 previously.

[Deepak Srivastava]

bails / bsorgi,

If u running from svn, everytime there is a new release and you do an update -
1. You also need to update civicrm-version.txt file before you fire the upgrade process. This file informs the current code version to upgrade process.
2. Make sure civicrm_domain.version is set to correct older version i.e the version your current db state is in. This generally don't have to be touched if correct db version is indicated.

For now if you are fully updated, edit civicrm-version.txt file to change the text to "2.2.7 Drupal PHP5" (for drupal) and then fire the upgrade and check.

[bsorgi]

Hi Deepack,

As in one of my earlier posts, there is no CiviReport option in drupal permissions... I am not installing from the SVN.

CiviCRM says it is running Version 2.2.7 although the database is definitely not. There are no instances of the report tables. The text file civicrm-version.txt was updated to the correct version before the upgrade process. Every time I have upgraded from 2.2 I always get a green box stating database is already running whatever new version I had been upgrading to.

In the database, it indicates I am running version 2.11.

[Dave Greenberg]

Bails / Bsorgi
So the DB upgrades are not getting run since the upgrade code thinks you're already on the "current" release. Just checked the code, and it gives you that message if the version in your DB is >= version of codebase you've just downloaded (i.e the one you are upgrading to).  Looks like this is a bug introduced when we first transitioned to the incremental automated upgrades - and we're looking at a fix for the code.

In the meantime - we need to ascertain exactly what version your DB is on so we can reset the DB version and get the updates to run properly. Can you both send a dump of your current database to Deepak on our team. He'll verify version and test proper upgrade.

deepak at webaccess dot co dot in

[bsorgi]

Sent.


Thanks a bunch.

[Eman0684]

Ok...I also tried to install latest version from SVN and have been having a host of problems.
1: the v2.2report branch didn't exist, so I just got v2.2 from svn.
2: v2.2 from svn always caused fatal error (Failed opening required  'CRM/Core/DAO/Domain.php')
3: So I took some files from v2.2 that I got from svn with working version then tried to run update  - didn't work since it said I already had version 2.2.5 running (changed it to 2.2.7)
and upgrade worked. CiviReport showed up in components list, but enabling it didn't create a menu entry but just an empty fieldset on the Administer CiviCRM page
4: Dowloaded v2.2.7 and uploaded it, then ran update - this said I was already running 2.2.7, so I changed to 2.2.8
5: This seemed to work, even created menu entry, until I clicked on CiviReport menu entry, then I got:"Fatal error: Call to undefined method CRM_Core_Option Group::getrowvalues(..."
6: I copied Option_Group.php from v2.2 I got from svn, since 2.2.7 didn't have it.
7: Now I get: "Fatal error: require_once() [function.require]: Failed opening required 'CRM/Report/DAO/Instance.php'" (and I checked, there is no DAO folder in CRM/Report).

What can I do now?