I might have missed something but I think there is no documentation about group validation.

i'm doing a push request

I think the testing chapter is "sound", but I haven't really looked at it yet and no work has gone into it in quite some time.

From the templating chapter of the book:

"In Symfony2, almost every part of a bundle can be overridden so that you can use and customize it for your specific application. "

After searching far and wide, ie. the book, cookbook, forum, google, etc. there does not seem too much meat beyond the brief statement above on how to accomplish this.

The references I know about so far are:

http://symfony.com/doc/2.0/book/templating.html#overriding-bundle-templates
http://symfony.com/doc/current/cookbook/event_dispatcher/class_extension.html
http://symfony.com/doc/current/cookbook/event_dispatcher/method_behavior.html
https://groups.google.com/forum/#!topic/symfony-users/o1hj4tQZB28

In particular, one might need to know how to extend things like: bundle controllers, models, entities, validation rules, routes, config settings, services, service extensions, forms, etc.

Keep up the great work on the documentation. It is really starting to take shape.

Hi,

I was reading the new released security documentation and just found a little issue in one example. The issue is found at cookbook/routing/scheme.rst.

Here is the current text

# If the current scheme is HTTPS
{{ path('secure') }}
# generates /secure

# If the current scheme is HTTP
{{ path('secure') }}
# generates https://example.com/secure

and should be like:

# If the current scheme is HTTP
{{ path('secure') }}
# generates /secure

# If the current scheme is HTTPS
{{ path('secure') }}
# generates https://example.com/secure

Notice the swap between HTTP/HTTPS, as the generated https schema is while using https, not http (well, I guess :-D)

There's a huge amount of people developing with Symfony on the Mac, often using the default Snow Leopard PHP install.

By defauly OS X lacks APC, MongoDB and memcache.
Fortunately, installing these extensions is VERY easy and hassle-free with brew.

brew install apc mongo-php memcache-php

A lot of people are put off with messing around with compiling/installing PHP extensions, so the barrier to entry is increased.
Might wanna add a cookbook entry for this and other Mac tricks (textmate bundles, etc)

I got bit by this so I thought I'd mention it. I added FOW\UserBundle to my app after I'd been working on other pieces. I found the strings on FOSUB's stock login page and others were not being translated. I found I needed to add the config entry to enable translation but that didn't fix the issue. I needed to clear my cache before the change was applied. Perhaps a little blurb suggesting "cache:clear" next to the instructions for adding the config entry is in order?

This chapter uses the development environment in order to show how to create pages in Symfony2:

http://localhost/app_dev.php/hello/Symfony

But in the chapter, instead of editing the routing_dev.yml (the one used by the development environment), we are told to edit the routing.yml, which could be confusing:

app/config/routing.yml

homepage:
pattern: /
defaults: { _controller: FrameworkBundle:Default:index }

hello:
resource: "@AcmeStudyBundle/Resources/config/routing.yml"

So I was wondering if this could be a mistake or if I'm missing something here.

We should probably add an example, or a note to the documentation showing how to implement Serializable in the user object. This seems to be a common pain point considering the number of threads that have been created on this topic.

In the book it states, that you can call the following from your controller class:
$form = $this->createFormBuilder($product)

but this function does not exists. Perhaps one has to add some configuration, but it should be stated in the book.

Instead I think you have to call

$factory = $this->get('form.factory');
$form = $factory->create(new JobType(), $job);

