ExpressionEngine® Answers is a question and answer site for administrators, end users, developers and designers for ExpressionEngine® CMS. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

First time using Better Workflow and it's been really great for the client.

However, we have a weird issue with previewing images. We're using the approach of having content images inside a Matrix and then placing image slugs within the content and using NSM Transplant to replace the slugs with CE Image.

When we look at the page preview in BW, the src for the image is empty. However, when we publish the page and look at it on the front-end, the images are output as we'd expect.

{exp:channel:entries {gv_param_disable_default}}
{!-- resolves a weird BW issue with Playa field --}


      {exp:ce_img:single src="{cf_content_hero_image}" allow_scale_larger="yes" width="1067"}


    {exp:nsm_transplant:content id="image_{row_count}"}
        {exp:ce_img:single src="{image}" width="{width}" class="{align}" alt="{alt}"}


share|improve this question
Are you by any chance storing the images on an amazon s3? – Philip Zaengle Dec 21 '12 at 3:13
no - they're stored locally – Steven Grant Dec 21 '12 at 4:57
What version of Better Workflow and Matrix are you using? Better Workflow support was just added to Matrix as of version 2.5, and that requires Better Workflow 1.5. – Derek Hogue Dec 27 '12 at 19:40
yeah using the latest version of everything – Steven Grant Dec 28 '12 at 0:41
up vote 2 down vote accepted

I started troubleshooting from Twitter. First off the caveats, I haven't used CE Image, Better Workflow or NSM Transplant. But my first thought was that the issue maybe NSM Transplant.

After watching the 'advanced' video for NSM Transplant, I'm fairly certain this maybe your issue.

When we look at the page preview in BW, the src for the image is empty. However, when we publish the page and look at it on the front-end, the images are output as we'd expect. - Steve Grant

I believe the reason for this, is because NSM Transplant does the replacements at the template level, so unless you've created the Preview template to also contain and use the {exp:nsm_transplant:content id="image_{row_count}"}{/exp:nsm_transplant:content} tags, then the images won't display in preview, because they don't currently exist for the record, NSM Transplant hasn't been called yet.

Are your preview pages custom designed? or are they just the Better Workflow preview pages?

You can check with Better Workflow/Electric Putty. Based on their docs, occassionally…

N.B. Better Workflow's preview feature relies on the standard /template_group/template/entry_id format for its URL so you should be able to simply select the channel's default template. However, depending on how your template is constructed, it may sometimes be necessary to create a 'preview specific' version. -ElectricPutty Documentation

But based on the video and reading skimming through the documentation, I wouldn't expect the images to fully display until after the post is published. So this maybe a situation where a specific preview template needs to be constructed for these items.

share|improve this answer

Just a thought, not an answer -- have you considered trying another snippet-move mechanism?

Stash ( appears to be like all Mark Croxton makes, pretty solid stuff.

It might be taking a different approach that could matter, when you're using it in the Better Workflow previewer. One way to see...

share|improve this answer
I've looked at Stash but unsure of how I'd implement it in this scenario without fundamentally changing how the template is built. – Steven Grant Dec 27 '12 at 0:04

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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