[SOLVED] Model Class Error

We've never heard of that error. We don't have (and never had) a JFBConnectModelProfiles file. I'm not sure what's trying to load that or why.

Can you let me know what version of Joomla you're using? Also, you're on v6.0.4 of JFBConnect now.. when you were running earlier versions, did you see this error.. or is this something new? Finally, can you try disabling all Social Profile plugins and see if the error goes away? If so, re-enable them one by one (if you use multiple) and see which one causes the error. That will help us narrow things down further.

Thanks,
Alex

I can see the error in your admin area as well. However, we can't recreate this issue on our development sites at all. We've also stepped through the code and can't see where the auto-loading of the ProfilesModel would be happening. The only reason that error would show is because Joomla is assuming it should (not because we're directly telling it to). There's simply nothing we can see that's telling it to do that though and this isn't something we've seen on any other Joomla sites or heard from any other users.

The good news is that this isn't causing any functional issues, and we don't see why it should. Of course, fixing it is good so we know what's happening.. but not necessary.

If you want us to investigate further, can you Private Message me FTP credentials for your site? That way, we can dig through your code to see what's different and causing the auto-loader to fail.

Thanks,
Alex

We found the cause of the problem. When the System - GAnalytics plugin is enabled, it's trying to load something in our component's admin area. It seems like that analytics component has it's own model named "Profiles", which is what our view is called. The system plugin is incorrectly detecting that a view named Profiles is loading and trying to load their profile model. There should be extra checks in that plugin to make sure that the view is actually in their component, not in any component.

If you disable the System - GAnalytics plugin, the message goes away.

There's nothing we can do to prevent the error message. It's completely caused by the other extension. From what we can see though, it shouldn't cause you any functional issues.

I'd contact the developer of that extension if you require a resolution.

I hope that helps explain, and thanks for your patience. This was not an easy issue to track down due to the obscure conflict.

Thanks,
Alex