Catchable fatal error after upgrade

1QuickSI

I just upgraded from 1.8.0.2 to 1.8.1 (both down loaded from this site). After the upgrade when I try to access a ticket I get:Catchable fatal error: Method DynamicFormEntryAnswer:() must return a string value in /home1/computm1/public_html/OSTicket/include/class.ticket.php on line 229I saw this over on GitHub:https://github.com/osTicket/osTicket-1.8/issues/300The code from clonemeagain's post said it fixed the issue but not sure how to apply the diff. Can I manually apply this to the file? Is this going to be fixed in the production version?

ntozier

That diff looks like its made for a different version thatn 1.8.1. (espec since that thread was started three months ago)edit include/class.dynamic_forms.phplocate line: 731-733Looks like: function __toString() { return $this->toString(); }If the diff is right change the return to: return ($this->toString()) ? $this->toString() : '';One of the devs posted 11 days ago saying that "We've fixed a couple instances of this error in the develop and

develop-next branches. Can you check to see if your instance has been

corrected?"

1QuickSI

Found: function __toString() { return $this->toString(); }

Tried to change it but did not work.

ntozier

Then you should probably update the thread over on github reporting your specific error.

1QuickSI

While I can help in finding and reporting issues as I come across them, I do not have the time to be bouncing between places to report an issue.

I can also duplicate this error by managing forms and changing 1 of the options from short answer to choices in V1.8.0.2

So I believe this to be a much deeper issue overall.

Thank you for your suggestions.

1QuickSI

I was able to "fix" the 1.8.1 site by changing the one of the forms under ticket details from "Choices" to "Short Description" This is the same place as I noted in my last reply.Hopefully this isolates the issue a bit more for the developers.

1QuickSI

In 1.8.0.2 It was configured as short answer and the error occurred when I changed it to choices.In 1.8.1 It was configured as choices and the error disappeared when I changed it to short answer.