Authentication Form Not Showing

Status
Not open for further replies.

mattbyzz

Customer
Basic Certified
Joined
Mar 14, 2022
Messages
3
Reaction score
0
Hi,

The live chat widget is installed on my website, however the authentication form is not showing (email and name or any combination thereof) and just a white space is shown. If I enable the GDPR setting, the tick box is shown but nothing else.

It is the same when I visit the chat link directly and it makes no difference which configuration I use.

I need to be able to pre-populate the name and email fields, and have read the thread on this, however the fields are not showing and even with the correct configuration the name still comes through as the generic webvisitor.

Am I missing something in the settings here?

Matt
 
Hi @mattbyzz are you using the wordpress plugin or the HTML code? is your pbx up to date running 18.0.8.917?

are you configuring the live chat from the webclient or desktop app?

could you please share the website in order to review the live chat. Thanks!
 
Hi Alejandro,

I am just using the html code as this is currently installed on a local laravel system. It is not just when the chat is embedded though, and I have attached a screenshot, as well as the chat link. Yes the PBX is the latest version 18.0 (Build 935).

https://byzzplus.3cx.uk:5001/callus/#LiveChat293649
 

Attachments

  • Screenshot 2023-08-30 at 08.30.41.png
    Screenshot 2023-08-30 at 08.30.41.png
    139.8 KB · Views: 2
Привет, Алехандро,

Я просто использую html-код, поскольку он в настоящее время установлен в локальной системе laravel. Однако это происходит не только при внедрении чата, и я приложил скриншот, а также ссылку на чат. Да, на УАТС установлена последняя версия 18.0 (Сборка 935).

https://byzzplus.3cx.uk:5001/callus/#LiveChat293649
Я вижу это так
11.jpg
 
Я вижу это так
Thanks Paurus, I have now worked out that it was because the cookie on the local machine had stored the value webuser as the name. I can now see that this is hardcoded and cannot be changed as this comes through to the 3cx system based on IP by the looks of it.

Thanks for your help with this.
 
Thanks Paurus, I have now worked out that it was because the cookie on the local machine had stored the value webuser as the name. I can now see that this is hardcoded and cannot be changed as this comes through to the 3cx system based on IP by the looks of it.

Thanks for your help with this.
I'm glad that everything worked out for you.
 
Status
Not open for further replies.

Forum statistics

Threads
111,973
Messages
590,078
Members
164,896
Latest member
sameage