Magento

This has probably been covered before but I couldn’t find it:

I create new email templates from admin > transactional emails

create the new template based on the standard magento one e.g. new order template
change the wording, alt tags etc
upload a new logo_email.gif image to my skin/images folder.
refresh cache etc
the image still goes to the one in the default skin (i.e. not in the skin I am using)

the skin is configured ok in admin and works on the rest of the site but within an email template it always looks for the default skin location instead of the one I am using......the url that calls the image appears to be ok too , i.e. <img src="{{skin url="images/logo_email.gif" _area=’frontend’}}

has anyone any ideas why this is happening? anyone have the same issue?

I know it is probably something I have missed but can’t figure for the life of me what it is.

thanks very much

I have occasionally forund such things, and solved it by deleting /var/cache THe whole folder /cache It recreates itself right away. Might solve your probelm, might not.  But it has for me with similar things that seeem inexplicable like this.

I’ve noticed the same problem. I tried the cache thing mentioned in this thread already, and it didn’t help in my case. I’ve had to replace the logo in my default theme directory. So, I just need to be careful when I upgrade to make sure the old image doesn’t get reintroduced.

Did you change your store configuration to show the new theme under Design / Themes?

You should place this new image in your custom theme folder and then point to this new custom theme in your configuration.

/skin/frontend/default/my_theme/images/logo-email.gif

The store will find all the rest of the images missing in the default theme.  I hope this makes sense.

Maybe try this:

<img src="{{skin url="images/logo_email.gif" _area=’frontend’ _theme=’your_theme’}}

@adimagento: It still doesn’t work, I just keep getting the default/default logo.

Has anyone come up with a solution to this problem?

I had this this problem as well.

The code points to exactly the same place as working html emails, I think this could be a bug.

If you feel this is a bug, please open up a bug report and we will examine it.

Same problem here, seems to be a bug.

in my case i made a new image file with a new name but even with the flag _theme=’my_theme’ it still points to the default/default direction… hmm lets wait

adimagento - 13 June 2008 08:33 PM

Maybe try this:

<img src="{{skin url="images/logo_email.gif" _area=’frontend’ _theme=’your_theme’}}

This fixed it for me, though change the single quotes ‘ to double quotes “

adimagento - 13 June 2008 08:33 PM

Maybe try this:

<img src="{{skin url="images/logo_email.gif" _area=’frontend’ _theme=’your_theme’}}

The following code worked for me
<img src="{{skin url="images/logo_email.gif" _area="frontend" _theme="your_theme"}}

there should be a “ instead of ‘ for area and theme

Hi,
If you have a package name different from the default, as per the Magento Design instructions, you need to change this line to:
<img src="{{skin url="images/logo_email.gif" _area="frontend" _package="your_package" _theme="your_theme"}} alt="store_name" .....

Hope this helps.

I’ve spent the last few hours customizing the default transactional emails. I don’t understand why the default ones have so much Magento demo junk in them.

But I figured out that you can use CMS Static Blocks in them.
I created a block for email_logo and email_style and email_contact_us so that these things can be easily changed in the admin and they are in just one location.

Then the part that goes in the email looks like this:

{{block type="cms/block" block_id="email_style"}}
or
{{block type="cms/block" block_id="email_contact_us"}}
{{block type="cms/block" block_id="email_logo"}}

I changed the default emails so my client doesn’t get the demo store email accidentally. The panel to edit the emails is okay, but I don’t see why the template load button is only available for a new email template. It should be there for those that already exist, so you can start from a template again if you need to. That’s the only way my client has to see what’s in each of them.

adimagento - 13 June 2008 08:33 PM

Maybe try this:

<img src="{{skin url="images/logo_email.gif" _area=’frontend’ _theme=’your_theme’}}

While this may work, I would still consider this a bug. It completely erases the ease of hosting multiple websites with Magento. For every website I want to setup, I need to setup separate transaction emails or no do no skinning in the emails. That doesn’t fit with the rest of how Magento works.

3rdRock - 27 September 2008 03:33 PM

adimagento - 13 June 2008 08:33 PM

Maybe try this:

<img src="{{skin url="images/logo_email.gif" _area=’frontend’ _theme=’your_theme’}}

While this may work, I would still consider this a bug. It completely erases the ease of hosting multiple websites with Magento. For every website I want to setup, I need to setup separate transaction emails or no do no skinning in the emails. That doesn’t fit with the rest of how Magento works.

I’ve done a little more sleuthing…

The new order template does set the skin url to the correct location. It appears to only be the other templates that are “kicked off” via the admin interface that are having this problem of not setting the skin url correctly.

I’ve even tried setting the config design parameters on each individual store, but everything defaults to the default/default skin.

I found the following in Core/Model/Design/Package.php

If I change the default package to my custom package, then the email will send fine. However, my admin breaks.

Modifying these won’t solve the problem because Magento should use the skin of the website that the order was placed on. Could you imaging ordering something from one store and then getting an email for the shipment confirmation that has a completely different logo at the top of the email? That wouldn’t be good for business.

I suspect that by the time things are getting to app/code/core/Mage/Core/Model/Email.php, the skin has already been lost. I don’t have a debugger, so I don’t know if the emails ever have the correct package and theme information during the send.

I have created a bug in the system for this issue because it is very critical for multi-store setups. Creating custom email templates for every single store is going to be a killer.

Came across the same problem, read the thread and tried all the suggestions. I came up with a simple alternative.

Create a folder call images in your root directory and place the logo_email.gif file in it.

Change this:

To this:

Hope this helps