Unknown Column Type "json" Requested Error After Removing SonataUserBundle And FOSUserBundle
While playing around with SonataUserBundle and FOSUserBundle I quickly found out that I had to remove both of them. Long story short, it seems that one of them is not yet supporting the latest version of the other.
Unknown column type json requested
Battle of the Email: Marketing vs. Transactional
It's a known fact that every company out there that has an online activity needs to engage its customers through technical information and increase awareness of its products via marketing campaigns. The problem is that in an email sending system that's not set-up properly, the latter of the two can and will affect the overall deliverability of the company.
How to Quickly Switch the Apache2 VirtualHost
If you're just a little bit like me, then you'll love working with only a single active VirtualHost on apache2. Since switching from one server to another needs a lot of Linux terminal commands, I've built a small bash script that will hopefully ease the process.
How to Quickly Switch the Apache2 VirtualHost
The Chain Design Pattern
Today's article is meant to show you how to go from plain-text tasks to a collection of classes that are meant to work together.Read more
Simple Symfony2.3 Pagination With Both Nativequery And Querybuilder (Doctrine)
Symfony2.3 pagination
I've allocated quite a reasonable amount of time to find a good bundle to achieve pagination AND use NativeQuery in the same time. I didn't. Maybe I should have searched more...Read more
Create a mailer in Rails 4
Create a mailer in Rails 4
Hello party people and polar bears! You were probably wondering how it is you send email using Ruby on Rails. Here's how you create an automated email system
that sends a confirmation email to each new user that registers to your app:Read more
Setup A Simple Ruby 2 On Rails 4 Environment With Vagrant And Virtual Box
Ruby 2 on rails 4 environment
Since a developer time is most valuable when dealing with actual ... development tasks, setting up the environment for a new project better take less or no time, so that the developer can focus on building the actual product rather than focusing on setting up things.Read more
Symfony2 Jobeet Day 16: The Mailer
* This article is part of the original Jobeet Tutorial, created by Fabien Potencier, for Symfony 1.4.
Mailer in jobeet
Yesterday, we added a read-only web service to Jobeet. Affiliates can now create an account but it needs to be activated by the administrator before it can be used. In order for the affiliate to get its token, we still need to implement the email notification. That’s what we will start doing in the coming lines.
The symfony framework comes bundled with one of the best PHP emailing solution: Swift Mailer. Of course, the library is fully integrated with symfony, with some cool features added on top of its default features. Let’s start by sending a simple email to notify the affiliate when his account has been activated and to give him the affiliate token. But first, you need to configure your environment:
# ... # ... mailer_transport: gmail mailer_host: ~ mailer_user: address@example.com mailer_password: your_password # ...
For the code to work properly, you should change the
address@example.com
email address to a real one, along with your real password.
Do the same thing in your app/config/parameters_test.yml
file.
After modifying the two files, clear the cache for both test and development environment:
php app/console cache:clear --env=dev php app/console cache:clear --env=prod
Because we set the mailer transport to gmail, when you will replace the email address from “mailer_user”, you will put a google email address.
You can think of creating a Message as being similar to the steps you perform when you click the compose button in your mail client. You give it a subject, specify some recipients and write your message.
To create the message, you will:
- call the
newInstance()
methond of Swift_message (refer to the Swift Mailer official documentation to learn more about this object). - set your sender address (From:) with
setFrom()
method. - set a subject line with
setSubject()
method. - set recipients with one of these methods:
setTo()
,setCc()
orsetBcc()
. - set a body with
setBody()
.
Replace the activate
action with the following code:
// ... public function activateAction($id) { if($this->admin->isGranted('EDIT') === false) { throw new AccessDeniedException(); } $em = $this->getDoctrine()->getManager(); $affiliate = $em->getRepository('IbwJobeetBundle:Affiliate')->findOneById($id); try { $affiliate->setIsActive(true); $em->flush(); $message = Swift_Message::newInstance() ->setSubject('Jobeet affiliate token') ->setFrom('address@example.com') ->setTo($affiliate->getEmail()) ->setBody( $this->renderView('IbwJobeetBundle:Affiliate:email.txt.twig', array('affiliate' => $affiliate->getToken()))) ; $this->get('mailer')->send($message); } catch(Exception $e) { $this->get('session')->setFlash('sonata_flash_error', $e->getMessage()); } return new RedirectResponse($this->admin->generateUrl('list',$this->admin->getFilterParameters())); } // ...
Sending the message is then as simple as calling the send()
method on the mailer instance and passing the message as an argument.
For the message body, we created a new file, called email.txt.twig
, that contains exactly what we want to inform the affiliate about.
Your affiliate account has been activated. Your secret token is {{affiliate}}. You can see the jobs list at the following addresses: http://jobeet.local/app_dev.php/api/{{affiliate}}/jobs.xml or http://jobeet.local/app_dev.php/api/{{affiliate}}/jobs.json or http://jobeet.local/app_dev.php/api/{{affiliate}}/jobs.yaml
Mailer in jobeet
Now, let’s add the mailing functionality to the batchActionActivate
too, so that even if we select multiple affiliate accounts to activate, they will receive their account activation email :
// ... public function batchActionActivate(ProxyQueryInterface $selectedModelQuery) { // ... try { foreach($selectedModels as $selectedModel) { $selectedModel->activate(); $modelManager->update($selectedModel); $message = Swift_Message::newInstance() ->setSubject('Jobeet affiliate token') ->setFrom('address@example.com') ->setTo($selectedModel->getEmail()) ->setBody( $this->renderView('IbwJobeetBundle:Affiliate:email.txt.twig', array('affiliate' => $selectedModel->getToken()))) ; $this->get('mailer')->send($message); } } catch(Exception $e) { $this->get('session')->setFlash('sonata_flash_error', $e->getMessage()); return new RedirectResponse($this->admin->generateUrl('list',$this->admin->getFilterParameters())); } // ... } // ...
The Tests
Now that we have seen how to send an email with the symfony mailer, let’s write some functional tests to ensure we did the right thing.
To test this new functionality, we need to be logged in. To log in, we will need an username and a password. That’s why we will start by creating a new fixture
file, where we add the user admin
:
namespace IbwJobeetBundleDataFixturesORM; use DoctrineCommonPersistenceObjectManager; use DoctrineCommonDataFixturesAbstractFixture; use DoctrineCommonDataFixturesFixtureInterface; use DoctrineCommonDataFixturesOrderedFixtureInterface; use SymfonyComponentDependencyInjectionContainerAwareInterface; use SymfonyComponentDependencyInjectionContainerInterface; use IbwJobeetBundleEntityUser; class LoadUserData implements FixtureInterface, OrderedFixtureInterface, ContainerAwareInterface { /** * @var ContainerInterface */ private $container; /** * {@inheritDoc} */ public function setContainer(ContainerInterface $container = null) { $this->container = $container; } /** * @param DoctrineCommonPersistenceObjectManager $em */ public function load(ObjectManager $em) { $user = new User(); $user->setUsername('admin'); $encoder = $this->container ->get('security.encoder_factory') ->getEncoder($user) ; $encodedPassword = $encoder->encodePassword('admin', $user->getSalt()); $user->setPassword($encodedPassword); $em->persist($user); $em->flush(); } public function getOrder() { return 4; // the order in which fixtures will be loaded } }
In the tests, we will use the swiftmailer
collector on the profiler to get information about the messages send on the previous requests. Now, let’s add some tests to check if the email is sent properly:
namespace IbwJobeetBundleTestsController; use SymfonyBundleFrameworkBundleTestWebTestCase; use SymfonyBundleFrameworkBundleConsoleApplication; use SymfonyComponentConsoleOutputNullOutput; use SymfonyComponentConsoleInputArrayInput; use DoctrineBundleDoctrineBundleCommandDropDatabaseDoctrineCommand; use DoctrineBundleDoctrineBundleCommandCreateDatabaseDoctrineCommand; use DoctrineBundleDoctrineBundleCommandProxyCreateSchemaDoctrineCommand; class AffiliateAdminControllerTest extends WebTestCase { private $em; private $application; public function setUp() { static::$kernel = static::createKernel(); static::$kernel->boot(); $this->application = new Application(static::$kernel); // drop the database $command = new DropDatabaseDoctrineCommand(); $this->application->add($command); $input = new ArrayInput(array( 'command' => 'doctrine:database:drop', '--force' => true )); $command->run($input, new NullOutput()); // we have to close the connection after dropping the database so we don't get "No database selected" error $connection = $this->application->getKernel()->getContainer()->get('doctrine')->getConnection(); if ($connection->isConnected()) { $connection->close(); } // create the database $command = new CreateDatabaseDoctrineCommand(); $this->application->add($command); $input = new ArrayInput(array( 'command' => 'doctrine:database:create', )); $command->run($input, new NullOutput()); // create schema $command = new CreateSchemaDoctrineCommand(); $this->application->add($command); $input = new ArrayInput(array( 'command' => 'doctrine:schema:create', )); $command->run($input, new NullOutput()); // get the Entity Manager $this->em = static::$kernel->getContainer() ->get('doctrine') ->getManager(); // load fixtures $client = static::createClient(); $loader = new SymfonyBridgeDoctrineDataFixturesContainerAwareLoader($client->getContainer()); $loader->loadFromDirectory(static::$kernel->locateResource('@IbwJobeetBundle/DataFixtures/ORM')); $purger = new DoctrineCommonDataFixturesPurgerORMPurger($this->em); $executor = new DoctrineCommonDataFixturesExecutorORMExecutor($this->em, $purger); $executor->execute($loader->getFixtures()); } public function testActivate() { $client = static::createClient(); // Enable the profiler for the next request (it does nothing if the profiler is not available) $client->enableProfiler(); $crawler = $client->request('GET', '/login'); $form = $crawler->selectButton('login')->form(array( '_username' => 'admin', '_password' => 'admin' )); $crawler = $client->submit($form); $crawler = $client->followRedirect(); $this->assertTrue(200 === $client->getResponse()->getStatusCode()); $crawler = $client->request('GET', '/admin/ibw/jobeet/affiliate/list'); $link = $crawler->filter('.btn.edit_link')->link(); $client->click($link); $mailCollector = $client->getProfile()->getCollector('swiftmailer'); // Check that an e-mail was sent $this->assertEquals(1, $mailCollector->getMessageCount()); $collectedMessages = $mailCollector->getMessages(); $message = $collectedMessages[0]; // Asserting e-mail data $this->assertInstanceOf('Swift_Message', $message); $this->assertEquals('Jobeet affiliate token', $message->getSubject()); $this->assertRegExp( '/Your secret token is symfony/', $message->getBody() ); } }
If you run the test now, you’ll get and error. To prevent this for happening, go to your config_test.yml
file and make sure that the profiler is enabled in the test environment. If it’s set to false
, change it to true
:
# ... framework: test: ~ session: storage_id: session.storage.mock_file profiler: enabled: true # ...
Now, clear the cache, run the test command in your console and enjoy the green bar :
phpunit -c app src/Ibw/JobeetBundle/Tests/Controller/AffiliateAdminControllerTest
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
Symfony2 Jobeet Day 15: Web Services
* This article is part of the original Jobeet Tutorial, created by Fabien Potencier, for Symfony 1.4.
Web services in jobeet
With the addition of feeds on Jobeet, job seekers can now be informed of new jobs in real-time.
On the other side of the fence, when you post a job, you will want to have the greatest exposure possible. If your job is syndicated on a lot of small websites, you will have a better chance to find the right person. That’s the power of the long tail. Affiliates will be able to publish the latest posted jobs on their websites thanks to the web services we will develop today.
Affiliates
As we already said in day 2 of this tutorial, an affiliate retrieves the current active job list.
The fixtures
Let’s create a new fixture
file for the affiliates:
namespace IbwJobeetBundleDataFixturesORM; use DoctrineCommonPersistenceObjectManager; use DoctrineCommonDataFixturesAbstractFixture; use DoctrineCommonDataFixturesOrderedFixtureInterface; use IbwJobeetBundleEntityAffiliate; class LoadAffiliateData extends AbstractFixture implements OrderedFixtureInterface { public function load(ObjectManager $em) { $affiliate = new Affiliate(); $affiliate->setUrl('http://sensio-labs.com/'); $affiliate->setEmail('address1@example.com'); $affiliate->setToken('sensio-labs'); $affiliate->setIsActive(true); $affiliate->addCategorie($em->merge($this->getReference('category-programming'))); $em->persist($affiliate); $affiliate = new Affiliate(); $affiliate->setUrl('/'); $affiliate->setEmail('address2@example.org'); $affiliate->setToken('symfony'); $affiliate->setIsActive(false); $affiliate->addCategorie($em->merge($this->getReference('category-programming')), $em->merge($this->getReference('category-design'))); $em->persist($affiliate); $em->flush(); $this->addReference('affiliate', $affiliate); } public function getOrder() { return 3; // This represents the order in which fixtures will be loaded } }
Now, to persist the data defined in your fixture file, just run the following command:
php app/console doctrine:fixtures:load
In the fixture file, the tokens are hardcoded to simplify the testing, but when an actual user applies for an account, the token will need to be generated Let’s create a function to do that in our Affiliate
class. Start by adding the setTokenValue
method to lifecycleCallbacks
section, inside your ORM
file:
# ... lifecycleCallbacks: prePersist: [ setCreatedAtValue, setTokenValue ]
Now, the setTokenValue
method will be generated inside the entity file when you will run the following command:
php app/console doctrine:generate:entities IbwJobeetBundle
Let’s modify the method now:
public function setTokenValue() { if(!$this->getToken()) { $token = sha1($this->getEmail().rand(11111, 99999)); $this->token = $token; } return $this; }
Reload the data:
php app/console doctrine:fixtures:load
The Job Web Service
As always, when you create a new resource, it’s a good habbit to define the route first:
IbwJobeetBundle_api: pattern: /api/{token}/jobs.{_format} defaults: {_controller: "IbwJobeetBundle:Api:list"} requirements: _format: xml|json|yaml
As usually, after you modify a routing
file, you need to clear the cache:
php app/console cache:clear --env=dev php app/console cache:clear --env=prod
The next step is to create the api
action and the templates, that will share the same action. Let us now create a new controller file, called ApiController
:
namespace IbwJobeetBundleController; use SymfonyBundleFrameworkBundleControllerController; use SymfonyComponentHttpFoundationRequest; use SymfonyComponentHttpFoundationResponse; use IbwJobeetBundleEntityAffiliate; use IbwJobeetBundleEntityJob; use IbwJobeetBundleRepositoryAffiliateRepository; class ApiController extends Controller { public function listAction(Request $request, $token) { $em = $this->getDoctrine()->getManager(); $jobs = array(); $rep = $em->getRepository('IbwJobeetBundle:Affiliate'); $affiliate = $rep->getForToken($token); if(!$affiliate) { throw $this->createNotFoundException('This affiliate account does not exist!'); } $rep = $em->getRepository('IbwJobeetBundle:Job'); $active_jobs = $rep->getActiveJobs(null, null, null, $affiliate->getId()); foreach ($active_jobs as $job) { $jobs[$this->get('router')->generate('ibw_job_show', array('company' => $job->getCompanySlug(), 'location' => $job->getLocationSlug(), 'id' => $job->getId(), 'position' => $job->getPositionSlug()), true)] = $job->asArray($request->getHost()); } $format = $request->getRequestFormat(); $jsonData = json_encode($jobs); if ($format == "json") { $headers = array('Content-Type' => 'application/json'); $response = new Response($jsonData, 200, $headers); return $response; } return $this->render('IbwJobeetBundle:Api:jobs.' . $format . '.twig', array('jobs' => $jobs)); } }
To retrieve the affiliate using his token, we will create the getForToken()
method. This method also verifies if the affiliate account is activated, so there is no need for us to check this one more time. Until now, we haven’t used the AffiliateRepository yet
, so it doesn’t exist. To create it, modify the ORM file as following, then run the command you used before to generate the entities.
IbwJobeetBundleEntityAffiliate: type: entity repositoryClass: IbwJobeetBundleRepositoryAffiliateRepository # ...
Once created, it is ready to be used:
namespace IbwJobeetBundleRepository; use DoctrineORMEntityRepository; /** * AffiliateRepository * * This class was generated by the Doctrine ORM. Add your own custom * repository methods below. */ class AffiliateRepository extends EntityRepository { public function getForToken($token) { $qb = $this->createQueryBuilder('a') ->where('a.is_active = :active') ->setParameter('active', 1) ->andWhere('a.token = :token') ->setParameter('token', $token) ->setMaxResults(1) ; try{ $affiliate = $qb->getQuery()->getSingleResult(); } catch(DoctrineOrmNoResultException $e){ $affiliate = null; } return $affiliate; } }
After identifying the affiliate by his token, we will use the getActiveJobs()
method to give the affiliate the jobs he required, belonging to the selected categories. If you open your JobRepository
file now, you will see that the getActiveJobs()
method doesn’t share any connection with the affiliates. Because we want to reuse that method, we need to make some modifications inside of it:
// ... public function getActiveJobs($category_id = null, $max = null, $offset = null, $affiliate_id = null) { $qb = $this->createQueryBuilder('j') ->where('j.expires_at > :date') ->setParameter('date', date('Y-m-d H:i:s', time())) ->andWhere('j.is_activated = :activated') ->setParameter('activated', 1) ->orderBy('j.expires_at', 'DESC'); if($max) { $qb->setMaxResults($max); } if($offset) { $qb->setFirstResult($offset); } if($category_id) { $qb->andWhere('j.category = :category_id') ->setParameter('category_id', $category_id); } // j.category c, c.affiliate a if($affiliate_id) { $qb->leftJoin('j.category', 'c') ->leftJoin('c.affiliates', 'a') ->andWhere('a.id = :affiliate_id') ->setParameter('affiliate_id', $affiliate_id) ; } $query = $qb->getQuery(); return $query->getResult(); } // ...
As you can see, we populate the jobs array using a function called asArray()
. Let’s define it:
public function asArray($host) { return array( 'category' => $this->getCategory()->getName(), 'type' => $this->getType(), 'company' => $this->getCompany(), 'logo' => $this->getLogo() ? 'http://' . $host . '/uploads/jobs/' . $this->getLogo() : null, 'url' => $this->getUrl(), 'position' => $this->getPosition(), 'location' => $this->getLocation(), 'description' => $this->getDescription(), 'how_to_apply' => $this->getHowToApply(), 'expires_at' => $this->getCreatedAt()->format('Y-m-d H:i:s'), ); }
The xml Format
Supporting the xml
format is as simple as creating a template:
<?xml version="1.0" encoding="utf-8"?> <jobs> {% for url, job in jobs %} <job url="{{ url }}"> {% for key,value in job %} <{{ key }}>{{ value }}</{{ key }}> {% endfor %} </job> {% endfor %} </jobs>
The json Format
Support the JSON
format is similar:
{% for url, job in jobs %} {% i = 0, count(jobs), ++i %} [ "url":"{{ url }}", {% for key, value in job %} {% j = 0, count(key), ++j %} "{{ key }}":"{% if j == count(key)%} {{ json_encode(value) }}, {% else %} {{ json_encode(value) }} {% endif %}" {% endfor %}] {% endfor %}
The yaml Format
{% for url,job in jobs %} Url: {{ url }} {% for key, value in job %} {{ key }}: {{ value }} {% endfor %} {% endfor %}
If you try to call the web service with a non-valid token, you will receive a 404 page
as a response, for all the formats. To see what you accomplished until now, access the following links: http://jobeet.local/app_dev.php/api/sensio-labs/jobs.xml or http://jobeet.local/app_dev.php/api/symfony/jobs.xml. Change the extension in the URL, depending on which format you prefer.
Web Service Tests
namespace IbwJobeetBundleTestsController; use SymfonyBundleFrameworkBundleTestWebTestCase; use SymfonyBundleFrameworkBundleConsoleApplication; use SymfonyComponentConsoleOutputNullOutput; use SymfonyComponentConsoleInputArrayInput; use DoctrineBundleDoctrineBundleCommandDropDatabaseDoctrineCommand; use DoctrineBundleDoctrineBundleCommandCreateDatabaseDoctrineCommand; use DoctrineBundleDoctrineBundleCommandProxyCreateSchemaDoctrineCommand; use SymfonyComponentDomCrawlerCrawler; use SymfonyComponentHttpFoundationHttpExceptionInterface; class ApiControllerTest extends WebTestCase { private $em; private $application; public function setUp() { static::$kernel = static::createKernel(); static::$kernel->boot(); $this->application = new Application(static::$kernel); // drop the database $command = new DropDatabaseDoctrineCommand(); $this->application->add($command); $input = new ArrayInput(array( 'command' => 'doctrine:database:drop', '--force' => true )); $command->run($input, new NullOutput()); // we have to close the connection after dropping the database so we don't get "No database selected" error $connection = $this->application->getKernel()->getContainer()->get('doctrine')->getConnection(); if ($connection->isConnected()) { $connection->close(); } // create the database $command = new CreateDatabaseDoctrineCommand(); $this->application->add($command); $input = new ArrayInput(array( 'command' => 'doctrine:database:create', )); $command->run($input, new NullOutput()); // create schema $command = new CreateSchemaDoctrineCommand(); $this->application->add($command); $input = new ArrayInput(array( 'command' => 'doctrine:schema:create', )); $command->run($input, new NullOutput()); // get the Entity Manager $this->em = static::$kernel->getContainer() ->get('doctrine') ->getManager(); // load fixtures $client = static::createClient(); $loader = new SymfonyBridgeDoctrineDataFixturesContainerAwareLoader($client->getContainer()); $loader->loadFromDirectory(static::$kernel->locateResource('@IbwJobeetBundle/DataFixtures/ORM')); $purger = new DoctrineCommonDataFixturesPurgerORMPurger($this->em); $executor = new DoctrineCommonDataFixturesExecutorORMExecutor($this->em, $purger); $executor->execute($loader->getFixtures()); } public function testList() { $client = static::createClient(); $crawler = $client->request('GET', '/api/sensio-labs/jobs.xml'); $this->assertEquals('IbwJobeetBundleControllerApiController::listAction', $client->getRequest()->attributes->get('_controller')); $this->assertTrue($crawler->filter('description')->count() == 32); $crawler = $client->request('GET', '/api/sensio-labs87/jobs.xml'); $this->assertTrue(404 === $client->getResponse()->getStatusCode()); $crawler = $client->request('GET', '/api/symfony/jobs.xml'); $this->assertTrue(404 === $client->getResponse()->getStatusCode()); $crawler = $client->request('GET', '/api/sensio-labs/jobs.json'); $this->assertEquals('IbwJobeetBundleControllerApiController::listAction', $client->getRequest()->attributes->get('_controller')); $this->assertRegExp('/"category":"Programming"/', $client->getResponse()->getContent()); $crawler = $client->request('GET', '/api/sensio-labs87/jobs.json'); $this->assertTrue(404 === $client->getResponse()->getStatusCode()); $crawler = $client->request('GET', '/api/sensio-labs/jobs.yaml'); $this->assertRegExp('/category: Programming/', $client->getResponse()->getContent()); $this->assertEquals('IbwJobeetBundleControllerApiController::listAction', $client->getRequest()->attributes->get('_controller')); $crawler = $client->request('GET', '/api/sensio-labs87/jobs.yaml'); $this->assertTrue(404 === $client->getResponse()->getStatusCode()); } }
Inside the ApiControllerTest
file, we test that the request formats are correctly received and the pages requested are correctly returned.
The Affiliate Application Form
Now that the web service is ready to be used, let’s create the account creation form
for affiliates. For that, you need to write the HTML form, implement validation rules for each field, process the values to store them in a database, display error messages and repopulate fields in case of errors.
First, create a new controller file, named AffiliateController
:
namespace IbwJobeetBundleController; use SymfonyBundleFrameworkBundleControllerController; use IbwJobeetBundleEntityAffiliate; use IbwJobeetBundleFormAffiliateType; use SymfonyComponentHttpFoundationRequest; use IbwJobeetBundleEntityCategory; class AffiliateController extends Controller { // Your code goes here }
Then, change the Affiliates
link in the layout:
<!-- ... --> <li class="last"><a href="{{ path('ibw_affiliate_new') }}">Become an affiliate</a></li> <!-- ... -->
Now, we need to create an action to match the route from the link you just modified it earlier:
namespace IbwJobeetBundleController; use SymfonyBundleFrameworkBundleControllerController; use IbwJobeetBundleEntityAffiliate; use IbwJobeetBundleFormAffiliateType; use SymfonyComponentHttpFoundationRequest; use IbwJobeetBundleEntityCategory; class AffiliateController extends Controller { public function newAction() { $entity = new Affiliate(); $form = $this->createForm(new AffiliateType(), $entity); return $this->render('IbwJobeetBundle:Affiliate:affiliate_new.html.twig', array( 'entity' => $entity, 'form' => $form->createView(), )); } }
We have the name of the route, we have the action, but we do not have the route. so let’s create it:
ibw_affiliate_new: pattern: /new defaults: { _controller: "IbwJobeetBundle:Affiliate:new" }
Also, add this to your routing
file:
# ... IbwJobeetBundle_ibw_affiliate: resource: "@IbwJobeetBundle/Resources/config/routing/affiliate.yml" prefix: /affiliate
The form file also needs to be created. But, even if the Affiliate
has more fields, we won’t display them all, because some of them must not be editable by the end user. Create your Affiliate
form:
namespace IbwJobeetBundleForm; use SymfonyComponentFormAbstractType; use SymfonyComponentFormFormBuilderInterface; use SymfonyComponentOptionsResolverOptionsResolverInterface; use IbwJobeetBundleEntityAffiliate; use IbwJobeetBundleEntityCategory; class AffiliateType extends AbstractType { public function buildForm(FormBuilderInterface $builder, array $options) { $builder ->add('url') ->add('email') ->add('categories', null, array('expanded'=>true)) ; } public function setDefaultOptions(OptionsResolverInterface $resolver) { $resolver->setDefaults(array( 'data_class' => 'IbwJobeetBundleEntityAffiliate', )); } public function getName() { return 'affiliate'; } }
Now, we need to decide whether or not the Affiliate
object is valid after the form has applied the submitted data to it. To do this, add the following code to your validation
file:
# ... IbwJobeetBundleEntityAffiliate: constraints: - SymfonyBridgeDoctrineValidatorConstraintsUniqueEntity: email properties: url: - Url: ~ email: - NotBlank: ~ - Email: ~
In the validation schema, we used a new validator, called UniqueEntity
. It validates that a particular field (or fields) in a Doctrine entity is (are) unique. This is commonly used, for example, to prevent a new user to register using an email address that already exists in the system.
Don’t forget to clear your cache after applying the validation constraints!
Finally, let’s create the view for the form too:
{% extends 'IbwJobeetBundle::layout.html.twig' %} {% set form_themes = _self %} {% block form_errors %} {% spaceless %} {% if errors|length > 0 %} <ul class="error_list"> {% for error in errors %} <li>{{ error.messageTemplate|trans(error.messageParameters, 'validators') }}</li> {% endfor %} </ul> {% endif %} {% endspaceless %} {% endblock form_errors %} {% block stylesheets %} {{ parent() }} <link rel="stylesheet" href="{{ asset('bundles/ibwjobeet/css/job.css') }}" type="text/css" media="all" /> {% endblock %} {% block content %} <h1>Become an affiliate</h1> <form action="{{ path('ibw_affiliate_create') }}" method="post" {{ form_enctype(form) }}> <table id="job_form"> <tfoot> <tr> <td colspan="2"> <input type="submit" value="Submit" /> </td> </tr> </tfoot> <tbody> <tr> <th>{{ form_label(form.url) }}</th> <td> {{ form_errors(form.url) }} {{ form_widget(form.url) }} </td> </tr> <tr> <th>{{ form_label(form.email) }}</th> <td> {{ form_errors(form.email) }} {{ form_widget(form.email) }} </td> </tr> <tr> <th>{{ form_label(form.categories) }}</th> <td> {{ form_errors(form.categories) }} {{ form_widget(form.categories) }} </td> </tr> </tbody> </table> {{ form_end(form) }} {% endblock %}
When the user submits a form, the form data must be persisted into database, if valid. Add the new create
action to your Affiliate
controller:
class AffiliateController extends Controller { // ... public function createAction(Request $request) { $affiliate = new Affiliate(); $form = $this->createForm(new AffiliateType(), $affiliate); $form->bind($request); $em = $this->getDoctrine()->getManager(); if ($form->isValid()) { $formData = $request->get('affiliate'); $affiliate->setUrl($formData['url']); $affiliate->setEmail($formData['email']); $affiliate->setIsActive(false); $em->persist($affiliate); $em->flush(); return $this->redirect($this->generateUrl('ibw_affiliate_wait')); } return $this->render('IbwJobeetBundle:Affiliate:affiliate_new.html.twig', array( 'entity' => $affiliate, 'form' => $form->createView(), )); } }
When submitting, the create action is performed, so we need to define the route:
# ... ibw_affiliate_create: pattern: /create defaults: { _controller: "IbwJobeetBundle:Affiliate:create" } requirements: { _method: post }
After the affiliate registers, he is redirected to a waiting page. Let’s define that action and create the view too:
class AffiliateController extends Controller { // ... public function waitAction() { return $this->render('IbwJobeetBundle:Affiliate:wait.html.twig'); } }
{% extends "IbwJobeetBundle::layout.html.twig" %} {% block content %} <div class="content"> <h1>Your affiliate account has been created</h1> <div style="padding: 20px"> Thank you! You will receive an email with your affiliate token as soon as your account will be activated. </div> </div> {% endblock %}
Now, the route:
# ... ibw_affiliate_wait: pattern: /wait defaults: { _controller: "IbwJobeetBundle:Affiliate:wait" }
After defining to routes, in order to work, you need to clear the cache.
Now, if you click on the Affiliates
link on the homepage, you will be directed to the affiliate form page.
Tests
The last step is to write some functional tests for the new feature.
namespace IbwJobeetBundleTestsController; use SymfonyBundleFrameworkBundleTestWebTestCase; use SymfonyBundleFrameworkBundleConsoleApplication; use SymfonyComponentConsoleOutputNullOutput; use SymfonyComponentConsoleInputArrayInput; use DoctrineBundleDoctrineBundleCommandDropDatabaseDoctrineCommand; use DoctrineBundleDoctrineBundleCommandCreateDatabaseDoctrineCommand; use DoctrineBundleDoctrineBundleCommandProxyCreateSchemaDoctrineCommand; use SymfonyComponentDomCrawlerCrawler; class AffiliateControllerTest extends WebTestCase { private $em; private $application; public function setUp() { static::$kernel = static::createKernel(); static::$kernel->boot(); $this->application = new Application(static::$kernel); // drop the database $command = new DropDatabaseDoctrineCommand(); $this->application->add($command); $input = new ArrayInput(array( 'command' => 'doctrine:database:drop', '--force' => true )); $command->run($input, new NullOutput()); // we have to close the connection after dropping the database so we don't get "No database selected" error $connection = $this->application->getKernel()->getContainer()->get('doctrine')->getConnection(); if ($connection->isConnected()) { $connection->close(); } // create the database $command = new CreateDatabaseDoctrineCommand(); $this->application->add($command); $input = new ArrayInput(array( 'command' => 'doctrine:database:create', )); $command->run($input, new NullOutput()); // create schema $command = new CreateSchemaDoctrineCommand(); $this->application->add($command); $input = new ArrayInput(array( 'command' => 'doctrine:schema:create', )); $command->run($input, new NullOutput()); // get the Entity Manager $this->em = static::$kernel->getContainer() ->get('doctrine') ->getManager(); // load fixtures $client = static::createClient(); $loader = new SymfonyBridgeDoctrineDataFixturesContainerAwareLoader($client->getContainer()); $loader->loadFromDirectory(static::$kernel->locateResource('@IbwJobeetBundle/DataFixtures/ORM')); $purger = new DoctrineCommonDataFixturesPurgerORMPurger($this->em); $executor = new DoctrineCommonDataFixturesExecutorORMExecutor($this->em, $purger); $executor->execute($loader->getFixtures()); } public function testAffiliateForm() { $client = static::createClient(); $crawler = $client->request('GET', '/affiliate/new'); $this->assertEquals('IbwJobeetBundleControllerAffiliateController::newAction', $client->getRequest()->attributes->get('_controller')); $form = $crawler->selectButton('Submit')->form(array( 'affiliate[url]' => 'http://sensio-labs.com/', 'affiliate[email]' => 'jobeet@example.com' )); $client->submit($form); $this->assertEquals('IbwJobeetBundleControllerAffiliateController::createAction', $client->getRequest()->attributes->get('_controller')); $kernel = static::createKernel(); $kernel->boot(); $em = $kernel->getContainer()->get('doctrine.orm.entity_manager'); $query = $em->createQuery('SELECT count(a.email) FROM IbwJobeetBundle:Affiliate a WHERE a.email = :email'); $query->setParameter('email', 'jobeet@example.com'); $this->assertEquals(1, $query->getSingleScalarResult()); $crawler = $client->request('GET', '/affiliate/new'); $form = $crawler->selectButton('Submit')->form(array( 'affiliate[email]' => 'not.an.email', )); $crawler = $client->submit($form); // check if we have 1 errors $this->assertTrue($crawler->filter('.error_list')->count() == 1); // check if we have error on affiliate_email field $this->assertTrue($crawler->filter('#affiliate_email')->siblings()->first()->filter('.error_list')->count() == 1); } public function testCreate() { $client = static::createClient(); $crawler = $client->request('GET', '/affiliate/new'); $form = $crawler->selectButton('Submit')->form(array( 'affiliate[url]' => 'http://sensio-labs.com/', 'affiliate[email]' => 'address@example.com' )); $client->submit($form); $client->followRedirect(); $this->assertEquals('IbwJobeetBundleControllerAffiliateController::waitAction', $client->getRequest()->attributes->get('_controller')); return $client; } public function testWait() { $client = static::createClient(); $crawler = $client->request('GET', '/affiliate/wait'); $this->assertEquals('IbwJobeetBundleControllerAffiliateController::waitAction', $client->getRequest()->attributes->get('_controller')); } }
The Affiliate Backend
For the backend, we will work with SonataAdminBundle
. As we said before, after an affiliate registers, he needs to wait for the admin to activate his account. So, when the admin will access the affiliates page, he will see only the inactivated accounts, to help him be more productive.
First of all, you need to declare the new affiliate service inside your services.yml file:
# ... ibw.jobeet.admin.affiliate: class: IbwJobeetBundleAdminAffiliateAdmin tags: - { name: sonata.admin, manager_type: orm, group: jobeet, label: Affiliates } arguments: - ~ - IbwJobeetBundleEntityAffiliate - 'IbwJobeetBundle:AffiliateAdmin'
After that, create the Admin file:
namespace IbwJobeetBundleAdmin; use SonataAdminBundleAdminAdmin; use SonataAdminBundleDatagridListMapper; use SonataAdminBundleDatagridDatagridMapper; use SonataAdminBundleValidatorErrorElement; use SonataAdminBundleFormFormMapper; use SonataAdminBundleShowShowMapper; use IbwJobeetBundleEntityAffiliate; class AffiliateAdmin extends Admin { protected $datagridValues = array( '_sort_order' => 'ASC', '_sort_by' => 'is_active' ); protected function configureFormFields(FormMapper $formMapper) { $formMapper ->add('email') ->add('url') ; } protected function configureDatagridFilters(DatagridMapper $datagridMapper) { $datagridMapper ->add('email') ->add('is_active'); } protected function configureListFields(ListMapper $listMapper) { $listMapper ->add('is_active') ->addIdentifier('email') ->add('url') ->add('created_at') ->add('token') ; } }
To help the administrator, we want to display only the inactivated accounts. This can be made by setting the ‘is_active’ filter to false
:
// ... protected $datagridValues = array( '_sort_order' => 'ASC', '_sort_by' => 'is_active', 'is_active' => array('value' => 2) // The value 2 represents that the displayed affiliate accounts are not activated yet ); // ...
Now, create the AffiliateAdmin controller file:
namespace IbwJobeetBundleController; use SonataAdminBundleControllerCRUDController as Controller; use SonataDoctrineORMAdminBundleDatagridProxyQuery as ProxyQueryInterface; use SymfonyComponentHttpFoundationRedirectResponse; class AffiliateAdminController extends Controller { // Your code goes here }
Let’s create the activate
and deactivate
batch actions:
namespace IbwJobeetBundleController; use SonataAdminBundleControllerCRUDController as Controller; use SonataDoctrineORMAdminBundleDatagridProxyQuery as ProxyQueryInterface; use SymfonyComponentHttpFoundationRedirectResponse; class AffiliateAdminController extends Controller { public function batchActionActivate(ProxyQueryInterface $selectedModelQuery) { if($this->admin->isGranted('EDIT') === false || $this->admin->isGranted('DELETE') === false) { throw new AccessDeniedException(); } $request = $this->get('request'); $modelManager = $this->admin->getModelManager(); $selectedModels = $selectedModelQuery->execute(); try { foreach($selectedModels as $selectedModel) { $selectedModel->activate(); $modelManager->update($selectedModel); } } catch(Exception $e) { $this->get('session')->getFlashBag()->add('sonata_flash_error', $e->getMessage()); return new RedirectResponse($this->admin->generateUrl('list',$this->admin->getFilterParameters())); } $this->get('session')->getFlashBag()->add('sonata_flash_success', sprintf('The selected accounts have been activated')); return new RedirectResponse($this->admin->generateUrl('list',$this->admin->getFilterParameters())); } public function batchActionDeactivate(ProxyQueryInterface $selectedModelQuery) { if($this->admin->isGranted('EDIT') === false || $this->admin->isGranted('DELETE') === false) { throw new AccessDeniedException(); } $request = $this->get('request'); $modelManager = $this->admin->getModelManager(); $selectedModels = $selectedModelQuery->execute(); try { foreach($selectedModels as $selectedModel) { $selectedModel->deactivate(); $modelManager->update($selectedModel); } } catch(Exception $e) { $this->get('session')->getFlashBag()->add('sonata_flash_error', $e->getMessage()); return new RedirectResponse($this->admin->generateUrl('list',$this->admin->getFilterParameters())); } $this->get('session')->getFlashBag()->add('sonata_flash_success', sprintf('The selected accounts have been deactivated')); return new RedirectResponse($this->admin->generateUrl('list',$this->admin->getFilterParameters())); } }
For the new batch actions to be functional, we have to add them in the getBatchActions
from the Admin
class:
class AffiliateAdmin extends Admin { // ... public function getBatchActions() { $actions = parent::getBatchActions(); if($this->hasRoute('edit') && $this->isGranted('EDIT') && $this->hasRoute('delete') && $this->isGranted('DELETE')) { $actions['activate'] = array( 'label' => 'Activate', 'ask_confirmation' => true ); $actions['deactivate'] = array( 'label' => 'Deactivate', 'ask_confirmation' => true ); } return $actions; } }
For this to work, you need to add the two methods, activate and deactivate, in the entity file:
// ... public function activate() { if(!$this->getIsActive()) { $this->setIsActive(true); } return $this->is_active; } public function deactivate() { if($this->getIsActive()) { $this->setIsActive(false); } return $this->is_active; }
Let’s now create two individual actions, activate and deactivate, for each item. Firstly, we will create routes for them. That’s why, in your Admin class, you will extend the configureRoutes function:
use SonataAdminBundleRouteRouteCollection; class AffiliateAdmin extends Admin { // ... protected function configureRoutes(RouteCollection $collection) { parent::configureRoutes($collection); $collection->add('activate', $this->getRouterIdParameter().'/activate') ; $collection->add('deactivate', $this->getRouterIdParameter().'/deactivate') ; } }
It’s time to implement the actions in the AdminController:
class AffiliateAdminController extends Controller { // ... public function activateAction($id) { if($this->admin->isGranted('EDIT') === false) { throw new AccessDeniedException(); } $em = $this->getDoctrine()->getManager(); $affiliate = $em->getRepository('IbwJobeetBundle:Affiliate')->findOneById($id); try { $affiliate->setIsActive(true); $em->flush(); } catch(Exception $e) { $this->get('session')->getFlashBag()->add('sonata_flash_error', $e->getMessage()); return new RedirectResponse($this->admin->generateUrl('list', $this->admin->getFilterParameters())); } return new RedirectResponse($this->admin->generateUrl('list',$this->admin->getFilterParameters())); } public function deactivateAction($id) { if($this->admin->isGranted('EDIT') === false) { throw new AccessDeniedException(); } $em = $this->getDoctrine()->getManager(); $affiliate = $em->getRepository('IbwJobeetBundle:Affiliate')->findOneById($id); try { $affiliate->setIsActive(false); $em->flush(); } catch(Exception $e) { $this->get('session')->getFlashBag()->add('sonata_flash_error', $e->getMessage()); return new RedirectResponse($this->admin->generateUrl('list', $this->admin->getFilterParameters())); } return new RedirectResponse($this->admin->generateUrl('list',$this->admin->getFilterParameters())); } }
Now, create the templates for the new added action buttons:
{% if admin.isGranted('EDIT', object) and admin.hasRoute('activate') %} <a href="{{ admin.generateObjectUrl('activate', object) }}" class="btn edit_link" title="{{ 'action_activate'|trans({}, 'SonataAdminBundle') }}"> <i class="icon-edit"></i> {{ 'activate'|trans({}, 'SonataAdminBundle') }} </a> {% endif %}
{% if admin.isGranted('EDIT', object) and admin.hasRoute('deactivate') %} <a href="{{ admin.generateObjectUrl('deactivate', object) }}" class="btn edit_link" title="{{ 'action_deactivate'|trans({}, 'SonataAdminBundle') }}"> <i class="icon-edit"></i> {{ 'deactivate'|trans({}, 'SonataAdminBundle') }} </a> {% endif %}
Inside your Admin file, add the new actions and buttons to the configureListFields function, so that they would appear on the page, to each account individually:
class AffiliateAdmin extends Admin { // ... protected function configureListFields(ListMapper $listMapper) { $listMapper ->add('is_active') ->addIdentifier('email') ->add('url') ->add('created_at') ->add('token') ->add('_action', 'actions', array( 'actions' => array('activate' => array('template' => 'IbwJobeetBundle:AffiliateAdmin:list__action_activate.html.twig'), 'deactivate' => array('template' => 'IbwJobeetBundle:AffiliateAdmin:list__action_deactivate.html.twig')))) ; } /// ... }
Now, clear your cache and try it on!
That’s all for today! Tomorrow, we will take care of the emails the affiliates will receive when their accounts have been activated.
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
Symfony2 Jobeet Day 14: Feeds
* This article is part of the original Jobeet Tutorial, created by Fabien Potencier, for Symfony 1.4.
Feeds in jobeet
If you are looking for a job, you will probably want to be informed as soon as a new job is posted. Because it is not very convenient to check the website every other hour, we will add several job feeds here to keep our Jobeet users up-to-date.
Template Formats
Templates are a generic way to render content in any format. And while in most cases you’ll use templates to render HTML content, a template can just as easily generate JavaScript, CSS, XML or any other format.
For example, the same “resource” is often rendered in several different formats. To render an article index page in XML, simply include the format in the template name:
- XML template name:
AcmeArticleBundle:Article:index.xml.twig
- XML template filename:
index.xml.twig
In reality, this is nothing more than a naming convention and the template isn’t actually rendered differently based on its format.
In many cases, you may want to allow a single controller to render multiple different formats based on the “request format”. For that reason, a common pattern is to do the following:
public function indexAction() { $format = $this->getRequest()->getRequestFormat(); return $this->render('AcmeBlogBundle:Blog:index.'.$format.'.twig'); }
The getRequestFormat
on the Request
object defaults to html
, but can return any other format based on the format requested by the user. The request format is most often managed by the routing, where a route can be configured so that /contact
sets the request format to html
while /contact.xml
sets the format to xml
.
To create links that include the format parameter, include a _format
key in the parameter hash:
<a href="{{ path('article_show', {'id': 123, '_format': 'pdf'}) }}"> PDF Version </a>
Feeds
LATEST JOBS FEED
Supporting different formats is as easy as creating different templates. To create an Atom feed for the latest jobs, create an index.atom.twig
template:
<?xml version="1.0" encoding="utf-8"?> <feed xmlns="http://www.w3.org/2005/Atom"> <title>Jobeet</title> <subtitle>Latest Jobs</subtitle> <link href="" rel="self"/> <link href=""/> <updated></updated> <author><name>Jobeet</name></author> <id>Unique Id</id> <entry> <title>Job title</title> <link href="" /> <id>Unique id</id> <updated></updated> <summary>Job description</summary> <author><name>Company</name></author> </entry> </feed>
In the Jobeet footer, update the link to the feed:
<!-- ... --> <li class="feed"><a href="{{ path('ibw_job', {'_format': 'atom'}) }}">Full feed</a></li> <!-- ... -->
Add a <link>
tag in the head section of the layout to allow automatic discover by the browser of our feed:
<!-- ... --> <link rel="alternate" type="application/atom+xml" title="Latest Jobs" href="{{ url('ibw_job', {'_format': 'atom'}) }}" /> <!-- ... -->
In the JobController
change the indexAction
to render the template according to the _format
:
// ... $format = $this->getRequest()->getRequestFormat(); return $this->render('IbwJobeetBundle:Job:index.'.$format.'.twig', array( 'categories' => $categories )); // ...
Replace the Atom template header with the following code:
<!-- ... --> <title>Jobeet</title> <subtitle>Latest Jobs</subtitle> <link href="{{ url('ibw_job', {'_format': 'atom'}) }}" rel="self"/> <link href="{{ url('ibw_jobeet_homepage') }}"/> <updated>{{ lastUpdated }}</updated> <author><name>Jobeet</name></author> <id>{{ feedId }}</id> <!-- ... -->
From the JobController (index action)
we have to send the lastUpdated
and feedId
to the template:
// ... $latestJob = $em->getRepository('IbwJobeetBundle:Job')->getLatestPost(); if($latestJob) { $lastUpdated = $latestJob->getCreatedAt()->format(DATE_ATOM); } else { $lastUpdated = new DateTime(); $lastUpdated = $lastUpdated->format(DATE_ATOM); } $format = $this->getRequest()->getRequestFormat(); return $this->render('IbwJobeetBundle:Job:index.'.$format.'.twig', array( 'categories' => $categories, 'lastUpdated' => $lastUpdated, 'feedId' => sha1($this->get('router')->generate('ibw_job', array('_format'=> 'atom'), true)), )); // ...
To get the date of the latest post, we have to create the getLatestPost()
method in the JobRepository
:
// ... public function getLatestPost($category_id = null) { $query = $this->createQueryBuilder('j') ->where('j.expires_at > :date') ->setParameter('date', date('Y-m-d H:i:s', time())) ->andWhere('j.is_activated = :activated') ->setParameter('activated', 1) ->orderBy('j.expires_at', 'DESC') ->setMaxResults(1); if($category_id) { $query->andWhere('j.category = :category_id') ->setParameter('category_id', $category_id); } try{ $job = $query->getQuery()->getSingleResult(); } catch(DoctrineOrmNoResultException $e){ $job = null; } return $job; } // ...
The feed entries can be generated with the following code:
{% for category in categories %} {% for entity in category.activejobs %} <entry> <title>{{ entity.position }} ({{ entity.location }})</title> <link href="{{ url('ibw_job_show', { 'id': entity.id, 'company': entity.companyslug, 'location': entity.locationslug, 'position': entity.positionslug }) }}" /> <id>{{ entity.id }}</id> <updated>{{ entity.createdAt.format(constant('DATE_ATOM')) }}</updated> <summary type="xhtml"> <div xmlns="http://www.w3.org/1999/xhtml"> {% if entity.logo %} <div> <a href="{{ entity.url }}"> <img src="http://{{ app.request.host }}/uploads/jobs/{{ entity.logo }}" alt="{{ entity.company }} logo" /> </a> </div> {% endif %} <div> {{ entity.description|nl2br }} </div> <h4>How to apply?</h4> <p>{{ entity.howtoapply }}</p> </div> </summary> <author><name>{{ entity.company }}</name></author> </entry> {% endfor %} {% endfor %}
LATEST JOBS IN A CATEGORY FEED
One of the goals of Jobeet is to help people find more targeted jobs. So, we need to provide a feed for each category.
First, let’s update the links to category feeds in the templates:
<div class="feed"> <a href="{{ path('IbwJobeetBundle_category', { 'slug': category.slug, '_format': 'atom' }) }}">Feed</a> </div>
<div class="feed"> <a href="{{ path('IbwJobeetBundle_category', { 'slug': category.slug, '_format': 'atom' }) }}">Feed</a> </div>
Update the CategoryController
showAction
to render the corresponding template:
// ... public function showAction($slug, $page) { $em = $this->getDoctrine()->getManager(); $category = $em->getRepository('IbwJobeetBundle:Category')->findOneBySlug($slug); if (!$category) { throw $this->createNotFoundException('Unable to find Category entity.'); } $latestJob = $em->getRepository('IbwJobeetBundle:Job')->getLatestPost($category->getId()); if($latestJob) { $lastUpdated = $latestJob->getCreatedAt()->format(DATE_ATOM); } else { $lastUpdated = new DateTime(); $lastUpdated = $lastUpdated->format(DATE_ATOM); } $total_jobs = $em->getRepository('IbwJobeetBundle:Job')->countActiveJobs($category->getId()); $jobs_per_page = $this->container->getParameter('max_jobs_on_category'); $last_page = ceil($total_jobs / $jobs_per_page); $previous_page = $page > 1 ? $page - 1 : 1; $next_page = $page < $last_page ? $page + 1 : $last_page; $category->setActiveJobs($em->getRepository('IbwJobeetBundle:Job')->getActiveJobs($category->getId(), $jobs_per_page, ($page - 1) * $jobs_per_page)); $format = $this->getRequest()->getRequestFormat(); return $this->render('IbwJobeetBundle:Category:show.' . $format . '.twig', array( 'category' => $category, 'last_page' => $last_page, 'previous_page' => $previous_page, 'current_page' => $page, 'next_page' => $next_page, 'total_jobs' => $total_jobs, 'feedId' => sha1($this->get('router')->generate('IbwJobeetBundle_category', array('slug' => $category->getSlug(), 'format' => 'atom'), true)), 'lastUpdated' => $lastUpdated )); }
Eventually, create the show.atom.twig
template:
<?xml version="1.0" encoding="utf-8"?> <feed xmlns="http://www.w3.org/2005/Atom"> <title>Jobeet ({{ category.name }})</title> <subtitle>Latest Jobs</subtitle> <link href="{{ url('IbwJobeetBundle_category', { 'slug': category.slug, '_format': 'atom' }) }}" rel="self" /> <updated>{{ lastUpdated }}</updated> <author><name>Jobeet</name></author> <id>{{ feedId }}</id> {% for entity in category.activejobs %} <entry> <title>{{ entity.position }} ({{ entity.location }})</title> <link href="{{ url('ibw_job_show', { 'id': entity.id, 'company': entity.companyslug, 'location': entity.locationslug, 'position': entity.positionslug }) }}" /> <id>{{ entity.id }}</id> <updated>{{ entity.createdAt.format(constant('DATE_ATOM')) }}</updated> <summary type="xhtml"> <div xmlns="http://www.w3.org/1999/xhtml"> {% if entity.logo %} <div> <a href="{{ entity.url }}"> <img src="http://{{ app.request.host }}/uploads/jobs/{{ entity.logo }}" alt="{{ entity.company }} logo" /> </a> </div> {% endif %} <div> {{ entity.description|nl2br }} </div> <h4>How to apply?</h4> <p>{{ entity.howtoapply }}</p> </div> </summary> <author><name>{{ entity.company }}</name></author> </entry> {% endfor %} </feed>
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.