Status of TDN
by Michael Perry · in Torque Developer Network · 01/28/2009 (2:31 pm) · 94 replies
For anyone who has tried accessing TDN over the past month, you may have run into login issues. We are quite aware of the problem, however solving the issue is proving more difficult than we anticipated.
* MediaWiki: 1.5.5
* PHP: 5.1.6 (apache2handler
* MySQL: 5.0.45-log
Compare that to the latest version of MediaWiki:
MediaWiki 1.15alpha (r46424)
PHP 5.2.4-2ubuntu5wm1 (apache2handler)
MySQL 4.0.40-wikimedia-log
TDN is outdated by 10 versions! This is a cause of concern because we are working with outdated functionality and outdated security measures. Late in 2008 TDN was compromised, which is why it was brought down temporarily. While the content was updated, the framework was neglected to the point where updating TDN to the latest version of MediaWiki is a major hurdle.
If you have access to TDN, but cannot get into the starter kit pages (Adventure Kit, Platformer Kit, and RTS Kit), we will be downloading and converting the pages to work within our Doc System framework. A new download link will be added to your account page to download the docs.
The big problem is with users who cannot log into TDN. This is because TDN is unable to create new accounts in the database. If you are given a link that goes to TDN, you can contact me or post in this thread. I will manually grab the doc and send it to you.
I am definitely going to work out a solution to start grabbing the best of the TDN docs and rolling them into our official sources. That's a hefty task, but when complete this may result in not needing TDN anymore. Again, we are still working out a plan of action.
I appreciate the patience everyone has shown. I'll try to do my best to help get this content into your hands.
Tech Information
TDN was created quite a while ago:* MediaWiki: 1.5.5
* PHP: 5.1.6 (apache2handler
* MySQL: 5.0.45-log
Compare that to the latest version of MediaWiki:
MediaWiki 1.15alpha (r46424)
PHP 5.2.4-2ubuntu5wm1 (apache2handler)
MySQL 4.0.40-wikimedia-log
TDN is outdated by 10 versions! This is a cause of concern because we are working with outdated functionality and outdated security measures. Late in 2008 TDN was compromised, which is why it was brought down temporarily. While the content was updated, the framework was neglected to the point where updating TDN to the latest version of MediaWiki is a major hurdle.
Short Term Solutions
For those of you who have access to all of TDN without any login problems, you are good to go.If you have access to TDN, but cannot get into the starter kit pages (Adventure Kit, Platformer Kit, and RTS Kit), we will be downloading and converting the pages to work within our Doc System framework. A new download link will be added to your account page to download the docs.
The big problem is with users who cannot log into TDN. This is because TDN is unable to create new accounts in the database. If you are given a link that goes to TDN, you can contact me or post in this thread. I will manually grab the doc and send it to you.
Long Term Plans
I am going to be dedicating more and more of my time to creating new content for our official docs. Spending time maintaining TDN tech and trying to fix old content will be a detriment to the official docs. We are weighing our options right now.I am definitely going to work out a solution to start grabbing the best of the TDN docs and rolling them into our official sources. That's a hefty task, but when complete this may result in not needing TDN anymore. Again, we are still working out a plan of action.
Using This Thread
This will be the place to post your need for specific tutorials. Also, whenever I have news about the status of TDN I will post it here. I'm locking down the other threads so we can start pushing more readers to this location. Feel free to send this link to anyone else who is experiencing TDN difficulties.I appreciate the patience everyone has shown. I'll try to do my best to help get this content into your hands.
About the author
Programmer.
#82
To put it short, besides any technical difficulties some users are having with TDN, I personally think it's downfall is lack of use. It's a great alternative way of getting 3rd party information out there. But that depends on the number of satisfied customers who are willing to follow through and learn from the support documentation that comes with the engine.
So I think creating and touching up on content already there is a great idea. But I would lean more towards official documentation.
08/29/2010 (7:32 am)
Ok, I'm sure this has been said before. But I think TDN's biggest problem is that it's information is submitted by the members of this site. And sadly it seems like less people submit content to help others or most people can't because they themselves are searching for the content. Some of the information on the network is unfinished too, making it hard to follow. I've noticed that the site has become mainly filled with dedicated fans who are busy on their own projects and don't have time to submit content. This leads to some people who are fresh customers getting stressed at the "lack" of support and leaving bad reviews to others.To put it short, besides any technical difficulties some users are having with TDN, I personally think it's downfall is lack of use. It's a great alternative way of getting 3rd party information out there. But that depends on the number of satisfied customers who are willing to follow through and learn from the support documentation that comes with the engine.
So I think creating and touching up on content already there is a great idea. But I would lean more towards official documentation.
#83
02/07/2011 (9:46 am)
@All - William Lee Sims discovered a bug over the weekend. Edits are not being saved when changing an existing article or creating a new one. I'm going to create a bug report out of this and post a link here. If you could take the time to confirm the steps to reproduce the bug, it will greatly help us in fixing it.
#84
Let me know if you can reproduce the issue.
02/07/2011 (10:00 am)
Please review this bug report: TDN edits not saving.Let me know if you can reproduce the issue.
#85
Also noticed that the various section edit links dotted through most TDN pages come up with no content when used, not sure if that's a new problem or something that's always happened. It seems to work fine on some pages (my profile page), partially on others and not at all on most that I've tried.
02/07/2011 (5:11 pm)
Reproduced here following the steps in the bug report - nothing useful to add unfortunately. Firefox 3.6 on the off chance it's relevant.Also noticed that the various section edit links dotted through most TDN pages come up with no content when used, not sure if that's a new problem or something that's always happened. It seems to work fine on some pages (my profile page), partially on others and not at all on most that I've tried.
#86
02/08/2011 (3:39 pm)
Seems fixed now, or at least i can edit it ok on IE8 win7-64, thanks guys! 
#87
I also added two templates which are merely renamed TGB templates, as that section seems to have received special attention.
{{Template:HubCategory | title}} creates a bolded section header meant for use inside the hub templates. Could be used in place of the horrible HTML mess that is used in most places, and BehaviorCategory etc. as used in the TGB section. Pure visual, no links.
{{Template:T3DTutorial | title | description}} creates a link to a tutorial page in the T3D/Tutorials/ namespace. Use this before starting on one and click the resulting link to create the tutorial in the right place. The benefit of keeping things under a namespace is that if the engine changes name (again!) the subpages move along with it, and redirects point to the right place.
02/13/2011 (3:51 am)
There's a T3D section now. Use {{Category:T3D}} at the bottom of any pages you create to sort them under that tag. Link your pages from the landing page, and try to use subpages/namespaces. Tutorials go in T3D/Tutorials/, for example.I also added two templates which are merely renamed TGB templates, as that section seems to have received special attention.
{{Template:HubCategory | title}} creates a bolded section header meant for use inside the hub templates. Could be used in place of the horrible HTML mess that is used in most places, and BehaviorCategory etc. as used in the TGB section. Pure visual, no links.
{{Template:T3DTutorial | title | description}} creates a link to a tutorial page in the T3D/Tutorials/ namespace. Use this before starting on one and click the resulting link to create the tutorial in the right place. The benefit of keeping things under a namespace is that if the engine changes name (again!) the subpages move along with it, and redirects point to the right place.
#88
Just a quick and innocent question, am I allowed to post torquescript code on it? Or must I post my code here (or TDN)? If I remember correctly, no engine code postings only, right?
03/04/2011 (6:11 pm)
Well, I am doing my bid to bring more customers to GarageGames in under my blog called Appetite 4 Coding.Just a quick and innocent question, am I allowed to post torquescript code on it? Or must I post my code here (or TDN)? If I remember correctly, no engine code postings only, right?
#89
03/04/2011 (7:13 pm)
TorqueScript code being posted on other sites is just fine =) 
#90
I was going to add some items to it but found I can't upload images (just tells me I haven't permissions <uploaddisabled_nopermissions>). Is this dead?
We're getting a lot of tutorials, How To's, etc being posted as resources that will get lost as they aren't easy to find in the resource section as there's no structure there.
I don't mind doing the grunt work to convert them over, or add links to the resource but don't want to waste the effort if TDN is to die.
08/13/2011 (3:47 am)
Any updates on the future for TDN? The Torque 3D area is woefully empty right now.I was going to add some items to it but found I can't upload images (just tells me I haven't permissions <uploaddisabled_nopermissions>). Is this dead?
We're getting a lot of tutorials, How To's, etc being posted as resources that will get lost as they aren't easy to find in the resource section as there's no structure there.
I don't mind doing the grunt work to convert them over, or add links to the resource but don't want to waste the effort if TDN is to die.
#91
It would be ideal if the wiki was fixed so we could upload images, but if I start transferring some posts I have space usable for any wiki entries I work on. I'm hosting a couple of the TDN section images already ;)
Fun fact: The section page gets 3000 to 6000 hits per month from a handful of hardcore users. Norway is topping the list, but I know much of that traffic isn't from me. The UK is second most of the time.
Rest of the world: You bloody slackers! TDN needs a hot content injection, so get to it!
08/13/2011 (5:25 am)
We need a compiled list of tutorials, how-tos and tips that fit TDN (basically anything but bug fixes should be there), and it should be stickied. One per engine in each respective public forum. Then volunteers with some clue (people familiar with the engine the content is for) could translate them to the wiki if the authors don't mind, crossing them off the list. Little snippets shouldn't be a problem to just grab & credit, I think.It would be ideal if the wiki was fixed so we could upload images, but if I start transferring some posts I have space usable for any wiki entries I work on. I'm hosting a couple of the TDN section images already ;)
Fun fact: The section page gets 3000 to 6000 hits per month from a handful of hardcore users. Norway is topping the list, but I know much of that traffic isn't from me. The UK is second most of the time.
Rest of the world: You bloody slackers! TDN needs a hot content injection, so get to it!
#92
08/13/2011 (3:27 pm)
Yeah exactly my thinking, would be great to get things organised on there.
#93
08/18/2011 (2:32 pm)
Any updates?
#94
1.Fetch a more recent wiki system which works with the server's PHP version. Must also have ACLs.
2.Make it live under the main domain.
3.Ensure a few different levels of access. The admins, editors (change permissions), users ( can create articles and edit their own).
4.Notification system for editors and admins to know when a mere mortal adds an article. They'll then link it from the appropriate section and tag it, possibly correcting any wiki markup errors they spot.
5.There shouldn't be any other markup than wiki markup. The wiki is only for information, and HTML+CSS gets in the way. We'll only need indices, tables, lists, paragraphs, footnotes, images and uploads. Layout doesn't need to be fancy, only easy to read.
6.There would be a few different sections, mostly like the current TDN. A section for each engine, but possibly a dedicated one for scripting and artist-related matters. A few volunteer editors would pick one or more sections they'll try to keep in check and watch over. All editors would get update notifications so they can cover for each other.
This can happen quickly. Start fresh with an empty wiki after deciding on a system. Set it up with the bare minimum of style, and a layout using the GG colours. Then the volunteers can start moving over content that is still valid, and make lists of content which needs updating.
Make the official documentation the place to find the basic reference, and the wiki the place for code snippets, extra tutorials, funky behaviours and anything else that might be buried in forum posts and resources.
09/06/2011 (10:59 pm)
OK,TDN needs a reboot.1.Fetch a more recent wiki system which works with the server's PHP version. Must also have ACLs.
2.Make it live under the main domain.
3.Ensure a few different levels of access. The admins, editors (change permissions), users ( can create articles and edit their own).
4.Notification system for editors and admins to know when a mere mortal adds an article. They'll then link it from the appropriate section and tag it, possibly correcting any wiki markup errors they spot.
5.There shouldn't be any other markup than wiki markup. The wiki is only for information, and HTML+CSS gets in the way. We'll only need indices, tables, lists, paragraphs, footnotes, images and uploads. Layout doesn't need to be fancy, only easy to read.
6.There would be a few different sections, mostly like the current TDN. A section for each engine, but possibly a dedicated one for scripting and artist-related matters. A few volunteer editors would pick one or more sections they'll try to keep in check and watch over. All editors would get update notifications so they can cover for each other.
This can happen quickly. Start fresh with an empty wiki after deciding on a system. Set it up with the bare minimum of style, and a layout using the GG colours. Then the volunteers can start moving over content that is still valid, and make lists of content which needs updating.
Make the official documentation the place to find the basic reference, and the wiki the place for code snippets, extra tutorials, funky behaviours and anything else that might be buried in forum posts and resources.
Torque Owner Andy Rollins
ZDay Game