$ composer require everlutionsk/ajaxcom-bundle

<?php
// app/AppKernel.php

// ...
class AppKernel extends Kernel
{
    public function registerBundles()
    {
        $bundles = array(
            // ...

            new Everlution\AjaxcomBundle\EverlutionAjaxcomBundle(),
        );

        // ...
    }

    // ...
}

Install @everlutionsk/ajaxcom-js via npm and include ajaxcom.js to your TWIG layout:

<script type="text/javascript" src="{{ asset('build/ajaxcom.js') }}"></script>

The last thing you need to do is provide some JavaScript handler within your TWIG layout - please follow @everlutionsk/ajaxcom-js documentation.

You don't need to configure anything if you wish to use the flash message templates provided by the bundle.

# all configuration is optional - following values are default
everlution_ajaxcom:
    flash_template: @EverlutionAjaxcom/flash_message.html.twig
    flash_block_id: flash_message
    persistent_class: ajaxcom-persistent
    blocks_to_render: # default value is empty array - when you provide this value, AjaxcomBundle will automatically render these blocks within each AJAX request
          - id: 'content'
          - id: 'navigation'
          - id: 'flash_message'
            refresh: true

By default AjaxcomBundle ignores blocks which are empty and if developer asks to render an empty block we filter out these instances. In case you want to re-render the block with empty content you should set refresh flag to true like you can see in above example.

When you want to set refresh flag from controller you need first add the block and then refresh it:

<?php

public function exampleAction()
{
    $this->addAjaxBlock('example');
    $this->refreshAjaxBlock('example');
    
    return $this->render('some/template');
}

The bundle works best with Bootstrap 3+ CSS framework.

Extend your controller from Everlution\AjaxcomBundle\Controller\Controller or use Everlution\AjaxcomBundle\Controller\AjaxcomTrait trait with your controller to obtain Ajaxcom functionality.

By default ajaxcom-js library will handle all link clicks except one with target="_blank" and all form submissions. If you need to change selector or you want to have some control over which links are handled by ajaxcom-js and which aren't you can override the default selectors within ajaxcom-js initialization. Please see the @everlutionsk/ajaxcom-js documentation.

Example:

<a href="https://www.google.com">External link</a> <!-- won't be handled by Ajaxcom -->
<a href="{{ path('remove_user') }}">Remove user</a> <!-- will be handled by Ajaxcom -->

The following methods can be combined - eg. you can render multiple blocks and remove multiple blocks and add as many JavaScript callbacks within one request as you wish.

Everlution's Ajaxcom bundle extends standard Symfony's render() method so you can integrate Ajaxcom with your project without any further changes within your codebase.

The render() method automatically decides if it responding to the Ajax or non-Ajax call so you don't need to handle special scenarios within your application.

The Ajaxcom bundle will handle your Symfony controller's action with Ajax and non-Ajax request automatically so you don't need to write your code twice - the bundle will always call the same action.

Within your standard Symfony controller's action you will have only tiny overhead which will setup the action's behaviour for handling the Ajax requests. The overhead methods are explained in next few sections.

In order to dynamically render only one block on page you need to fit following two conditions:

1. the block which you want to render is enclosed within twig block
2. the twig block is enclosed within DOM element with ID which has same name as the block

By default the TWIG does not support hyphens in block names so if you need to use hyphens within your ID's we are automatically convert hyphens to underscores for you. Hence you can use hyphens within your ID's with combination of the same name for TWIG block - you just need to replace hyphens with underscores. Example: id='custom-block' and {% block custom_block %} will be automatically matched by AjaxcomBundle.

Twig:

<div id="list">
    {% block list %}
        // this is the HTML which will be replaced/removed ...
    {% endblock %}
</div>

PHP:

$this->renderAjaxBlock("list");

In action of your controller simply call renderAjaxBlock where you need to provide the block ID (eg. TWIG block name).

When your action is called via Ajax request the JSON response for Ajaxcom library will contain information about which block should be re-rendered with which HTML.

If you want to remove some DOM element dynamically for instance after deleting some row from table you can use removeAjaxBlock() method where you will simply provide CSS selector of the element which you want to remove.

Twig:

<table>
    <tbody>
        <tr id="row-1"><td>1.</td></tr>
        <tr id="row-2"><td>2.</td></tr>
        <tr id="row-3"><td>3.</td></tr>
    </tbody>
</table>

PHP:

$this->removeBlock("#row-2");

// OR you can use any CSS selector

$this->removeBlock("tr:nth-child(2)");

The above code (both examples) will remove middle row from the table after the action is called.

Result:

<table>
    <tbody>
        <tr id="row-1"><td>1.</td></tr>
        <!-- the #row-2 has been removed -->
        <tr id="row-3"><td>3.</td></tr>
    </tbody>
</table>

