Topic-icon Twitter registration/login - disable user ID and name editing

Active Subscriptions:

None
10 years 5 months ago #38813 by none
Hi Alex,

I upgraded to 5.2.1. I have a new issue. Changing the frontend language by Falang the custom Twitter button disappears. Google, Facebook button are ok.
The topic has been locked.
Active Subscriptions:

None
10 years 5 months ago #38814 by none
...also when I set the username to "generated but disabled" it just doesnt work. I still can change it, edit it on frontend.
The topic has been locked.
Support Specialist

Changing the frontend language by Falang the custom Twitter button disappears.

I can't imagine why this isn't working. Can you let me know where we can test on your site and any steps we need to take to do so?

also when I set the username to "generated but disabled" it just doesnt work. I still can change it, edit it on frontend.

Again, let us know where we can test. This is working for us, but it's possible we missed something.. but need to see it in action to understand what.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
10 years 5 months ago - 10 years 5 months ago #38832 by none
Hi Alex,

Here is my test site url: reloaded.vinnumber.info/
The absence of Twitter button on other language was Falang's fault. I still dont know how but it works now.
Here is a screenshot about my "Disabled" settings in JFBconnect, but you can go to my test page and try to login by twitter and you will see that once you returned from twitter page you still will be able to edit the name and the username as well.

File Attachment:


Regards
Last edit: 10 years 5 months ago by none.
The topic has been locked.
Support Specialist
I just tested. I am not able to edit the username field whatsoever. It 'looks' like the other fields, but I can't click into it or, if I tab into it, I can't type anything.

The 'Name' field is not something we have a disable setting for.. so it's editable.

Can you test again just for the username field and let me know if that's working as expected. The Name field request was something I didn't see in your original request and not something we have the option to hide or disable right now.

Let me know if the above is working as expected and we can make progress on the rest.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
10 years 5 months ago #38847 by none
Hi Alex,

Its been 100% my fault. Sorry, you are right. I didnt even try it because I expected it to grey out where I cant even click in the field. But its working as expected. I cant delete anything from the field or edit.
Username would be the same thing if you could implement the same feature in the future versions.

Thanks Alex
The topic has been locked.
Support Specialist
No problem. Glad we could help explain a little. Just so you know, you can add specific styling to the disabled inputs to make them greyed out or otherwise obvious to the user, like:
input:disabled {
color: red;
background: blue;
}
That can go in your template's CSS stylesheet.. the exact location is specific to each template though.

I hope that helps! We'll look into adding an option to disable the 'name' field as well in an upcoming release. If it's critical for you, we should be able to help you with a line of code or so that would do it now as well.

Thanks,
Alex
The topic has been locked.