Ok, maybe i didn't read the end of the text carefully. The last
paragraph i see is about "Requiring Special Credentials to Edit
Pages". And here, the last thing i can read is an app.yml example (in
a black box):
all:
a:
edit_sufficient_credentials: ed
So no credits you mentioned. The next thing is the green footer of the
general symfony page ... If that's not the end, then you're right ...
Sorry about my post :(
Michael
On 15 Feb., 12:02, Tom Boutell <[email protected]> wrote:
> It is definitely cutting off in the middle of an app.yml example for
> me. It should end with a credits and community section, but it's
> cutting out about halfway through. I think perhaps you weren't sure
> what to expect at the end.
>
> On Mon, Feb 15, 2010 at 3:50 AM, [email protected]
>
>
>
>
>
> <[email protected]> wrote:
> > I see no problems with this long README. Tried Chrome, IE 8 / 7,
> > Firefox, Opera ... works perfectly.
>
> > Michael
>
> > On 13 Feb., 18:13, Tom Boutell <[email protected]> wrote:
> >> Please have a look at the apostrophePlugin README:
>
> >>http://www.symfony-project.org/plugins/apostrophePlugin?tab=plugin_re...
>
> >> The Symfony site's markdown rendering ends abruptly halfway through
> >> the document.
>
> >> We're rendering the same document successfully here using the latest
> >> stable release of PHP markdown, just calling markdown() on our source:
>
> >>http://www.apostrophenow.com/home/readme
>
> >> I should note that on the first try a slightly older version of PHP
> >> markdown gave us an empty page (!), so we upgraded to 1.0.1n and then
> >> we had no problems:
>
> >>http://michelf.com/projects/php-markdown/
>
> >> Is there a maximum length for READMEs on the Symfony plugins site? If
> >> so please document this and if possible adjust the
> >> newly-uploaded-plugin validator to check for READMEs that are too
> >> large, as I wasn't aware of the problem until I happened to scroll to
> >> the bottom, so I imagine others will make the same surprising
> >> discovery.
>
> >> (Yes, our manual is rather long, but giving people enough information
> >> isn't exactly a bug. (: We'll probably break it into multiple pages at
> >> some point)
>
> >> It would also be nice if the deeper heading levels didn't render as
> >> rather small italicized text, as they are still headings, but that's a
> >> detail, not a bug.
>
> >> Apologies for reporting this just as we're all getting ready to attend
> >> Symfony Live. Looking forward to meeting folks!
>
> >> --
> >> Tom Boutell
> >> P'unk Avenue
> >> 215 755 1330
> >> punkave.com
> >> window.punkave.com
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "symfony developers" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected].
> > For more options, visit this group
> > athttp://groups.google.com/group/symfony-devs?hl=en.
>
> --
> Tom Boutell
> P'unk Avenue
> 215 755 1330
> punkave.com
> window.punkave.com
--
You received this message because you are subscribed to the Google Groups
"symfony developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en.
