Warning: htmlspecialchars() : Invalid multibyte sequence in argument about compasselephantbundle HOT 9 CLOSED

😃
thank you for reporting this...

Looks like the error is generated in the data collector...
could you please try to remove the service from the container by removing these lines, clear the cache and see if the problem is gone?

from compasselephantbundle.

Thank you for your quick reply!

I have removed the data_collector.cypress_compass_elephant service definition from the listener.xml file and the error is gone (nothing in the profiler anymore) but the file is not updated (but I believe this service must be useful at some point :) )

from compasselephantbundle.

in fact the bundle should work well without the collector, it is responsible only of the profiler...have you tried to change something in the sass file (or touch it from the command line) just to trigger the update?

from compasselephantbundle.

I just performed a few more tests.

In that case, I change the _settings.scss file, which is where we store our variables.
Even with the service removed, the new css file is not built and therefore not caught by the assetic:dump --watch option.

Nonetheless, I have noticed that the php app/console cypress🧭compile command generates the file properly (and it is well caught by the assetic process)

from compasselephantbundle.

This is why this bundle exists at all. Assetic do not recognize well the assets dependencies. So now (without the collector) everything should work well right?

from compasselephantbundle.

Sorry, I might have confused you with my setup.
Please let me elaborate on what is the issue (and remove assetic from the equation).

On my machine:

1. I change _settings.scss
2. I display the home page
3. A new css file (style.css) is generated (it is generated outside the web folder and is picked up by assetic, but that it does not seem to be the issue)

On my colleague's machine:

1. I change _settings.scss
2. I display the home page
3. The style.css is not generated. Since we have an error, I believe the compass listener works properly but the generation fails at some point.

Assetic is not really related, sorry I should have simplified the problem.

Right now, I have no clue of what is going on and what I could do to continue the investigation. If you have leads, I would be happy to investigate.
Thanks again! 👍

from compasselephantbundle.

also here no clues 😃

try to investigate further and let me know if you find something useful.
The only things I can suggest is to find that little difference between your setups. If it works for you (and for me) it should work for your colleague too!

from compasselephantbundle.

Thank you for the time spent on this issue.
For the time being, my colleague uses a compass watch in order to make the whole thing works.
Nonetheless, I will try to gather more information. Maybe the debug mode could help solving this mystery!
Thanks again for your work!

from compasselephantbundle.

let me know if you find the light! Maybe it's a bug that could be fixed...

from compasselephantbundle.