KB Nested Content Elements

Copyright © by Bernhard Kraft <kraftb@no spam pleasethink-open.at>
Published under the Open Content License available from http://www.opencontent.org/opl.shtml

Table Of Contents

• 1. EXT: KB Nested Content Elements
  • 1.1. Introduction
    • What does it do?
    • Screenshots
  • 1.2. Users manual
    • Copy & Paste
    • Variable column templates
  • 1.3. Adminstration
  • 1.4. Configuration
    • Creating container templates
    • Setting up the Container Folder
    • Including the static template
    • Import and Export of nescefe elements
    • When you are making exports or imports of pages with kb_nescefe elements, or if you are exporting/importing kb_nescefe elements on their own you have to consider some special circumstances.
    • First of all you should notice that template records can usually only exist on sysfolder pages. So if you are making an export of some branch of your website the sysfolder with the kb_nescefe template records will usually not be part of the export. The export module allows you to make an export with a static reference to the kb_nescefe template records. If the kb_nescefe templates have the same UIDs on the source and target system this is the best choice. You can achieve this behaviour by marking the table “kb_nescefe_containers” in the export mask to “Use static relations” (Tab “Configuration”).
    • If you want to transfer the kb_nescefe template records to the target system along with the exported records you should not mark the table for “Use static relations”. Instead have a look at the bottom of your structure going to be exported. There you should see an area labeled “Outside pagetree”. In this section you will see all records going to be exported which are not in the current branch of your tree but referenced from within the exported records. Just make sure the “Exclude” checkbox is not set. In the case you are making an export with the template records included you'll have to verify that the extension option”Templates on normal pages” is set via the Extension Manager. This allows kb_nescefe template records to exist on normal pages. Else they would not get imported on the target system as they will get relocated to the root-page of the exported branch which is most probably not a sys-folder.
    • Read online
    • Read online
    • The last option you have for taking care of template records is to manually define which template record will get used for each kb_nescefe element on the target system. You can enforce this by checking the “Exclude” checkbox for each template record and set the Drop-Down of each container field of kb_nescefe elements to “Editable” like seen in the screenshot above. On the target system you will get an input field for each kb_nescefe element. Fill in the UID of the template record which should get used for this container.
    • Update from previous versions
  • 1.5. Intention
  • 1.6. Sponsoring
  • 1.7. Changelog

This document is related to version 1.1.1 of the extension kb_nescefe.