Magento email templates "Error in template processing" - magento-1.9.1

I'm pulling my hair out with this one so hopefully someone can help.
I upgraded my "Mage_All_Latest" package to the latest one (1.9.1.0) and since then my transactional emails don't seem to have any styles. The ones that I've created myself under System->Transactional Emails are working but the standard ones just don't work. Below is what I get when I preview, this is also how it is received when sent (it still contains the order details however, just no header/footer or style):
{Error in template processing} {{inlinecss file="email-inline.css"}}
Thank you for your order from .
Once your package ships we will send an email with a link to track your order. Your order summary is below. Thank you again for your business.
Order Questions?
Your order #
Placed on
Bill to:
Payment method:
{Error in template processing}
Thanks for any help advance.

I recommend you do an update via shell ./mage upgrade-all or reinstall via magento connect. It is possible that some packages where missing on your install or patches have been applied.
I had magento 1.9.0.1 with the same problem. I upgraded via shell to 1.9.1.0 and the email header/footer issue was fixed!
Once fixed, you should see options for Email Header Template, Email Footer Template and Non-inline CSS File(s) under Design > Transactional Emails.

I had the same problem once then i found it happened because i changed the Email template in local/... and the Magento changed the email template in the new version so i copied my change to the new template and every thing went back to normal

Related

spartacus sampledata inconsistency: spartacus requests "shipping-address" but in 2105 sampledata there is only "delivery-address"-> Checkout broken

I have setup the current version of spartacus (4.3) with Sap Commerce 2205 according to the installation instructions.
No customizations have been done to backend or frontend.
I observe the following issue when trying to enter the checkout in electronics and apparel store:
The request just is being sent in an endless loop because the stroefront requests "shipping-address" which does not exist.
Only "delivery-address" exists. Even when changing the page label of the contentpage to "shipping-address" so that the request from teh frontend can be fulfilled, the checkout page just remains empty and is not functional.
Any ideas what can be done to fix this ootb error?
Image with the endless loop requests
Ok, after some more research, i can answer this myself:
The naming in the impex files in the sampledata for 2105 (the most current sampledata) has been changed from "shipping" to "delivery".
But the spartacus frontend (still) asks for and expects a page with "shipping"-label and "shipping"-components.
A workaround is to go through the files in the sampledata and adjust delivery to shipping where necessary and import the relevant lines in the backend.
Would be great if SAP fixes this inconsistency to not throw off people setting up the system according to the official documentation.
For reference, the specific changes need to get it working for me are as follows - for electronics content catalog. The other catalogs require similar changes.
Source file: spartacussampledata/import/contentCatalogs/electronicsContentCatalog/cms-responsive-content.impex
ContentPage.label : /checkout/delivery-address -> /checkout/shipping-address
CMSFlexComponent.flexType : CheckoutDeliveryAddress -> CheckoutShippingAddress
$contentCatalog=electronics-spaContentCatalog
$contentCV=catalogVersion(CatalogVersion.catalog(Catalog.id[default=$contentCatalog]),CatalogVersion.version[default=Online])[default=$contentCatalog:Online]
INSERT_UPDATE ContentPage;$contentCV[unique=true];uid[unique=true];name;masterTemplate(uid,$contentCV);label;defaultPage[default='true'];approvalStatus(code)[default='approved'];homepage[default='false']
;;CheckoutDeliveryAddress;Checkout Delivery Address Page;MultiStepCheckoutSummaryPageTemplate;/checkout/shipping-address
INSERT_UPDATE CMSFlexComponent;$contentCV[unique=true];uid[unique=true];name;flexType
;;CheckoutDeliveryAddressComponent;Checkout Delivery Address Component;CheckoutShippingAddress

shopify-buy SDK cant checkout or add items to cart anymore

