Forum Replies Created
-
That would be awesome, thanks!
in reply to: New Update Available – v1.0.89Subscribers never have rights to publish, so they never see the edit screens at all anyway. Contributors can edit and submit posts for review, and they should not see these controls when submitting their articles on the backend.
in reply to: New Update Available – v1.0.89ok thanks. I have another question about this update. It is great that post restriction can be done at the post level in the publish box, but how can I hide this feature from non-admins? (I have a contributor role that I don’t want to see these choices at all, just the “submit for review” button as normal)
in reply to: New Update Available – v1.0.89if they change their email address, will the system automatically reverify them via email as it does during registration? if not, is there a way to make this happen? That would solve the security issue I believe because they would always need to verify their email address…
in reply to: Edit page says email is taken for existing userNotice: Trying to get property of non-object in /home/mysiteurl/wp-content/plugins/userpro/functions/template-redirects.php on line 8
Notice: Trying to get property of non-object in /home/mysiteurl/wp-content/plugins/userpro/functions/template-redirects.php on line 9
in reply to: New Update Available – v1.0.89I figured it out!
VERY IMPORTANT (Hopefully this will help others): You must not make fields (like email and password) required on the edit page. One of my admins did this and that was the cause of the problem!
in reply to: Edit page says email is taken for existing userThe form is also giving warnings about the password not being set…which leads me to believe that the EDIT page somehow thinks it is a new REGISTRATION page…Any idea how to solve this?
in reply to: Edit page says email is taken for existing userUGH, this happens for for other users too! I am logged in as admin, I go to their profile to make any changes, and this warning about a taken email shows up. Please help, we can’t launch like this, we need to be able to edit profiles.
in reply to: Edit page says email is taken for existing userignore comment above please that was meant for another issue, not this thread. Sorry.
in reply to: New Update Available – v1.0.89UGH, this happens for for other users too! I am logged in as admin, I go to their profile to make any changes, and this warning about a taken email shows up. Please help, we can’t launch like this, we need to be able to edit profiles.
in reply to: New Update Available – v1.0.89See my comment above, they are pasted in
in reply to: New Update Available – v1.0.89Yes, I had purposely had all PHP errors showing in my code while trying to clean up my site. I just thought you would want to know about the errors. I know they are hidden when I am not showing errors, but they are still there. thanks.
in reply to: New Update Available – v1.0.89Latest plugin shows these errors when I try a search for content that does not exists (a search with no results):
Notice: Trying to get property of non-object in /home/mysiteurl/wp-content/plugins/userpro/functions/template-redirects.php on line 8
Notice: Trying to get property of non-object in /home/mysiteurl/wp-content/plugins/userpro/functions/template-redirects.php on line 9
in reply to: New Update Available – v1.0.89I was finally able to fix this myself, hopefully this will help someone else:
1. Originally, I kept trying to remove the bad data from the serialized string in the DB, but every time I did UserPro would revert to the default fields, erasing all my data, and I had to keep restoring my backup with the bad data.
2. The key to solving this was the a:xx number at the beginning of the field. Very important that the xx match the number of items in the serialized data, or it will all be lost. you can easily figure out this number by counting all your fields (including the errors) in the userpro admin under role based fields.
3. The field is in the options table, and it is called “userpro_fields”. Remove the offending data (I did it by editing the field in PHPmyadmin), make sure the number is correct, then save.
Like I said, hopefully this will help someone else, because good luck getting any support here.
in reply to: strange error when viewing role based fieldsI tried downloading my db and applying a serialization fix from here: https://github.com/Blogestudio/Fix-Serialization
BUT when I reuploaded my DB, all fields were gone from UserPro!! So I had to restore my backup and I am back to the problem above…Can you please suggest a fix that will not delete all of my painstakingly entered fields?
in reply to: strange error when viewing role based fields