Problems after upgrade to Joomla 3.2

Hi,

Today when I upgraded to Joomla 3.2 on a development site I encountered some problems with Chronoform:

1. Submitting a form causes the website to crash (the browser only displays a blank page with this url: http://dev.fib.se/kontakt?chronoform=kontakt3&event=submit)

2. I can't access the Chronoforms controlpanel within the admin GUI (also only a blank page with this url: http://dev.fib.se/administrator/index.php?option=com_chronoforms) whereas all other installed components (K2, K2Shop, Akeeba and others) works as usual

Chronoforms works perfect when I restore a the dev website back to Joomla 3.1.5.

An suggestion what may have occured?

Best regards

Hi arvendal,

Please see this FAQ

Bob

Thanks! It solved the problem.

Best regards

Sorry!

I only checked the admin GUI Before I answered. The problem still exist when I try to submit a form, i e blank page and URL=http://dev.fib.se/kontakt?chronoform=kontakt3&event=submit

Anything more that I must do?

Rgds

Hi,

I am sorry to have to ask once more about this issue but the frontend form doesn't work even though I copied the files mentioned. It's just a blank page with the URL http://dev.fib.se/kontakt?chronoform=kontakt3&event=submit after hitting the submit button.

I would appreciate any help in this matter. The backend works OK now.

Best regards

Hi arvendal,

Max released new versions of the component, plug-in and module today. Please upgrade and see if that resolves the problems.

Bob

No, sorry. It did not help.
I installed the updated Chronoforms extensions in the old Joomla 3.1.5 and the same problem arose, i e blank page. Problem still continued after upgrading to Joomla 3.2. So the updated extensions did not help.

Backend works, but not submitting forms at frontend.

By the way, I'm using Chrome.

Hi arvendal,

Please see this FAQ

Bob

Thanks for your response!
I changed the error display to maximum and then the anti-spam characters crashed.

I looked inside the form actions and found this error message:

Strict Standards: Only variables should be assigned by reference in /home/f/fib/www/joomla/administrator/components/com_chronoforms/form_actions/email_gh/email_gh.php on line 32

And inside the email_gh actions I found this:

Strict Standards: Only variables should be assigned by reference in /home/f/fib/www/joomla/administrator/components/com_chronoforms/form_actions/email_gh/email_gh.ctp on line 219

I would like to test to remove the captcha function, but when I do that the whole action window empties out, i e I cannot simply remove the captcha action without destroying the whole quite complicated form I have created.

How do I continue from here?

Best regards

Hi arvendal,

Neither of the Strict Standards messages are actual problems, so we still don't know quite what is happening. I have no idea why the Captcha should be causing a problem in Joomla! 3.2 - I haven't seen any other reports of that.

What exactly does 'crashed' mean? Does it still happen with Error Reporting set back to None?

Bob

Hi,
everthing works when I go back to error display = none.
"Crash" means that instead of the character row generated by captcha there's the symbol of broken image link.
Adn the captcha displays ok when error display is none.
Best rgds

Hi arvendal,

OK - I suspect that when Error Reporting is set at Maximum there is an error message getting inserted into the PHP somewhere that breaks the code. Those can be hard to pin down :-(

Is everything OK now with Error Reporting at None?

Bob

Sadly, no. When I set the error messages to none, the captcha code only display a broken image link.

I have tested the new Joomla on a development site, which I created by restoring the original website via Akeeba backup to a dev.original-domain.se site. I don't know if this may cause any problem, but this method has always worked well when I want to check any eventual conflict before upgrading the sharp site.

But I am also working on a new site with a fresh Joomla 3.2 installation. This is on a different web host. I can check if I get the same problem if I install Chronoforms on that site as well.

I'll be back when I tested this and some more things I came to think about writing this message.

Best regards

Once more, sorry!
I was convinced I had turned the error message back to none, but I had not. I'm getting too confused now I think, when I go in and out of the backend, tweaking this and that. I am really sorry for providing you with wrong info in my previous message.

So: All is almost well when error message = none. The problem is that a blank page is generated when submitting the form. Before Max had updated Chronoform I also got this problem when trying to access the component in backend. But that was solved with the updated Chronoform.

But the frontend problem is still there...

Best regards

I think I have found something!

The message was successfully sent when I turned on debug in Chronoforms (I know, I should have done that earlier) and used the button "Test form" instead of using the form on the actual web page. See attached file for debug info.
[attachment=0]debug-chronoforms.txt[/attachment]

Is this information any helpful?

Best regards

Hi,

I just checked what happens if I use the latest Chronoforms together with a fresh Joomla 3.2 installation: it works. 🙂

But that leaves me with two alternatives why the other combination of latest Chronoform and latest Joomla doesn't work:

1. Something server specific (my successful test described above was on another host)
2. Some conflict with another extension

What else can it be? It beats me...

Best rgds

I am getting the same results as you have described, once I disabled the cUrl action the form was able to send an email. But my problem is that I need it to submit to a 3rd party CRM ... so I still have a problem:(

Hi arvendal,

If you are using any of the [GH] actions then they have a problem since the last ChronoForms upgrade :-(

There's a quick fix to search the action files and replace JParameter with JCFParameter.
In most it just occurs once like this in the main action_name.php :

	function run($form, $actiondata)
	{
		$mainframe = JFactory::getApplication();	
		$params = new JCFParameter($actiondata->params);
		$user = JFactory::getUser();

I'm working on upgrading them all but right now I'm fighting too many deadlines.

Bob

OK! This may be the solution!
I am using GH email action.

But no worries. I will try your fix. Or I'll wait for your update.

Thanks!

Best rgds

Hi arvendal,

I updated all of the widely used actions this morning (a few of the more obscure ones will need to wait until next week).

Bob

Thanks Greyhead I will try it out and report back!


UPDATE: Fixed! thanks alot this helped, i will buy you a beer on Friday(payday)🙂

Hi,

I have also tested your solution and now the website is up and running in its full glory. Thanks for you fine support.

There's a nota bene, though: The Joomla upgrade to 3.2 causes sometimes an error in the email functon. See this thread: http://forum.joomla.org/viewtopic.php?f=706&t=825772

This also happened to me. So even after updating all Chronoforms extensions and GH actions my website refused to send any form message. I was almost going to throw the PC out of the window, but I got a system error message in another extension that pointed me in that direction. A quick search on the Internet and voilá: just save the global configuration (with no actual changes) and the send email function is back in business.

A beer's coming up!

Best rgds

Hi arvendal,

I found it for myself early this morning and added a FAQ here about it . . . cost me more lost hair.

Bob

Hi,

I'm using the lates Chronoforms core and plugin on Joomla 3.1.6 and the Show_Html_GH action. If using this action I get the following error message:

Fatal error: Call to a member function get() on a non-object in .../com_chronoforms/form_actions/show_html_gh/cfaction_show_html_gh.php on line 84

This is happening on your update action from 13th November.

Do you have maybe a quick fix for this?

EDIT: Fixed! Replace "$this->params" with "$params"

Thank you in advance!

Cheers,
Dan

Hi,

I found the email GH action to work properly with 3.1 even without upgrading it. But in 3.2 the email sending bug is causing the action to generate a fatal error. Luckily, after changing the email pref fomr PHP mail to Sendmail and back again, the fatal error disappars in my case. I never updated the action with the new versions Greyhaed published 13-11.

Best regards,

Erik