I have task to export Activities including 'Descriptions' filed which contains HTML of the stored email treads. I have to export this field/column as parsed text (not HTML codes, only a real content of the mails).
Actually, when Activities listing is displayed in web, Descriptions column displays exactly what I need, but when I export it to excel, this columns displays HTML codes (and is limited to 1044 chars, so there is no any real body content).
Please, give some advice or link where I can learn how to export this field as it looks in web.
Thanks.
Unfortunately, plain text email body is not stored automatically by OOB CRM. All you have is Rich text stored description field.
There are multiple different solutions to strip the HTML tags & store the plain text in a different field viz code solution, no-code configuration solution using third party like North52, etc.
If you have developers in your team, then C# Plugin would be the best bet to strip & store on creation of Email record itself.
Would a Report Wizard report work to give you the results you need?
Also, Arun's answer was marked as correct (as it should be...) My only advice would be to store the email body without the HTML tags in a different field. I've found that stripped HTML tags can do funny things to formatting.
I have Magento 1.8.1.0. Recently I've installed Russian pack, the result wasn't appropriate enough, cause some phrases on frontend remained in English
I know there's handy way to translate Magento using cvs-files.
The question is where I can find proper cvs-file? Does installed theme concerns translation some how? I know I'm asking newbie questions, I've read several posts, but I haven't made up my mind how to translate Magento.
Many thanks in advance.
Hope you are doing well,
As i have gone through your question that you want to translate your websites front end in Russian if user has selected the language Russian.
For this you are required to work out the translate.csv files which will be available in your theme Package.
Example : app/design/frontend/default/SecuareWeb/locale/de_DE
In the locale folder you will find the folder for Russian language open that folder and you will find the file where you are required to add the required translation text in it.
How to add translation text in translate.csv file is given below.
Example:
"This is the demo of translation in Russian","Это демо-трансляции на русском языке"
And one thing i would like add is that make sure your front end .phtml files must contain the text in $this->__("Example");. If you have added all the text like this then only then it will allow you for translation other wise it will not translate a text.
Hope this might be use full to you !!!
Waiting for your valuable comments in regards to your Question !!!
There are different ways to achieve translation in Magento so you can find multiple directory containing static csv files and also a database table.
All the modes have same structure: key/value. For example: "String to translate","String translated".
Inline Translation (database table: core_translate):
following best practices in Magento, you should use inline-translation aka database saved translation in rare cases. It is harder to mantain and can be buggy. It has first precedence, so any translation you do via inline translation will override the other 'modes'.
Theme level Translation (file in app/design/frontend/your_package/your_theme/ru_RU/translate.csv):
you can place any string to be translated in the translate.csv. It has second precedence.
Locale translation (file in app/locale/ru_RU/Module_Name.csv):
the suggested way to do translation as it will keep translation separated by each module and is easier to maintain. For example: Mage_Catalog.csv etc.
Each module in Magento can specify its csv file containing translation and sometimes the same string has different modules trying to translate, so if your translation does not work check between multiple file by a quick editor search. It will be overridden by the two above modes.
Note:
Magento will load all the csv files and build up a giant tree and caches it. So before scratching your head because the string is not translated as you wished in the frontend:
1. clean the cache.
2. check for any same key string which comes after your translated string. For example: in the same csv Line 100 will override Line 1 if the key string are the same.
3. check for any same key string in the mode which has higher precedence. For example: inline translation will override any csv based translated string.
It may be easier for you to go to the admin backend System -> Configuration -> Developer and switch "Translate Inline" "Enabled for Frontend" to "Yes".
Then, refresh the frontend and you can change the translation directly at your web browser.
The translation is saved in the database table core_translate just for the case you want to do it in a test environment and copy the translation later on to the production.
Take care that without client restrictions (System -> Configuration -> Developer) everyone will see the translation options.
btw. You may need to clear the cache and refresh the webpage in order to see your changes.
We have been programming an application for the next two weeks to make a valid csv file to import to Magento.
But, we have a problem with importing in general, as we get the error that Magento can't find the required columns: sku. I've been looking through a lot of forums.
I have seen it could be the visibility but we have that in our csv. I will give you an example of how our csv looks like:
sku,name,ean,manufacturer,price,msrp,tax_class_id,qty,_category,is_in_stock,status,description,_type,visibility,_attribute_set,color,geluidssysteem,platform_consoles,protection,connection,kabel_lengte,lader,nintendo_platform,model,megapixels,geschikt_foto_video_tas,schermdiagonaal,size,keyboard_layout,geheugen,draagstijl_headset,materiaal,type_camera,type_toetsen,left_right_handed,vermogen,toetesenbord_verlicht,sensorkeuze,stroom_voorziening,connection_mouse,
MRM-01855,AA FUSION AUDIO 3.5mm to 3.5mm Jack kabel 1 meter wit,5060166512163,Advanced Accessories,3.18,,2,6,Nintendo/Nintendo bundels,1,1,Boomsjors,simple,4,PC kabels,Green,,,,Universal,1.8 Meter,,,,,,,,,,,,,,,120w,,,,,
We also had the problem that the description contains a comma and then messes up our csv.
If you need any more information, let me know!
Please make sure you are using the utf-8 encoded file format for your .csv file. This error occurs mostly with wrong formated file content.
To make it correct please open your .csv file in editor and go to 'Save As'-> Select File Type as 'MSDOS CSV(.csv)' and save.
Hope this will help...
I'm trying to accomplish something that will let a user download a file from a web application onto their system. The file will contain a unique five digit code. Using this unique five digit code the users can search for a file in their file system.
I'm wondering where is the best place to put this five digit code in a file so that users can easily search for the file. The simplest approach would be to put it in the name of the file, however, users can change the name of the file easily.
I'm looking for a filed where I can put the code so that users won't be able to modify it but will still be able to search for it. Is this possible?
If you say File.. what kind of file format do you mean. I'm asking because a file is just a pile of bytes and you can append your 5 digit code every where in the file, if it is your own file format. But if you tell us which file format you use, probably there are some fields which can be used to search for it. As example Tiff has many tags. Images have other meta data. etc
I'm trying to localize my Core Data model in order to display better error messages. I followed the instructions on http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/CoreData/Articles/cdUsingMOM.html without success.
My model file is v8.xcdatamodel, so my strings file is v8Model.string. I want to have the property "name" displayed as "Name". So I added the line
"Property/name" = "Name";
to the strings file. But it just does nothing when an error message is displayed. Any ideas what I missed?
thanks,
Martin
Your strings file should be v8Model.strings, but maybe that's just a typo in your question. Notice also that .strings files must be saved in UTF-16 encoding, as documented here.
The .strings file should be saved in the appropriate localization folder, such as en.lproj.