You can subscribe to this list here.
2002 |
Jan
(30) |
Feb
(6) |
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
|
Nov
|
Dec
|
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: Terrence B. <met...@gm...> - 2005-12-23 15:06:51
|
ExtUtils::MakeMaker was not getting the $VERSION from Everything.pm because it was a lexical not a package variable. The enclosed diff fixes this: --- Everything.pm.orig=092005-12-23 07:04:30.000000000 -0800 +++ Everything.pm=092005-12-23 07:04:51.000000000 -0800 @@ -24,7 +24,7 @@ my $everythingLog =3D "/tmp/everything.errlog"; # Used by Makefile.PL to determine the version of the install. -my $VERSION =3D 0.8; +our $VERSION =3D 0.8; # Arrays for error caching use vars qw(@fsErrors); @@ -33,7 +33,7 @@ use vars qw(%NODEBASES); # Are we being run from the command line? -use vars qw($commandLine); +use vars qw($commandLine); sub BEGIN { |
From: Jason B. N. <ai...@tr...> - 2003-09-10 15:17:29
|
I'm going through the installation again to make sure I didn't mess something up along the way. One thing that I noticed is that when I run 'perl Makefile.PL' in the root level of the install dir, I get a warning: WARNING: Setting VERSION via file 'Everything.pm' failed at /usr/local/lib/perl5/5.6.1/ExtUtils/MakeMaker.pm line 484 Is there an easy way to downgrade to the CGI.pm that you guys are using? Thanks for the help so far. j On Tue, 2003-09-09 at 19:02, Nathan Oostendorp wrote: > Hey Jason, > > I can't peg what would be going wrong causing unwarranted escaping. My > only thought is that behavior might be different in CGI.pm 2.99 > > You /can/ login via url by doing: > index.pl?op=login&user=USERNAME&passwd=PASSWORD > > take a look at [openform] -- that's what creates the form post which > seems to be messing you up. You might also want to see what > $ENV{script_name} returns. > > good luck, sorry I can't be more precise, > > --n > > > > On Tuesday, September 9, 2003, at 02:38 PM, Jason Bradley Nance wrote: > > > Any idea what I should be doing to try and debug this? This issue is a > > show-stopper for me since I can't login... =) I'd love to be able to > > use the Everything Engine for my site. > > > > j > > > > > > On Fri, 2003-09-05 at 23:23, Jason Bradley Nance wrote: > >> Hey Nate, > >> > >>> what is the distro you are running on? > >> > >> RedHat 7.2 with (CPAN) updated Perl modules. > >> > >>> what version of CGI.pm do you have? > >> > >> 2.99 I believe. > >> > >>> what version of apache/mod_perl? > >> > >> Apache 1.3.26 and mod_perl 1.27 > >> > >> Thanks a bunch. > >> > >> j > >> > >> > >>> > >>> Everything was written against some older versions of the above > >>> components so newer versions might not be as compatable. > >>> > >>> let me know, > >>> > >>> --nate > >>> > >>> > >>> On Friday, September 5, 2003, at 04:14 PM, Jason Bradley Nance wrote: > >>> > >>>> After a fresh install of Pre-1.0 I attempt to login as > >>>> root, but I get a 404 and the URI is all messed up. > >>>> The submit URI appears like this: > >>>> > >>>> http://host.dom/everything/%2Feverything%2Findex.pl > >>>> > >>>> Instead of this: > >>>> > >>>> http://host.dom/everything/index.pl > >>>> > >>>> My esite install command line looked like this: > >>>> > >>>> sudo bin/install_esite --noapacheconf > >>>> --edir=/usr/local/everything > >>>> --web=/usr/local/apache/htdocs/html-www/everything > >>>> everything > >>>> > >>>> I also tried installing to the root of the virtual host instead of > >>>> to a > >>>> subdir, but I still get a 404 when i submit (to login) and the URL > >>>> looks > >>>> like this: > >>>> > >>>> http://host.dom/%2Findex.pl > >>>> > >>>> Any input would be greatly appreciated. > >>>> > >>>> j > >>>> > >>>> > >>>> -- > >>>> Jason Bradley Nance > >>>> ai...@tr... > >>>> Tres Geek > >>>> http://tresgeek.net/ > >>>> > >>>> - > >>>> What would you cry for? > >>>> Swallow your pride for? > >>>> What would you go wild for? > >>>> > >>>> -Poe, "Wild" > >>>> -- > >>>> > >>>> > >>>> > >>>> ------------------------------------------------------- > >>>> This sf.net email is sponsored by:ThinkGeek > >>>> Welcome to geek heaven. > >>>> http://thinkgeek.com/sf > >>>> _______________________________________________ > >>>> Everydevel-bugs mailing list > >>>> Eve...@li... > >>>> https://lists.sourceforge.net/lists/listinfo/everydevel-bugs > >> > >> > >> > >> ------------------------------------------------------- > >> This sf.net email is sponsored by:ThinkGeek > >> Welcome to geek heaven. > >> http://thinkgeek.com/sf > >> _______________________________________________ > >> Everydevel-bugs mailing list > >> Eve...@li... > >> https://lists.sourceforge.net/lists/listinfo/everydevel-bugs > > -- > > Jason Bradley Nance > > ai...@tr... > > Tres Geek > > http://tresgeek.net/ > > > > - > > What would you cry for? > > Swallow your pride for? > > What would you go wild for? > > > > -Poe, "Wild" > > -- > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Everydevel-bugs mailing list > > Eve...@li... > > https://lists.sourceforge.net/lists/listinfo/everydevel-bugs |
From: Nathan O. <na...@va...> - 2003-09-09 23:58:59
|
Hey Jason, I can't peg what would be going wrong causing unwarranted escaping. My only thought is that behavior might be different in CGI.pm 2.99 You /can/ login via url by doing: index.pl?op=login&user=USERNAME&passwd=PASSWORD take a look at [openform] -- that's what creates the form post which seems to be messing you up. You might also want to see what $ENV{script_name} returns. good luck, sorry I can't be more precise, --n On Tuesday, September 9, 2003, at 02:38 PM, Jason Bradley Nance wrote: > Any idea what I should be doing to try and debug this? This issue is a > show-stopper for me since I can't login... =) I'd love to be able to > use the Everything Engine for my site. > > j > > > On Fri, 2003-09-05 at 23:23, Jason Bradley Nance wrote: >> Hey Nate, >> >>> what is the distro you are running on? >> >> RedHat 7.2 with (CPAN) updated Perl modules. >> >>> what version of CGI.pm do you have? >> >> 2.99 I believe. >> >>> what version of apache/mod_perl? >> >> Apache 1.3.26 and mod_perl 1.27 >> >> Thanks a bunch. >> >> j >> >> >>> >>> Everything was written against some older versions of the above >>> components so newer versions might not be as compatable. >>> >>> let me know, >>> >>> --nate >>> >>> >>> On Friday, September 5, 2003, at 04:14 PM, Jason Bradley Nance wrote: >>> >>>> After a fresh install of Pre-1.0 I attempt to login as >>>> root, but I get a 404 and the URI is all messed up. >>>> The submit URI appears like this: >>>> >>>> http://host.dom/everything/%2Feverything%2Findex.pl >>>> >>>> Instead of this: >>>> >>>> http://host.dom/everything/index.pl >>>> >>>> My esite install command line looked like this: >>>> >>>> sudo bin/install_esite --noapacheconf >>>> --edir=/usr/local/everything >>>> --web=/usr/local/apache/htdocs/html-www/everything >>>> everything >>>> >>>> I also tried installing to the root of the virtual host instead of >>>> to a >>>> subdir, but I still get a 404 when i submit (to login) and the URL >>>> looks >>>> like this: >>>> >>>> http://host.dom/%2Findex.pl >>>> >>>> Any input would be greatly appreciated. >>>> >>>> j >>>> >>>> >>>> -- >>>> Jason Bradley Nance >>>> ai...@tr... >>>> Tres Geek >>>> http://tresgeek.net/ >>>> >>>> - >>>> What would you cry for? >>>> Swallow your pride for? >>>> What would you go wild for? >>>> >>>> -Poe, "Wild" >>>> -- >>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> This sf.net email is sponsored by:ThinkGeek >>>> Welcome to geek heaven. >>>> http://thinkgeek.com/sf >>>> _______________________________________________ >>>> Everydevel-bugs mailing list >>>> Eve...@li... >>>> https://lists.sourceforge.net/lists/listinfo/everydevel-bugs >> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by:ThinkGeek >> Welcome to geek heaven. >> http://thinkgeek.com/sf >> _______________________________________________ >> Everydevel-bugs mailing list >> Eve...@li... >> https://lists.sourceforge.net/lists/listinfo/everydevel-bugs > -- > Jason Bradley Nance > ai...@tr... > Tres Geek > http://tresgeek.net/ > > - > What would you cry for? > Swallow your pride for? > What would you go wild for? > > -Poe, "Wild" > -- > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Everydevel-bugs mailing list > Eve...@li... > https://lists.sourceforge.net/lists/listinfo/everydevel-bugs |
From: Jason B. N. <ai...@tr...> - 2003-09-09 18:38:18
|
Any idea what I should be doing to try and debug this? This issue is a show-stopper for me since I can't login... =) I'd love to be able to use the Everything Engine for my site. j On Fri, 2003-09-05 at 23:23, Jason Bradley Nance wrote: > Hey Nate, > > > what is the distro you are running on? > > RedHat 7.2 with (CPAN) updated Perl modules. > > > what version of CGI.pm do you have? > > 2.99 I believe. > > > what version of apache/mod_perl? > > Apache 1.3.26 and mod_perl 1.27 > > Thanks a bunch. > > j > > > > > > Everything was written against some older versions of the above > > components so newer versions might not be as compatable. > > > > let me know, > > > > --nate > > > > > > On Friday, September 5, 2003, at 04:14 PM, Jason Bradley Nance wrote: > > > > > After a fresh install of Pre-1.0 I attempt to login as > > > root, but I get a 404 and the URI is all messed up. > > > The submit URI appears like this: > > > > > > http://host.dom/everything/%2Feverything%2Findex.pl > > > > > > Instead of this: > > > > > > http://host.dom/everything/index.pl > > > > > > My esite install command line looked like this: > > > > > > sudo bin/install_esite --noapacheconf > > > --edir=/usr/local/everything > > > --web=/usr/local/apache/htdocs/html-www/everything > > > everything > > > > > > I also tried installing to the root of the virtual host instead of to a > > > subdir, but I still get a 404 when i submit (to login) and the URL > > > looks > > > like this: > > > > > > http://host.dom/%2Findex.pl > > > > > > Any input would be greatly appreciated. > > > > > > j > > > > > > > > > -- > > > Jason Bradley Nance > > > ai...@tr... > > > Tres Geek > > > http://tresgeek.net/ > > > > > > - > > > What would you cry for? > > > Swallow your pride for? > > > What would you go wild for? > > > > > > -Poe, "Wild" > > > -- > > > > > > > > > > > > ------------------------------------------------------- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > _______________________________________________ > > > Everydevel-bugs mailing list > > > Eve...@li... > > > https://lists.sourceforge.net/lists/listinfo/everydevel-bugs > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Everydevel-bugs mailing list > Eve...@li... > https://lists.sourceforge.net/lists/listinfo/everydevel-bugs -- Jason Bradley Nance ai...@tr... Tres Geek http://tresgeek.net/ - What would you cry for? Swallow your pride for? What would you go wild for? -Poe, "Wild" -- |
From: Jason B. N. <ai...@tr...> - 2003-09-06 04:18:06
|
Hey Nate, > what is the distro you are running on? RedHat 7.2 with (CPAN) updated Perl modules. > what version of CGI.pm do you have? 2.99 I believe. > what version of apache/mod_perl? Apache 1.3.26 and mod_perl 1.27 Thanks a bunch. j > > Everything was written against some older versions of the above > components so newer versions might not be as compatable. > > let me know, > > --nate > > > On Friday, September 5, 2003, at 04:14 PM, Jason Bradley Nance wrote: > > > After a fresh install of Pre-1.0 I attempt to login as > > root, but I get a 404 and the URI is all messed up. > > The submit URI appears like this: > > > > http://host.dom/everything/%2Feverything%2Findex.pl > > > > Instead of this: > > > > http://host.dom/everything/index.pl > > > > My esite install command line looked like this: > > > > sudo bin/install_esite --noapacheconf > > --edir=/usr/local/everything > > --web=/usr/local/apache/htdocs/html-www/everything > > everything > > > > I also tried installing to the root of the virtual host instead of to a > > subdir, but I still get a 404 when i submit (to login) and the URL > > looks > > like this: > > > > http://host.dom/%2Findex.pl > > > > Any input would be greatly appreciated. > > > > j > > > > > > -- > > Jason Bradley Nance > > ai...@tr... > > Tres Geek > > http://tresgeek.net/ > > > > - > > What would you cry for? > > Swallow your pride for? > > What would you go wild for? > > > > -Poe, "Wild" > > -- > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Everydevel-bugs mailing list > > Eve...@li... > > https://lists.sourceforge.net/lists/listinfo/everydevel-bugs |
From: Nathan O. <na...@va...> - 2003-09-05 21:00:54
|
Hey Jason, It looks like what's happening is your urls are being url escaped when they should not be. Quick question: what is the distro you are running on? what version of CGI.pm do you have? what version of apache/mod_perl? Everything was written against some older versions of the above components so newer versions might not be as compatable. let me know, --nate On Friday, September 5, 2003, at 04:14 PM, Jason Bradley Nance wrote: > After a fresh install of Pre-1.0 I attempt to login as > root, but I get a 404 and the URI is all messed up. > The submit URI appears like this: > > http://host.dom/everything/%2Feverything%2Findex.pl > > Instead of this: > > http://host.dom/everything/index.pl > > My esite install command line looked like this: > > sudo bin/install_esite --noapacheconf > --edir=/usr/local/everything > --web=/usr/local/apache/htdocs/html-www/everything > everything > > I also tried installing to the root of the virtual host instead of to a > subdir, but I still get a 404 when i submit (to login) and the URL > looks > like this: > > http://host.dom/%2Findex.pl > > Any input would be greatly appreciated. > > j > > > -- > Jason Bradley Nance > ai...@tr... > Tres Geek > http://tresgeek.net/ > > - > What would you cry for? > Swallow your pride for? > What would you go wild for? > > -Poe, "Wild" > -- > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Everydevel-bugs mailing list > Eve...@li... > https://lists.sourceforge.net/lists/listinfo/everydevel-bugs |
From: Jason B. N. <ai...@tr...> - 2003-09-05 20:14:49
|
After a fresh install of Pre-1.0 I attempt to login as root, but I get a 404 and the URI is all messed up. The submit URI appears like this: http://host.dom/everything/%2Feverything%2Findex.pl Instead of this: http://host.dom/everything/index.pl My esite install command line looked like this: sudo bin/install_esite --noapacheconf --edir=/usr/local/everything --web=/usr/local/apache/htdocs/html-www/everything everything I also tried installing to the root of the virtual host instead of to a subdir, but I still get a 404 when i submit (to login) and the URL looks like this: http://host.dom/%2Findex.pl Any input would be greatly appreciated. j -- Jason Bradley Nance ai...@tr... Tres Geek http://tresgeek.net/ - What would you cry for? Swallow your pride for? What would you go wild for? -Poe, "Wild" -- |
From: Nate O. <na...@va...> - 2002-04-08 21:10:55
|
testestsetests -- nate oostendorp va software corporation senior codebase engineer, sourceforge.net |
From: <no...@so...> - 2002-03-13 10:45:32
|
Bugs item #529382, was opened at 2002-03-13 05:45 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=529382&group_id=39838 Category: Interface (example) Group: None Status: Open Resolution: None Priority: 3 Submitted By: Jay Bonci (jaybonci) Assigned to: Nobody/Anonymous (nobody) Summary: Invalid type_nodetype on node throws 500 Initial Comment: If a type_nodetype on a node get's corrupted (or the parent type gets whacked), we throw a 500 error when trying to view the node. This makes it really hard to clean up after it (with a nuke or what not, just to get it out of the main node table). In an ideal world, we should simply resort to the displaytype and permissions for that of an object of type [node]. This would be the safest best (as we wouldn't need to assume that the type is there for anything else). It would also allow system maintainers to whack the node enough to clean it up (or edit it's type or whatever other thing they should choose to do to the now dead object). This is similar to the previous issue of ecore tossing a 500 when an invalid displaytype is given, but it has more to do with the types than does anything else. Low priority of course. --jay ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=529382&group_id=39838 |
From: <no...@so...> - 2002-02-08 23:58:59
|
Feature Requests item #515057, was opened at 2002-02-08 15:58 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426096&aid=515057&group_id=39838 Category: None Group: None Status: Open Priority: 5 Submitted By: Nate Oostendorp (n_oostendorp) Assigned to: Nobody/Anonymous (nobody) Summary: Flexibility in sending Everything::Mail Initial Comment: It seems like it would be easy if we used Mail::Mailer rather than Mail::Sender to be able to use some mailing options: If they have "mail" on the system, use that rather than connecting to an outside mailer, or use their machines 'sendmail'. Also, the "mail settings" node should maybe be initialized by the Makefile (on setup) or with install_esit. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426096&aid=515057&group_id=39838 |
From: <no...@so...> - 2002-02-08 21:19:32
|
Bugs item #514181, was opened at 2002-02-07 01:57 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=514181&group_id=39838 Category: Import/Install Difficulty Group: v1.0 (example) Status: Closed Resolution: Fixed Priority: 5 Submitted By: Jay Bonci (jaybonci) Assigned to: chromatic (chromatic) Summary: A Nodetype can extend itself Initial Comment: When editing a nodetype, if you happen to have a typo, or for whatever reason you are very silly, you can set a nodetype to "extend" itself. This send the request into what seems like an infinite loop. I waited a bit before killing apache to reload it. A simple check should be enough to fix it, but still, I thought I'd mention it here, as I don't exactly know the fix / checking procedure for ecore. Thanks. ---------------------------------------------------------------------- >Comment By: Nate Oostendorp (n_oostendorp) Date: 2002-02-08 13:19 Message: Logged In: YES user_id=297846 heh, re: tests -- yeah, i need to get off my ass and actually install everything on a new machine and try 'em out. ---------------------------------------------------------------------- Comment By: chromatic (chromatic) Date: 2002-02-08 13:01 Message: Logged In: YES user_id=2274 Patch really uploaded this time, but the fix has already been checked into CVS. You'll just have to trust me on the test case, until you rule one way or another on including them. ---------------------------------------------------------------------- Comment By: Nate Oostendorp (n_oostendorp) Date: 2002-02-08 12:53 Message: Logged In: YES user_id=297846 Hey guys. chromatic: yeah, fixing the top level insert function should do the trick. I don't see your patch anywhere though... You can email it to me, but you should have cvs access -- if that's still a problem let me know. ---------------------------------------------------------------------- Comment By: chromatic (chromatic) Date: 2002-02-08 11:58 Message: Logged In: YES user_id=2274 Easily enough fixed in insert(). I added a check to see if the type_nodetype and extends_nodetype fields match. If so, the node defaults to extending 'node'. This may not be the best approach, but I don't think this should be a failure, especially as we don't yet have a good way to handle logical constraints. I also added a test in the appropriate suite. Patch attached with my suggested fix. nate, any comments? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=514181&group_id=39838 |
From: <no...@so...> - 2002-02-08 21:01:52
|
Bugs item #514181, was opened at 2002-02-07 01:57 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=514181&group_id=39838 Category: Import/Install Difficulty Group: v1.0 (example) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Jay Bonci (jaybonci) Assigned to: chromatic (chromatic) Summary: A Nodetype can extend itself Initial Comment: When editing a nodetype, if you happen to have a typo, or for whatever reason you are very silly, you can set a nodetype to "extend" itself. This send the request into what seems like an infinite loop. I waited a bit before killing apache to reload it. A simple check should be enough to fix it, but still, I thought I'd mention it here, as I don't exactly know the fix / checking procedure for ecore. Thanks. ---------------------------------------------------------------------- >Comment By: chromatic (chromatic) Date: 2002-02-08 13:01 Message: Logged In: YES user_id=2274 Patch really uploaded this time, but the fix has already been checked into CVS. You'll just have to trust me on the test case, until you rule one way or another on including them. ---------------------------------------------------------------------- Comment By: Nate Oostendorp (n_oostendorp) Date: 2002-02-08 12:53 Message: Logged In: YES user_id=297846 Hey guys. chromatic: yeah, fixing the top level insert function should do the trick. I don't see your patch anywhere though... You can email it to me, but you should have cvs access -- if that's still a problem let me know. ---------------------------------------------------------------------- Comment By: chromatic (chromatic) Date: 2002-02-08 11:58 Message: Logged In: YES user_id=2274 Easily enough fixed in insert(). I added a check to see if the type_nodetype and extends_nodetype fields match. If so, the node defaults to extending 'node'. This may not be the best approach, but I don't think this should be a failure, especially as we don't yet have a good way to handle logical constraints. I also added a test in the appropriate suite. Patch attached with my suggested fix. nate, any comments? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=514181&group_id=39838 |
From: <no...@so...> - 2002-02-08 20:53:50
|
Bugs item #514181, was opened at 2002-02-07 01:57 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=514181&group_id=39838 Category: Import/Install Difficulty Group: v1.0 (example) >Status: Open Resolution: Accepted Priority: 5 Submitted By: Jay Bonci (jaybonci) Assigned to: chromatic (chromatic) Summary: A Nodetype can extend itself Initial Comment: When editing a nodetype, if you happen to have a typo, or for whatever reason you are very silly, you can set a nodetype to "extend" itself. This send the request into what seems like an infinite loop. I waited a bit before killing apache to reload it. A simple check should be enough to fix it, but still, I thought I'd mention it here, as I don't exactly know the fix / checking procedure for ecore. Thanks. ---------------------------------------------------------------------- >Comment By: Nate Oostendorp (n_oostendorp) Date: 2002-02-08 12:53 Message: Logged In: YES user_id=297846 Hey guys. chromatic: yeah, fixing the top level insert function should do the trick. I don't see your patch anywhere though... You can email it to me, but you should have cvs access -- if that's still a problem let me know. ---------------------------------------------------------------------- Comment By: chromatic (chromatic) Date: 2002-02-08 11:58 Message: Logged In: YES user_id=2274 Easily enough fixed in insert(). I added a check to see if the type_nodetype and extends_nodetype fields match. If so, the node defaults to extending 'node'. This may not be the best approach, but I don't think this should be a failure, especially as we don't yet have a good way to handle logical constraints. I also added a test in the appropriate suite. Patch attached with my suggested fix. nate, any comments? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=514181&group_id=39838 |
From: <no...@so...> - 2002-02-08 19:58:18
|
Bugs item #514181, was opened at 2002-02-07 01:57 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=514181&group_id=39838 Category: Import/Install Difficulty Group: v1.0 (example) >Status: Pending >Resolution: Accepted Priority: 5 Submitted By: Jay Bonci (jaybonci) >Assigned to: chromatic (chromatic) Summary: A Nodetype can extend itself Initial Comment: When editing a nodetype, if you happen to have a typo, or for whatever reason you are very silly, you can set a nodetype to "extend" itself. This send the request into what seems like an infinite loop. I waited a bit before killing apache to reload it. A simple check should be enough to fix it, but still, I thought I'd mention it here, as I don't exactly know the fix / checking procedure for ecore. Thanks. ---------------------------------------------------------------------- >Comment By: chromatic (chromatic) Date: 2002-02-08 11:58 Message: Logged In: YES user_id=2274 Easily enough fixed in insert(). I added a check to see if the type_nodetype and extends_nodetype fields match. If so, the node defaults to extending 'node'. This may not be the best approach, but I don't think this should be a failure, especially as we don't yet have a good way to handle logical constraints. I also added a test in the appropriate suite. Patch attached with my suggested fix. nate, any comments? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=514181&group_id=39838 |
From: <no...@so...> - 2002-02-07 09:57:06
|
Bugs item #514181, was opened at 2002-02-07 01:57 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=514181&group_id=39838 Category: Import/Install Difficulty Group: v1.0 (example) Status: Open Resolution: None Priority: 5 Submitted By: Jay Bonci (jaybonci) Assigned to: Nobody/Anonymous (nobody) Summary: A Nodetype can extend itself Initial Comment: When editing a nodetype, if you happen to have a typo, or for whatever reason you are very silly, you can set a nodetype to "extend" itself. This send the request into what seems like an infinite loop. I waited a bit before killing apache to reload it. A simple check should be enough to fix it, but still, I thought I'd mention it here, as I don't exactly know the fix / checking procedure for ecore. Thanks. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=514181&group_id=39838 |
From: <no...@so...> - 2002-01-29 10:34:14
|
Bugs item #510072, was opened at 2002-01-29 02:33 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=510072&group_id=39838 Category: Interface (example) Group: v1.0 (example) Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Gigantic Node Lister forgets nodetype Initial Comment: There's a bug in the Gigantic Node Lister, which causes it to forget what nodetype you were listing when you page forward to the next 100. It's a pretty easy fix, you just need to put the query parameters $group and $type in the URL string for the "Next XXX" link... This is what I did: 86: my $type = $query->param('whichtype'); 87: my $group = $query->param('whichgroup'); 88: 89: $type ||= "alltypes"; 90: $group ||= "nogroup"; 91: 92: $nav .= "<a href=" . 93: urlGen ({node_id => getId ($NODE), next => ($prev) }) . 94: ">Previous " . ($offset-$prev) . " entries...</a>" 95: if ($offset > 0); 96: 97: $nav .= "</td><td align=center>($offset-" . ($offset+int(@$ref)) . 98: ") of $totalRows</td><td align=right>"; 99: 100: $nav .= "<a href=" . 101: urlGen ({node_id => getId ($NODE), next => $next, whichtype => $type, whichgroup => $group}) . 102: ">Next " . ($totalRows - $next > $limit ? $limit : $totalRows - $next ) . 103: " entries...</a>" if ($next < $totalRows); Note in the last urlGen call, the addition of the whichtype and whichgroup key/value pairs, and the above declarations and assignments of $type and $group from the $query structure. I know, it's simple, but it's definately nicer this way :) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=510072&group_id=39838 |
From: <no...@so...> - 2002-01-28 05:22:26
|
Bugs item #508388, was opened at 2002-01-25 02:19 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=508388&group_id=39838 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Jay Bonci (jaybonci) Assigned to: Nobody/Anonymous (nobody) Summary: Can't have usernames ending in a pipe Initial Comment: We throw a server error when creating usernames that end in a pipe character. Try creating asdasd| as a username. asdasd|asd works, but the former does not. Dumb, I know, but it's possible someone might want a username with like |joe|. Personally, I think disallowing the pipe character is a good bet, seeing as it would break all pipe-linking. <br><br> The error I get is: <pre> Create a new user Can't coerce array into hash at /usr/local/lib/perl5/site_perl/5.6.1/Everything/HTML .pm line 641. </pre> <br><br> This was tested on the ecore current I have (non-CVS). ---------------------------------------------------------------------- >Comment By: chromatic (chromatic) Date: 2002-01-27 21:22 Message: Logged In: YES user_id=2274 I'm all for this. We could disallow square brackets too, for obvious linking reasons. There are checks on Everything2 and on Perl Monks to try to weed out duplicate usernames. Slash has something similar. There's room to perform similar things in the Engine. Combined with the bug about invalid dbtable names, could we add a node method like "validateTitle()" to all nodetypes where this would be useful? It should be called from "insert()", obviously. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=508388&group_id=39838 |
From: <no...@so...> - 2002-01-25 10:20:28
|
Bugs item #508388, was opened at 2002-01-25 02:19 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=508388&group_id=39838 Category: None Group: None Status: Open Resolution: None >Priority: 3 Submitted By: Jay Bonci (jaybonci) Assigned to: Nobody/Anonymous (nobody) Summary: Can't have usernames ending in a pipe Initial Comment: We throw a server error when creating usernames that end in a pipe character. Try creating asdasd| as a username. asdasd|asd works, but the former does not. Dumb, I know, but it's possible someone might want a username with like |joe|. Personally, I think disallowing the pipe character is a good bet, seeing as it would break all pipe-linking. <br><br> The error I get is: <pre> Create a new user Can't coerce array into hash at /usr/local/lib/perl5/site_perl/5.6.1/Everything/HTML .pm line 641. </pre> <br><br> This was tested on the ecore current I have (non-CVS). ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=508388&group_id=39838 |
From: <no...@so...> - 2002-01-25 10:19:52
|
Bugs item #508388, was opened at 2002-01-25 02:19 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=508388&group_id=39838 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jay Bonci (jaybonci) Assigned to: Nobody/Anonymous (nobody) Summary: Can't have usernames ending in a pipe Initial Comment: We throw a server error when creating usernames that end in a pipe character. Try creating asdasd| as a username. asdasd|asd works, but the former does not. Dumb, I know, but it's possible someone might want a username with like |joe|. Personally, I think disallowing the pipe character is a good bet, seeing as it would break all pipe-linking. <br><br> The error I get is: <pre> Create a new user Can't coerce array into hash at /usr/local/lib/perl5/site_perl/5.6.1/Everything/HTML .pm line 641. </pre> <br><br> This was tested on the ecore current I have (non-CVS). ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=508388&group_id=39838 |
From: <no...@so...> - 2002-01-25 01:32:08
|
Bugs item #508244, was opened at 2002-01-24 17:32 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=508244&group_id=39838 Category: Interface (example) Group: v1.0 (example) Status: Open Resolution: None Priority: 3 Submitted By: Jay Bonci (jaybonci) Assigned to: Nobody/Anonymous (nobody) Summary: dbtable edit page allows reserved words Initial Comment: Quasi bug, quasi feature request. <br><br> When editing any dbtable, you can enter reserved words into it (causing mysql to fail miserably). This code is primarily in dbtable.pm, but it may be trivial to have it reference a setting of forbidden keywords, attached to this bug. Otherwise, it is easy to make the mistake of trying to create table and column names of type [character], [order], or [key] (or berkeley_db I suppose, but I mean cmon). <br><br> Attached is a Data::Dumper dump of all the reserved keywords for mySQL latest (lowercased). It allows you to simply import it into a setting, and was ripped directly from the mySQL documentation. <br><br> (Note, I'm bugging this because, even though I could fix it probably, I am short on time, and there are millions of bored people across the globe, that possibly one of which could fix) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=508244&group_id=39838 |
From: <no...@so...> - 2002-01-24 23:51:39
|
Bugs item #508213, was opened at 2002-01-24 15:51 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=508213&group_id=39838 Category: Interface (example) Group: v1.0 (example) Status: Open Resolution: None Priority: 3 Submitted By: Jay Bonci (jaybonci) Assigned to: Nobody/Anonymous (nobody) Summary: Invalid displaytype tosses Apache 500 Initial Comment: eCore chucks a 500 if you give it a bad displaytype variable. This is bad, yes, but not terrible. Suggestion: If you throw it a bad displaytype param, have it: * default back to displaytype=display * toss a document in the default theme (Tough Beans, cannot find node, or maybe a "bad display method") It really shouldn't 500, but it's really minor. This happens on the E2 site, and in recent versions of eCore. Thanks --jay ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=508213&group_id=39838 |
From: <no...@so...> - 2002-01-24 23:17:59
|
Bugs item #508120, was opened at 2002-01-24 12:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=508120&group_id=39838 Category: Import/Install Difficulty Group: v1.0 (example) Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: group table not created during install Initial Comment: Fresh website engine instalation results in a partial install. Missing table grouptable causes errors when deleting nodes. It has been found that the table was not created by running install_esite. Looking through the code for install_esite and the table directory. There is no mention of the table "grouptable". ---------------------------------------------------------------------- >Comment By: Nate Oostendorp (n_oostendorp) Date: 2002-01-24 15:17 Message: Logged In: YES user_id=297846 It seems like the grouptable field on the "nodegroup" nodetype didn't get set to "nodegroup" like it should have. this comment: http://everydevel.com/index.pl?displaytype=display&node_id=2099&lastnode_id=2099 Says that apparently running something like this: create table grouptable ( grouptable_id int(11) DEFAULT '0' NOT NULL auto_increment, rank int(11) DEFAULT '0' NOT NULL, node_id int(11) DEFAULT '0' NOT NULL, orderby int(11) DEFAULT '0' NOT NULL, PRIMARY KEY($tableid,rank) ) at least fixes the error message -- but you shouldn't be getting it in the first place. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=508120&group_id=39838 |
From: <no...@so...> - 2002-01-24 20:19:30
|
Bugs item #508120, was opened at 2002-01-24 12:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=508120&group_id=39838 Category: Import/Install Difficulty Group: v1.0 (example) Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: group table not created during install Initial Comment: Fresh website engine instalation results in a partial install. Missing table grouptable causes errors when deleting nodes. It has been found that the table was not created by running install_esite. Looking through the code for install_esite and the table directory. There is no mention of the table "grouptable". ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426093&aid=508120&group_id=39838 |
From: <no...@so...> - 2002-01-20 22:18:15
|
Feature Requests item #505613, was opened at 2002-01-18 17:52 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426096&aid=505613&group_id=39838 Category: None Group: None >Status: Pending Priority: 5 Submitted By: Martin Espinoza (hyperdrink) Assigned to: Nobody/Anonymous (nobody) Summary: easier check for location-like nodes Initial Comment: I had to modify the node bucket because it checks to see if a node is a location node rather than checking to see if it acts like a location node. It would be nice to have either isOfTypeOrExtends, or isLocation specifically, which would detect if it is or extends location, naturally. ---------------------------------------------------------------------- >Comment By: chromatic (chromatic) Date: 2002-01-20 14:18 Message: Logged In: YES user_id=2274 Passing 1 as the second parameter (the $recurse flag) to Everything::Node::isOfType() ought to fix this. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426096&aid=505613&group_id=39838 |
From: <no...@so...> - 2002-01-19 01:52:12
|
Feature Requests item #505613, was opened at 2002-01-18 17:52 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426096&aid=505613&group_id=39838 Category: None Group: None Status: Open Priority: 5 Submitted By: Martin Espinoza (hyperdrink) Assigned to: Nobody/Anonymous (nobody) Summary: easier check for location-like nodes Initial Comment: I had to modify the node bucket because it checks to see if a node is a location node rather than checking to see if it acts like a location node. It would be nice to have either isOfTypeOrExtends, or isLocation specifically, which would detect if it is or extends location, naturally. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=426096&aid=505613&group_id=39838 |