well if its only when you use a certian module then that clearly points fault at that module lol.

Trust me, brother- I have done all I can to try to get a case with the devs. All they want to do is clear my cache and scoot me along, only to encounter the issue again a few days later. I told them exactly where /when /why gave codes, produced logs, and they say "if we can fix the error, we cannot escalate the case to the devs"

It's so frustrating that they will not own up and fix the error... Could it possibly be because of a server downgrade? Or is this simply a flawed code that they do not wish to address? It is not something that will be fixed soon, that is for sure- but they will not even assist an integration to their merging company. They say use us or use them- although you must pay for data migration if you wish to switch to a non-broken program. We are comfortable not making any change, but they are forcing the changes on us.

Me no likey.

This post was edited by TheDiscoveryChannel on Jan 30 2013 02:26pm