Step by step implementation kind of frustrating

I am getting frustrated over the limited implementation chosen for the step by step registration. It is more a tab by tab registration.

But the decision to implement it this way did not take into account that steps on registration != tab positions on profile.

So for my use case to have a 4 step registration with having the fields grouped in a logical way it is getting terribly complicated to rearrange them for profile view.

The only way I see is to use the main field for registration layout and the add a second field for each field you want to have on a different position for profile view which is a custom HTML field to simply show the contents of the original field.

This is ridicolous. But it is getting better: Custom HTML fields cannot be ajaxified. Which means that the fantastic ajaxtext function does not work on them and is utterly useless. The only way I see to solve this is to duplicate the field connect and add an autoaction which kind of synchronizes the database contents between them.

So basically for a simple task like having a field shown on different position for registration and profile view with full functionality I have to create 2 times the same field, have it 2 times in the database, have to maintain it 2 times and have to take care of the auto action logic to make sure that the sync works.

So I think this approach is not a modern one and it is not good. I think step by step registration must have its own display logic as it displays. The way it is it creates too many tabs which are useless often, when there is only one single field in there to be filled out.

I believe CB2.0 requires a major rework here to decouple the registration process from the profile layout.

Profile View, Profile Edit, and Registration layouts all roughly relate to one another. Once we've our layout editor and XML frontend all these issues go away. What you're wanting is absolutely planned (decoupling of the views), but for now this is how it works. I agree the current usage is not ideal and we absolutely would've loved to of have this improved before releasing CB 2.x, but the reality sets in that there would of been no CB 2.x this year if we kept delaying to add such features. So we opted for a gradual improvement, which we believe fairs much better for our users.

krileon wrote: Once we've our layout editor and XML frontend all these issues go away. What you're wanting is absolutely planned (decoupling of the views)

This fuels some hope. Thanks. Now hopefully the rewrite of Gorupjive brings a facebook like multifunctional wall lots of my issues are gone. I hope to see this soon as it is mandatory for an uptodate approach.