[Trigunflame]

Originally Posted by Andreas

Interesting
I wrote a little windows application to prepare a "slipstreamed" vBulletin with all Plugins included back in beta stage.

Worked very well, though you loose the flexibility of the Plugin system:
You can't easily enable/disable Plugins/Products through ACP anymore, as this requires reprocessing the files.
And having them +w might not be a too good option, especially in shared environments.

Well this is the thing, you Will be able to easily "enable/disable" the plugins and products from the ACP; this system will not hinder the use of that, I will keep a cache of the hook_name => file pairs, by good use of power of preg via comments I can control where code is placed in the vbulletin files and be able to add and remove plugin code easily (Only) on the needed files, no need to scan the files again for every plugin code change.

As for the chmod options, there is a truth to that; but I can probably write a suitable php implementation that can control the chmod options to a degree when files need to be wrote, then set back to 755.. ofcourse this will defer depending on the system; in the end people can always chmod their files to 777 when they want to make a change, then back to 755 when they finish.