Forge not accepting update

[SamGoody]

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!

[SamGoody]

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

[Fábio M. Costa]

it dont even show an error message? It simply stops?

--
Fábio Miranda Costa
Solucione Sistemas
Engenheiro de interfaces

[SamGoody]

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 <fabiomco...@gmail.com> wrote:
> it dont even show an error message? It simply stops?
>
> --
> Fábio Miranda Costa
> Solucione Sistemas
> Engenheiro de interfaces
>

[Ryan Rampersad]

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.

--
Ryan Rampersad
www.ifupdown.com

[pradador]

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.

[Aaron Newton]

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.

[SamGoody]

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 <aa...@iminta.com> 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.
>

[ken]

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?

[fakedarren]

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

[ken]

@fakedarren

I'm willing to help with the forge. Looking at the source I think it
needs major update. I've been using symfony for more than 2 years so I
know every aspect of it.

[Guillermo Rauch]

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]

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, but I can't fix the problem since I don't know what it is.

--
Ryan Rampersad
www.ifupdown.com

[Guillermo Rauch]

This fix was only for updates. I'll look into your specific scenario shortly.

--
Guillermo Rauch
http://devthought.com

[SamGoody]

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 <rau...@gmail.com> 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 <ryan.ramper...@gmail.com>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>,

[Guillermo Rauch]

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.

[Guillermo Rauch]

Sam, 

I just pushed a fix for the Color Picker plugin, you should be able to add it without problems.

As far as MooRTE is concerned, I'm not getting any error 500s. I get a problem with the YAML header of moorte.js.

If you look at http://github.com/siteroller/moorte/blob/master/Source/moorte.js, you'll see that the comment snippet (between the --- and ... delimiters) is not valid YAML. You can use this tool to test your YAML before committing.

Let me know how it goes.

[SamGoody]

Thanks.

It works.

The 500 err is gone.

The colorpicker is in.

Moorte does seem to have an err, but that is my own. Will fix that.

Thanks so very much.

You guys rock. 'Specially Guiller.

Sam

On Mar 7, 1:46 pm, Guillermo Rauch <rau...@gmail.com> wrote:
> Sam,
>
> I just pushed a fix for the Color Picker plugin, you should be able to add
> it without problems.
> As far as MooRTE is concerned, I'm not getting any error 500s. I get a
> problem with the YAML header of moorte.js.
>

> If you look athttp://github.com/siteroller/moorte/blob/master/Source/moorte.js, you'll see

> that the comment snippet (between the --- and ... delimiters) is not valid

> YAML. You can use this tool <http://yaml-online-parser.appspot.com/> to test

[MrIsaacs]

hey there guys, i had the same problems here in my
forge: http://mootools.net/forge/p/gniusBackground .
i've already parsed my codes with yaml online parser
and can't find any failure. have changed my script header
several times and can't figure it out what my problem is.

thanks in advance,
MrIsaacs

[Aaron Newton]

Do you get any sort of error message?

[Dimitar Christoff]

I updated plugins earlier today and no such problems. though - if I
have more than 1 remote tag, it failed to bind the download to the
latest - ignoring the current: from the yml file - which has kind of
forced me to only have 1 tag available to download at any given time.

[MrIsaacs]

i get this errormessage:

POST http://mootools.net/forge/add-6 500 (Internal Server Error) and i just have one tag...

any other suggestions?

thanks so far

MrIsaacs

[Dimitar Christoff]

you have an empty line at the bottom of the file:
https://github.com/MrIsaacs/gniusBackground/blob/0.5.5/package.yml -
have you tried w/o it?

--
Dimitar Christoff

"JavaScript is to JAVA what hamster is to ham"
http://fragged.org/ - @D_mitar - https://github.com/DimitarChristoff

[Andrea Dessì]

I had problems since last november with the forge and then I gave up.

Did you remember? https://groups.google.com/d/msg/mootools-users/bVFqSGFHoUI/oByjWNSbjfgJ

Tried all those tricky things with spaces and versions and encoding but no way.

--
Andrea 

[Aaron Newton]

<sigh>

The problem here, everyone, is that the forge was authored by a developer who is now focused on his own startup (Guillermo Rauch over at LearnBoost.com) and he has no time to help support it. The rest of the dev team is also otherwise engaged or focused on other aspects of the project. Thus we have this unfortunate middle ground where we can't easily address the problems you encounter.

The source for the forge is all online. It's all PHP. If ANYONE here would like to help us maintain it, to debug these issues and add features, please, PLEASE dig in.

[Arian Stolwijk]

code: https://github.com/mootools/mootools-forge

[Dimitar Christoff]

cool, did not know there was a repo for it. anyway, this has shed some
light on the mysterious yml file here:

