The simplest blog on symfony 2

Hi% username%!
symfony is a popular PHP framework, on which quite a few serious projects have been created . But in the Russian-speaking community, it is much less common. Whether this is due to a higher threshold of entry, or the lack of Russian-language documentation.
In this article I want to talk about creating a simple blog on symfony2.

Step 0. Software Requirements

Web server (for example, Apache) from 5.3.2 or higher.
Database server We will use MySQL.
Git (optional).

Step 1. Installation.

There are two ways: download the archive from the site or use git. We will go to the second, because many bundles are updated following the repository.
At the root of the web server, execute the following commands:

git clone https://github.com/symfony/symfony-standard.git symfony
cd symfony
php bin/vendors.php

Follow the link http: //localhost/symfony/web/config.php . Here symfony will write requirements and recommendations for setting up a web server.
In my case, you only need to specify the date.timezone directive in php.ini.
There, at the bottom of the page is written the location of your php.ini.
After you fix all the problems, you will find the most interesting.
Follow the link from the same page, http: //localhost/symfony/web/app_dev.php/_configurator/ .
Here you can set up a connection to the database and set a secret key to prevent a CSRF attack.
After that, symfony will be configured, or it will prompt you to enter the resulting configuration itself, if the app / config / parameters.ini file is not writable.
Here it is worth mentioning the bundles. In this case, we will use AcmeDemoBundle - already created bundle to create demo applications. I will not go into the bundles, I will only say that in symfony2 of them, like from bricks, your application is built.
We also need another bundle - FOSUserBundle. It provides everything you need to work with users - login, registration, password confirmation and more.
Download:

git submodule add -f git://github.com/FriendsOfSymfony/UserBundle.git vendor/bundles/FOS/UserBundle

Add a new namespace (namespace) in app / autoload.php:

