Sam, The reason I closed the GitHub issue and the uservoice thread is because the issue was fixed at the time. I personally emailed all the authors that had been having problems and all were resolved, except yours, and the issue had to do with special characters in tags. Since it only affected updates, and you were experiencing it as well, I wrongly assumed your had been fixed.
This issue will be resolved before monday. Sorry for the trouble. On Sun, Mar 7, 2010 at 3:05 AM, SamGoody <[email protected]> wrote: > In a desperate plea to fix the update/submit '500 internal error' bug: > > Its been another month and a half. > > My GITHUB issue report has since been closed. > > Several others on the UserVoice page have the same frustration. > > But the Forge issue has not been dealt with. > > We are closing in on 350 buggy non-working downloads. > > We have another plugin waiting in the wings. > > But the Forge issue has not been fixed. > > Please, please - is there someone that could possibly help Guiller to > fix this? > The forge is really a wondrously good thing, and I appreciate the work > that has gone into it. > But it really is important that the Forge not mess up the hard work of > us plugin authors - which is what it has so far done for me. > > The plugins are: > MooRTE - Wysiwyg editor: http://mootools.net/forge/p/moorte > CollerRoller - Color Picker: > http://github.com/siteroller/ColorRoller-MooTools-Color-Picker > > I don't believe there are any special characters anywhere. There may > be something in the package.yaml files done wrong, but nothing I can > pick out. The response is always a "500 internal error". > > Thanks > > > On Jan 26, 7:13 am, Guillermo Rauch <[email protected]> wrote: > > This fix was only for updates. I'll look into your specific scenario > > shortly. > > > > On Mon, Jan 25, 2010 at 9:12 PM, Ryan Rampersad < > [email protected]>wrote: > > > > > > > > > I'm still getting a 500 error when trying to add a new plugin. Other > people > > > have uploaded plugins just fine, so it must be my plugin< > http://github.com/ryanmr/GoodCarousel>, > > > but I can't fix the problem since I don't know what it is. > > > > > On Mon, Jan 25, 2010 at 10:54 PM, Guillermo Rauch <[email protected] > >wrote: > > > > >> Everyone, > > > > >> Sorry I couldn't get to this earlier, I've been really busy at work. > > >> The update problem was related to special characters in tag names, and > > >> has been fixed. It affected a small percentage of plugins, but for > > >> those it did affect, it was obviously frustrating as the forge > > >> wouldn't give any explanation other than an error 500. > > > > >> I could only test in my local stage server, so of course if something > > >> didn't go as planned, let me know. > > > > >> @ken > > > > >> Your assessment about the update action is incorrect. executeUpdate is > > >> not implemented because it's simply not being used. Please look at the > > >> executeAdd function. The update functionality has been in the forge > > >> since the very first release and it only was failing when the tags had > > >> special characters in them. > > >> What major update do you think the code needs? It's currently using > > >> Symfony 1.2 (end of maintenance is next month, but upgrading to > > >> 1.3/1.4 is simple and will be done). Same for Propel 1.3 to Propel > 1.4. > > > > > -- > > > Ryan Rampersad > > >www.ifupdown.com > > > > -- > > Guillermo Rauchhttp://devthought.com > -- Guillermo Rauch http://devthought.com
