[Solved] Ajax Validation not working with Joomla 3.3 and latest github update.

Makulia

Member
When I tried to validate field via ajax, I have got this error in Chrome console:
Uncaught SyntaxError: Unexpected token < mootools-core-uncompressed.js:5626.

Additional info:
Joomla verison: Joomla! 3.3.0 Stable [ Ember ] 30-April-2014 14:00 GMT
Fabrik: from may 23 2014

It doesn't matter what type of field or what type of validation we are using. Error is always the same!

Link to this form: dev.kadis.org/obuchenie/seminary/raspisanie-seminarov/pravila-ischisleniya-posobij-po-vremennoj-netrudosposobnosti-i-v-svyazi-s-materinstvom

Please, help !

If you need admin account to investigate this issue, just pm me!
 

Attachments

  • bug1.png
    bug1.png
    56.9 KB · Views: 530
I can't replicate, ajax validation is working on my site.
But there's no mootools-core-uncompressed.js loading on my site, where does it come from?
Did you try with the standard Joomla protostar template?
 
I can't replicate, ajax validation is working on my site.
But there's no mootools-core-uncompressed.js loading on my site, where does it come from?
Did you try with the standard Joomla protostar template?

Yep. Same with Protostar. mootools-core-uncompressed.js appears when Joomla debugging is enabled in CP. So it has relation to this issue.

After some debugging i have found that this problem is related to preg_replace_callback function:

Code:
a    "<br />\n<b>Deprecated</b>:  preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in <b>/home/appmanager/www/dev.kadis.org/public_html/components/com_fabrik/models/form.php</b>

I have updated url for debugging: dev.kadis.org
 

Attachments

  • bug2.png
    bug2.png
    50.2 KB · Views: 476
The issue sounds like a php deprecated warning being issued inside an ajax response because joomla error reporting is set to maximum or similar.
 
The issue sounds like a php deprecated warning being issued inside an ajax response because joomla error reporting is set to maximum or similar.

Yes, sounds right. After setting warning level in Joomla CP to "none", problem is gone.
 
So the cause of this does need to be fixed so that it works when error reporting is not "none" or "simple".
 
Are you running PHP5.5?
As far as I can see this is a deprecated warning of PHP5.5 (Joomla is recommending 5.4) - but it should be fixed in Fabrik anyway.
 
Are you running PHP5.5?
As far as I can see this is a deprecated warning of PHP5.5 (Joomla is recommending 5.4) - but it should be fixed in Fabrik anyway.

Yes, I have red about this deprecation and agree that it should be fixed anyway. Btw, php 5.5.9. Thank you all for the quick replys! It helps a lot!
P.S. I am trying to migrate my site from J2.5 to J3.3 and it is a little bit painful :(
 
We are in need of some funding.
More details.

Thank you.

Members online

Back
Top