Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Custom Tab for New Content Wizard #143

Open
sassenbach-digital opened this issue Oct 30, 2018 · 6 comments
Open

Feature Request: Custom Tab for New Content Wizard #143

sassenbach-digital opened this issue Oct 30, 2018 · 6 comments

Comments

@sassenbach-digital
Copy link

sassenbach-digital commented Oct 30, 2018

First of all: Thank you for your work and for this awesome extension!

It would be great to be able to decide on which tab to place the new elements in the New Content Wizard. Usually I don't want my custom elements to be mixed in with the standard ones.

Something like an optional input field during export, "Custom Tab Title".
I know I can overwrite the NewContentElementWizard.ts, but I'd like to avoid messing with the exported extension.

https://app.leanboard.io/board/140a0fbe-9fd0-431a-b74e-a45cc516ee92
LeanBoard

@IchHabRecht
Copy link
Owner

Hi @sassenbach-digital,

Thank you for your request. To keep the mask_export extension small and usable, I will not implement such an option to the export. To not touch the export, I recommend to add your own configuration to an sitepackage. You might find some useful information in my example sitepacke for mask exports at https://github.com/IchHabRecht/my_maskexport_sitepackage

@sassenbach-digital
Copy link
Author

Ok, I understand that. But how would you override the New Content Wizard once the elements have already been added by the exported extension?

@IchHabRecht
Copy link
Owner

I will add some pageTS to the sitepackage example once I have time. Basically you can use removeFromList() to remove the export content elements from common tab and add those elements to your own tab instead.

@sassenbach-digital
Copy link
Author

Great, thanks!

@IchHabRecht
Copy link
Owner

Hi @sassenbach-digital,

Attached you find a pageTS configuration file to remove exported content elements (here from the test export) from the common tab and re-add the fields to an own tab. This is basically some copy & past work to do. Do you think it would be better to prevent the pageTS from the export being included by default? This would mean in your case, you don't have to remove it from any tab but just copy & paste the file from export to your sitepackage and change the tab name.

NewContentElementWizard.txt

@sassenbach-digital
Copy link
Author

That would make it easier for me, but it would make mask_export harder to use out of the box without some custom configuration.
I think the best way is to keep the pageTS as it is, but add a comment and link to your copy & paste solution. And maybe introduce a default extra tab like 'mask_export elements', so new users are prompted to adapt it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants