Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Just released Live Support for osC


Guest

Recommended Posts

Does anybody know why the helping status is not updating in the database??

 

Therefore causing the live help not to show busy to a second user trying to contact Admin?

 

Instead it opens 2 conversations, and continues to show all conversations to both users wanting help.

Bit of a problem really.

 

I had the same isues of not updating the database to end sessions, but I got that fixed.

But for some reason it is not telling 'helping' in the db whether I actually am or not.

 

Any ideas?

I'm sure I am just missing something simple, but it is bugging me!

 

Thanks

 

CC.

Link to comment
Share on other sites

  • Replies 93
  • Created
  • Last Reply

Top Posters In This Topic

I had the same isues of not updating the database to end sessions, but I got that fixed

 

what fix did you come up with.

 

send me what is happening to my email address and I will look at it to see what I can do to fix the problem

 

Mike

Link to comment
Share on other sites

Hi!

 

I have my tep in different languages.

The live support is working nice with the default language, but when I switch to e.g. spanish and click the support button, the window pops up and it shows the shop in the window.

 

I tried around and around, but its always the same.

 

Someone has an answer?

 

Greets,

 

Bj?rn

Link to comment
Share on other sites

Bugger I have not kept up with this thread.

 

I still have the problem of the support not showing as busy.

It still isnt updating the DB to show busy.

 

I will email my code to you Mike.

Will be with you soon.

 

CC.

Link to comment
Share on other sites

I am just looking at the table structure in the data base. I really don't know if this is a problem or if this is how it is supposed to be.

 

CREATE TABLE ls_techs (

 tech_id int(11) NOT NULL auto_increment,

 support_tech varchar(20) NOT NULL default '',

 password varchar(25) NOT NULL default '',

 support_group varchar(255) NOT NULL default '',

 status varchar(10) default NULL,

 helping varchar(255) NOT NULL default '',

 PRIMARY KEY  (tech_id),

 UNIQUE KEY yech_id (tech_id)

) TYPE=MyISAM;

 

the UNIQUE KEY has yech_id , is this what it should be?

Link to comment
Share on other sites

That is a typo.

 

should be ls_techs

 

for those of you that are getting the error

 

Live Support is currently open

Currently only 1 window can be open

 

right now you need to currently open up phpMyAdmin, locate ls_techs and change status to "no"

Link to comment
Share on other sites

That is a typo.

 

should be ls_techs

 

for those of you that are getting the error

 

Live Support is currently open

Currently only 1 window can be open

 

right now you need to currently open up phpMyAdmin, locate ls_techs and change status to "no"

 

So are you saying this:

CREATE TABLE ls_techs ( 

tech_id int(11) NOT NULL auto_increment, 

support_tech varchar(20) NOT NULL default '', 

password varchar(25) NOT NULL default '', 

support_group varchar(255) NOT NULL default '', 

status varchar(10) default NULL, 

helping varchar(255) NOT NULL default '', 

PRIMARY KEY (tech_id), 

UNIQUE KEY yech_id (tech_id) 

) TYPE=MyISAM;

 

Should actually be this:

CREATE TABLE ls_techs ( 

tech_id int(11) NOT NULL auto_increment, 

support_tech varchar(20) NOT NULL default '', 

password varchar(25) NOT NULL default '', 

support_group varchar(255) NOT NULL default '', 

status varchar(10) default NULL, 

helping varchar(255) NOT NULL default '', 

PRIMARY KEY (tech_id), 

UNIQUE KEY ls_techs (tech_id) 

) TYPE=MyISAM;

 

CC.

Link to comment
Share on other sites

This seems like a great contribution, but a little buggy for me just yet. Anyone know of anything a little more stable? I have a customer in a rush, so i don't really have time to debug this or write my own....

 

Will definitely keep an eye on this area!!

 

-M

Link to comment
Share on other sites

  • 1 month later...

I tried to follow the updates, but i went wrong along ths line. I am getting this error in the admin section when i click on the tools/live support

 

TABLE_LS_VARIABLES doesn't exist

 

select v.color, a.ls_variable_option from ls_variables v, TABLE_LS_ATTRIBUTES a where v.color = a.ls_attributes_id

 

I looked and the sql script did not create these two tables and they were not in the install text to add the define statemnts to the application_top.php

 

 

Can anyone help me out ??????

 

Thanks

Link to comment
Share on other sites

I don't know if this is an error or even if it has been brought up before. In the installation instructions it says:

copy the following files over to your CATALOG folder

(these files go in the root directory of your catalog folder)

 

- live_support.php

- ls_comm_exit.php

- ls_comm_main.php

- ls_comm_top.php

- ls_exit.php

- ls_infobar.php

- ls_start.php

The file ls_comm_exit is not in the catalog directory of the module installation files. This is true for v12c, v12d and v13. Is this a typo or is the file missing?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...