annekas
New Member
I'm posting this just to lend a hand to other folks who are knowledgeable enough to be dangerous!
My site is still Joomla 2.5.28, Fabrik 3.0.9. I was trying to empty a list and it appeared that the records were still there. I couldn't delete a single record either. Apparently. I feared that something had gone awry and I would have to make the upgrade to J3/Fabrik 3.x before I was ready.
After bothering Hugh (I apologize again, Hugh!), he suggested checking the actual database table in phpMyAdmin. There were zero records...i.e. the empty had worked, though they still showed in Administrator.
I then realized that I had turned on caching yesterday. When I turned off caching, the view list contents showed no records.
Hugh tells me that Fabrik is supposed to clear the cache, but apparently in my case it did not. BTW, I just looked and that list -- and probably all the others I have built -- have the Disable Caching option for the list set to No, so it does not override the Joomla caching.
So, check your caching if you have this issue before panicking, like I did.
Issue resolved.
Thanks again to Hugh for his boundless patience with my barely competent self.
My site is still Joomla 2.5.28, Fabrik 3.0.9. I was trying to empty a list and it appeared that the records were still there. I couldn't delete a single record either. Apparently. I feared that something had gone awry and I would have to make the upgrade to J3/Fabrik 3.x before I was ready.
After bothering Hugh (I apologize again, Hugh!), he suggested checking the actual database table in phpMyAdmin. There were zero records...i.e. the empty had worked, though they still showed in Administrator.
I then realized that I had turned on caching yesterday. When I turned off caching, the view list contents showed no records.
Hugh tells me that Fabrik is supposed to clear the cache, but apparently in my case it did not. BTW, I just looked and that list -- and probably all the others I have built -- have the Disable Caching option for the list set to No, so it does not override the Joomla caching.
So, check your caching if you have this issue before panicking, like I did.
Issue resolved.
Thanks again to Hugh for his boundless patience with my barely competent self.