We have a fairly competent error reporting and mysql system in place. It can perform basic queries, and we will definitely improve upon it as time goes on.
The next steps:
We need to make a few markup changes to the files. I should have these minor changes done in the next few minutes.
Then using the DB scheme I gave, we can all split paths, or travel the same one... but either way, we need to make these things (see docs for where to put the files):
1) admin interface for customization
- admin.php, etc... goes in the home folder
- all other files under /admin
2) polls interface
- polls.php goes in the home folder
- all other files under /polls
3) forums interface
- forums.php goes in the home folder
- all other files under /forums
4) news system
- news.php goes in the home folder
- all other files under /news
Please POST any questions here before making new files / folders if you are not sure. Also, here is the plan for how we want users to be able to implement all of this stuff.
1) Admin console: Accessed directly through the admins web browser.
2) News:
Must place include_once("./phpwebmastertls/news.php"); in the top of the page they wish to include news on, and PrintPHPWebTlsNews(); where they want the news to print. All new articles are set through news_admin.php in the home folder.
2) Polls, same as news, except function calls like PrintPHPWebTlsPoll('POLL_TITLE_HERE'); or RANDOM for POLL_TITLE_HERE.
3) Forums, the webmaster will create a forums.php file on his server (not in our folder), with two lines:
include_once('./phpwebmastertls/forum.php');
printforum();
=========
NOTE:
FORUM and ADMIN must send start of doc. tags like <head> and <body>, etc... and </body></html>... because they will be all that is printed on a separate page.
POLL and NEWS will not include that because they will be plugged into existing pages.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Quote: FORUM and ADMIN must send start of doc. tags like <head> and <body>, etc... and </body></html>... because they will be all that is printed on a separate page. End Quote
Doesn't make sense, do you mean don't send <head> and <body> as they will be included.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
On reading it, I think he means that the FORUM and ADMIN pages should include all the head and body tags, because they will be self-contained pages, and won't use /lib/system/header.php and /iib/system/footer.php files.
Is this accurate? I am kind of wondering about that, myself, but *shrug* :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-08-20
Yah, that is correct, the FORUM and ADMIN pages will be separate pages.
The POLL and NEWS MUST NOT send <HTML><HEAD><BODY> tags, etc... because it will already be included within the body of an existing page.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-08-20
If you want to do something, assign yourself the task through the tasks page (select an existing one please, and go in and change the "assigned to" so that you are highlighted.) Keep in mind that you can highlight more than one name at a time, please do not unhighlight another name to highlight yourself, rather, highlight both.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a question about the news table: is the 'archive' column noting whether a given row is _already_ archived, or _should be_ archived? Is the intent for that column to have something like 0 = not_archived_dont_archive 1 = not_archived_do_archive 2 = archived ... or ... ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-08-20
On lots of sites (SourceForge project summary, nehe.gamedev.net, php.net, counter-strike.net), you see the news articles listed down the front page.
Then, you see at the bottom, click here to view articles from the past, or something like that.
Past articles are "archived", the ones that display on the front are "active". If the archive column is set to 1, then we do not want it on the initial display, but only when the user clicks a link.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are the forums meant to be accessed seperately or to be included on a page? I'm about to start write post and view post / forum pages and need to know.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-08-20
Forums will be accessed separately (included from a file with one line, the include statement).
Since we dont know the filename the user will assign to the forums, create FORM tags like this:
I've been doing a little alpha testing of a kind of forum system I've knocked up. Yes it can be done via include but for many reasons I feel it should be a seperate section *but* still use user-management, etc. For the following reasons:
1) URL's - basically there may be a problem if the forums are included in a page that has a query string as this may need to be forwarded.
2) Coding - It's not that I can't do it, but I feel it may create a few problems with linking pages.
3) Functions - Hopefully in the future we will be able to add certain options and extra features. It will be easier to impliement these features into a seperate system.
If you still feel strongly about having it as an include then I will code it as so, but I strongly recommend that it's accessed via /forum/ and not via an include.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We have a fairly competent error reporting and mysql system in place. It can perform basic queries, and we will definitely improve upon it as time goes on.
The next steps:
We need to make a few markup changes to the files. I should have these minor changes done in the next few minutes.
Then using the DB scheme I gave, we can all split paths, or travel the same one... but either way, we need to make these things (see docs for where to put the files):
1) admin interface for customization
- admin.php, etc... goes in the home folder
- all other files under /admin
2) polls interface
- polls.php goes in the home folder
- all other files under /polls
3) forums interface
- forums.php goes in the home folder
- all other files under /forums
4) news system
- news.php goes in the home folder
- all other files under /news
Please POST any questions here before making new files / folders if you are not sure. Also, here is the plan for how we want users to be able to implement all of this stuff.
1) Admin console: Accessed directly through the admins web browser.
2) News:
Must place include_once("./phpwebmastertls/news.php"); in the top of the page they wish to include news on, and PrintPHPWebTlsNews(); where they want the news to print. All new articles are set through news_admin.php in the home folder.
2) Polls, same as news, except function calls like PrintPHPWebTlsPoll('POLL_TITLE_HERE'); or RANDOM for POLL_TITLE_HERE.
3) Forums, the webmaster will create a forums.php file on his server (not in our folder), with two lines:
include_once('./phpwebmastertls/forum.php');
printforum();
=========
NOTE:
FORUM and ADMIN must send start of doc. tags like <head> and <body>, etc... and </body></html>... because they will be all that is printed on a separate page.
POLL and NEWS will not include that because they will be plugged into existing pages.
Quote: FORUM and ADMIN must send start of doc. tags like <head> and <body>, etc... and </body></html>... because they will be all that is printed on a separate page. End Quote
Doesn't make sense, do you mean don't send <head> and <body> as they will be included.
On reading it, I think he means that the FORUM and ADMIN pages should include all the head and body tags, because they will be self-contained pages, and won't use /lib/system/header.php and /iib/system/footer.php files.
Is this accurate? I am kind of wondering about that, myself, but *shrug* :-)
Yah, that is correct, the FORUM and ADMIN pages will be separate pages.
The POLL and NEWS MUST NOT send <HTML><HEAD><BODY> tags, etc... because it will already be included within the body of an existing page.
If you want to do something, assign yourself the task through the tasks page (select an existing one please, and go in and change the "assigned to" so that you are highlighted.) Keep in mind that you can highlight more than one name at a time, please do not unhighlight another name to highlight yourself, rather, highlight both.
I have a question about the news table: is the 'archive' column noting whether a given row is _already_ archived, or _should be_ archived? Is the intent for that column to have something like 0 = not_archived_dont_archive 1 = not_archived_do_archive 2 = archived ... or ... ?
On lots of sites (SourceForge project summary, nehe.gamedev.net, php.net, counter-strike.net), you see the news articles listed down the front page.
Then, you see at the bottom, click here to view articles from the past, or something like that.
Past articles are "archived", the ones that display on the front are "active". If the archive column is set to 1, then we do not want it on the initial display, but only when the user clicks a link.
Are the forums meant to be accessed seperately or to be included on a page? I'm about to start write post and view post / forum pages and need to know.
Forums will be accessed separately (included from a file with one line, the include statement).
Since we dont know the filename the user will assign to the forums, create FORM tags like this:
<form action="<?php echo $GLOBALS['HTTP_SERVER_VARS']['PHP_SELF']; ?>" method="post/get">
As is standard, use post when posting data to the forums, logging in, etc... Use get when retrieving data (viewing posts, threads, etc...).
I've been doing a little alpha testing of a kind of forum system I've knocked up. Yes it can be done via include but for many reasons I feel it should be a seperate section *but* still use user-management, etc. For the following reasons:
1) URL's - basically there may be a problem if the forums are included in a page that has a query string as this may need to be forwarded.
2) Coding - It's not that I can't do it, but I feel it may create a few problems with linking pages.
3) Functions - Hopefully in the future we will be able to add certain options and extra features. It will be easier to impliement these features into a seperate system.
If you still feel strongly about having it as an include then I will code it as so, but I strongly recommend that it's accessed via /forum/ and not via an include.