I will ask Guillermo to give us all a rough idea on when the current Forge issues will be resolved. If it's going to be a while, I'll try and free up some time to look into it myself. Apologies, I can imagine how frustrating it must be, the Forge has had these issues for a long time now.
Cheers Darren On Jan 25, 12:27 pm, ken <[email protected]> wrote: > I checked the source and pluginActions::executeUpdate is not yet > implemented. So it's not really a bug but a missing feature. Can > somebody tell me how the update mechanism works? > > On Jan 25, 8:15 pm, SamGoody <[email protected]> wrote: > > > > > The forge update button is still not working. > > > The MooRTE plugin now has nearly 150 downloads. > > > And every one of them is broken. > > > Shortly after committing we found a major issue - not sure how it > > passed through testing - and went to correct it. > > > Now, nearly a month later, with dozens of attempts to update it > > ignored, I still have the same buggy commit up there. > > > Unsurprisingly, this has been a negative experience with our users - I > > don't know how many we still have. > > > A bug report was filed on the github branch, the IRC channel was > > haunted, to no avail. > > > Please; The forge is supposed to help the community, I beseech, beg, > > implore, and request if anyone who can look into this issue can > > please, please look into it. > > > Sincerely, a poor, desperate, Mootools developer. > > > On Jan 11, 9:32 pm, Aaron Newton <[email protected]> wrote: > > > > FYI, the principal developer of the forge, Guillermo Rauch, has been on > > > vacation for the last three weeks. I heard from him today; expect to see > > > some action on this stuff relatively soon. > > > > On Mon, Jan 11, 2010 at 11:23 AM, pradador <[email protected]> wrote: > > > > I've had the same problem for a while now with two of my plugins. The > > > > third one updates fine though even with new tags and changes. The > > > > update just stops at the "Verifying JS files" with no error message on > > > > Safari 4. > > > > > On Jan 11, 1:08 pm, Ryan Rampersad <[email protected]> wrote: > > > > > I had this very same problem last week and I never was able to fix it. > > > > > > If you take a look with firebug, you might notice that that step > > > > > returns > > > > a > > > > > 500 internal server error. > > > > > > On Mon, Jan 11, 2010 at 11:50 AM, SamGoody <[email protected]> > > > > > wrote: > > > > > > Yes. It simply stops. > > > > > > 4 hours later it still says: Verifying README.md and package.yml > > > > > > Loading indicator a little past the halfway mark.. staying put. > > > > > > > Same thing was happening before, only first reaching the 'Verifying > > > > > > JS > > > > > > files' stage. > > > > > > > Tried on Firefox and Chrome (in the hope that it was just waiting > > > > > > for > > > > > > some Mootools response that wasn't being fired). > > > > > > > Any help appreciated > > > > > > > On Jan 11, 2:30 pm, Fábio M. Costa <[email protected]> wrote: > > > > > > > it dont even show an error message? It simply stops? > > > > > > > > -- > > > > > > > Fábio Miranda Costa > > > > > > > Solucione Sistemas > > > > > > > Engenheiro de interfaces > > > > > > > > On Mon, Jan 11, 2010 at 10:02 AM, SamGoody <[email protected]> > > > > wrote: > > > > > > > > Update: I deleted all the old tags, with the thought that > > > > > > > > perhaps > > > > that > > > > > > > > one of the older projects was causing issues. > > > > > > > > > Now the only tag is the current one: 0.55 > > > > > > > > Didn't help. > > > > > > > > > Sam > > > > > > > > > On Jan 11, 12:33 pm, SamGoody <[email protected]> wrote: > > > > > > > > > The Forge is not accepting the update for the MooRTE class. > > > > > > > > > > Class:http://mootools.net/forge/p/moorte > > > > > > > > > > GITHub project page:http://github.com/siteroller/moorte > > > > > > > > > > v0.54 was hanging on the words 'Verifying JS files'. > > > > > > > > > v0.55 hangs on the "Verifying README.md and package.yml" > > > > > > > > > The package.yml is the same as was during initial (accepted) > > > > commit > > > > > > > > > except the update of the version number. > > > > > > > > > I don't know what I did to the README that would upset the > > > > updater. > > > > > > > > > > How do I go about finding the err? > > > > > > > > > > Thanks guys! > > > > > > -- > > > > > Ryan Rampersadwww.ifupdown.com