On the PDO session storage cookbook entry (https://github.com/symfony/symfony-docs/blob/master/cookbook/configuration/pdo_session_storage.rst), we show how the connection information from Doctrine can be re-used for the PDO connection used by the session storage.

However, a better solution to this would be to actually re-use Doctrine's wrapped PDO connection (see @stof's comment here: #209 (comment)). I think this should be added to the chapter and should probably replace the section where we reference the Doctrine connection parameter placeholders.

On this page http://symfony.com/doc/current/book/doctrine/orm.html it says to do the following to get an entity manager:

$em = $this->get('doctrine')->getEntityManager();

which doesn't work in current version and just gives a service not found message. The following does get an entity manager:

$em = $this->get('doctrine.orm.entity_manager');

More of an issue with the Symfony2 website. When I'm browsing through a long list of links, would be nice to know which ones I have visited, and it is kinda best-practice too.

The current cache chapter should be modified slightly to give more real-world use cases as soon as possible and then gradually introduce more advanced topics and theory.

In http://symfony.com/doc/current/book/security.html , under "Avoid Common Pitfalls", bullet nr. 2, in the third YAML snippet, under "secured_area", there is an incorrect option.
The option name should be "form_login" instead of "login_form".

All of the indexes in the book need to be checked and updated.

The Security docs mention "authentication can be handled in any number of ways, including via a form login, X.509 certificate, or by authenticating the user via Twitter"

It would be cool to back this up with an example

Hi all.

Very necessary documentation on the use of the AsseticBundle. I tried use it in my project and have many questions.
Existing documentation:
http://www.slideshare.net/kriswallsmith/assetic-symfony-live-paris
http://sftuts.com/using-assetic-in-symfony2-for-css-compression
http://symfony.com/doc/2.0/cookbook/assetic/yuicompressor.html

On http://symfony.com/doc/current/contributing/documentation/index.html under "Questions and feedback", there is a link to the old trac bug tracker. This should instead link to the new bug tracker.

I cannot contribute a fix for this because the left pane is outside the documentation.

The bundles chapter is a little dry and focused on the bundle author. The original intention was:

• Organization, configuration, best-practices, community bundles, how to document a bundle, etc.
• Possibly also details on extending/overriding a bundle

For the most part, if we put details about bundles here, we can reference this chapter from elsewhere in the book. This chapter probably won't be terribly long.

At the bottom of http://symfony.com/doc/current/book/doctrine/orm.html , the next chapter is « The Controller » (the previous is "Doctrine DBAL", which is OK).

Buc according to the index, it should be Validation.

It seems It depends directly from symfony.com , I can't find the error in the source code.

It is written that required option is only in order to set the new html5 "required option".

However it is not the case, because this option can also be use to add an empty value (or option) as it is written for choice field : "Adding an empty value" section of https://github.com/symfony/symfony-docs/blob/master/reference/forms/types/choice.rst.

Then this section should be simply copy to :
https://github.com/symfony/symfony-docs/blob/master/reference/forms/types/entity.rst

As stated in the title: there is no explanation for the "grouping" option for number field type.

In the "Routing" chapter there is an error in the second code window in the third line.

namespace Acme/BlogBundle/Controller; // has wrong slashes

namespace Acme\BlogBundle\Controller; // use backslashes instead.

for example there is one link to
http://symfony.com/doc/current/glossary/book/service_container.html,
which should be
http://symfony.com/doc/current/book/service_container.html

Typo in: http://symfony.com/doc/current/book/page_creation.html#the-source-src-directory

"being" written instead of "begin" in:

When you begin development, you'll being to populate the directory with bundles that contain your application code.

I would love to see a technical breakdown of how forms work. The relationship between Factories, Builders, Types, and finally the Extensions that render them.

This isn't really a cookbook article. It would probably be an addendum to the existing core docs. Does anyone else think this would be a helpful addition to the current form documentation?

the old symfony-reloaded.org website used to show the index generated by Sphinx. The symfony.com website does not seems to show it. It would be a good idea to add it back.

I've trying finding documentation on this matter to no help so I'm writing to mention the issue. There is no documentation available on how to alter the segment separators for symfony2. I was trying to use an e-mail address as a slug for the route /account/{email} but as Stof on IRC mentioned the default are . and / so in other words e-mail would not be accepted. The behaviour can be altered per route though with a simple:

options: { segment_separators: ['/'] }

under the needed route.

I think this would be of benefit for others seeking this information too, so I think this should be added on the book, at the chapter on routing or a a new recipe for routing.

In http://symfony.com/doc/current/book/doctrine.html

The create action added to the DefaultController of the AcmeStore bundle needs the use of the Product entity. Without it, it causes a fatal error : Fatal error: Class 'Acme\StoreBundle\Controller\Product' not found in /Users/jmaelstaf/Development/htdocs/sftest/src/Acme/StoreBundle/Controller/DefaultController.php on line 18

// src/Acme/StoreBundle/Controller/DefaultController.php
use Symfony\Component\HttpFoundation\Response;
**use Acme\StoreBundle\Entity\Product; //missing statement**
// ...

public function createAction()
{
    $product = new Product();
    $product->setName('A Foo Bar');
    $product->setPrice('19.99');
    $product->setDescription('Lorem ipsum dolor');

    $em = $this->get('doctrine')->getEntityManager();
    $em->persist($product);
    $em->flush();

    return new Response('Created product id '.$product->getId());
}

This needs to be covered both with respect to validation as well as how to setup a form to validation against a specific group.

There's a cookbook article (or will be, upon merge of the doctrine branch) that contains details about hooking up event listeners and subscribers with Doctrine events. I believe that this document is horribly outdated (and should really be expanded as it's a fairly common requirement).

The article "How Symfony2 differs from symfony1" available at:
http://symfony.com/doc/current/cookbook/symfony1.html
has a broken link to the sandbox:
https://github.com/symfony/symfony-sandbox

