TOPIC: Custom Fields not displaying / updating

I just upgraded to DT Register 2.6.8 and have the same problem. It's pretty serious because my client relies on those custom fields and they have updates they need now.

I asked the host if they could upgrade PHP from 5.1.6 and they said:

"What version are you looking to go to? There are lots of different versions. It probably doesn't matter, however. The system that you are on only supports PHP 5.1.x. It does not support 5.2+. Is that a requirement?"

Is it a requirement? Is there anything else I can do? Can I un-install 2.6.8 and re-install an older version without affecting the existing data?

Laurie

I went ahead and rolled back to DT Register 2.6.5 since that seemed easier than getting the host to upgrade its PHP. The rollback fixed the problem, and also fixed the other problem I posted about (pay later records only appear as "failed"). I guess I'll stick with 2.6.5 until you have a more stable upgrade.

This is not a "stable" issue. 2.6.8 is very stable... just in recent enhancements to the custom fields, the need to go beyond PHP 5.1.6 came into play due to a known issue in that version of php. It's not a DT Register problem. We are not going to backtrack so you still will eventually need to get a more stable version of php in place. Anyway...

I've been looking into this with my host. They're running PHP 5.1.6 because they're using Red Hat Enterprise Linux -- they could install a later version for me but would lose RedHat support and be responsible for security updates on their own from that point forward.

So this affects anyone who runs RHEL, it's not an isolated problem. I talked to another developer who had the same trouble and is planning to sit out DT Register upgrades until you have workarounds for the conflicts, or until RHEL 6 comes out, which runs on PHP 5.3. He said you guys have some of the cleanest code he's ever seen -- we're not saying there's anything wrong with DT Register, we're happy customers -- but there IS a conflict here and I wish your response was more complete than "just go upgrade your PHP."