https://github.com/mootools/mootools-forge/blob/master/misc/PROJECT.instructions.md

I never knew about Stable: <tag>, which in turn explains my inability
to sustain multiple tags and have download point to latest.

also, looks like though it lacks support for ```javascript GH
flavoured markdown, it works with #JS - so it has cleared up a few
issues :)

[Timo Henke]

strange that they use jquery over at learnbooth - my bet would have
been they use moo ...

https://github.com/mootools/mootools-forge

is this the real forge source? ... using sympfony framework. I'm a PHP
DEV on my own but never messed with symfony or cake yet.

I will have a look inside if i may spot the bug (bet not but will give
it a try)

On 14 Jan., 23:18, Aaron Newton <anut...@gmail.com> wrote:
> <sigh>
>
> The problem here, everyone, is that the forge was authored by a developer
> who is now focused on his own startup (Guillermo Rauch over at
> LearnBoost.com) and he has no time to help support it. The rest of the dev
> team is also otherwise engaged or focused on other aspects of the project.
> Thus we have this unfortunate middle ground where we can't easily address
> the problems you encounter.
>
> The source for the forge is all online. It's all PHP. If ANYONE here would
> like to help us maintain it, to debug these issues and add features,
> please, PLEASE dig in.
>
>
>
>
>
>
>
> On Sat, Jan 14, 2012 at 2:05 AM, Andrea Dessì <nkj...@gmail.com> wrote:
> > I had problems since last november with the forge and then I gave up.
> > Did you remember?
> >https://groups.google.com/d/msg/mootools-users/bVFqSGFHoUI/oByjWNSbjfgJ
>
> > Tried all those tricky things with spaces and versions and encoding but no
> > way.
>
> > --
> > Andrea
>

> > On Sat, Jan 14, 2012 at 01:15, Dimitar Christoff <christ...@gmail.com>wrote:
>
> >> you have an empty line at the bottom of the file:
> >>https://github.com/MrIsaacs/gniusBackground/blob/0.5.5/package.yml-
> >> have you tried w/o it?
>

> >> On 12 January 2012 14:56, MrIsaacs <ivan.isa...@windowslive.com> wrote:
> >> > i get this errormessage:

> >> > POSThttp://mootools.net/forge/add-6500 (Internal Server Error) and i

[MrIsaacs]

i've updated the package.yml file and the problem is still there.

don't know what to do... \:

[Timo Henke]

could you send the exact error + url + maybe the header stuff (from
firebug)?

I jumped into the git of the forge and tried to understand the symfony
style ...

what i found (should not be related to the actual problem) is in

lib/ForgeToolkit.class.php

public static function createRecursiveDirectory($path){
if (!file_exists($path)) @mkdir($path, 0777, true);
}

the check should be !is_dir($path) ... not !file_exists() ... should
be changed IMHO.

[MrIsaacs]

my problem is, that firefox 9.0.1 don't have firebug and i can't get it this way.

if google chrome's javascript-console can do it, here it is:

• POST http://mootools.net/forge/add-6 500 (Internal Server Error)

1. Class.sendmootools-1.2.2-core+more.js:340
2. extend._ownermootools-1.2.2-core+more.js:97
3. (anonymous function)mootools-1.2.2-core+more.js:102
4. extend._ownermootools-1.2.2-core+more.js:97
5. Class.sendpluginskit.js:73
6. extend._ownermootools-1.2.2-core+more.js:97
7. (anonymous function)pluginskit.js:110
8. Class.callChainmootools-1.2.2-core+more.js:103
9. extend._ownermootools-1.2.2-core+more.js:97
10. Class.onCompletemootools-1.2.2-core+more.js:288
11. extend._ownermootools-1.2.2-core+more.js:97
12. Class.completemootools-1.2.2-core+more.js:287
13. extend._ownermootools-1.2.2-core+more.js:97
14. Class.stepmootools-1.2.2-core+more.js:284
15. extend._ownermootools-1.2.2-core+more.js:97
16. emootools-1.2.2-core+more.js:57

and here is the header part:

1. Request URL:
   http://mootools.net/forge/add-6
2. Request Method:
   POST
3. Status Code:
   500 Internal Server Error
4. Request Headersview source
1. Accept:
   application/json
2. Accept-Charset:
   ISO-8859-1,utf-8;q=0.7,*;q=0.3
3. Accept-Encoding:
   gzip,deflate,sdch
4. Accept-Language:
   de-DE,de;q=0.8,en-US;q=0.6,en;q=0.4
5. Connection:
   keep-alive
6. Content-Length:
   35
7. Content-type:
   application/x-www-form-urlencoded; charset=UTF-8
8. Cookie:
   km_dbg=0; km_ai=72BRXcI%2FQh7WlMR3ULqrE3ogm%2Bg%3D; mooforge=aj5rbujvudfna2fmjd65fpv7p0; __utma=231269507.2146457339.1325350867.1326876709.1326879252.12; __utmb=231269507.11.10.1326879252; __utmc=231269507; __utmz=231269507.1326638714.10.2.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=(not%20provided)
9. Host:
   mootools.net
10. Origin:
    http://mootools.net
11. Referer:
    http://mootools.net/forge/p/gniusBackground
12. User-Agent:
    Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.75 Safari/535.7
13. X-Request:
    JSON
14. X-Requested-With:
    XMLHttpRequest
5. Form Dataview URL encoded
1. addid:
   13268802636095074f16960796459
6. Response Headersview source
1. Connection:
   close
2. Content-Encoding:
   gzip
3. Content-Length:
   26
4. Content-Type:
   text/html
5. Date:
   Wed, 18 Jan 2012 09:51:08 GMT
6. Server:
   Apache/2.2.3 (CentOS)
7. Vary:
   Accept-Encoding
8. X-Powered-By:
   PHP/5.2.6

thank you for your help guys!

[MrIsaacs]

whats kind of encoding-type the js-file needs?

because of the apostrophe in my surname...

now i have changed it to utf-8 and try it again.

i'll tell you the results after i've tried it (;

[MrIsaacs]

oke.... id didn't worked :/

next step?

[Timo Henke]

afaik it should be utf-8 to be international

[Timo Henke]

i think the people behind mootools.net should have a look in the
webserver error log ... maybe that'll help to track the error down to
its root.

[MrIsaacs]

i concur

[MrIsaacs]

i thought so that no one could help me. when i find it out i will post it here no problems dude. you can't imagine how much this s*** is bugging me...

[Arian Stolwijk]

It's very annoying indeed. Maybe you could try to use https://github.com/arian/mootools-form-upload as a template and adjust it for your plugin. It's probably something very small in your package.yml or js headers. Of course the forge should give much better feedback.

[Timo Henke]

yes ... hard to "debug" a source by just its github stuff ... what
would help is if someone who has direct access to the online-system
will try to upload a plugin with an reproduceable problem and debug
the shit right out of it by adding some logging and debug-shit. error
500 could also be some runtime error by the webserver in an cgi
environment (cgi wrapper kicked off the script because it exceeds some
limit like runtime or memory).

Also an real Error 500 (not a forgotten content-type header :-) ) is
not realy catchable by the PHP Script as it is produced by some parent
instance.

Hope and pray ...

On 31 Jan., 14:34, Arian Stolwijk <stolwijk.ar...@gmail.com> wrote:
> It's very annoying indeed. Maybe you could try to usehttps://github.com/arian/mootools-form-uploadas a template and adjust it

> for your plugin. It's probably something very small in your package.yml or
> js headers. Of course the forge should give much better feedback.
>

[MrIsaacs]

hi arian, thank you for your idea but it also seems not to work. i've copied your js code and your yaml file and it also halts on verifying-js-file with the same 500 error. maybe you can take a look at my repository ('gniusBackground') and tell me what i've done wrong.

thank all you guys for your help

MrIsaacs

[MrIsaacs]

oke mootools.net-people, now check this out and please check your server error logs. please do me this favor. i want to upload much more plugins but in the first place i want to fix this plugins issue and then i will look forward for other plugins.

your MrIsaacs

[MrIsaacs]

...check this (gniusBackground.js) out and please...

[MrIsaacs]

okey guys,

i've solved my problem. the problem was neither the js-file not the yaml-file. the failure comes just when i put a too large 'png-image' as a screenshot for my plugin as a thumb. the min resolution must be in can be larger but ideally 200x100. i've tried a 'jpeg' in larger resolution and no error message comes out. my upadating process ended with, guess what: Done!

very thankfull for help folks!

[Rolf Langenhuijzen]

I have looked at the source of Forge too at github but I haven't used
Symfony before either, so even though the code is not that hard to
read, it's all a bit different than other stuff I'm used too.

If I have some time real soon I'll review it locally and will start
with the image thing. I have not found a config setting that limits
images sizes or file sizes or anything really.

[Rolf Langenhuijzen]

Aha, we might want to temper this one:
https://github.com/mootools/mootools-forge/blob/master/config/app.yml

This doesn't tell me any about restrictions though, only final sizes
after image handling during plugin upload. Or maybe these settings are
required and anything larger throws an error.

(mind you I'm using this thread now as a post-it note to self with
scribbles I might want to check later when I dive into it)

[MrIsaacs]

you got my yes, but don't no if you asked me or someone else. doesn't matter. the more answers you got the more you're allowed from everyone.

cheers folks!!