Ok .. I have read all your comments so I can follow say to that;
1. TP vs PortaMx
I have take a look on the install package of TP1.05 .. and I see it's the same as in PortaMx.
The one difference is that TP uses "boardmod" styled and PortaMx XML styled modfiles.
If that the Problem? I think no .. but if it, then is that a problem of SMF.
And .. have anybody TP installed on a SMF 2 system? Works TP's install with the packedmanger of SMF 2?
2. Coding techniques
The code of TP is never that, what I would give out of my office. That provoke errors .. and when I read on TP site, I see that.
Hundred of $_GET, hundred of "if" .. "else" .. no secure checking for $_GET's .. That is a invitation for attacks.
A good code MUST be absolutly clear structured and protected for attacks.
SMF go the right way on this, with the new database functions and mutch more. PortaMx follow these codestructure.
Also SMF implemented a caching technique for languages and more to make the system faster. TP make many queries on the database without I see one block. PortaMx take normaly 2 queries for all the setting and blocks. Of course we need often more queries .. but that is depended on the blocktype. And static blocks like Themes, Download and other have a cache, so it's not need to create the content on each page call.
3. The upgrade cycle
The upgrade cycle is crrently very short .. but that is a temporary.
We stay on a time, who more user test the portal and of course find more bugs.
I think on a better upgrade system ...
4. Categorie/Articles and Download manager
We start the implementation of this parts (first Cat/Article, then the DL-Manager), but I can't say when it's done.
While PortaMx have no Download manager, you can use the Download mod from SMF mod site, it works with PortaMx.