$loader->registerNamespaces(array( 'FOS' => __DIR__. '/../vendor/bundles' , // your other namespaces ); 

Add a new bundle to our application in the file app / AppKernel.php:

public function registerBundles() { return array( // ... new FOS\UserBundle\FOSUserBundle(), // ... ); } 

In app / config / security.yml, replace the providers parameter:

security: providers: fos_userbundle: id: fos_user.user_manager 

And we also change the firewalls and access_control to allow anonymous access for all pages, except for the message creation page.

firewalls: main: pattern: .* form_login: provider: fos_userbundle login_path: /login use_forward: false check_path: /login_check failure_path: null logout: true anonymous: true access_control: - { path: /post/new, role: ROLE_USER } - { path: /.*, roles: IS_AUTHENTICATED_ANONYMOUSLY} 

In app / config / config.yml, remove auto_mapping: true and add the following:

doctrine: orm: mappings: FOSUserBundle: ~ AcmeDemoBundle: ~ # your other bundles 

and at the end of the file we add:

 fos_user: db_driver: orm firewall_name: main class: model: user: Acme\DemoBundle\Entity\User 

You also need to add it to the framework translator to enable the translation of strings. In particular, the FOSUserBundle lines.

framework: translator: { fallback: en } 

Step 2. Creating models.

Create files in the src / Acme / DemoBundle / Entity directory. If there is no such folder, create it.
Post.php:

<?php namespace Acme\DemoBundle\Entity; use Doctrine\ORM\Mapping as ORM; /** * * @ORM\Entity */ class Post { /** * @var integer $id * * @ORM\Id * @ORM\Column(name="id", type="integer") * @ORM\GeneratedValue(strategy="AUTO") */ private $id; /** * @ORM\ManyToOne(targetEntity="User", inversedBy="posts") * @ORM\JoinColumn(name="user_id", referencedColumnName="id") */ public $user; /** * @var string $title * * @ORM\Column(name="title", type="string", length=255) */ public $title; /** * @var text $description * * @ORM\Column(name="description", type="text") */ public $description; }

Comments before variables - annotations. There should be no difficulties in their use, unless, of course, one wonders “how does it work?”.
User.php:

<?php namespace Acme\DemoBundle\Entity; use FOS\UserBundle\Entity\User as BaseUser; use Doctrine\ORM\Mapping as ORM; /** * @ORM\Entity * @ORM\Table(name="fos_user") */ class User extends BaseUser { /** * @ORM\Id * @ORM\Column(type="integer") * @ORM\generatedValue(strategy="AUTO") */ protected $id; /** * @ORM\OneToMany(targetEntity="Post", mappedBy="fos_user") */ public $posts; public function __construct() { parent::__construct(); // your own logic } }

We inherit from FOS \ UserBundle \ Entity \ User, so that in addition to the two fields that we specified, several more fields will be generated, including username, password and email.
After writing the models, we can safely create the tables:

php app/console doctrine:schema:create

Step 3. Creating a controller.

Create a PostController.php file in the src / Acme / DemoBundle / Controller / folder:

<?php namespace Acme\DemoBundle\Controller; use Symfony\Bundle\FrameworkBundle\Controller\Controller; use Acme\DemoBundle\Entity\Post; use Sensio\Bundle\FrameworkExtraBundle\Configuration\Template; class PostController extends Controller { /** * @Template() */ public function indexAction() { $em = $ this -> get ( 'doctrine' )->getEntityManager(); $posts = $em->getRepository( 'AcmeDemoBundle:Post' )->findAll(); return array( 'posts' => $posts); } /** * @Template() */ public function newAction() { $post = new Post(); // $post->user = $ this -> get ( 'security.context' )->getToken()->getUser(); // , , $form = $ this -> get ( 'form.factory' ) ->createBuilder( 'form' , $post) ->add( 'title' , 'text' ) ->add( 'description' , 'textarea' ) ->getForm(); $request = $ this -> get ( 'request' ); if ($request->getMethod() == 'POST' ) { $form->bindRequest($request); if ($form->isValid()) { $em = $ this -> get ( 'doctrine' )->getEntityManager(); $em->persist($post); $em->flush(); return $ this ->redirect($ this ->generateUrl( 'post_index' )); } } return array( 'form' => $form->createView()); } }

Why do I need Template () before each action? Without him instead

return array('posts' => $posts);

we would have to write

return $this->render('AcmeDemoBundle:Post:index.html.twig', array('posts' => $posts));

Step 4. Templates.

In src / Acme / DemoBundle / Resources / views / Post we will create a view for each action.
index.html.twig:

{% extends 'AcmeDemoBundle::layout.html.twig' %} {% block content %} {% if is_granted('ROLE_USER') %} < div >< a href ="{{ path(" post_new ") }}" > New Post </ a ></ div > {% endif %} {% for post in posts %} < h2 > {{ post.title}} </ h2 > {{ post.description }} < div > by {{ post.user.username }} </ div > {% else %} . {% endfor %} {% endblock %} 

new.html.twig:

{% extends 'AcmeDemoBundle::layout.html.twig' %} {% block content %} < h1 > New Post </ h1 > < form action ="{{ path(" post_new ") }}" method ="post" > {{ form_widget(form) }} < input type ="submit" class ="symfony-button-grey" value ="Create" /> </ form > {% endblock %} 

About the Twig template engine is already partially mentioned in Habré , but there is also excellent official documentation , though in English.

Step 5. Routes.

In app / config / routing.yml we register our routes and do not forget about UserBundle

post_index: pattern: /post defaults: { _controller: AcmeDemoBundle:Post:index } post_new: pattern: /post/new defaults: { _controller: AcmeDemoBundle:Post:new } fos_user_security: resource: "@FOSUserBundle/Resources/config/routing/security.xml" fos_user_user: resource: "@FOSUserBundle/Resources/config/routing/user.xml" prefix: /user * This source code was highlighted with Source Code Highlighter .

Now our blog will be available via the link http: //localhost/symfony/web/app_dev.php/post , and when you try to go to http: //localhost/symfony/web/app_dev.php/post/new you will be redirected to the page the entrance.

Afterword

I do not pretend to be a complete guide and originality, it is rather a quick start note for an application for myself.
I would be happy if someone come in handy, just do not give up help and criticism.
Who will have questions - ask, I think on Habré there are people who are engaged in this framework.
In addition, we have a jabber conference symfony@conference.jabber.ru

Source: https://habr.com/ru/post/120645/

All Articles