disable and delete account fields not showing

I have just tested the disable account function and found that once the account has been disabled by the user they are no longer able to log into their account.
I take it they have to contact the admin to have it reinstated?

I would have thought that the user should still be able to log in and re activate the account without having to trouble admin.

I also discovered that upgrading by installing the new 1.9 comprofiler deleted the general configuration settings. Most importantly it set the allow user registration field to be the same as global setting but as that is disabled for cb it meant that no one could register. I wondered why I had been getting no new registrations since upgrading.
There should be a warning at least in the ReadMe file so that one can check this.

Anyway at least my users can now suspend or delete their own accounts and that is great, thanks.

I have just tested the disable account function and found that once the account has been disabled by the user they are no longer able to log into their account.

Yup, that's what it's supposed to do. It completely blocks the account using Joomlas block account variable.

I take it they have to contact the admin to have it reinstated?

Yes, you can use whatever contact form extension you like for them to contact you.

I would have thought that the user should still be able to log in and re activate the account without having to trouble admin.

Currently it does not do this. It is planned to be improved, but I did not want future plans to delay CB Privacy release.

I also discovered that upgrading by installing the new 1.9 comprofiler deleted the general configuration settings. Most importantly it set the allow user registration field to be the same as global setting but as that is disabled for cb it meant that no one could register. I wondered why I had been getting no new registrations since upgrading.
There should be a warning at least in the ReadMe file so that one can check this.

That should never be the case. If an existing CB install is present it doesn't touch configuration. If you did a migration though that might explain a loss of some data.

I don't think I did a migration I just uploaded the comprofiler.zip workflows and login files via the main extension installer as the readme file instructed.

But today I am told by a person who wants to subscribe that she got no confirmation email. I found another person who hadn't finalised their registration so I sent them both confirmation emails.

I then registered a test user but there was no confirmation mail sent and using the cb user management to resend the confirmation did nothing.
I have also discovered that the profile logger emails are being sent to admin but but the forgot username and password emails from the login page are not.

I am quite sick at the moment but I can't see any reason the mails are not being sent. I do know that until I upgraded to 1.9 everything was working as it should do.

Try using Mass Mailer within CB > User Management by selecting your users checkbox and clicking the Mass Mailer button then see if the email sends to your self fine. If not then there could be some sort of mailer configuration issues or maybe even a mail server issue.

I used the mass email first so it wasn't that. While searching the forum I found a post that said use the [confirm] tag in the pending email.
I tried that and it started sending out confirmation emails.

But this pisses me off no end. In all prior versions of CB I have never filled in anything in the email part of the setup and people have gotten their confirmation emails. It appears that you have removed the default system of having the appropriate email sent depending on whether the subscriber settings are admin approved self subscribe or neither.

You know use the one email form and it is up to the admin to put tags in the email. That is bullshit.

I previously hesitated to upgrade to 1.9 because everything I had done was working ok. My fears were realised because NOWHERE in the upgrade instructions did it talk about this change and warn that you would have to re do the confirm email.
That is one of the first things that should have appeared in the upgrade instructions.

CB only sends an email if you've configured it to send an email. As long as I've been on the team this has always been the case. For confirmation email to send you need to have the Pending email configured in CB > Configuration > Registration. The same is said for the Welcome email.

You should not have to redo any of the emails. It should've kept your existing configuration. If it didn't then it should've at least had the default (both emails are default configured properly). So something happened in the upgrade process to clear those parameters or you never configured them to begin with.