Difference between revisions of "Talk:Geeklog 1.3x Documentation"
| Line 15: | Line 15: | ||
[[User:Tomw|TomW]] Here are my suggestions for these questions: | [[User:Tomw|TomW]] Here are my suggestions for these questions: | ||
# It is very easy to make a new page just refer to it. I would suggest that version specific notes be included on their own page like this <nowiki>[[ModulePageSubjectEtc 1.3.8 note]]</nowiki> | # It is very easy to make a new page just refer to it. I would suggest that version specific notes be included on their own page like this <nowiki>[[ModulePageSubjectEtc 1.3.8 note]]</nowiki> | ||
| + | # It doesn't matter on things like this, perhaps we could add a page to each update page for gotcha's like this. Be the first and start the trend. | ||
| + | #Security is not a big issue. I will keep an eye on it, as sysop I have the ability to ban users and ips and I will. The wiki keeps a history and I make a daily backup also, so I can get back to previous versions. | ||
Revision as of 14:27, 6 July 2004
User:Netbuster I was excited to learn about this Wiki project and decided to add some personal experiences, as i just refreshed my memory by recent upgrade to 1.3.9 But, I started typing all little things I noticed and realized, doc page becomes clogged too much.
I added one note here for obvious thing which happens with me always and under all hostings, and then thought one more note about checking permissions, under installation steps, there is an advise for check.php script. It is currently running not correctly, so first my move was to write it, like this NOTE: As of 1.3.9sr1 version, running check.php will help you to identify whether permissions are set correctly only till you get an error regarding SQL. Once SQL related error occurs, download error.log and read the error. It will mean that permissions for logs/ folder are set and geeklog writes to it. But errors regarding SQL are not for you to worry at that point, omit it for now and go to the step 4
But then I removed it from there, since I started thinking that at the same spot I have to describe how to correct errors, which error is good and which is not, what to do etc. It may become a 2 page story just describing a current work of one script, while it may all change in the next version So, having said all of this, my questions are:
- Should we have a version related errors file or how wiki doc will change if 1.3.10 will be released and function differently
- If someone spots a bug or an error, is Documentation is a write space for describing it and if yes, what spot? Should it be under Problems? May be version differencies? I remember from previous installations, there are numerious little but important changes from version to version and automatic updates not always catch them
- Not related, but ... What about security? I registered my account and even without proving an email I was logged on immediately to edit stuff. What if someone will delete or add advertisement entries all over the place?
TomW Here are my suggestions for these questions:
- It is very easy to make a new page just refer to it. I would suggest that version specific notes be included on their own page like this [[ModulePageSubjectEtc 1.3.8 note]]
- It doesn't matter on things like this, perhaps we could add a page to each update page for gotcha's like this. Be the first and start the trend.
- Security is not a big issue. I will keep an eye on it, as sysop I have the ability to ban users and ips and I will. The wiki keeps a history and I make a daily backup also, so I can get back to previous versions.
