I have tirelessly tried to create and save an email template to no avail. I have tried different locales and all the templates load fine. But whenever I try to save the template I get this error message - "The template Name must not be empty." although the template name field is filled. What could be the problem?
I strongly recommend the Yireo Email Override extenson (see https://www.yireo.com/software/magento-extensions/email-override). One advantage is templates are stored as files and so can be managed through source control (such as git).
Your problem is mod_security. A fast way to see if that is the problem disable mod_security and try again (http://www.inmotionhosting.com/support/website/modsecurity/disable-mod-security-via-modsec-manager).
Remember to enable again mod_security then find which rule make you problems
http://www.inmotionhosting.com/support/website/modsecurity/find-and-disable-specific-modsecurity-rules
and then make changes to your files (file permission etc.) or you can disable that rules (not recommended).
I had the same issue and addressed it as follows. I deleted most of the content I wanted to have in the email leaving behind just our logo (I suspected the system was rejecting something in the content). I saved the template without most of the content. It saved properly. I then opened up the template and pasted in the rest of my html and saved it.
Related
I am trying to transalte the defualt Cookie Restriction Mode Message in Magento 2.3.2. I've tried, adding the whole message in my bg_BG.csv file in my custom child theme where all my other translations are located but the new translation is not applied. I've tried searching for a Block but I do not have one. Is there something which I am not doing correctly?
What you are doing wrong is that you should not add the whole message at once in your custom bg_BG.csv file. If you check the Cookie message itself is split in two parts:
1st:
We use cookies to make your experience better.
2nd:
To comply with the new e-Privacy directive, we need to ask for your consent to set the cookies.
You have to translate both the messages separately. After that deploy static content and clean cache.
I am new to Oracle UCM(already hate it) and I have this bug on the standart "Content information" page when displaying "Folder" meta - instead of DCOLLECTIONNAME I get DCOLLECTIONID from COLLECTIONS table. Now we have two versions of UCM installed on different servers, one with our custom module and one without it, you can guess which one works fine :-) I checked settings in admin aplet / Configuration manager and they are the same on both servers, so my next thought was there must be some problem with page template(I found some function named getCollectionPathFromID somewhere which does exactly what I need but dont know where to put it to make it work). Can anyone point me to the right direction? I found some template called std_page.htm but it contains realy huge amount of code... Any help would be appreciated.
What specific versions of WebCenter Content are you using? Are the two instances on the exact same version? You can find this information on the Configuration for instance name page.
How are you trying to view the data?
Are you calling &IsSoap=1 or &IsJava=1? Or are you meaning the display of the folder name/path on the page is showing dCollectionID?
I assume that based on dCollectionID you are using the Folders_g (Contribution Folders) component and not FrameworkFolders.
Can you provide a link to download your custom component? It sounds like this may be the culprate.
I am trying to figure out why the tinyMCE WYSIWYG editor in the CMS module of Magento will not upload images. I can create/delete folders but any file will simply not get uploaded, and there seems to be no message as to why the file is not successfully written on the server.
Anyone may have an idea why?
** Update **
I'm using Magento 1.6.2. I have tried to track down the problem and it seems that the controller never gets executed. I have added a line to log the arguments in the uploadAction() action (in Mage_Adminhtml_Cms_Wysiwyg_ImagesController) and nothing gets logged.
This is project inherited from someone else, and was modified to some extend, but nothing seems to point out that this part of Magento would have been touched in anyway by the modifications.
** EDIT**
The project associated with this question has been dropped and I no longer can provide an answer to this question. If anyone can confirm a working answer (as this problem was apparantly common with Magento), I will gladly mark that answer as "accepted".
Otherwise, I will flag this question for removal for the aformentioned reasons.
Thank you.
Other than solutions provided here, it may occur when you use a CDN (or a different domain) for your javascript and media files in admin panel. If you use CDN, use it for your website(s) scope and use your own domain for default scope. It will make your website(s) media and javascript files to be loaded from CDN, and backend's media and javascript files to be loaded from your own domain. This will solve your problem.
There are some known issues with flash image uploader on Magento. Unfortunately when it falls, it falls silently. Here are some cases when smth can break it:
if you try to use it with secured connection using open ssl certificate
if you're using it on server with apache authentication
on some Magento versions with prototype 1.7
I think the latter is your best bet. Maybe you should try to apply the patch from here: http://www.magentocommerce.com/boards/viewthread/4348/P45/#t327010
In my case it was a cross domain problem, and one quite hard to find if you ask me...
What was puzzling me was that the uploader for product images was working like a charm but the one in the CMS section was failing completely silently. We are serving the skin folder from an Amazon S3 bucket, and the flash uploader lives under that folder.
Interestingly enough, our version of Magento (1.7.0.2) is using two different methods to calculate the path to the SWF file, depending whether you are under CMS or Product update.
The CMS file (app/design/adminhtml/default/default/template/cms/browser/content/uploader.phtml) is using the following method to embed the Flash Uploader:
<?php echo $this->getSkinUrl('media/uploader.swf') ?>
While the Product image uploader is using:
<?php echo $this->getUploaderUrl('media/uploader.swf') ?>
In our case, the first one resolves to the AWS S3 url, obviously in a separate domain, while the second one will still reference the local domain's url.
So yeah, the quick, dirty fix would be to replace getSkinUrl for getUploaderUrl in app/design/adminhtml/default/default/template/cms/browser/content/uploader.phtml. Alternatively you can extend the core to load a different template in which you would have replaced that method.
I hope this helps somebody... I wish I had found something like this five days ago when I first stumbled upon the issue :-)
Are you using flash uploader with https? If so, is your secure address in differente domain (usually used in shareds ssl)?
I got some trouble with this. I solved by installing a flash uploader disabler plugin.
You can download the plugin with this downloader key:
http://connect20.magentocommerce.com/community/Dull_Uploader
I hope it helps.
On a Magento 1.11.1 site (Pro).
When I go to the URL [site]/customer/account/create I should get the form for creating a customer from the file /frontend/base/default/template/persistent/customer/form/register.phtml in block Mage_Customer_Block_Form_Register. Instead there is no such block included (show hints and show blocks enabled).
The customer login form works [site]/customer/account/login by displaying the form from file /frontend/base/default/template/persistent/customer/form/login.phtml in block Mage_Customer_Block_Form_Login. This works fine.
I'm using basically the modern theme with modifications (in a separate directory).
Also, customers are still able to create an account via the checkout process.
Is there an configuration parameter that might be set that could disable the standalone 'create customer account' functionality?
Could I have some issue with the templating that is getting in the way of displaying this register block?
So far I have not found the program logic that controls whether the register block is included or removed or anything? I've checked on file permissions and everything else I could think of, but there is obviously something I am overlooking or not aware of.
Any pointers on discovering the source of the problem would be appreciated.
this is probably really easy, but here goes:
My changes to the magento email templates don't show in the emails.
What am I doing wrong? Do I need to reinstall magento to get the updates? Am I simply editing the wrong files?
Thanks...
UPDATE: So now:
I have a fresh magento install
I haven't touched the Transactional Emails admin
I don't have locale set to 'en_US' (but since 1.4 that shouldn't be a problem right? Anyway, I tried setting the locale but it didn't help)
I ERASED the entire app/locale/en_US/template/email/ catalog
With this setup I completed an order and I still get the default email.
The only thing I can think of is I'm coming at this from the wrong direction, but I can't for the life of me figure it out.
Is it possible that your email templates are already saved into the database, and that your changes of the files are therefore not editing the correct version of the templates? Take a look at System -> Transactional Emails to see any templates that have been "promoted" to the database.
Hope that helps!
Thanks,
Joe
Make sure you have the proper locale selected within the admin if you are using the Transactional Emails to create new templates. Also you can also edit the files directly via
/app/locale/[language]-[country]/template/email/