CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Installing CiviCRM »
  • Standalone Installations (Moderator: cap10morgan) »
  • As of 3.2 standalone isn't supported anymore
Pages: [1]

Author Topic: As of 3.2 standalone isn't supported anymore  (Read 2942 times)

xavier

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4453
  • Karma: 161
    • Tech To The People
  • CiviCRM version: yes probably
  • CMS version: drupal
As of 3.2 standalone isn't supported anymore
August 16, 2010, 02:15:52 pm
As per kurund suggestion, the easiest is to install a minimal drupal, then:

1. Backup your current standalone CiviCRM db.
2. If you are on 3.1.x, first install Drupal and do fresh install of CiviCRM ( same as your current version). Make sure CiviCRM works and logout from drupal.
3. Empty civicrm_uf_match, civicrm_cache, civicrm_menu table of your standalone CiviCRM db.
4. Update civicrm_domain.config_backend to null
5. In your drupal - civicrm: change civicrm dns settings in civicrm.settings.php to point civicrm standalone db.
6. Now login to drupal and go to http://example.org/civicrm/menu/rebuild?reset=1

It would be very appreciated if you detail the steps you've taken and publish that in the wiki to help others.
-Hackathon and data journalism about the European parliament 24-26 jan. Watch out the result

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Installing CiviCRM »
  • Standalone Installations (Moderator: cap10morgan) »
  • As of 3.2 standalone isn't supported anymore

This forum was archived on 2017-11-26.