You can add as many JavaScript callbacks as you wish. First argument of addCallback() is name of function which should be called after rendering the HTML, second is array of parameters which will be passed to the function as an object.

Example:

PHP:

$this->addCallback('Table.init', ['some' => 'data', 'other' => ['data', 'etc']]);

var Table = function() {
    return {
        init: function(data){
            var some = data.some;
            var otherArray = data.other;
            
            // initialize table with provided data
        };
    }
};

You don't actually need to use this function if you would write your JavaScript in a following way:

// additional.js
var App = {
    additional: function () {
        // some additional functionality
        console.log('executing App.additional');
    },
    // more functions within App namespace
}

App.additional();

The App.additional() will be executed every time the browser downloads additional.js file - no matter if the request is being handled with or without Ajaxcom. You just need to make sure that you are adding the <script src="additional.js"></script> to your DOM via Ajaxcom where it is needed.

The AjaxcomBundle will add all scripts within javascripts block to your page automatically (they will be inserted after the last <script> within your code).

You can easily replace class in any DOM object you want by invoking replaceClass() with two arguments - first is CSS selector of your choice and second is class which you want to replace current one with.

You can easily avoid replacing url of the target page by invoking doNotChangeUrl().

The flash messages are automatically handled by Ajaxcom bundle. When the request is called via Ajax the flashes which are in the session bag are rendered automatically.

You only need to include provided twig template somewhere within your twig layout:

{% include "@EverlutionAjaxcom/flash_message.html.twig" %}

When you call addFlash() from your controller, please use Everlution\AjaxcomBundle\Flash to provide the flash message type:

$this->addFlash(Everlution\AjaxcomBundle\Flash::SUCCESS, 'Your request has been successfully handled by Ajaxcom bundle');

// you can use following constants:
// Everlution\AjaxcomBundle\Flash::SUCCESS
// Everlution\AjaxcomBundle\Flash::ERROR
// Everlution\AjaxcomBundle\Flash::WARNING
// Everlution\AjaxcomBundle\Flash::INFO

All forms are by default handled by ajaxcom-js. You can change this behaviour by overriding the default forms selector while initializing ajaxcom-js. Please follow @everlutionsk/ajaxcom-js documentation.

In order to reuse data source between for instance multiple tabs you can easily create Twig functions by extending our BaseDataSource.

Simply add to your services.yml following statement:

    AppBundle\DataProvider\:
        resource: '../../src/AppBundle/DataProvider'
        tags: ['twig.extension']

You can specify any folder within your project you want. In this example we have chosen AppBundle\DataProvider namespace.

Each class within this namespace which extends Everlution\AjaxcomBundle\DataSource\BaseDataSource is scanned for public methods with suffix Provider via reflexion and we are creating the simple Twig functions from these methods. Let's see the example:

// AppBundle\DataProvider\Example.php

// simple function which returns static array
public function navigationProvider() {
    return [ 
        // some data... 
    ];
}

// you can use parametrical functions and injected services as well
public function userProfileProvider(int $id) {
    return $this->someService->getData($id);
}

After creating such class you can simply call the function within twig:

{{ dump(navigation()); }} {# will dump static array #}

{% for item in userProfile(2) %}
   {{ dump(item) }}
{% endfor %}

If you want to use AjaxcomBundle seamlessly you should copy @EverlutionAjaxcom\layout_bootstrap_4.html.twig to your project (eg. AppBundle) and modify it to your needs.

This way the AjaxcomBundle will handle tasks such as replacing JavaScripts, StyleSheets and MetaTags for you.

When you are using blocks from @EverlutionAjaxcom\layout_bootstrap_4.html.twig you should be all set up.

When you decide to set up your layout manually following sections will help you to understand how the automatic replacement works.

1. all JavaScript which should be included on every page needs to contain class='ajaxcom-persistent' (or anything you have set within configuration of bundle)
2. your main layout which you are extending must contain {% block javascripts %}{% endblock %}
3. when you are extending your main layout and you are rewriting javascripts block AjaxcomBundle will load scripts from this block automatically for you

1. same as JavaScript, all StyleSheets which should be included on every page needs to containe class='ajaxcom-persistent' (or anything you have set within configuration of bundle)
2. your main layout which you are extending must contain {% block stylesheets %}{% endblock %}
3. when you are extending your main layout and you are rewriting stylesheets block AjaxcomBundle will load styles from this block automatically for you

1. all meta tags which should be present on every page needs to contain class='ajaxcom-persistent' (or anything you have set within configuration of bundle)
2. your main layout which you are extending must contain {% block metatags %}{% endblock %}
3. when you are extending your main layout and you are rewriting metatags block AjaxcomBundle will load meta tags from this block automatically for you
4. if you want to change title of page your layout needs to contain <title>{% block title %}{% endblock %}</title> and you need to rewrite title block within template where you extending your main template

• add complex usage example