Relinked a bunch of Assets in Wygwam fields to take of advantage of the dynamic link to the Asset. Moved the Assets from a local file upload source to and S3 source. As a result, assets paths now look like this when rendered in a Wygwam field on the front-end:

<img src="{assets_412:http://s3.amazonaws.com/API/images/about/filename.jpg}" />

Looks like a bug? Is there a fix for this?

1 Answer 1


I've got a bug report posted about this, but I do not have a fix for it at the moment. I've added a note to update you here once the release is in that fixes it.

  • 1
    Thanks Lisa! Just an FYI, this is currently working for me: In Wygwam file helper.php I added the following line of code after line 889: preg_match_all("/\\{assets_(\\d*):((.*)(\\}))/uU", $data, $matches); On line 889, it appears the when replacing the {assets_xxx} tags the code assumes there is also a {filedir_xxx} tag after the colon. In my experience this isn't always the case, which means those never get parsed.
    – Synergema
    Commented Mar 21, 2013 at 18:00
  • Thanks for sharing what you found out, Synergema! I'm glad you were able to get it working for your site. :)
    – Lisa
    Commented Mar 21, 2013 at 19:02
  • Synergema - I've got a fix locally I can send you if you want to test it out. Shoot an email to [email protected] if you do.
    – Brad Bell
    Commented Mar 22, 2013 at 22:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.