Flag of Ukraine
SymfonyCasts stands united with the people of Ukraine

Smartly Updating Elements for all Users

Keep on Learning!

If you liked what you've learned so far, dive in!
Subscribe to get access to this tutorial plus
video, code and script downloads.

Start your All-Access Pass
Buy just this tutorial for $12.00

With a Subscription, click any sentence in the script to jump to that part of the video!

Login Subscribe

With the power to return a normal redirect from our controller and publish a Mercure update to modify any part of any user's page, we can now really clean up our review system. After a successful form submit, we redirect to a page that renders _reviews.html.twig... which includes the reviews list on top and also the review form down here. Then... we send this same thing to the user via the stream update. The only reason we're doing this is so that the review list updates for all users, not just the user that submitted the form.

So... you can see that there's some duplicated work going on. But worse, there's a bug! Copy the URL and open this same page in an incognito window. Notice that we are not logged in. Let's pretend that this tab represents a user in Argentina... and the other tab is a user in Ukraine.

Let's refresh and have our Ukrainian friend submit a new review... this will be review number 21. When we submit, it looks good here. On the other user's page, the review shows up... but oh! It also shows a success message! So when our Ukrainian user submitted a new review, our Argentinian friend suddenly saw a success message!

That's... ya know... not what we want. But I can already see the problem: in the turbo stream, we're sending the entire _reviews.html.twig template to all users... which includes the reviews list... but also the flash message and the form.

Splitting the Reviews Frame and Stream

No worries: we just need to be a bit more careful. The entire _reviews.html.twig template is surrounded by a <turbo-frame>. But we really only need the frame to surround the form... because we can update the reviews list via the stream.

Check it out: at the bottom of the reviews list, close that <turbo-frame>. Now, create a new <turbo-frame> with id="", how about, product-reviews-form. We don't need a closing tag... because we already have one.

... lines 1 - 2
<turbo-frame id="product-{{ product.id }}-review">
... lines 4 - 13
<turbo-frame id="product-reviews-form">
... lines 19 - 44

Oh, and in this case, we don't need to make the id dynamic for each product because we're not going to update this with a Turbo Stream. So there's no risk of affecting the wrong page.

With just this change, the form now lives in a different frame. And so, if we were to refresh the page and submit the form... it now only affects this part of the page.

The next step is to make sure that our stream update sends back the list, not the list and the form. To do that, we need to isolate the list into its own template. Copy that turbo frame and, inside templates/product/, create a new file called, how about, _reviews_list.html.twig. Paste the frame here.

<turbo-frame id="product-{{ product.id }}-review">
{% for review in product.reviews %}
<div class="component-light my-3 p-3">
<p><i class="fas fa-user-circle me-2"></i>{{ review.owner.email }} <i class="fas fa-star ms-4"></i> {{ review.stars }}/5</p>
{{ review.content }}
{% else %}
<p>This product has not been reviewed yet!</p>
{% endfor %}

Back in the other template, include this.

<div {{ turbo_stream_listen('product-reviews') }}></div>
{{ include('product/_reviews_list.html.twig') }}
... lines 4 - 6
<turbo-frame id="product-reviews-form">
... lines 8 - 33

Nice. Oh, but in the new template, we don't actually need this to be a Turbo frame anymore. Change this to be a div. Think about it: we're not using any Turbo frame features with this... we just need an element that we can target from our turbo stream. A turbo-frame would have worked... it just wasn't necessary.

<div id="product-{{ product.id }}-review">
... lines 2 - 11

Anyways, stream this template instead: _reviews_list.html.twig.

Sweet! Testing time! Refresh both tabs... and let's post review number 22.

When I submit here... perfect! The review form area updated thanks to the frame. Then the stream took care of adding the review here and updating the quick stats area. In the other browser, the quick stats updated, we see the new review, but it did not mess with the form area.

Appending the New Review

Look back at reviews.stream.html.twig. Right now we're streaming and replacing the entire reviews list. That's probably fine... but because we know that a single new review was just added, we could, instead, send only the new review in the stream instead of everything. We don't have to do this, but let's try it.

First, over in _reviews.html.twig, on the id, I'm going to add a -list to the end. I'm doing this just to make its meaning more obvious: it's a list, not a single review. Repeat this in the stream template.

