Symfony/Twig "Asset" function in dev mode

Question

I am trying to render an image in a Twig template like this:

<img src="{{ asset('bundles/mybundle/images/no-image.png') }}" alt="no image available" />

It is being rendered like this (with a leading slash):

<img src="/bundles/mybundle/images/no-image.png" alt="no image available" />

which causes the server to look for an image in http://myserver.com/bundles/mybundle/images/no-image.png

The problem is when I am viewing the page in dev mode, it doesn't generate the correct asset url. What it should be is:

<img src="bundles/mybundle/images/no-image.png" alt="no image available" />

which would cause the server to look in the correct location:

http://myserver.com/app_dev.php/bundles/mybundle/images/no-image.png

Is there some way around this issue? I want the images in dev mode to run through app_dev.php

My reason is because I have different error reporting setup for dev and prod, and the images are going through prod which is triggering email errors that I don't want to receive while working in dev. — Steven Musumeche
– Steven Musumeche, Commented Jul 25, 2014 at 15:21
Images don't go throught any front controller, you can give a look to your /web/.htaccess file , You will notice that files are served directly — Filo
– Filo, Commented Jul 25, 2014 at 15:23
If I used assetic, they would, so when just using the asset function, they aren't? — Steven Musumeche
– Steven Musumeche, Commented Jul 25, 2014 at 15:28
@StevenMusumeche if you use assetic, they would only do so in Dev mode, so you don't need to dump the files every time. Use the front controller only for files that need PHP to run. — Wouter J
– Wouter J, Commented Jul 25, 2014 at 21:20

Wouter J · Accepted Answer · 2014-07-25 21:24:29Z

1

Assetic uses PHP to combine, minify and modify the assets. In development, these assets can change continue, you don't want to execute the dump command each time you changed something. That's why Assetic has a use_controller setting so assetic combines, minifies and modifies the files at request time and then returns the response as a correct CSS or JS file.

With normal assets, like images, JS files, CSS files, etc., there is nothing dynamic to run. The browser should simply request the images from the server, where they are stored. So this shouldn't go via the framework.

answered Jul 25, 2014 at 21:24

Wouter J

42k15 gold badges113 silver badges114 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Steven Musumeche Over a year ago

So my issue is that because I am on a dev server, often the images will not exist. Since they are trying to be accessed via "prod" mode, the error reporting config for production is activated (email logs, etc), which I am trying to avoid. Is that possible without copying all of the images to my dev server (100+ GB)?

Collectives™ on Stack Overflow

Symfony/Twig "Asset" function in dev mode

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related