Ok here is a short version of what happened:

Began migrating clients to new billing system once i got clientexec fully installed (mind you I was just using paypal initially). Then I decided it was time for a merchant gateway account (went and got one with an authorize.net reseller). Ok good this far, just tonight added in mcrypt and curl to php4 and well this is where the havok begins. I had done this as I read it was necessary for cc merchant signups thus doing what I had seen is deemed needed. In any case now all signups all the data is not viewable and it sends emails to a local address instead of what is in the system (clientexec). No idea what went wrong or anything I've already placed a ticket in with clientexec, posting here though so everyone who reads here will know about being careful with changes of any kind (as I probably ended up screwing it up somewhere not realizing it even). If anyone has any ideas where to look please feel free to email/PM or post here.

-Justin

Most likely when you upgraded php you went to php 4.3.10

If that is the case then all you need to do is go get the latest ioncube loaders from ioncube.com and use those instead of your older ones.

This hapened to me too, i updated the ioncube loaders and it is working fine now

yup PTNHosting, clientexec finally answered my helpdesk ticket this morning and it turned out to be ioncube, guess I will need to update the loaders sometime when I finally want to upgrade.

-Justin

Originally posted by jschurawlow
... clientexec finally answered my helpdesk ticket this morning ...

You make it sound as if your ticket was open forever. Total elapsed time before you were given the answer was 6 hrs 41 mins

When you are in need 6 hours is like Days :)

PTNHosting yeah I second that, Alberto I do realize it was done is a timely fashion but, least I say the internet doesn't sleep and neither can a billing system. In any case Alberto I suggest posting an announcement or mass emailing customers regarding the ioncube issue with it needing to be upgraded so others like me will not be left in the same boat.

-Justin

There is information on the forums about that, and when you registers, like me, that information was already there. :)

Ah aight, I probably missed it in my searches on there. Undoubtedly I did as I had no idea that there was even an issue with ioncube when upgrading (presumed it would at least work after reinstall with upgrading php). I ended up just downgrading php back to 4.3.9 and adding the mcrypt and curl into my configure args and it worked then once i reinstalled ioncube into it. I would still think it'd be a good idea for clientexec to put in a note about it on their billing system so when people login you'd have it showing up right in front of you. Would make life alot easier then needing to go hunt down details about such a bug that most of us knewer to clientexec had no clue about.

Alberto, thank you for the response on here with regard to this, I had thought it was an mcrypt issue with upgrading php hadn't thought of ioncube even being a cause at all, namely due to the fact that the current data already in clientexec was totally accessible only new data being added was not being read correctly.

-Justin

Not a problem at all. And yes when you are in need, minutes seem like hours.

Take care and see you in our forums.