Resolved replacement rule for export category_link node

Glad to know that your issues are solved. It would be great if you can give us a review on Joomla extension directory

Good news! Recent changes in work! It turned out that the new restore template will not replace the old and creating the new. I'm Sorry!!! :blush: I have not seen immediately. :woohoo: :blink: Thank you! Good work! :silly:

Hello,
The problem should not be with your category_link field but i guess with product_url, apply the new rule i created 'character replace' to this field too and try doing the export.

XML don't support & directly as it is a reserved character and this is the reason it has to be enclosed with CDATA, may i know why you are avoiding CDATA tags?

No changes. There is a problem.

Hello,
Can you restore the attached modified template and see if it works? I have added a new replace rule to custom field with category_link. You can restore template from CSVI Pro maintenance menu, select CSVI Pro on first option, restore template on second option. Try and let me know.



csvi_templates_20161021_modified.xml

Yes of course

Hello,
The link says that your file still has issue. Can you send me your export template XML to check? You can backup your template from CSVI maintenance menu, select CSVI Pro on first option, Backup templates on the second option, select your export template and click continue. Post the downloaded XML file.

Yes, the special character

&

after saving replaced by &.

Hello,
Ok, But did you try generating XML file and you still see issue? The special character & is encoded and saved in default value text field so you should not be seeing the issue.

Thank you. But "&" not saved in the default value...

Hello,
Seems like you have edited your previous post and we did not get any notification on the new message. Please post a new message instead of editing the old one so we know that there is a new message.

Regarding the issue in your XML file, the problem is with & in category_link in your XML file. It has to be encoded in XML file. So in your template fields where you have set default value of category_link, change & to

&

and export the XML file again. That should solve your issue.

Hi. Are there any solutions? The problem is still actual. :unsure:

link

Hello,
This don't seem to be a problem with CDATA tag, must be something else. Can you post the XML file to check?

The CDATA tag cannot break an XML because it is part of the XML definition. What can be the case is that the target system is incapable of handling CDATA tags.

OK. I choose to Use CDATA tag - Yes, and I see: screen 1
i choose to Use CDATA tag - No, and I see : screen 2

Hello,

The first does not work in field custom to disable the file CDATA tag - immediately breaks the XML file

The CDATA tag cannot break an XML because it is part of the XML definition. What can be the case is that the target system is incapable of handling CDATA tags.

The second problem in the field category_link does not work SEF URL. Such a file directory will not accept.

CSVI can't turn it into a SEF URL because there is no code to create that SEF URL. What is wrong with a regular URL?

If it has to be SEF, the only thing I can think of is to create a second rule that replaces the non-SEF URL with a SEF URL. Where you find the regular URL and replace it with the SEF URL. That will be quite a few rules I guess, depending on how many categories you have.

:woohoo: Thank you so much! It really helps! But two problems remained. The first does not work in field custom to disable the file CDATA tag - immediately breaks the XML file . The second problem in the field category_link does not work SEF URL. Such a file directory will not accept. :dry:

Hello,

One question: how do I can do in the xml file export link to the product category.

I have built you a template you can use as an example. This template exports the product SKU and the category link using a combine rule.

Go to the Maintenance page in CSVI and choose CSVI Pro -> Restore template. Select the attached template to be restored. This will add a new template to your system called laconcorde.

Check the fields for this template, there are 3 fields of which 1 is unpublished. It is unpublished because you don't want to export the ID but just use it as part of the category link. There will also be a combine rule that puts the custom field and the ID together to create the full link.

Of course you will need to change the hostname to match yours unless you own example.com

Let me know how it goes.

The category_link value index.php?option=com_virtuemart&view=category&virtuemart_category_id= should be got from somewhere so you can combine this with virtuemart_category_id and have it exported.

Hey. it's great, but in the field name csvi no have field virtuemart_category_id field name csvi, I see only virtuemart_product_id and virtuemart_vendor_id. IWhat i can use?

then you can create a combine rule with your new field and virtuemart_category_id and have it exported.

here a link to an article on "The combine plugin lets you combine multiple fields into a single field during import." but I need export.

One question: how do I can do in the xml file export link to the product category. I asked about this in a letter prior to purchase. the response was positive. I need a step by step guide.

Hello,
My apologies, mistake is mine as in my previous post the solution i gave was all thinking it was for import. Default value is used only for import and dont work for export. The category_link value index.php?option=com_virtuemart&view=category&virtuemart_category_id= should be got from somewhere so you can combine this with virtuemart_category_id and have it exported. One way is you can have a field created in your categories table and have the default value stored in the field, then you can create a combine rule with your new field and virtuemart_category_id and have it exported.

One other way is you can create your own custom available field for category_link and write your own override file and add some code to get the category_link field created and exported with other fields. The custom available field feature is coming with a new structure in our next release but the patch and explanation of using it is explained in the thread here.