TOPIC: [SOLVED] Categories not saving with new events - site broken

Hi Nathan,

Thank you for following up on this thread. I am trying to understand your last post.

Once we update the package again and you update, you'll be fine.

Are you saying that the issue has been resolved and will be included in the next release? I am running the most recent 2.8.7 on j2.5.

Thanks

Nathan,
As the fix for this is merely redirecting database requests, couldn't you provide the code for us to apply while you guys put together the next release package?

My client is understandable upset by the length of time it's taking to fix the issues with adding events and saving categories?

I realise you have quality standards for releases but this issue has been out there for sometime and effectively cripples DTReg.

This is critical!!! Running Joomla 2.5.14 and DT Register 2.8.7

We are seriously considering dropping dtregister as an event system. Every update are a mess and most of the times buggy.

Now we have the same problem as the subject describes, though also old events wont change categories. I do not care what the technical issue is, I want the system to function.

I can't wait until a new release because we are in production!!
Not beta, not alpha, not preview!

As sead, this is critical, and I do not want to experience this anymore.
If dt register does not give us an easy fix immediately when such bugs appear, you are out. Easy as that!

Nathan

Could you please share the fix for this? I opened a ticket and I really don’t need a full update just the files that are affected or even tell me what files and the code to change. My client is extremely frustrated with the product as we seemed to have fixed the issue with double billing but now caused another issue.

We're in the same boat right now as you.

We've delayed out registration launch by a week over this. The software is crippled and we're totally out of time.

We have the same issue with our installation as well, but to put things into perspective, the issue is only a problem in the back-end, not customer facing. Annoying, but not crippling.

That said, even little things like this bring the product's integrity and stability into question.

There have been a number of updates since the issue was first raised, well over a year ago. It is concerning this has not been fully resolved in an update by now.

I'm a bit gun shy with a "fix" I would prefer a stable release that resolves the issue. Is there an ETA?