I followed the J3.5 issue advice, using latest version of chronoforms and applied the isis3 template, however under php 7.04
On my 3.5 site with the above in place I am presented with the error below and unable to go further than the login screen
syntax error, unexpected 'clone' (T_CLONE), expecting identifier (T_STRING) or '('
If Max is able to say if the above string could be in either chrono package to rule it out, it would be great.
A second issue on my 3.5.1 site, which is a clean install with just Chronoforms and Chronoconnectity I have a error 500 when trying to access either component, this is with the latest chrono extensions and also tried the isis3 template.
Many thanks in advance😀
On my 3.5 site with the above in place I am presented with the error below and unable to go further than the login screen
syntax error, unexpected 'clone' (T_CLONE), expecting identifier (T_STRING) or '('
If Max is able to say if the above string could be in either chrono package to rule it out, it would be great.
A second issue on my 3.5.1 site, which is a clean install with just Chronoforms and Chronoconnectity I have a error 500 when trying to access either component, this is with the latest chrono extensions and also tried the isis3 template.
Many thanks in advance😀
I have solved the first issue, rather than using isis3 template I needed to replace the following line
with
it would be good if either the problem area in the js that's being called by the template is identified, as it maybe that the template needs a PR raising on issues.joomla.com with a solution
I will try the template adjustment on my bugtesting site tomorrow if I get a chance.
Thanks to @albian for spotting this one.
$doc->addScriptVersion($this->baseurl . '/templates/' . $this->template . '/js/template.js');
with
$doc->addScriptVersion($this->baseurl . '/templates/hathor/js/template.js');
it would be good if either the problem area in the js that's being called by the template is identified, as it maybe that the template needs a PR raising on issues.joomla.com with a solution
I will try the template adjustment on my bugtesting site tomorrow if I get a chance.
Thanks to @albian for spotting this one.
Hi Twincarb,
I'm running the latest CFv5.0.11 release on Joomla! 3.5.0 with PHP 7,02 and the Isis3 template and haven't seen any errors so far.
Is there anything in the server logs that gives a clue about the source of the 500 error?
Bob
I'm running the latest CFv5.0.11 release on Joomla! 3.5.0 with PHP 7,02 and the Isis3 template and haven't seen any errors so far.
Is there anything in the server logs that gives a clue about the source of the 500 error?
Bob
Morning Bob,
This is on a bugtesting site which has got the latest chronoforms installed, I manually commented out the breaks as said in the FAQ and chronoforms now works, but chronoconectivity still isn't playing and is leaving no errors in the logs.
I still have the other issue with the other error, it just takes a bit of time for the opcache to update, which has been noted by others on joomla.
mod_fcgid: stderr: PHP Fatal error: 'break' not in the 'loop' or 'switch' context in /var/www/vhosts/example.co.uk/bugtesting.example.co.uk/libraries/cegcore/helpers/html.php on line 45, referer: http://bugtesting.davewebbersystems.co.uk/administrator/index.php
This is on a bugtesting site which has got the latest chronoforms installed, I manually commented out the breaks as said in the FAQ and chronoforms now works, but chronoconectivity still isn't playing and is leaving no errors in the logs.
I still have the other issue with the other error, it just takes a bit of time for the opcache to update, which has been noted by others on joomla.
Hi Twincarb,
That 'break' error is documented in this FAQ and is fixed in CFv5.0.11 - I just checked the code in the package I downloaded yesterday. I'm bemused about why you are seeing that :-(
Bob
That 'break' error is documented in this FAQ and is fixed in CFv5.0.11 - I just checked the code in the package I downloaded yesterday. I'm bemused about why you are seeing that :-(
Bob
H Bob,
I have just completed, a new install and started with chronoforms first, that loads without any issues.
Then installed Chronoconectivity and it came up with the same issue as above, applying the fix in the FAQ solves it.
I am trying to replicate the fault I had before, I believe that will be another component.
My component versions are Chronoforms: 5.0.11
Chronoconectivity: 5.0.3
I have just completed, a new install and started with chronoforms first, that loads without any issues.
Then installed Chronoconectivity and it came up with the same issue as above, applying the fix in the FAQ solves it.
I am trying to replicate the fault I had before, I believe that will be another component.
My component versions are Chronoforms: 5.0.11
Chronoconectivity: 5.0.3
Hi,
CFv5.0.11 has the latest library files, so please install it AFTER connectivity, until a new update for Connectivity is released.
Regards,
Max
CFv5.0.11 has the latest library files, so please install it AFTER connectivity, until a new update for Connectivity is released.
Regards,
Max
Thanks Max,
I will install Chronoforms again.
Just found the issue to the other problem, which was a conflict with my nginx conf settings. So all is good here😀
Dave
I will install Chronoforms again.
Just found the issue to the other problem, which was a conflict with my nginx conf settings. So all is good here😀
Dave
Hi Dave,
I hadn't spotted the problem of installing CC after CF :-( I have added a warning to the FAQ,
Bob
I hadn't spotted the problem of installing CC after CF :-( I have added a warning to the FAQ,
Bob
Hi TwinCarb,
I looked at albion's fix It looks odd to be loading the hathor js file into isis? I checked the code and the two are quite different.
On the other hand, the template.js files in Isis and Isis3 only have one difference - line 32 has been removed in Isis3
Bob
I looked at albion's fix It looks odd to be loading the hathor js file into isis? I checked the code and the two are quite different.
On the other hand, the template.js files in Isis and Isis3 only have one difference - line 32 has been removed in Isis3
input.trigger('change');
Bob
This topic is locked and no more replies can be posted.