Gallaway wrote:
Scott M. Likens wrote:
Ahh,
Then you need to remove any other offending ruby libraries that do
not reside in /opt/local/lib
Next time try not to find ancient arcane bugs that make me think
your running panther... :)
FYI, it's usually just in /usr/lib (libruby??.dylib??
homas Gallaway wrote:
Scott M. Likens wrote:
Hi,
Using Macports or system Ruby?
lhc:/var/www/atomlab atom$ gem env
RubyGems Environment:
- RUBYGEMS VERSION: 1.3.2
- RUBY VERSION: 1.8.7 (2009-04-08 patchlevel 160) [powerpc-darwin8]
- INSTALLATION DIRECTORY: /opt/local/lib/ruby/gems/1.8
-
Hi,
Using Macports or system Ruby?
On Apr 27, 2009, at 10:29 PM, Thomas Gallaway wrote:
I just spent 2 days figuring this out but it seems the issue is one
of the gems in the vendor/gems directory.
Machine is a Mac Mini G4 1.25ghzisch with 10.4.6isch? (Anybody else
dislike the new intel m
http://www.pillowfactory.org/2008/06/06/twitter-plugin-for-typo
On Oct 14, 2008, at 2:50 PM, Bill McGonigle wrote:
Is anybody updating their Twitter feed automatically with Typo?
I've seen a few sites that will pose as intermediaries, backed on
trackback pings but I'm not real keen on handi
post'
/usr/lib64/ruby/1.8/timeout.rb:53:in `timeout'
Finished in 22.50511 seconds
464 examples, 2 failures
Figured i'd say it, try it...
Thanks,
Scott
On Jul 21, 2008, at 11:13 AM, de Villamil Frédéric wrote:
Hello,
After a long time of development, Typo 5.1 "Cartier
another web
server just to run Typo from Typo's own docs, perhaps I wouldn't be
complaining about the docs.
You have issues with
Typo and want help. Is this really how you ask for help?
I certainly wasn't asking Scott for help, and he certainly wasn't
providing any. He jum
On Jul 16, 2008, at 5:09 PM, JZ wrote:
On Wed, Jul 16, 2008 at 4:22 AM, Scott Likens <[EMAIL PROTECTED]> wrote:
To whomever it may concern,
I notice the common thread here. How to deploy typo?
There is many ways to deploy typo, the most common is
1) FastCGI.
We all know, it sucks
On Jul 16, 2008, at 3:36 PM, Chet Farmer wrote:
Scott,
You persist in answering questions that I'm not asking. At this
point, I won't give a damn about Typo deployment again until some
time *after* the bug fixes I require are deployed, if then.
Your ongoing insistence that Ty
On Jul 16, 2008, at 3:47 PM, Chet Farmer wrote:
We are comparing an Apple to a Pear, LAMP is not the same as LAMR
or a Ruby on Rails install. Please stop comparing it, you are
doing nothing useful by doing that.
Are you really saying you can't compare a Ruby app with a LAMP app?
That's r
On Jul 16, 2008, at 6:43 AM, Chet Farmer wrote:
On Jul 16, 2008, at 6:04 AM, Scott Likens wrote:
Which portion of the documentation needs to be revised? FastCGI?
Mongrel?
Honestly, all of it. I know that's a broad answer, but it's the
truth. Compare the installation experience
On Jul 16, 2008, at 6:38 AM, Chet Farmer wrote:
Beats me. Perhaps you should refer to the first portion of my reply
to you last night.
It's clearly a problem, though. It's also a problem that the purpose
of Mongrel isn't made clear; you just have to take on faith that
it's something you n
On Jul 16, 2008, at 12:12 PM, Rodger Donaldson wrote:
Why is mod_proxy working with mongrel such an exercise?
That's it as a whole, 7 whole lines. Add that to your apache
configuration in a Virtualhost area for your blog and startup typo
and you should be golden.
At which point you wonder
On Jul 16, 2008, at 12:14 AM, Rodger Donaldson wrote:
Chet Farmer wrote:
Now, there's no real difference with Mongrel/Webrick if you run
nginx or Apache or lighttpd. It works, it's well documented and
takes the most amount of memory (actually all of them really take
the same amount of me
ails like this
just tick me off. They provide no help to speak of while insisting
there is no problem.
Also, proofreading is a good idea.
On Jul 15, 2008, at 10:22 PM, Scott Likens wrote:
To whomever it may concern,
I reckon that would be me, among others.
I notice the common thread her
y if you
fix what is broken, without reporting it and giving a patch so it can
be addressed. Not everyone is a developer, not everyone can program
ruby on rails. But Frédéric cannot fix a bug he is not aware of, nor
can Piers.
Thank you for your time.
Sincerely,
Scott M. Likens___
Hi Arun,
I see this topic was touched on but I figured hey... let's beat it to
death!
Typically with major version changes of the "Rails" Core, from 2.0 to
2.1, the application needs to be "ported" to the new version.
Depending on the changes this may be easy, or painful.
However, when
Hi,
It wasn't that I had any doubt that db:create should work, it was that
rake task is defined in rails, and not typo. So I felt it was more
rails related. Where it's casued or ended, I don't know.
it works for me with regular ruby 1.8.6, I don't use jruby so I did
not test, but I assu
Arun,
First you need to modify the database.yml so it has permission to
access typo_dev typo_tests or typo.
If you want to run with root that's fine.
at a shell prompt type,
mysqladmin create typo
mysqladmin create typo_dev
mysqladmin create typo_tests
then you can try rake db:create
On
Okay this is plain silly,
what does your config/database.yml show?
Which Adapter are you using SQLite3? MySQL?
If you are using MySQL please create the database, db:create does not
create the database for you.
... and if you are unaware of how to do that, then please read the
manual for w
missions.
I've made sure that ~typo is set to 777, and~typo/public (and all
files/subdirectories) is also set to 777. Thishasn't resolved the problem.
Does anyone have any ideas I could try? I'd be grateful for any advice offered.
Scott
#!/usr/bin/env ruby
#
# You may specify the
asted that points this out is,
>> ActionController::MissingTemplate (Missing layout ../../themes/
>> laughingatyou/layouts/default in view path /Users/carney/
>> 8Misbehaving/themes/laughingatyou/views:/Users/carney/8Misbeha
>> ving/app/views):
Hope this helps
Scott
On
he restart fails... not very likely since it's a restart but I've
seen it happen.
BTW, I just did that, it disabled it, re-started typo and it started
working again without restarting apache... running Apache 2.2.8
Hope that helps.
Scott
On Feb 16, 2008, at 8:17 AM, Pat Ferrel wrote:
Okay, I'm going to explain why Dir::tmpdir is different on Linux and
OS X.
this is fairly easy, if you grok the tmpdir.rb you can see why.
we take this bit of code
for dir in [ENV['TMPDIR'], ENV['TMP'], ENV['TEMP'],
ENV['USERPROFILE'], @@systmpdir, '/tmp']
if dir and
eleted out of public/.
Scott
On 4/4/07, Eamon Ford <[EMAIL PROTECTED]> wrote:
> Hi Guys,
> I'm running Typo on Dreamhost with shared hosting. Apparently, this
> is a problem, because I keep getting 500 errors, and it used to be
> only sometimes, but then it started getting
Or a full-blown CMS! I don't think Typo (or, indeed, most blogging
engines) could be easily modified to do this. Maybe look at Drupal,
Joomla, or something like that?
On 2/17/07, Trejkaz <[EMAIL PROTECTED]> wrote:
> On Saturday 17 February 2007 08:21, Robert Sanford wrote:
> > I'm looking for a
Out of curiosity, how will page caching work any better with extra
headers? It doesn't store *any* HTTP headers at all on disk, even
content-type.
Scott
On 1/5/07, Piers Cawley <[EMAIL PROTECTED]> wrote:
> It turns out that fragment caching really doesn't play nicely with
I really *like* threads for this sort of thing. Pity Ruby's threads
are so weak, and double pity that Rails freaks out if you even
*mention* the word "thread" around it.
Scott
On 12/29/06, Piers Cawley <[EMAIL PROTECTED]> wrote:
> "Scott Laird" <[EMAIL PROT
Thanks. I this was one of those "looked like a good idea at the time"
patches that probably shouldn't have went in in the first place.
I wish that dealing with background processing wasn't such a pain with
Rails. Ugh.
Scott
On 12/28/06, Piers Cawley <[EMAIL PROTECT
week of my life. Hopefully I'll be able to make more
progress in the next few days.
Scott
On 10/19/06, Piers Cawley <[EMAIL PROTECTED]> wrote:
> Would anyone be awfully upset if I removed the DNS blacklist based
> spam checking for the time being? I want to try and pluginize the
>
Ooh. Cool.
Scott
On 10/8/06, Steve Lenti <[EMAIL PROTECTED]> wrote:
> Here is a stupid little macro plugin for typo I wrote so you can type
> and it will embed the youtube code into a
> post. It took all of two minutes but I would love to go further by
> maybe incorporati
Try looking at the trunk--it has a number of multi-blog changes. This
might Just Work.
Scott
On 10/6/06, hemant kumar <[EMAIL PROTECTED]> wrote:
>
> Before save I tried setting following method call. doesn't work... :(
>
> @article.set_blog_id(this_blog.id)
>
>
I'm working on a solution, but it'll probably take a couple weeks
before it's really ready for use. If I hear back from planetargon
anytime soon, then we might be able to upgrade Trac again and make it
stop spamming in the mean time.
Scott
On 10/4/06, Ernie Oporto <[EMAIL
I haven't seen this before. File a bug, I'll look at it when I can.
Scott
On 10/1/06, Alastair Rankine <[EMAIL PROTECTED]> wrote:
> Here I am, killing spam again. I've let it accumulate for a couple of
> days so now I've got a fair bit. Only trouble is that t
ters still allow spam to be submitted, but if the comment
fails the spam check then it's dropped into the DB flagged as spam and
it's not displayed. Look at the feedback tab in the admin UI to
filter things.
Scott
Scott
___
Typo-list mailing list
Typo-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/typo-list
Yeah, but Typo itself has *always* used nofollow for comments, yet
comment spammers have developed tools to spam Typo.
I honestly don't think that the spam-tools people care a bit about nofollow.
Scott
On 9/29/06, Thomas, Mark - BLS CTR <[EMAIL PROTECTED]> wrote:
> That&#x
Yeah, the thought has occurred to me. Two problems:
1. No RSS feeds of new issues. Email notification is there now, though.
2. No easy way to import past bugs.
How important are these to people?
Scott
On 9/29/06, Piers Cawley <[EMAIL PROTECTED]> wrote:
> "Scott Laird"
e's not
a whole lot I can do without them--I don't have write access to either
Trac or our Apache config.
Scott
On 9/29/06, Thomas, Mark - BLS CTR <[EMAIL PROTECTED]> wrote:
>
> > Hey does anyone police Trac for spam? Can we make it take
> > registered users only or
er to
sweep everything if one doesn't already exist.
We should probably also add a 'if comment is published' in there
somewhere, because even spam comments are nuking my cache.
Scott
On 9/28/06, Piers Cawley <[EMAIL PROTECTED]> wrote:
> At the moment we're holding whitebo
rstand and replace it with new code that I'll have to
learn.
Perhaps we should consider finishing up 4.1 first and then start on
this? When is Rails 1.2 due?
Scott
On 9/28/06, Piers Cawley <[EMAIL PROTECTED]> wrote:
> You may or may not know that I have a local branch in my SVK
&
Look in the logs.
Scott
On 9/27/06, mathew <[EMAIL PROTECTED]> wrote:
> OK, Akismet doesn't seem to be helping either. How do I find out if
> the Akismet service is even being contacted?
>
> This is very frustrating. Without any spam filtering, typo is pretty
> muc
I have no idea why svk decided to commit this, but no files were
changed. Weird.
Scott
-- Forwarded message --
From: typo <[EMAIL PROTECTED]>
Date: Sep 26, 2006 7:05 PM
Subject: Re: [typo] #1110: Make markup_help_popup XHTML compliant
To: undisclosed-recipients
#1110
That's part of the issue, but it'd be nice if *every* link to /admin
(or /accounts) used https while non-authenticated links still use
http. That's a bit harder to do from Apache.
Scott
On 9/21/06, Linda Derezinski <[EMAIL PROTECTED]> wrote:
> Scott,
>
> I b
> I do this on the Apache side using redirects, but it isn't pretty.
>
> I tried that and with ProxyPass setting and it only fails. Could you
> paste me your redirection ?
Sooner or later I'd like to make this a config option--if it's set,
then Typo generates all /admin UR
Yeah, that's what I told myself a couple weeks back, but I've moved
from the 'vacation+conference' state to the 'vacation-induced-backlog'
state at work. Sooner or later...
Scott
On 9/20/06, Piers Cawley <[EMAIL PROTECTED]> wrote:
> Just a heads'
Not really--it's a name-based virtual host, so that won't help.
It shouldn't matter, though--DNS has been updated. It'll take a while
to spread, but it'll start working soon-ish.
Scott
On 9/14/06, Ben Reubenstein <[EMAIL PROTECTED]> wrote:
> Would it help tem
Patrick Lenz (scoop)
Scott
On 9/14/06, Levi McCallum <[EMAIL PROTECTED]> wrote:
> What, does Tobi still control it?
>
>
> On 9/14/06, Scott Laird <[EMAIL PROTECTED]> wrote:
> > Our IP got changed out from underneath us. We don't control the DNS
> >
Our IP got changed out from underneath us. We don't control the DNS
ourselves; I'm trying to get it changed.
Scott
On 9/14/06, Levi McCallum <[EMAIL PROTECTED]> wrote:
> neather
>
>
> On 9/14/06, Matt Rose <[EMAIL PROTECTED]> wrote:
> > I can't see
Who owns typosphere's DNS record?
Scott
-- Forwarded message --
From: David Gibbons <[EMAIL PROTECTED]>
Date: Sep 13, 2006 11:37 AM
Subject: typosphere.org dns
To: Scott Laird <[EMAIL PROTECTED]>
Hey Scott, Our hosting provider yanked one of our IPs from us.
File a bug, and I'll look at it when I can. Last-modified is easy
enough, we'll just add it to our cache code. I'm not sure about
etags.
Scott
On 9/13/06, Alastair Rankine <[EMAIL PROTECTED]> wrote:
> Typographers,
>
> One question that has been bugging me
It wasn't our key that expired; there was a key hard-wired into the
Flickr library that we've bene using. See
http://www.typosphere.org/trac/changeset/1256 for the fix.
If this works for everyone then I'll build Typo 4.0.4 and release it soon.
Scott
On 8/31/06, Chris Saylor &l
Not quite. We're fairly close to having it work on the current trunk,
but none of the admin tools are there, and the permission checking
system doesn't work like you'd expect.
Scott
On 8/31/06, Hemant . <[EMAIL PROTECTED]> wrote:
> Is it possible to host multiple si
I'll update it ASAP; probably tonight.
Scott
On 8/30/06, Andy Ciordia <[EMAIL PROTECTED]> wrote:
>
> Just started to get:
>
> " could not be displayed because:
> Invalid API Key (Key has expired)"
>
> On photos that were pulled with the method.
>
ything up. But that'll probably be a bit longer still, and
things will break at least once more when we move themes into
vendor/plugins.
Scott
On 8/26/06, Sterling Anderson <[EMAIL PROTECTED]> wrote:
> I just updated my blog to the trunk yesterday and was surprised when
> my them
On 8/23/06, Piers Cawley <[EMAIL PROTECTED]> wrote:
> "Scott Laird" <[EMAIL PROTECTED]> writes:
>
> > On 8/23/06, Doug Bromley <[EMAIL PROTECTED]> wrote:
> >> Definately not old code. Cleaned out entirely. I haven't tried it
> >
en in the current
trunk--we've made a bunch of schema changes without updating all of
the converters.
Scott
___
Typo-list mailing list
Typo-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/typo-list
On 8/22/06, Piers Cawley <[EMAIL PROTECTED]> wrote:
> "Scott Laird" <[EMAIL PROTECTED]> writes:
> > Since we're breaking everything for 4.1 anyway, this would be a
> > *great* time to make structural improvements. Perhaps we could even
> > go as
g issues that I
haven't spent much time thinking about, but I'm sure they're solvable.
Scott
On 8/22/06, Steve Longdo <[EMAIL PROTECTED]> wrote:
> Now that the sidebars have been split out is there a plan to make their
> inclusion/installation an optional process a
I suppose it would make the trick work on multiple web servers
> > while only having to write the redirection code once. :-)
>
> Oh, that's easy. We already have a redirection controller.
Yeah. Typo's least-used feature :-).
Scott
___
Typo-list mailing list
Typo-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/typo-list
o the (small) amount of work needed to move
Typo themes into vendor/plugins, just so we can use Rails
plugin-management tools to install themes. I can take care of this
later this week, unless Piers really wants to do it :-).
Scott
___
Typo-list mailing list
Typo-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/typo-list
http://home.leetsoft.com/liquid/
I've been wondering the same thing. I haven't really looked at
Liquid's performance, but I wouldn't mind adding it as an option.
Scott
___
Typo-list mailing list
Typo-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/typo-list
If you're writing it just to make yourself happy and
serve your own needs, then have fun. If you're trying to build
something that lots of people will adopt, then you're going to have to
do a lot of work to beat Flickr, though.
Scott
___
Typo-list mailing list
Typo-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/typo-list
\003 is Control-C, which isn't a Unix line ending character. Is it
just this one file?
Scott
On 8/19/06, Brian Hutchison <[EMAIL PROTECTED]> wrote:
> Is anyone else having problems with the 4.0.x code (including trunk) under
> Windows? I'm running Windows XP SP2 and I
h it. Frankly, the $25/year
they want for "professional" memberships is probably less then I'd pay
maintaining my own site for a year.
Scott
___
Typo-list mailing list
Typo-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/typo-list
be in the
minority on this, though :-).
I can see moving to restful URLs for API-ish code like the feeds (and
then mirroring them with PUT, DELETE, to replace the admin interface),
but it's not clear to me that more restful permalink URLs really
achieves any particular goal. Can you give a couple examples?
Scott
___
Typo-list mailing list
Typo-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/typo-list
ow it isn't exactly hard. But see above.
This brings up a reasonably obvious question that I haven't seen asked
yet--why not turn off RBL and like Akismet take care of it? Akismet
seems pretty fast, and I've been happy with its error
Yeah, it's a cache hit. There's no easy way to keep rails from logging it.
On 8/20/06, Piers Cawley <[EMAIL PROTECTED]> wrote:
> Gary Shewan <[EMAIL PROTECTED]> writes:
>
> > Checking the logs I'm getting a lot of these 'errors':
> >
> > Filter chain halted as [# > actionpack/lib/action_controlle
Oops--it worked at the time, but newer code has already broken it.
Try r1243, it should be fixed.
Scott
On 8/18/06, David Richardson <[EMAIL PROTECTED]> wrote:
> Migrations broken.
>
> == FixCanonicalServerUrl: migrating
> ===
> rake
On 8/18/06, Dick Davies <[EMAIL PROTECTED]> wrote:
> On 18/08/06, Scott Laird <[EMAIL PROTECTED]> wrote:
> > This is just a heads-up--I'm going to commit a big block of 4.1 code
> > soon-ish and then head out of town for a couple days, possibly without
> > net
grab your feed.
The multi-blog code will probably start soon-ish. It's a fairly
simple progression from where we're at now, although the first pass on
multi-blog support won't include any extra permission checking, so all
users will have admin access to all blogs. Obviously this is
value stability, don't go past r1232 for now.
Scott
___
Typo-list mailing list
Typo-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/typo-list
Typo 4.0.3 is out. It's a bugfix release, with a week's worth of small fixes.
This is the last "mainline" 4.0.x release. I just made a maintenance
branch for 4.0.x. I'm going to start adding 4.1 features to the trunk
soon,
;m not entirely sure where I should be
> looking. My naive guess is that this is somehow related to the new state
> changing code, and perhaps the state of a piece of content changes
> differently depending on whether it was created through the fronte
ced on trunk after it was branched.
Hmm. Mail notifications work for me. The jabber ones used to work
for me, but I haven't retested. I'll work on them once I've finished
merging my big block of 4.1 code.
The current trunk (r1230) is still 4.0.x; 4.0.3 will be out
It should be possible. I think Piers has something clever planned for
sidebars, but I'm not quite sure what it is yet .
Scott
On 8/17/06, Steve Longdo <[EMAIL PROTECTED]> wrote:
> Will approach you are using for textfilters work in migrating sidebars from
> comp
FWIW, I tracked down the leak--my new route cache wasn't actually
working right, so it was losing 1 string per Article. Fixed :-). I
haven't tested the trunk yet, or any of the admin pages.
Scott
On 8/16/06, Scott Laird <[EMAIL PROTECTED]> wrote:
> I'm doing a bit of
about adding a 'save' after HTML generation, but that'd
screw up update times, which are visible in a number of feeds.
So I ripped *_html out and moved it to the fragment cache. Filters
are fast enough now that running uncached isn't a big deal in dev mode
306 Aug 16 20:13 typo_textfilter_code
drwxr-xr-x9 slaird staff 306 Aug 16 20:21 typo_textfilter_flickr
...
$ ruby ./test/unit/text_filter_test.rb
Loaded suite ./test/unit/text_filter_test
Started
.
Finished in 0.884198 seconds.
9 tests, 98 assertions, 0 failures, 0 errors
Scott
That looks like your web server is telling dispatch.fcgi to exit. In
general, Apache's mod_fastcgi is more stable if you configure static
FCGI dispatchers; use google to find config details. If you're using
a different web server, then you're on your own, sorry.
Scott
On 8/16/0
I'm probably going to package up 4.0.3 tomorrow. I've seen people
talk about a couple bugs that I don't see in trac. If you have a
4.0.x bug that needs to be fixed in 4.0.3, can you make sure that it's
in trac tagged with milestone 4.0.3 within the next 8-12 ho
It's worked fine for me in testing. Which version of Typo, and what
do you mean by "work correctly"?
Scott
On 8/16/06, Linda Derezinski <[EMAIL PROTECTED]> wrote:
>
> Anyone using Mongrel Rails with Typo?
>
> We ended up having to turn off caching to get it
I'm doing a bit of memory testing in my 4.1 tree, and I haven't found
anything all *that* exciting yet. I'm using a objectspace profiler by
Ryan Davis, lightly modified to produce a bit more info. Two things
seem obvious:
1. Cached hits don't leak anything. The total number of objects
per t
tegories? Can you explain them, how they differ from our current
category system, and what you'd use them for?
Scott
___
Typo-list mailing list
Typo-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/typo-list
#x27;ve fixed this in my 4.1 tree, but I haven't
tested that part yet. I'm still busy deprecating old helpers.
Scott
___
Typo-list mailing list
Typo-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/typo-list
gt; DTrace is coming with Leopard. <>
I kind of doubt that dtrace will be very useful in debugging memory
use inside of Ruby code--the interpreter will probably swizzle things
enough to screw up dtrace. OTOH, it'll probably be nice for I/O
work...
Scott
___
On 8/15/06, Paul Brown <[EMAIL PROTECTED]> wrote:
> On 8/15/06, Scott Laird <[EMAIL PROTECTED]> wrote:
> > One thing I'd recommend (if you aren't doing this already) is to build
> > a memory profiler component with an action that dumps your memory
> >
accessible.
If one of these was easily available, then I wouldn't have to write my
own when I start working on memory leaks. Hint, hint.
Scott
On 8/15/06, Steve Longdo <[EMAIL PROTECTED]> wrote:
> On TextDrive the profiling code has enough overhead it kills the thread
> sometime
On 8/15/06, Scott Laird <[EMAIL PROTECTED]> wrote:
> On 8/15/06, Josh Knowles <[EMAIL PROTECTED]> wrote:
> > On 8/15/06, Josh Knowles <[EMAIL PROTECTED]> wrote:
> > > I thought it might be something like this but was given no log message
> > indicating tha
the right direction!
>
> So even with the removal of the majority of the components my two processes
> are still hovering around 42-48meg, is this normal?
>
> Josh
That's still higher then I'd like to see, but it's within the range
that people have reported.
Scott
On 8/15/06, Piers Cawley <[EMAIL PROTECTED]> wrote:
> "Scott Laird" <[EMAIL PROTECTED]> writes:
>
> > On 8/15/06, Piers Cawley <[EMAIL PROTECTED]> wrote:
> >> "Scott Laird" <[EMAIL PROTECTED]> writes:
> >>
> >> >
On 8/15/06, Piers Cawley <[EMAIL PROTECTED]> wrote:
> "Scott Laird" <[EMAIL PROTECTED]> writes:
>
> > Next, I cleaned up a bunch of helper code. We had at *least* 8 copies
> > of the article permalink generation code, and a pile of redundant ways
> >
Er, yeah--we need to fix that. presumed_ham -> ham shouldn't trigger
notifications.
Scott
On 8/14/06, Gary Shewan <[EMAIL PROTECTED]> wrote:
> I like the 'Ham?' or 'Spam?' filtering, but if you have an
> established blog and want to limit the list in f
have time to clean up themes. This probably won't be the last
incompatible theme/sidebar/text filter change for 4.1, but we'll have
some good things that will make up for it soon--trust us :-).
Scott
___
Typo-list mailing list
Typo-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/typo-list
down) and the processed format (for importers that
don't understand the original format).
Next, can you rename export:page to export:static or something
similar? I'd rather not be *too* Typo-specific :-).
Also, how does this represent things like:
- per-article trackback/comment open
FWIW, I'm working on URL cleanups in a local branch. I'm throwing out
a lot of code :-).
Scott
___
Typo-list mailing list
Typo-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/typo-list
We haven't looked at it yet. It's not a high priority, because the
current code works well enough, and I don't really expect to see habtm
disappear in the near future, no matter how little the Rails core
likes it.
Is there actually an advantage to converting existing code?
Sc
ran 'typo config
PATH database=mysql' should be able to use 4.0.2, unlike 4.0.1.
Sorry. In addition, it's now possible to install directly onto MySQL
(and Postgres). I'll document it once the 4.0.2 madness has subsided.
Scott
___
Ty
On 8/10/06, Phillip Toland <[EMAIL PROTECTED]> wrote:
> On 8/10/06, Scott Laird <[EMAIL PROTECTED]> wrote:
> > I'd like to get native mysql support into the installer. I'd really
> > like to get it in *today*. So I'd like some help. It's not all
I can see if happening with your site, but it's not happening with my
site. Let's test a few more, and then release 4.0.3 if we need to. I
don't have time to test this before we spit out 4.0.2, unfortunately.
Scott
On 8/10/06, Paul Barry <[EMAIL PROTECTED]> wrote:
>
#x27;yml' method that builds a database.yml, and a
create_database method that can create a MySQL db.
If someone can implement this *now* and let me know, then I can
include it in Typo 4.0.2. The source lives in
http://rails-app-installer.googlecode.com/svn/trunk; you should be
able to check
There should be a 4.0.2 today.
Scott
On 8/10/06, Eric Sendelbach <[EMAIL PROTECTED]> wrote:
> Since rails 1.1.6 is out, so can we expect a typo 4.0.2 soon since the patch
> for 1.1.5 is to upgrade and apparently didn't fix all the holes?
>
> http://weblog.rubyonrails.or
1 - 100 of 508 matches
Mail list logo
