Resolved category_path combined question

Hello Jimmy,

Glad to hear all is finally solved. You are fast becoming a CSVI Expert

Perhaps you can help me out and post a review at the Joomla! Extension Directory

Hi Roland,

Cant thankyou enough, such fast and efficient support, it puts others to absolute shame!!!

Many thanks again Roland!!! Legend!!!

Hey Jimmy,

Before applying the patch I linked, did you also apply the patch posted in the thread at the top of the page? This is the main patch, the second one is a fix to that. Give that a try.

Hi Roland,

Once again many thanks, I applied the patch but it hasn't made any difference with regards to trying to setup the import as an menu item, still the same problem im afraid.

Thanks again for your help Roland, hoping its a quick one for you as im desperate to finish this project, thanks!!!!!

Hey Jimmy,

Front-end import is not part of the current release, this will come in the next release version 6.6.0. You can find the patch for front-end import in this thread.

Hi Roland,

At last, I got it perfect many many thanks for your help!

BUT I have an issue when adding this to the menu to run on the frontend, unfortunetly it only shows me export templates in the 'Select template' dropdown although i have selected 'COM_CSVI_IMPORT_FRONTEND' on the menu type dropdown, also the language is missing for import but not export (and only the export templates show no matter if import or export menu types are selected).

Ive completed this job if I can add this menu item, so im very keenly awaiting your help.

Many thanks in advance!!!!

Hello,

What you are doing wrong is not specifying all the fields in your import file. You now have only 4 fields defined in your import template. Basically what you are saying is that the import file only has 4 fields. That is not the case is it? How would CSVI know which columns to pull in? You added 4 fields, so CSVI pulls in the first 4 columns.

You must add all the columns in your import file. The ones you don't want to import you choose the fields skip so that CSVI will skip them.

Hi Roland,

Thanks again for your reply/help!

Ive checked the fields and removed all the rules, its not random now and is importing the first 4 columns.
Im attempting to use the same import file for k2 items and k2 category params (as I believe, you said previously I could).

Basically for the 4 fields required 3 of them will have the same data for all categories therefore I was hoping i could use default values in the field settings and only the category_path will change, which will be made up of properties/[the-id-taken-from-import-file] the other fields.

K2 Category import category_path properties/[id-of-field-from-import]
K2 Category import inheritFrom Properties
K2 Category import theme properties
K2 Category import extraFieldsGroup 1

But yes currently the import just pulls the first 4 columns ignoring the default values set for 3 fields.

And the rule seems to be ignored or doesn't make sense to me for the category_path

Your help would be once again very much appreciated, many thanks in advance!!!

Hello Jimmy,

I can tell you for sure that CSVI isn't randomizing the data by itself, it simply shows how you configured the template.

Check the fields you have assigned to your template if they are in the same order as the fields are in your import file.

If needed start removing all the assigned rules to the fields of your import template. Look at what you have and assign rules as you need them.

Hi Roland,

Thanks again for your reply/help!

Good news the category_path is now appearing on the preview although all the preview data makes absolutely no sense to me at all (it has all changed and replaced with random data from the import file), ive been trying to work out some relation between the data and setting/import file, but cant, as i say, it all seems random?

Sorry about this, your help would (as usual) very much appreciated and thanks again!

Jimmy,

The problem is you had set your template to Use file for configuration instead of using the fields you assigned to the template. I changed that, you can check the preview now.

Hi Roland,

Whatever I try I cannot get the category_path column to show on the preview.

Its difficult to set it up the same as different fields are available I tried with the combine but no joy im afraid, heres what I got:

TEMPLATE FIELDS:
Field name: category_path
Rules: category_path-category-import

Field name: combine
Your field: categorypath_Properties
Default value: Properties
Rules: category_path-category-import

Field name: combine
Your field: Properties_PropertyID (this is the name of the column containing the ID in the import file)
Rules: category_path-category-import

RULES:
Name: category_path-category-import
Action: import
Plugin: combine
Source fields: categorypath_Properties,Properties_PropertyID
Target field: category_path
Combine character: /

To clarify the category_path needs to be:
Property/[Properties_PropertyID]

(Property/ will be the same for all items imported)

Please tell me what im doing wrong, call me an idiot if you want lol
Thanks again!

Hey Jimmy,

Have you configured the id_field the same for the category import as it is configured for the product import? If it is your own type of field you can use the combine field. In your rule you would use this field to combine the category path.

Hi, Thanks again for your reply, sorry if im confusing!

Ok so for the item import; the category_path is made up from a field on the import file 'id_field' with the import this field is copied (rule) and a root directory and slash added 'example_dir/' (rule) before being placed in category_path field.

Can the same thing be done with the category import? If so how as my id_field does not appear in the list (like it does for the item import).

Hope thats makes sense, sorry!

Hello,

I am not sure I understand the question so I am going to guess. The field category_path is the same for both the product and category import.

Can you give me a clearer example of the problem you see?

Hi, Im back on this task again and getting there. Thanks again for your help, great support!

So ive made the export, and have created the import template, im just preparing the import file (im using 1 import file for both the k2 item and categories as you advised), just 1 question please...

The category_path currently (on my item import) this is made up from a 1 field (not named category_path) the import copys it to category_path and adds a rule which places a_root_folder/ (a folder and a slash) at the begining. Ideally id like to keep it like this for the category import, but just looking at the category import available fields, im not sure its possible to use the other fields on my import file although i spotted custom field?

(I really want to avoid having to ask my client to enter data for this column also, i need to keep the process as simple as possible)

Once again your help is very much appreciated, thanks again!

Jimmy,

I think UNFORTUNETLY it will be easier to have my client add the category and set the parameters manually in the admin (which they will not be happy about!).

You simply can't update your complete website with 1 import. You can of course put all the fields into 1 file and use this 1 file for both imports.

Your logic is the wrong way around. First you run the category import (if you have any new categories) and then you run the item import.

Just the templates you configure you will need to add all the fields and set the ones you don't want to use to skip.
Your customer, will have to enter the category details somewhere.

I think UNFORTUNETLY it will be easier to have my client add the category and set the parameters manually in the admin (which they will not be happy about!).

As your method will mean, running the item import (which creates the new category) then running the k2 category params import, and then running the item import again (which will populate the extra fields etc) right?

This 100% cant be done on the same import? As all the parameters will remain the same for all subcategories added and will be the same as the parent category.

Once again many thanks!

Hello,

Hi Thanks again, trying this but getting confused again, im getting to the 'Select fields' section of the export, i select Group fields I can see inheritFrom but there seems only a facility to add this fields, I see nowhere to add settings inherit from theme etc.

Check the K2 category params export and K2 category params import tutorial to know how to do import and export process.

Also can I ask my client will be adding new categories via the main import file, will this process be necessary everytime new categories are added.

Yes because these are category settings and cannot be edited or updated while doing item import. You need to do it with category import only.

Hi Thanks again, trying this but getting confused again, im getting to the 'Select fields' section of the export, i select Group fields I can see inheritFrom but there seems only a facility to add this fields, I see nowhere to add settings inherit from theme etc.

Also can I ask my client will be adding new categories via the main import file, will this process be necessary everytime new categories are added.

Once again your help is much appreciated, many thanks!