I stumbled across some stuff using CMSimport today that I think would be nice to have fixed if it's possible and not way too much work.
Last thing first...when the import is done could you remove the prev/next buttons? I caught myself clicking "next" instead of doing a refresh in the content tree :) (And I think that regular editors will be a bit confused about the buttons still being there when the imort is done).
When the source that should be imported to have been chosen would it be possible to limit the dropdownlist of document types that the content could be mapped to? So instead of listing all document types available it would only list those that are allowed to be created undr the root node where the imported nodes will be created?
I've said it before and I'm saying it again - I love this package! :)
Great comments thanks. Reagarding teh prev next buttons is the next button enabled? I will remove it for a next version. Previous will exists because you can go back modify a setting and import again. You mention editors? Did you already checkout the Import DashBoard. This is new in V2.1 and allows you as a developer to define an import definition and editors can select the import definition and upload a file and just hit import (it's on page 32 of the documentation). Think you like that :)
Your other point is also interesting but I know some users are using cmsimport to import data into folders where the user isn't allowed to add documents. I need to think about this one since it makes sense maybe some sort of advanced setting to overrule the default behaviour.
The next button is clickable, but nothing happens when clicking it. You're of course right about the prev button :)
Nope, must admit that I have not had a thourough look at the documentation - must read it in greater detail and thanks for the hint.
Ah yes...good point. Maybe it makes sense to be able to add data even though one can't create the document type. But would be nice to limit access somehow so that it's not all nodes that are available.
UI enhancements
Hi Richard
I stumbled across some stuff using CMSimport today that I think would be nice to have fixed if it's possible and not way too much work.
Last thing first...when the import is done could you remove the prev/next buttons? I caught myself clicking "next" instead of doing a refresh in the content tree :) (And I think that regular editors will be a bit confused about the buttons still being there when the imort is done).
When the source that should be imported to have been chosen would it be possible to limit the dropdownlist of document types that the content could be mapped to? So instead of listing all document types available it would only list those that are allowed to be created undr the root node where the imported nodes will be created?
I've said it before and I'm saying it again - I love this package! :)
/Jan
Hi Jan,
Great comments thanks. Reagarding teh prev next buttons is the next button enabled? I will remove it for a next version. Previous will exists because you can go back modify a setting and import again. You mention editors? Did you already checkout the Import DashBoard. This is new in V2.1 and allows you as a developer to define an import definition and editors can select the import definition and upload a file and just hit import (it's on page 32 of the documentation). Think you like that :)
Your other point is also interesting but I know some users are using cmsimport to import data into folders where the user isn't allowed to add documents. I need to think about this one since it makes sense maybe some sort of advanced setting to overrule the default behaviour.
Thanks,
Richard
Hi Richard
Sorry for my late reply on this one.
The next button is clickable, but nothing happens when clicking it. You're of course right about the prev button :)
Nope, must admit that I have not had a thourough look at the documentation - must read it in greater detail and thanks for the hint.
Ah yes...good point. Maybe it makes sense to be able to add data even though one can't create the document type. But would be nice to limit access somehow so that it's not all nodes that are available.
/Jan
is working on a reply...