Answers.Body: <p>The fix to the file CRM/Utils/System/Joomla.php suggested in the link 
  <a href="https://github.com/civicrm/civicrm-core/pull/11062/files?diff=unified" rel="noreferrer">https://github.com/civicrm/civicrm-core/pull/11062/files?diff=unified</a>
  made the cron jobs run again for CiviCRM 4.7.25 and Joomla 3.8.1.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-10-09T18:41:38.493Z
Answers.Text: I installed the patch linked to above on Oct 6th, and have not since a problem with the CRON since.
Answers.UserDisplayName: Neil Z
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-02-05T16:27:32.000Z
Answers.Text: Note that this fix won't solve all uses of Joomla cron for some CiviCRM installs.  The patch on https://issues.civicrm.org/jira/browse/CRM-20904 is also necessary.
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-10-09T12:49:47.810Z
Answers.LastActivityDate: 2017-10-09T12:49:47.810Z
Answers.UserDisplayName: Marcelo Mig
Answers.Body: <p>I took the plunge and upgraded Joomla to 3.8.0 today. I am seeing two problems with it and CiviCRM 4.7.24:</p>
  
  <ul>
  <li>cron jobs are not running</li>
  <li>In the backend, the Administer > Directories page is broken (only loads partially). There are 3 instances of "ReferenceError: CRM is not defined" appearing in Firebug console.</li>
  </ul>
  
  <p>I have not looked into these any further yet. Cron jobs were definitely working prior to the Joomla upgrade but I don't know if the Directories page was already broken.</p>
  
  <p>UPDATE: I've posted on <a href="https://issues.civicrm.org/jira/browse/CRM-21203" rel="nofollow noreferrer">CRM-21203</a> some changes to CRM/Utils/System/Joomla.php that get cron jobs working (doesn't fix the Directories page). Joomla 3.8.0 has changed the location of some files in libraries/</p>
  
  <p>Joomla 3.8.0 is a required security update for all previous versions.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-20T07:00:10.040Z
Answers.Text: I have raised a bug report:
  https://issues.civicrm.org/jira/browse/CRM-21203
Answers.UserDisplayName: Jern
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-20T10:51:54.713Z
Answers.Text: Do you also have JoomSEF installed?
Answers.UserDisplayName: Jern
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-20T11:47:44.377Z
Answers.Text: Thanks for confirming and creating the Jira issue. No I'm not using JoomSEF. I noticed that in Joomla 3.7, the class JObject is defined in libraries/joomla/object/object.php. In Joomla 3.8.0 object.php is not present and JObject is not defined anywhere else.
Answers.UserDisplayName: Andrew Thompson
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-20T11:57:18.067Z
Answers.Text: Actually I can see now that JObject is now supposed to be an alias for CMSObject so not sure what the problem is.
Answers.UserDisplayName: Andrew Thompson
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-20T13:58:25.100Z
Answers.Text: I suspect that the JObject error may be just be a symptom. It could be that something in CiviCRM doesn't take account of the new routing regime in Joomla 3.8.
  https://docs.joomla.org/J3.x:New_Routing_System
  This could also explain the Directories page mess-up.
Answers.UserDisplayName: Jern
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-21T11:39:03.240Z
Answers.Text: I submitted issue https://issues.civicrm.org/jira/browse/CRM-21209 about the Directories problem.
  
  As a workaround hack, you can create folder "version" under /libraries/cms/, and create an empty file "version.php" in the new folder. Not pretty, but it seems to work.
Answers.UserDisplayName: Jern
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-21T11:49:43.123Z
Answers.Text: Sorry. I see you already submitted  issues.civicrm.org/jira/browse/CRM-21208
Answers.UserDisplayName: Jern
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-22T15:41:23.967Z
Answers.Text: I posted on the Joomla forum about the CRON issue, https://forum.joomla.org/viewtopic.php?p=3493718#p3493718, and got this reply:
  ------------------------------------------------------------------------------- > 
  This is no surprise. The router is completely rewritten in 3.8.0.
  You have to contact the developer of the script.
  <-------------------------------------------------------------------------------
  
  Again, it appears that no one in the CiviCRM group is taking any notice of those of us using Joomla.
