You probably know this already, but that system setting would be inside the asset manager namespace, not part of the core, so to find/change it you would need to select that namespace in the system setting interface.
You're free to create any new System Settings you need. Just use assman.skip_templates as the key. I'm not sure about the value, but I'd guess it's a comma-separated list of Template IDs (no spaces).
OK got it. Thank you for the usefull info guys.
peace&love / bike&ride
Update:
I tried without success. I made new setting under System Settings and comma separated list of Templates to be excluded but nothing happens.
There is also the following issue:
When I go to Extras -> Asset Manager it leads to nothing but a page with wrong styled screen.
There are no Error Logs. I'm using MODx version 2.4.2-pl and Asset manager 1.1.1
You can see the settings that I made and the error screen in the attached files.
peace&love / bike&ride
Did you look in the 'assman' namespace (or whatever its namespace is called) for an existing assman.skip_templates System Setting? If there's one there, it might override the one you created.
It's possible. See if that skip_templates code is in the plugin you have.
Another thing to try is to put this tag on any page and see what it produces:
[[++assman.skip_templates]]
It should show 1,2,3 (or whatever you put in the System Setting).
I give this also a try but no results.
Finally I wrote an email to the guy which is developing the extra and he told me that there is absolutely a difference between the Github version of *any* repository and what is released by a 3rd party.
In this case I'll need to install the extra from github.
There is an extra called Repoman which is from the same developer and you can develop, transport packages or contribute to existing MODx projects and I think it can be used also to install and use Github releases. So I'm going to test it and see what can be done.
Will post if there are any updates.
peace&love / bike&ride
People often push changes to GitHub before releasing a new package. In my case, I generally push them to the dev branch and leave the master branch at the last stable version, but everyone does things their own way.
If you look
here, you can see that Version 1.1.1 was released in 2014 and there have been a number of commits since then. The option to skip templates wasn't added until June of 2015.