After a fresh install on Pantheon all CiviCRM menu items link to a "Page not found"

I have a previous installation of CiviCRM Starter Kit that works. It has a very different Resource URL:
PREVIOUS INSTALL gotpantheon.com/profiles/civicrm_starterkit/modules/civicrm/
LATEST INSTALL gotpantheon.com/profiles/civicrm_starterkit/modules/civicrm/install/index.php//profiles/civicrm_starterkit/modules/civicrm

I also has a very different Civicrm.setting.php with a bunch of Pantheon systems settings.

Is anyone else hitting this problem?

CommentFileSizeAuthor
#1 Screen Shot 2013-05-21 at 2.55.27 AM.png781.16 KBkreynen
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

kreynen’s picture

Version: 7.x-3.3-rc3 » 7.x-3.3
FileSize
781.16 KB

This is fixed in the 3.3 release which should be showing up on Pantheon now, but it won't fix the civicrm.settings.php file created on install. The Pantheon specific code in the civicrm.settings.php is added by patching the civicrm.settings.tpl #1978142: Include Pantheon settings in civicrm.settings.tpl

This was a caused by a combination of a mistake I make while trying to automate the process of updating the Pantheon install automatically when a new release is packaged on Drupal.org and a change in the tags Drupal.org allows in the releases.

Until yesterday?, Drupal.org allowed alpha, beta, and rc tags on point releases like 3.3-rc3. I was using the 3.3 to keep track of the version of CiviCRM included and the rc3 to track new packages for that release. So when Features pushed both features and security update when moving from 2.0-beta2 to 2.0-rc1, I tried to package 3.3-rc4. I wasn't showing up in the list of releases I could package, I thought it was just lag in Drupal.org pulling updates from Git because of DrupalCon. After several hours, it still wasn't showing up so I started looking into what was happening.

mallezie’s picture

Priority: Normal » Major

I assume the civicrm.settings file is 'by design' to work on pantheon.

I can still confirm, that a fresh pantheon install has broken menu links.

If you check out the Resource URL page http://civicrm.pantheonurl.com/civicrm/admin/setting/url?reset=1

These are defined as:
CiviCRM Resource URL:
http://civicrm.pantheonurl.com/profiles/civicrm_starterkit/modules/civic...
Image Upload URL:
http://civicrm.pantheonurl.com/profiles/civicrm_starterkit/modules/civic...

If we check the 'Cleanup Caches and Update Paths': http://civicrm.pantheonurl.com/civicrm/admin/setting/updateConfigBackend...

We could use this to change the base url: wich should fix the problem:
Old Base URL: http://civicrm.pantheonurl.com//profiles/civicrm_starterkit/modules/civi...
to New Base URL: http://civicrm.pantheonurl.com/profiles/civicrm_starterkit/modules/civicrm/

However, the submit action for this form, links to a wrong path, caused by the wrong base path we are trying to fix ;-)
Page not found: "/profiles/civicrm_starterkit/modules/civicrm/install/index.php/civicrm/admin/setting/updateConfigBackend" cannot be found.
However this actually makes civicrm not usable, and not repairable.
Therefore i'm raising priority to major.
If there are any tests i could do, i'm glad to help.

kreynen’s picture

Version: 7.x-3.3 » 7.x-4.3-rc1
Status: Active » Needs review

The was fixed in later releases of the 3.x branch, but after tagging a releasing 3.3 that was the only "supported" release could be 3.3. Didn't matter how much newer a rcX release was, 3.3 trumped it. I tried to get that deleted #2001816: Please delete the 3.3 release for CiviCRM Starter Kit so I could continue using the -rc tags, but for some reason that wasn't possible even though 3.3 included a version of Webform with a security issues.

So now I've restarted the numbering with 7.x-4.3-rc1 where 4.3 indicated that the kit includes the latest version of CiviCRM 4.3. I've started a page of documentation about how to update the .make files used to build the CiviCRM Starter Kit distribution. I really need to find some co-maintainers for this since I can't always drop what I'm doing and respond to these issues.

If managing the patches and .make files makes sense to you can you have time to help with this, please let me know.

mallezie’s picture

Status: Needs review » Fixed

Thanks, this update seems indeed to fix the base-url. (i've just tested)
Therefore closing issue.

Not quite sure if i have time to help, i'll try to triage the queue for now, and i'm willing to add some documentation.
We're starting a big Civicrm project on work, and if we're going with pantheon, and therefore this starterkit, perhaps i could also help with patches, and make file. I'll keep you updated on that.

Greetings

kreynen’s picture

@mallezie The testing of new Pantheon installs is the most time consuming part of this. This was only an issue because of my attempts to automate pushing the "supported", packaged Drupal.org release to Pantheon. The install shouldn't be an issue again until 4.4.

I really see get https://drupal.org/project/features_civicrm get to a stable release so it can be included in this. Unfortunately I don't have any bandwidth left to help with that :(

My CiviCRM for Developers, Site Builders, and Themers sessions for DrupalCamp Austin was approve later this month. I've proposed the same session for DrupalCamp Colorado the following week.

I'm going to keep pushing both Pantheon and Features CiviCRM, but obviously we need more people to step up and help with both.

mallezie’s picture

i don't mind testing the pantheon installs, i'm glad to take part in this piece.

Please don't include features_civicrm in pantheon, it's far from stable, it's just testable (i tag an alpha each time something is testable, but it's far from feature-complete, and i stumble on quite a lot bugs in the CiviCRM API). it will be further developed in the coming months (i guess to get something stable / feature complete by november / december, occording to my work planning (we develop it for a project here)).

If there is video footage / slides afterward the session, i'd love to hear about. But from Europe those camps are quite far to attend in person ;-) (Perhaps we could meet at Drupalcon Prague?)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.