J-BusinessDirectory - JBD 5.5.0 Beta "Improved import mechanism" for different langauges?
Support Forum
Hi the new great JBD 5.5.0 Beta have arrived with some great import mechanism its says:
"It has never been easier to import a high number of business listings. The new import mechanism will allow importing a high number of listings with one click without the need of splitting the big files into smaller parts."
I wonder how you import for JED with more langauges than one std language ie english?
How do you make an import file for different languas with one click where you have the english language file and a second language file translated and syncronized?
How do you do that?
The doc didnt say much about this.. the one import file have 3 columns with type 1,2,3 (4) and it would be good to have some explanations how to do this...
| category | subcategories | type |
Import business listings from CSV
By importing a default list of businesses via an import tool (admin control panel/business listings/import from CSV). The import mechanism and how to format the CSV file is presented in the following chapters. https://cmsjunkie.com/docs/jbusinessdirectory/pupolatingbusinessdir.html#import-business-listings-from-csv
Hi,
For categories, it is not possible at the moment to import the content in multiple languages.
For business listings, the user manual link is https://cmsjunkie.com/docs/jbusinessdirectory/businessdiradmin.html#id9
You can import the content in multiple languages for name, slogan, short description, description, meta description.
E.g. name_en-GB,name_es-ES
The easiest way is to export a CSV file and then import it back with all the details.
Thks for update.
For categories, it is not possible at the moment to import the content in multiple languages.
Would it be possible to improve this if you have rows for different langauges synced that could be imported in one file? can you do this by sql and do you have any tutorial about this if you can make that work?
Hi,
It is complicated to do this manually.
We will offer support for this in the next version.