Answers.UserDisplayName: Neil Z
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-22T18:28:59.077Z
Answers.Text: I think there are those using joomla who help maintain Civi - 3.8 was a pretty new release and destined to break some things - this has been a great post and highlighted the need to add some tweaks to the next Civi release. Thank you all for your comments
Answers.UserDisplayName: Josh Mailman
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-23T00:05:57.677Z
Answers.Text: I guess I'm going to have to create a local WAMP site for Joomla betas, and then install CiviCRM to see what breaks in future
Answers.UserDisplayName: Neil Z
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-24T13:30:05.263Z
Answers.Text: FWIW ... I tried the suggested patch in CRM-21203, and my CRON is still not running.   The fix for the JROUTER messages worked, but the CRON is still not running.
Answers.UserDisplayName: Neil Z
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-20T04:36:41.517Z
Answers.LastActivityDate: 2017-09-21T01:01:30.377Z
Answers.LastEditDate: 2017-09-21T01:01:30.377Z
Answers.UserDisplayName: Andrew Thompson
Answers.Body: <p>I have a post-3.8 upgrade issue: I don't think it's related to the issue above but sharing in answer to the OP: <a href="https://civicrm.stackexchange.com/questions/20609/joomla-3-8-civicrm-4-7-x-front-end-error-500-when-logged-in">Joomla 3.8 &amp; CiviCRM 4.7.x - front-end error 500 when logged in</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-26T16:09:53.233Z
Answers.LastActivityDate: 2017-09-26T16:09:53.233Z
Answers.UserDisplayName: Nic
Answers.Body: <p>The issue was not fixed in 4.7.27, appears to be slated for 4.7.28.  Manually applying the fix in Joomla.php file here seems to have resolved it <a href="https://github.com/civicrm/civicrm-core/pull/11062" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/pull/11062</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-11-14T16:55:52.437Z
Answers.LastActivityDate: 2017-11-14T16:55:52.437Z
Answers.UserDisplayName: Troy Mumm
Body: <p>I am not looking to be first on this - just wanted to see if anyone is running J3.8 and current release of Civi.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-09-26T03:42:37.123Z
Comments.Text: I upgraded to Joomla 3.8 last week and have been having the same cron error ever since. I tried the tweaks mentioned here: https://issues.civicrm.org/jira/browse/CRM-21203 But those don't solve the issue. It would be great if there could be a definitive fix. Every time I either update Joomla or CiviCRM, something breaks with CiviCRM. Without fail. Is there an official fix for this yet? Five days without a running cron is a big hassle.
Comments.UserDisplayName: severdia
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-09-26T16:35:57.560Z
Comments.Text: As a reminder, Stack Exchange is not a discussion forum, but a Q&A site. Consider rephrasing to something that solicits definitive answers, and where members of the community can vote for a "best" answer.
Comments.UserDisplayName: choster
Tags: <joomla><upgrade>
Title: Issues with running Joomla 3.8 and Civi
ThreadText: # Issues with running Joomla 3.8 and Civi
  
  (Asked by: username_0 on 2017-09-20)
  
  I am not looking to be first on this - just wanted to see if anyone is running J3.8 and current release of Civi.
  
  **Tags:** joomla, upgrade
  
  > **Comments:**
  > **username_1**: I upgraded to Joomla 3.8 last week and have been having the same cron error ever since. I tried the tweaks mentioned here: https://issues.civicrm.org/jira/browse/CRM-21203 But those don't solve the issue. It would be great if there could be a definitive fix. Every time I either update Joomla or CiviCRM, something breaks with CiviCRM. Without fail. Is there an official fix for this yet? Five days without a running cron is a big hassle.  
  > **username_2**: As a reminder, Stack Exchange is not a discussion forum, but a Q&A site. Consider rephrasing to something that solicits definitive answers, and where members of the community can vote for a "best" answer.  
  
  ---
  
  ## 4 answers
  
  ### Answer by username_3 on 2017-10-09. Score: 6
  
  The fix to the file CRM/Utils/System/Joomla.php suggested in the link
  <https://github.com/civicrm/civicrm-core/pull/11062/files?diff=unified>
  made the cron jobs run again for CiviCRM 4.7.25 and Joomla 3.8.1.
  
  > **Comments:**
  > **username_4**: I installed the patch linked to above on Oct 6th, and have not since a problem with the CRON since.  
  > **username_5**: Note that this fix won't solve all uses of Joomla cron for some CiviCRM installs.  The patch on https://issues.civicrm.org/jira/browse/CRM-20904 is also necessary.  
  
  ---
  
  ### Answer by username_6 on 2017-09-20. Score: 2
  
  I took the plunge and upgraded Joomla to 3.8.0 today. I am seeing two problems with it and CiviCRM 4.7.24:
  
  * cron jobs are not running
  * In the backend, the Administer > Directories page is broken (only loads partially). There are 3 instances of "ReferenceError: CRM is not defined" appearing in Firebug console.
  
  I have not looked into these any further yet. Cron jobs were definitely working prior to the Joomla upgrade but I don't know if the Directories page was already broken.
  
  UPDATE: I've posted on [CRM-21203](https://issues.civicrm.org/jira/browse/CRM-21203) some changes to CRM/Utils/System/Joomla.php that get cron jobs working (doesn't fix the Directories page). Joomla 3.8.0 has changed the location of some files in libraries/
  
  Joomla 3.8.0 is a required security update for all previous versions.
  
  > **Comments:**
  > **username_7**: I have raised a bug report: https://issues.civicrm.org/jira/browse/CRM-21203  
  > **username_7**: Do you also have JoomSEF installed?  
  > **username_6**: Thanks for confirming and creating the Jira issue. No I'm not using JoomSEF. I noticed that in Joomla 3.7, the class JObject is defined in libraries/joomla/object/object.php. In Joomla 3.8.0 object.php is not present and JObject is not defined anywhere else.  
  > **username_6**: Actually I can see now that JObject is now supposed to be an alias for CMSObject so not sure what the problem is.  
  > **username_7**: I suspect that the JObject error may be just be a symptom. It could be that something in CiviCRM doesn't take account of the new routing regime in Joomla 3.8. https://docs.joomla.org/J3.x:New_Routing_System This could also explain the Directories page mess-up.  
  > **username_7**: I submitted issue https://issues.civicrm.org/jira/browse/CRM-21209 about the Directories problem.  As a workaround hack, you can create folder "version" under /libraries/cms/, and create an empty file "version.php" in the new folder. Not pretty, but it seems to work.  
  > **username_7**: Sorry. I see you already submitted  issues.civicrm.org/jira/browse/CRM-21208  
  > **username_4**: I posted on the Joomla forum about the CRON issue, https://forum.joomla.org/viewtopic.php?p=3493718#p3493718, and got this reply: ------------------------------------------------------------------------------- >  This is no surprise. The router is completely rewritten in 3.8.0. You have to contact the developer of the script. <-------------------------------------------------------------------------------  Again, it appears that no one in the CiviCRM group is taking any notice of those of us using Joomla.  
  > **username_0**: I think there are those using joomla who help maintain Civi - 3.8 was a pretty new release and destined to break some things - this has been a great post and highlighted the need to add some tweaks to the next Civi release. Thank you all for your comments  
  > **username_4**: I guess I'm going to have to create a local WAMP site for Joomla betas, and then install CiviCRM to see what breaks in future  
  > **username_4**: FWIW ... I tried the suggested patch in CRM-21203, and my CRON is still not running.   The fix for the JROUTER messages worked, but the CRON is still not running.  
  
  ---
  
  ### Answer by username_8 on 2017-09-26. Score: 1
  
  I have a post-3.8 upgrade issue: I don't think it's related to the issue above but sharing in answer to the OP: [Joomla 3.8 & CiviCRM 4.7.x - front-end error 500 when logged in](https://civicrm.stackexchange.com/questions/20609/joomla-3-8-civicrm-4-7-x-front-end-error-500-when-logged-in)
  
  
  ---
  
  ### Answer by username_9 on 2017-11-14. Score: 0
  
  The issue was not fixed in 4.7.27, appears to be slated for 4.7.28. Manually applying the fix in Joomla.php file here seems to have resolved it <https://github.com/civicrm/civicrm-core/pull/11062>
  
  
  ---
  
  