API Error(s) Create Failed Name required

[tldagent]

When I send emails to my support ticket system they seem to work fine.

However when my partner does it from the UK in AOL, instead of opening a ticket, I get this error:

The subject line of the email says: API Error(s)

The content says: Create Failed Name required

Did a search and haven't found any solutions or similar errors that others have experienced with this.

My emails are piped to the API.

Thank you in advance for your help with this.

[cheong999]

I am encountering this problem of "Create Failed Name required" too. This is sent in an email to the administrator email account.


I noticed that the error message gets throwed out from line 85-91 of pipe.php as follows:

if(!$ticket){ //New tickets...
$ticket=Ticket::create($var,$errors,'email');
if(!is_object($ticket) || $errors){
api_exit(EX_DATAERR,'Create Failed '.implode("\n",$errors)."\n\n");
}
$msgid=$ticket->getLastMsgId();
}else{

.....

Is there anyone is able to help?

[tldagent]

I don't know if there's any help. Seems as though Open source collaboration isn't working within this Script.

While it's appreciated that this component is available, I do wish that there were better collaboration efforts regarding this. That's what a wiki is for.

[peter]

osTicket wiki is reserved for "How To" documentation and not meant to be a discussion board. Otherwise it becomes like a forum making it pointless for documentations. In this particular case you wanted to use a wiki for a bug report :confused: It is exactly the type of things I want to keep out of the wiki.

It is helpful IF you could use the bug tracker (http://osticket.com/forums/project.php?projectid=1)to file bug reports. The bug in question is fixed in RC3 release.

[tldagent]

osTicket wiki is reserved for "How To" documentation and not meant to be a discussion board. Otherwise it becomes like a forum making it pointless for documentations. In this particular case you wanted to use a wiki for a bug report :confused: It is exactly the type of things I want to keep out of the wiki.

It is helpful IF you could use the bug tracker (http://osticket.com/forums/project.php?projectid=1)to file bug reports. The bug in question is fixed in RC3 release.

Actually, I wasn't trying to say the wiki documentation should be the bug report at all or a forum. What I'm saying is a wiki could be used for collaborative documentation... Meaning the users of the OsTicket could assist in writing and updating the wiki documentation. That's the whole idea behind a wiki. This the documentation can be put together by those who actually use the product. It is always much more effective. Then you can focus more of your time on the development of it. There are several instances during my installation where the wiki documentation didn't quite do the trick. If I'd have had access to it, I would have updated it right then and there.

As far as the forum, many questions go unanswered, like this one. How was I to know it was a bug when I never received an answer to begin with and I posted a link to the question in another thread on this forum... which wasn't answered there as well.

Hope to see this thing grow. I admired the efforts of the past osticket and this one seems to be ok but as of right now, I've not actually been able to get it to work properly and it has not been easy getting answers.

Thanks for your efforts. I will update to the latest version and see if I can get it to work.

[peter]

tldagent,

I agree that the documentation should be put together by users using the product. The problem with giving open access to the wiki is the fact that the documentation can end up being a forum like discussion and require policing to just make sure it stays accurate and clean (no spam). At the moment access to the wiki depends on forum reputation which in turn is based on posts and general forum participation. The assumption being forum members who're active answering questions and helping other members know the system best. Of course this is not always true but it is a trade off we are willing to take to keep the documentation to the point.

I don't think it is reasonable to expect every forum questions to be answered. I can not possibly answer every question posted in forum discussions due to limited time at hand. As you know, this is a community forum with relatively small number of members with even smaller number active answering questions compared to the old osTicket forum. The current osTicket is at it's infancy at best, not even 2 months old!

That said, I think it would be helpful if members like yourself (see posting history (http://osticket.com/forums/search.php?searchid=13625)) join in and help the community grow by participating more instead of simply complaining. That would be a give and take collaboration we can all be proud of as osTicket community.