After doing an upgrade from Joomla 3.2 to 3.2.1, I am getting a server error if I try to access the Chronoforms component in the backend. Anyone else having this issue? It is happening both on my local setup and online.
Thanks in advance.
Thanks in advance.
Alright, answered my own question, I think. After checking and discovering that there was an update to chronoforms v4 release (4.0.4), I applied that and it seems to be working now. Sorry for jumping ahead and posting without fully investigating potential solutions! Hopefully this might help someone else out down the road. 🙂
Sorry for posting up such a storm, but I have something to add after doing some more work with this.
Anytime I call a form with {chronoforms} ... {/chronoforms} within an article, I cannot save it without getting a 500 Internal Server Error. So, it seems my problem is still lingering. We use chronoforms pretty heavily on this particular site (loads of different forms are needed), but it isn't live just yet. Any ideas?
Again, this is a recent Joomla 3.2 to 3.2.1 update with Chronoforms v4.0.4
Anytime I call a form with {chronoforms} ... {/chronoforms} within an article, I cannot save it without getting a 500 Internal Server Error. So, it seems my problem is still lingering. We use chronoforms pretty heavily on this particular site (loads of different forms are needed), but it isn't live just yet. Any ideas?
Again, this is a recent Joomla 3.2 to 3.2.1 update with Chronoforms v4.0.4
Thanks for helping!
Yes, the form loads fine and I get the confirmation message when I run a test.
I think I have narrowed it down to being connected to how I have the forms in the articles.
Pretty much anytime that I use the {chronoforms}formname{/chronoforms} snippet to call a particular form, whether saving the article or even if it was already present in the article before the recent update, I get an Internal Server Error.
As a test, I added one of the forms as a menu item, and it worked just fine. Definitely related to loading the forms within an article.
Yes, the form loads fine and I get the confirmation message when I run a test.
I think I have narrowed it down to being connected to how I have the forms in the articles.
Pretty much anytime that I use the {chronoforms}formname{/chronoforms} snippet to call a particular form, whether saving the article or even if it was already present in the article before the recent update, I get an Internal Server Error.
As a test, I added one of the forms as a menu item, and it worked just fine. Definitely related to loading the forms within an article.
You guys are wonderful! Thank you so much for the support.
sloanthrasher --- your offer to look into is very much appreciated, but not needed. Bob's suggestion fixed it for me. I've been using Chronoforms for a while, and it slipped my mind that I may need to updated the plugin as well.
Thanks again! 😀
sloanthrasher --- your offer to look into is very much appreciated, but not needed. Bob's suggestion fixed it for me. I've been using Chronoforms for a while, and it slipped my mind that I may need to updated the plugin as well.
Thanks again! 😀
This topic is locked and no more replies can be posted.
