Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

new ticket error #261

Closed
ngodkin opened this issue Dec 6, 2013 · 5 comments
Closed

new ticket error #261

ngodkin opened this issue Dec 6, 2013 · 5 comments
Labels

Comments

@ngodkin
Copy link

ngodkin commented Dec 6, 2013

I have a test server setup that basically is a mirror of our live server. I upgraded the test server, without errors, to the new release yesterday( osTicket (v1.8.0-rc2-100-g18e9350)) to test out some of the new features. Its a LAMP setup: CentOS 6 apache 2.2.15 mysql 5.1.69 php 5.3.3. When i create a new ticket, i receive this error:

Also, I made the e-mail field a drop down selection list with the list feature, if that is of any help.

Warning: mysqli_stmt::bind_param(): Invalid type or no types specified in /var/www/html/include/class.orm.php on line 889 Fatal error: Uncaught exception 'Exception' in /var/www/html/include/class.orm.php:908 Stack trace: #0 /var/www/html/include/class.orm.php(927): MysqlExecutor->next() #1 /var/www/html/include/class.orm.php(363): MysqlExecutor->getArray() #2 /var/www/html/include/class.orm.php(403): ModelInstanceIterator->fillTo(0) #3 /var/www/html/include/class.orm.php(312): ModelInstanceIterator->offsetGet(0) #4 /var/www/html/include/class.orm.php(136): QuerySet->offsetGet(0) #5 /var/www/html/include/class.user.php(81): VerySimpleModel::lookup(Array) #6 /var/www/html/include/class.ticket.php(2043): User::fromForm(Array) #7 /var/www/html/open.php(47): Ticket::create(Array, Array, 'Web') #8 {main} thrown in /var/www/html/include/class.orm.php on line 908

@greezybacon
Copy link
Contributor

Could you apply the patch from #268 and say if that fixes it?

@ngodkin
Copy link
Author

ngodkin commented Dec 10, 2013

I applied the changes, and receive the sames error as above. Is it calling on the new function __toString?

@greezybacon
Copy link
Contributor

Has this been corrected in later versions of the develop branch?

@greezybacon
Copy link
Contributor

Bump

@greezybacon
Copy link
Contributor

Please reopen this issue if you're able to produce the issue again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants