9
this is ok for you. but labelling it as 2.0.13.2 is misleading as it no longer is 2.0.13.2 and can't be supported as such.
users will inevitably install it, and when they have problems they are likely to come here for support. we're gonna ask them what version they use and they're gonna say 2.0.13.2, we're gonna see debug messages or error messages on lines pointing to things that may not be 2.0.13.2 related and this will hinder giving correct support for it.
i'm not familiar with half of those hacks.
with the exception of autologin.
profiles hack v2 and auto image resize because i wrote those hacks.
the best people to ask for help when a hack goes wrong is the person who wrote the hack, he/she may have an updated version or fix. now if i release an updated version of profiles hack that may fix a few bugs (and there is a couple i know of) the users who installed this hack will not know that they need it. they also will not know exactly how to implement the fix because the files line numbers and such will probably be different aswell.
when XOOPS 2.0.13.3 or 2.0.14 or whatever comes out, users will also not know or be aware and may inevitably upgrade to the newer version inevitably overwriting the hacks and then totally breaking their site. where are they gonna go for support to fix it? who will they lay the blame on? xoops.org of course.
in essence you are going to have to support this on your own, users will have to wait for you to do the updates. and you most probably will have to wait for those who wrote the hacks (in some instances to update their hacks), we don't know what hacks you will have installed and we definitely wouldn't know, the only answer possible would be to say do the update and then re apply the hacks. or don't upgrade till the hacks are updated or till you have sorted it.
this is only a few of the problems that will arise from this hacked version, and as such it would be unwise to use xoops.org as a support place for it, as it is essentially a fork version.
don't get me wrong, i know your intentions are good but i don't think you thought this out well enough.
hacks are hacks for that very reason, the reason that once you hack your site, official support is out because a dev only likes to support a code that is their liability, most will help if you have installed hacks, but they would need to know beforehand. it's same as a warranty, once you break the seal, the warranty is void. only an unhacked core can be fully guaranteed officially.