<div id="product-{{ product.id }}-review-list">
... lines 2 - 11

... lines 1 - 6
<turbo-stream action="replace" target="product-{{ product.id }}-review-list">
{{ include('product/_reviews_list.html.twig') }}

Now over in _reviews_list.html.twig, copy the div for a single review and isolate it into its own template: _review.html.twig. Back in the list, include that.

<div class="component-light my-3 p-3">
<p><i class="fas fa-user-circle me-2"></i>{{ review.owner.email }} <i class="fas fa-star ms-4"></i> {{ review.stars }}/5</p>
{{ review.content }}

<div id="product-{{ product.id }}-review-list">
{% for review in product.reviews %}
{{ include('product/_review.html.twig') }}
{% else %}
<p>This product has not been reviewed yet!</p>
{% endfor %}

So no changes yet, just some reorganization. But now, in the stream, change the action to append... and include the single review template.

That's nice! In _review.html.twig, this needs a review variable. In ProductController... let's see: we're only passing a product variable right now. Also pass a newReview variable set to the review... which is $form->getData().

Back in the stream, pass in a review variable set to newReview.

... lines 1 - 20
class ProductController extends AbstractController
... lines 23 - 74
public function productReviews(Product $product, CategoryRepository $categoryRepository, Request $request, EntityManagerInterface $entityManager, HubInterface $mercureHub)
... lines 77 - 91
$update = new Update(
$this->renderView('product/reviews.stream.html.twig', [
'product' => $product,
'newReview' => $reviewForm->getData(),
... lines 99 - 114
... lines 116 - 123

... lines 1 - 6
<turbo-stream action="append" target="product-{{ product.id }}-review-list">
{{ include('product/_review.html.twig', {
review: newReview,
}) }}

Let's try the whole flow. Refresh both tabs. We're filling in review number 23. Submit and... sweet! Three things just happened. First the form area updated thanks to the Turbo frame system. Second, the new review was appended to the list thanks to the stream. And finally, the quick stats area was updated also thanks to the stream.

Over in the incognito tab, it's almost the same. The reviews list has the new review and the quick stats area updated... all without affecting the form area.

Next: let's celebrate by visually highlighting the new review the moment it pops onto the page.

Leave a comment!

Login or Register to join the conversation

I am using UX Turbo, I watched this doc : https://github.com/symfony/...
I wanted to know if it is possible to push data to selected users through a query, but also push other data to a single user.
The idea is to recreate a kind of notification bar like Facebook.
For instance: "User A" mentions me in a comment. I would then be the only one to be notified. Only me will receive this notification.
Another case, "User B" posts a link. All users who are friends of this person should be notified.
I don't see how to do it at all. Thank you for helping me :)


Hey Sébastien J. !

It's an excellent question. It comes down to smartly designing your topics, and it IS a bit tricky. For example, if we want to be able to push messages ONLY to User A, then User A needs to be subscribed to only a topic FOR them - e.g. topic_userA. Then, if you want to be able to publish a message to all the friends of User B, then you either need to: (A) have those listeners all listening to a topic for this specific thing - e.g. topic_friends_of_UserN, or (B) you need to publish this message multiple times: publishing it once for EACH friend's private topic (e.g. topic_userD and topic_userF if User D and User F are the 2 friends of User B). Really, (B) is probably the only real solution... as if you tried idea (A), then if a user had 100 friends, they would need to be listening to 101 topics (their own person topic + 1 topic for each of their friends).

So, like I said, tricky! But it's all about delivering messages to the right people... by designing who listens to which topic and then delivering to the correct topics. And, by the way, while it might seem weird to deliver the same message "User B posted a link!" 100 times to 100 different topics (for User B's 100 friends), by leveraging Messenger, you can do this fairly easily.

I hope this at least gives you some ideas!



Thank you very much weaverryan.
I'll try :)

Cat in space

"Houston: no signs of life"
Start the conversation!

What PHP libraries does this tutorial use?

// composer.json
    "require": {
        "php": ">=8.1",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "composer/package-versions-deprecated": "", //
        "doctrine/annotations": "^1.0", // 1.13.1
        "doctrine/doctrine-bundle": "^2.2", // 2.3.2
        "doctrine/orm": "^2.8", // 2.9.1
        "phpdocumentor/reflection-docblock": "^5.2", // 5.2.2
        "sensio/framework-extra-bundle": "^6.1", // v6.1.4
        "symfony/asset": "5.3.*", // v5.3.0-RC1
        "symfony/console": "5.3.*", // v5.3.0-RC1
        "symfony/dotenv": "5.3.*", // v5.3.0-RC1
        "symfony/flex": "^1.3.1", // v1.18.5
        "symfony/form": "5.3.*", // v5.3.0-RC1
        "symfony/framework-bundle": "5.3.*", // v5.3.0-RC1
        "symfony/property-access": "5.3.*", // v5.3.0-RC1
        "symfony/property-info": "5.3.*", // v5.3.0-RC1
        "symfony/proxy-manager-bridge": "5.3.*", // v5.3.0-RC1
        "symfony/runtime": "5.3.*", // v5.3.0-RC1
        "symfony/security-bundle": "5.3.*", // v5.3.0-RC1
        "symfony/serializer": "5.3.*", // v5.3.0-RC1
        "symfony/twig-bundle": "5.3.*", // v5.3.0-RC1
        "symfony/ux-chartjs": "^1.1", // v1.3.0
        "symfony/ux-turbo": "^1.3", // v1.3.0
        "symfony/ux-turbo-mercure": "^1.3", // v1.3.0
        "symfony/validator": "5.3.*", // v5.3.0-RC1
        "symfony/webpack-encore-bundle": "^1.9", // v1.11.2
        "symfony/yaml": "5.3.*", // v5.3.0-RC1
        "twig/extra-bundle": "^2.12|^3.0", // v3.3.1
        "twig/intl-extra": "^3.2", // v3.3.0
        "twig/string-extra": "^3.3", // v3.3.1
        "twig/twig": "^2.12|^3.0" // v3.3.2
    "require-dev": {
        "doctrine/doctrine-fixtures-bundle": "^3.4", // 3.4.0
        "symfony/debug-bundle": "^5.2", // v5.3.0-RC1
        "symfony/maker-bundle": "^1.27", // v1.31.1
        "symfony/monolog-bundle": "^3.0", // v3.7.0
        "symfony/stopwatch": "^5.2", // v5.3.0-RC1
        "symfony/var-dumper": "^5.2", // v5.3.0-RC1
        "symfony/web-profiler-bundle": "^5.2", // v5.3.0-RC1
        "zenstruck/foundry": "^1.10" // v1.10.0

What JavaScript libraries does this tutorial use?

// package.json
    "devDependencies": {
        "@babel/preset-react": "^7.0.0", // 7.13.13
        "@fortawesome/fontawesome-free": "^5.15.3", // 5.15.3
        "@hotwired/turbo": "^7.0.0-beta.5", // 1.2.6
        "@popperjs/core": "^2.9.1", // 2.9.2
        "@symfony/stimulus-bridge": "^2.0.0", // 2.1.0
        "@symfony/ux-chartjs": "file:vendor/symfony/ux-chartjs/Resources/assets", // 1.1.0
        "@symfony/ux-turbo": "file:vendor/symfony/ux-turbo/Resources/assets", // 0.1.0
        "@symfony/ux-turbo-mercure": "file:vendor/symfony/ux-turbo-mercure/Resources/assets", // 0.1.0
        "@symfony/webpack-encore": "^1.0.0", // 1.3.0
        "bootstrap": "^5.0.0-beta2", // 5.0.1
        "chart.js": "^2.9.4",
        "core-js": "^3.0.0", // 3.13.0
        "jquery": "^3.6.0", // 3.6.0
        "react": "^17.0.1", // 17.0.2
        "react-dom": "^17.0.1", // 17.0.2
        "regenerator-runtime": "^0.13.2", // 0.13.7
        "stimulus": "^2.0.0", // 2.0.0
        "stimulus-autocomplete": "https://github.com/weaverryan/stimulus-autocomplete#toggle-event-always-dist", // 2.0.0
        "stimulus-use": "^0.24.0-1", // 0.24.0-2
        "sweetalert2": "^11.0.8", // 11.0.12
        "webpack-bundle-analyzer": "^4.4.0", // 4.4.2
        "webpack-notifier": "^1.6.0" // 1.13.0