Hi. i am in a bit of trouble. I upgraded my joomla website from 1.7 to 2.5 including my chronoforms extension. Everything seemed to work well. However, i just went to test a different form and i got the following error...
"Fatal error: Call to protected JDatabaseMySQL::__construct() from context 'CfactionCustomCode' in /home/xxxxxx/public_html/administrator/components/com_chronoforms/form_actions/custom_code/custom_code.php(19) : eval()'d code on line 18"
Does anybody know why this might happening?
This is fairly urgent and so your help will be greatly appreciated
Hi glens1234,
What code you you have in the Custom Code action?
Bob
Hi glens1234,
Ah, OK I hadn't realised that the code was creating a new site - that makes more sense. It looks as though the either the DB creation, or something in the table creation is failing to give this error.
Could it be a problem with the table prefix as jos_ is no longer standard in Joomla! 2.5??
Bob
Hi glens1234 ,
From a quick look one is using $db and the other $db1. Given that $db (or $database) is usually used for the current Joomla! database I'd switch both of these to something different and distinct.
This isn't a big problem as the scope of the variable will be limited to the current code block but it does help avoid confusion.
Bob
ok thanks. ill look into that now. i was just wandering...
I noticed a Data To Session event onSubmit and a Session To Data event on FinishProcess. Both of which are there but they are blank (not configured). Could it be that the chronoforms upgrade removed the configuration for these events? Im speculating of course, but it seems to me that these need to be configured in order to pass the data between the forms. I have looked for some tutorials about these event but i havent seen anything. could that be the reason why the UPDATE statement is not working and if so could you inform me how to configure these events?
BTW, i checked phpmyadmin to look at the values of the variables and they are still default. They do not get updated.
EDIT: Actually, ignore that. If the site name is being generated based on the names entered on the signup form then it must be storing this data somewhere. hmmm. im lost😟
Thanks.
HI glens1234,
The only configuration for the Session/Data actions it to make sure that they both have the same Session Key if they are in different forms as the default is to use the form name.
Bob