I think we're missing several things from the form chapter that are important, and I'd like to get a list of them here.

If you can think of things you'd like to see in the form documentation, please add them in the comments below.

Again I might have missed something, but I didn't see any documentation about the AdvancedUserInterface.

Pages deleted during the refactorings of the doc are not removed from the online doc, which means that some outdated doc are still available on line (and potentially indexed by google).

article: "How to Expose a Semantic Configuration"

section:"Creating an extension"

sentence: "To define a semantic configuration, create a Dependency Injection extension that extends Extension who's class name..."

The link to the api code file for "Extension" is broken, returns 404 not found.

I thought that it might be a good cookbook article to write down some basic principles about using a DIC.

Here are some notes that I took:

• Law of Demeter
• Many people use the singleton pattern because it is so incredibly easy to access some data; however, this is a global state and should be recognized as an anti-pattern! DIC to the rescue!
  ---> Example of hierarchy built by DIC, which basically means: Bottom-Up approach, not top-down
• Don't use Service Locator -> one time bootstrapping, that should be it! (However, there might be usecases for RAD - see the discussion on it)
• keyword "new" is bad! if you use it: refactor!
• Hollywood principle -> forces you to program against an interface, not a concrete implementation
• Want to configure objects at runtime? Inject a Builder Object!
• Advantage over factories: Factories may be static and need for testing some method to enable mocking; but as they're static, you must make sure that you tear everything down after your test. With DI, you don't need that!
• Dependencies become obvious with DI and they are part of the API

ANTI-Patterns

• Should I inject the container into my objects?
  --> No! This is an anti-pattern. None of your objects should be aware that something like a DIC even exists.

Examples:

Maybe one could give some example about using the DIC in a real use-case. Maybe one could show how to replace switch-statements (which obviously should never be used in OO code).

I think we definitely need a cookbook article on this.

There's a great blog post on some extensions here, but nothing in the context of symfony2 (that I could find). This is something everyone is sure to want to use.

On the documentation we can read that to setup our cache & log dir we need to issue this two commands.

sudo chmod +a "www-data allow delete,write,append,file_inherit,directory_inherit" app/cache app/logs
sudo chmod +a "yourname allow delete,write,append,file_inherit,directory_inherit" app/cache app/logs

But on linux this command fails:

pate@christophe:/var/www/Sf2MCQ$ sudo chmod +a "www-data allow delete,write,append,file_inherit,directory_inherit" app/cache app/logs
chmod: mode invalide: `+a'
Pour en savoir davantage, faites: « chmod --help ».

See here: http://bundles.symfony-reloaded.org/frameworkextrabundle/annotations/converters.html

The special _locale routing parameter is mentioned in the translation chapter, but a note should be added to the routing chapter. We already mention the _format parameter.

This chapter would include basic introductions into common extension points, such as hooking into core events, adding helpers/twig extensions, etc.

The example line should be: validation: { enabled: true, enable_annotations: true }

On the PDO session storage cookbook (https://github.com/symfony/symfony-docs/blob/master/cookbook/configuration/pdo_session_storage.rst), the XML and PHP versions of the configuration are missing.

These need to be completed.

Add a note that usernames for the in_memory provider cannot contain the following chars: "-" and numbers only

The latter only applies to YML configuration.

There should be an note that defining this:

security:
    providers:
         in_memory:
            users:
                70: { password: pass, roles: 'ROLE_USER' }
                user-name: { password: pass, roles: 'ROLE_USER' }

Will fail, and user should write something like instead:

security:
    providers:
         in_memory:
            users:
                - { name: 70, password: pass, roles: 'ROLE_USER' }
                - { name: user-name, password: pass, roles: 'ROLE_USER' }

Related issues symfony/symfony#1176 and symfony/symfony#1024.

Similar to the Advanced Symfony Forms article in "More With Symfony", we should have a cookbook article illustrating how to have a dynamic number of fields / embedded forms that can be specified by the front end.

An example of this would be a form with multiple uploads, where a user can click "add another upload" and upload as many files (or up to a certain number of files) as they want. This could also be worked into the proposed Create Custom Field Type article.

Kudos to you guys for adding placeholders in the cookbook. I think that's a great idea!

The glossary link on the side of http://symfony.com/doc/current/ currently points to http://symfony.com/doc/current/glossary/index.html.

That's fine, except that all links inside the document now have incorrect paths. The intended link per sphinx should be:
http://symfony.com/doc/current/glossary.html (which works, but isn't the link used in the nav).

The link used in the nav should change, and the current glossary page should probably either go away or be a 301 redirect to the new glossary page.

Write documentation how to get the raw object value into your twig template (form.vars.value)

Copy/pasted from symfony/symfony#784 (comment)