Recently all my Shopify apps have stopped working due to this error. I can still pull data from the api (photos, titles, etc) but I can no longer add items to my cart or check out. this error isn't just happening on my current build but previous builds too. I think I might have made too many requests due to refreshing pages and have been banned from the API temporarily (I've had this happen with another API before). but it's now been 2 days and still no fix.
I'm pretty confident there's nothing wrong with my code because it's happening to other websites that were working before & haven't been touched for a while.
package used: "shopify-buy": "^2.11.0"
Thanks,
Mitchell D
turns out this error occurred because I was in PAUSE AND BUILD mode. so I must be on a plan to add items to the cart using the API? they must have made this change recently

SharePoint Workflow Only Works For Me?

Ok, I have a workflow built in SharePoint 2010, built in SharePoint Designer. It is set up to begin whenever a new item is created. The library is also set up to create new items based on email attachments. So the goal is for users to email the attachments to the library and the workflow takes over.
The workflow only works for me. The other people attempting to use it are listed as Full Control in the permissions. They are using the correct email address, and the library is creating the new items based on the attachments. The problem is that the workflow keeps saying error occurred.
The error says something about some columns needing different types of data, but when I email to the library it goes off without a hitch.
I am completely stumped as to what could be different about them sending the email instead of me.
Sorry I got kind of long winded, and thanks in advance for any help.
The system account is not allowed to initiate workflow on its own. There is a powershell that you need to run to enable system account to run workflow. Also try impersonation in workflow.
Here found it.
stsadm.exe –o setproperty –propertyname declarativeworkflowautostartonemailenabled –propertyvalue yes
Not sure what was wrong with it, but I just deleted it then rebuilt it and now it works. Don't think I did anything different so I'm not sure.

Issue in submitting and updating the safari extension

I have my safari extension in the gallery.
Now I made few minor changes in my code and then resubmitted it for review (it takes a month to review, :( that is really a long time)
After almost a month, I received an email from safari , that my extension is rejected because of this Issue
Please strip the extended attributes (xattr -c path/to/extension.safariextension) and rebuild your Safari Extension package using the latest version of Safari.
I tried the above command but every time I face the same issue.
and also I am confused that if every time I update my code, I need to resubmit extension for review, then what is the use of this link:
https://developer.apple.com/library/archive/documentation/Tools/Conceptual/SafariExtensionGuide/UpdatingExtensions/UpdatingExtensions.html
also, when I was going through all this, I got an email from safari that my certificate (which is used in extension builder to create .extz file) is going to expire in a month
I created a new certificate and created a new extz file.
but don't know that do I need to resubmit my extension or just update it on webserver.
so basically I have 3 issues/ confusions
Do I need to resubmit extension everytime I update code or just updating extz on web server will work
what do I have to do for this:
"extension description within the Safari extension preference pane appears to be a placeholder"
Safari Extension certificate expires in a year, everyYear I need to resubmit extension or can update extz with new certificate on web server will work
Thanks in Advance
================update======================================
Submitting Extension removing extended attributes is actually resolved
by just running this command from MAC xattr -c path/to/extension.safariextension, and then rebuild and submit.
So, Question 2 is resolved , now I just want to clarify about other 2 parts of my question 1st and 3rd.
Had same issue with this placeholder -issue, fixed by adding/modifying proper Description in Information -section of Extension Builder.

Auto email response from Shopify api

I've successfully created a script that will import username/passwords etc into Shopify (using the api).
However, when I do this an automatic email is sent to the customer. I don't need this and can't find a way of either modifying it or turning it off. There is no mention of the email in the api documentation which has meant me finding out the hard way (by some clients complaining!)
The email is not the same one that is sent to the customer when a new account is set up. So where does it come from? How can I switch it off/modify it's contents?
Any ideas?
Well, after some digging I found where the email message was being generated from. It is one of the default messages that are already set up in Shopify (Customer Account confirmation) under 'Emails & Notifications'.
Just make sure you change this before you start running your shop as the default message is a little 'dry'.
Thanks for your help guys.