I'm going to make one big obvious statement here since this thread is being spread around on Internet forums to incite dramatic and FUD filled responses.
The "errors" are because we, the developers, increased the error reporting level in freepbx 13 dramatically. It's very high now. The error reporting change was done several months ago and was talked at length in at least two recent blogs (the reasoning and such). Unfortunately, It broke many things but it's also solved many things..
This is both good and bad:
Good in that it stops crappy code and helps to fix buggy code. Freepbx has long since been attacked for its subpar code. We want to make this a thing of the past.
Bad in that many unsupported modules break. Are they hard to fix? No not really and if you set your own error reporting level in freepbx (yes it's documented) the module will work just fine. Guess what you can also fix them and we will publish them. Just like what we did for custom contexts last month. More people should just come along and fix things. It helps us all out.
Freepbx itself is very flexible. You can modify the code. Sign your own modules. Change error reporting levels. This is what makes it so open and yes also free.
There are over 40 contributed modules ( https://github.com/FreePBX-ContributedModules ). OSS endpoint is one of them because I work on core freepbx now. The FUD spreaders like to make it seem like there is a different motive but there's not. I like to spend my free time cycling and building a life. I don't want to code 24/7. Does anyone want to work 24/7? Is the development of open source endpoint manager more important than developments in freepbx? Our stats this last year speak for themselves.
There is a recent thread on the PIAF forums where it looked like they were going to revive the project. Which we were happy for (me especially!). Unfortunately the last few posts in the topic appear to be a ploy to poke the bear (their words), speculate about me (wrong information) and insinuate that the high error level was enacted to break this single module because it was being talked about in the PIAF forums. It doesn't look hopeful at this point. It's a shame people believe the FUD they read in other places but I can't control that.
I suggest if you really want OSS Endpoint to work and be updated that you talk to the group of individuals on PIAF and help them get back on track. One can only hope they will listen.
Here's the commit from May 5th well before internet speculation and rumors.