When I upgraded from CBSubs 2.0.2 to CBSubs 3.0, I noticed that the site returned an Error 500 on the front end, but would allow me to access the backend. I checked through my server logs, which indicated that the problem was caused by CiviCRM. However, when I uninstalled CiviCRM, the site still would give an Error 500 on the front end. After some more troubleshooting, I uninstalled CBSubs 3.0, and the front end started displaying again.
I would rather not have to use an outdated version of CBSubs, but I don't know what would cause the Error 500 when installing CBSubs 3.0. Do any of you have any suggestions on how to fix this? Do you believe this may be a bug?
I am using CB 1.9, Joomla 2.5.8, PHP 5.3.20, MySQL 5.5.29, and Apache 2.2.23 on a Linux server. CBSubs 2.0.2 worked when installed in this environment.
Install CBSubs 3.0, navigate to CBSubs > Settings then Save, now check frontend and see if issue persists. Ensure you've upgraded all of CBSubs to 3.0. If issue persists enable debug mode and maximum error reporting in Joomla global configuration then test again to expose the error and provide any on-screen errors you see.
Kyle (Krileon) Community Builder Team Member Before posting on forums:
Read FAQ thoroughly
+
Read our Documentation
+
Search the forums CB links:
Documentation
-
Localization
-
CB Quickstart
-
CB Paid Subscriptions
-
Add-Ons
-
Forge
-- If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
-- If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please
send me a private message
with your thread and will reply when possible!
-- Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
-- My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.
I apologize for the late reply. I took your advice and found that the error was really caused by a missing database table for the JoomlaWatch component, not by anything in CB.
krileon
