⚠ In case you've missed it, we have migrated to our new website, with a brand new forum. For more details about the migration you can read our blog post for website migration. This is an archived forum. ⚠

  •     

profile picture

Ajax loading wrong actions url



muldock

muldock
  • profile picture
  • Member

Posted 10 November 2017 - 19:16 PM

Hi!

 

I have setup Grocery CRUD with my application and everything works fine except when an ajax call is made (pagination for example) and all the actions urls are incomplete, leading to a 404 error if clicked.

I attached 2 files, one showing the right destination url and the second one after an (any) ajax call.

Just for knowledge, I am using .htaccess to hide 'index.php', but the "problem" already existed before this change.

 

UPDATE

It seems the problem is with the flexgrid theme, I changed it to datatables and everything worked fine.


Amit Shah

Amit Shah
  • profile picture
  • Member

Posted 11 November 2017 - 08:10 AM

Well.. this is undoubtedly not possible without something wrong in code / configurations.

Code - i dont think so - cuz had this been issue - it would have affected everyone not just you..

Configuration - quite possible.

When u hit in the url in browser - it was picked up correctly by the crud - on first page. I doubt - but am willing to agree that it is quite possible. But then when it is hit on second page - it fails ... now only reason i can believe in the same is - quite possible - it is picking up the base_url / site_url .. the result for the url can be all set in the application/config.php.

Now i will 1st like u to have a look in the same - if it aint there - then what i want you to share an insight - have u made any changes in the core library for your own customization needs? If so, that is where u need to have a look into the same. If not, then i will recommend - re-download a fresh copy of GC and set it in there.

 

Hope either of above analysis will help you fix your issue.

 

Happy GCing :)


muldock

muldock
  • profile picture
  • Member

Posted 13 November 2017 - 17:59 PM

Thanks for replying!

 

I just found out the problem was a Google Module (mod_pagespeed) that was active on my server provider.