Forum
You are not logged in. Please note that you need to log in before posting.
#1 2010-06-08 21:16:40
- mariodac
- Member
- Registered: 2009-09-03
- Posts: 49
Another BUG
Algis
I'm sorry; I must sound like a broken record...same thing
Ok this one is when rescheduling an appointment
From Admin, reschedule customer appt, confirmed appt and error is shown below, although the rescheduling is complete once you hit the browser back button.
I tried it on a clean installation and received the same error
-------------------------------------------------------------------------------------------------
Warning: Illegal offset type in isset or empty in /home/body/public_html/schedule/core/lib/ntsObject.php on line 79
Warning: Illegal offset type in isset or empty in /home/body/public_html/schedule/core/lib/ntsUserIntegrator.php on line 368
MySQL error - 1054: Unknown column 'Array' in 'where clause'. The query was:
SELECT
*
FROM
ha40_users
WHERE
ha40_users.id = Array
LIMIT 1
Warning: Illegal offset type in /home/body/public_html/schedule/core/lib/ntsUserIntegrator.php on line 377
Warning: Illegal offset type in /home/body/public_html/schedule/core/lib/ntsUserIntegrator.php on line 381
Warning: Illegal offset type in /home/body/public_html/schedule/core/lib/ntsObject.php on line 86
Warning: Illegal offset type in isset or empty in /home/body/public_html/schedule/core/lib/ntsObject.php on line 79
Warning: Illegal offset type in isset or empty in /home/body/public_html/schedule/core/lib/ntsUserIntegrator.php on line 368
MySQL error - 1054: Unknown column 'Array' in 'where clause'. The query was:
SELECT
*
FROM
ha40_users
WHERE
ha40_users.id = Array
LIMIT 1
Warning: Illegal offset type in /home/body/public_html/schedule/core/lib/ntsUserIntegrator.php on line 377
Warning: Illegal offset type in /home/body/public_html/schedule/core/lib/ntsUserIntegrator.php on line 381
Warning: Illegal offset type in /home/body/public_html/schedule/core/lib/ntsObject.php on line 86
Warning: Illegal offset type in isset or empty in /home/body/public_html/schedule/core/lib/ntsObject.php on line 79
Warning: Illegal offset type in isset or empty in /home/body/public_html/schedule/core/lib/ntsUserIntegrator.php on line 368
MySQL error - 1054: Unknown column 'Array' in 'where clause'. The query was:
SELECT
*
FROM
ha40_users
WHERE
ha40_users.id = Array
LIMIT 1
Warning: Illegal offset type in /home/body/public_html/schedule/core/lib/ntsUserIntegrator.php on line 377
Warning: Illegal offset type in /home/body/public_html/schedule/core/lib/ntsUserIntegrator.php on line 381
Warning: Illegal offset type in /home/body/public_html/schedule/core/lib/ntsObject.php on line 86
Warning: Illegal offset type in isset or empty in /home/body/public_html/schedule/core/lib/ntsObject.php on line 79
Warning: Illegal offset type in isset or empty in /home/body/public_html/schedule/core/lib/ntsUserIntegrator.php on line 368
MySQL error - 1054: Unknown column 'Array' in 'where clause'. The query was:
SELECT
*
FROM
ha40_users
WHERE
ha40_users.id = Array
LIMIT 1
Offline
#2 2010-06-08 21:29:57
- mariodac
- Member
- Registered: 2009-09-03
- Posts: 49
Re: Another BUG
A few more things I noticed with this BUG
once you go back to the appointment (popup page) the information for the user is not listed, all it says is ACTIVE but username and the other fields are blank.
ON the clean install the reschedule email was sent but on the current working install somehow it failed to send the reschedule emails.
Also after you try to reschedule and then reject the appointment, NO email is sent out
If you just reject an appointment that has not been rescheduled -- then the email is sent out
Thank you
Last edited by mariodac (2010-06-08 21:37:41)
Offline
#3 2010-06-10 21:10:23
- mariodac
- Member
- Registered: 2009-09-03
- Posts: 49
Re: Another BUG
Algis
Is this one also resolved in 4.2.3 ??
Thanks
Offline
#4 2010-06-13 17:04:22
Re: Another BUG
Hello,
please take my apologize for this flow of new bugs, they appeared after new recurring apps feauture introduction. I'm doing my best to react and fix everything in shortest time.
Thank you for your time and patience.
This reschedule bug is fixed in ver. 4.2.4
Offline
