117
think thats the way its supposed to work.
my thoughts on that are:
admins usually 'approve' news articles submitted to the site by regular users, and they would be the ones to activate the extended text.
Due to the 'methodology' used for programming that scenario, the edit functions and all else fit into the same category.
Nowadays it seems that MANY of the people using XOOPS are creating 'seudo admins' that are contributing to the sites in many ways and administering select functions within it (the ideal web community), however, these people are not always known well enough to be trusted with complete control of the module or the site.
Hopefully future development of the core and the new module structure that goes with it will allow for selective admin privelidges on all of the forms used in the module (we're seeing that with the new customizable user registration form).
So it seems only logical...to me any way...that the next progression of that will be to be able to assign access to specific areas of the modules admin functions. (Imagine each module having group perms and settings like the XOOPS core does, so each new module you install can be customized almost as much to the full extent of the XOOPS core, without affecting the core)
Anyway, the best part about it is that the code for the XOOPS cms is pretty straight forward and workarounds can be done without too much aggravation!