Answers.Body: <p>The first issue to raise is that CiviCRM 4.4 is not necessarily compatible with Joomla 3.5 according to this post: <a href="https://civicrm.org/blog/colemanw/announcing-civicrm-445" rel="nofollow">https://civicrm.org/blog/colemanw/announcing-civicrm-445</a>  Since CiviCRM 4.6 apparently <em>is</em> compatible with Joomla 2.5, I suggest upgrading Civi first from 4.4 to 4.6.  Most CiviCRM documentation has to do with upgrading CiviCRM, rather than upgrading Joomla, so I'm not prepared to give advice on Joomla upgrades specifically.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-07-12T19:46:27.507Z
Answers.LastActivityDate: 2016-07-12T19:46:27.507Z
Answers.UserDisplayName: CiviTeacher
Answers.Body: <p>The point that Stuart (CiviTeacher) made is a good general principle: separate your CiviCRM upgrade from your CMS upgrade. Reduce the number of moving parts.</p>
  
  <p>Specifically regarding Joomla 2.5 to 3.5, there's not too much to worry about from the CiviCRM perspective so long as you're running a CiviCRM version that's compatible with both Joomla versions (like 4.6.x, as Stuart suggested).  My coworkers and I have run a number of these without incident.</p>
  
  <p>In practice, you'll probably want to copy your Joomla site, upgrade the copy and upgrade or replace it's extensions, and then make that copy be the new production site.  This works great for a CMS, where you can tell everyone, "Hold your edits: I'm upgrading the site."  However, with CiviCRM, someone might make a donation out of the blue during the time you're upgrading the site copy.</p>
  
  <p>Plan on copying the CiviCRM tables from the J2.5 site to the J3.5 site just before launch. If CiviCRM is the same version, and you're using the same URL, you'll just need to check the file paths (in the two <code>civicrm.settings.php</code> files, and then by visiting Administer - System Settings - Clear Caches and Update Paths) and then clear the contents of <code>media/civicrm/templates_c</code> and <code>media/civicrm/ConfigAndLog</code>.</p>
  
  <p>But again, the big thing is to keep the CiviCRM part of it as simple as possible by doing a regular CiviCRM upgrade, a Joomla upgrade, and then (if necessary) a regular CiviCRM upgrade to your final intended version.  Don't mix CiviCRM changes into the Joomla upgrade work.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-08-12T02:49:10.353Z
Answers.LastActivityDate: 2016-08-12T02:49:10.353Z
Answers.UserDisplayName: Andie Hunt
Body: <p>I am in the throes of making the upgrade captioned above. If there was a documented procedure or a list of potential issues to help I would be grateful. Maybe I should upgrade CiviCRM to a leter version first??</p>
  
Tags: <joomla><upgrade>
Title: Any procedure to upgrade Joomla 2.5.28 to Joomla 3.5 with CiviCRM 4.4.4?
ThreadText: # Any procedure to upgrade Joomla 2.5.28 to Joomla 3.5 with CiviCRM 4.4.4?
  
  (Asked by: username_0 on 2016-06-06)
  
  I am in the throes of making the upgrade captioned above. If there was a documented procedure or a list of potential issues to help I would be grateful. Maybe I should upgrade CiviCRM to a leter version first??
  
  **Tags:** joomla, upgrade
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2016-07-12. Score: 1
  
  The first issue to raise is that CiviCRM 4.4 is not necessarily compatible with Joomla 3.5 according to this post: <https://civicrm.org/blog/colemanw/announcing-civicrm-445> Since CiviCRM 4.6 apparently *is* compatible with Joomla 2.5, I suggest upgrading Civi first from 4.4 to 4.6. Most CiviCRM documentation has to do with upgrading CiviCRM, rather than upgrading Joomla, so I'm not prepared to give advice on Joomla upgrades specifically.
  
  
  ---
  
  ### Answer by username_2 on 2016-08-12. Score: 0
  
  The point that Stuart (username_1) made is a good general principle: separate your CiviCRM upgrade from your CMS upgrade. Reduce the number of moving parts.
  
  Specifically regarding Joomla 2.5 to 3.5, there's not too much to worry about from the CiviCRM perspective so long as you're running a CiviCRM version that's compatible with both Joomla versions (like 4.6.x, as Stuart suggested). My coworkers and I have run a number of these without incident.
  
  In practice, you'll probably want to copy your Joomla site, upgrade the copy and upgrade or replace it's extensions, and then make that copy be the new production site. This works great for a CMS, where you can tell everyone, "Hold your edits: I'm upgrading the site." However, with CiviCRM, someone might make a donation out of the blue during the time you're upgrading the site copy.
  
  Plan on copying the CiviCRM tables from the J2.5 site to the J3.5 site just before launch. If CiviCRM is the same version, and you're using the same URL, you'll just need to check the file paths (in the two `civicrm.settings.php` files, and then by visiting Administer - System Settings - Clear Caches and Update Paths) and then clear the contents of `media/civicrm/templates_c` and `media/civicrm/ConfigAndLog`.
  
  But again, the big thing is to keep the CiviCRM part of it as simple as possible by doing a regular CiviCRM upgrade, a Joomla upgrade, and then (if necessary) a regular CiviCRM upgrade to your final intended version. Don't mix CiviCRM changes into the Joomla upgrade work.
  
  
  ---
  
  