[19:57:51] <ReWoP> when i type tiki-index.php?page="some page name" there should be a error msg that would say "page does not exist, want to go back or grate page" now there is the browser error "The page cannot be found [19:58:26] <sylvieg> did you type the url with the " [19:58:37] <ReWoP> *(not "grate page" but "create page") [19:58:42] <ReWoP> nop [19:59:32] <ReWoP> i tryed to erase DB and re-intall tiki and nothing.... [20:00:14] <sylvieg> what url did it display at the error [20:00:46] <ReWoP> u coul try it its online -> http://dme.uma.pt/jcardoso/Research/Projects/seed/tiki-index.php?page=fgbn [20:02:35] <sylvieg> mdavey around? [20:03:24] <sylvieg> I don't know why it is done like this but when there is an error the header sent is HTTP/1.0 404 Not FOund with the clssic tiki page [20:03:49] <sylvieg> I suppose your browser catches the 404 and yop [20:04:14] <sylvieg> better to ask mdavey ... I suppose it is himl that added that why this line is here [20:04:40] <sylvieg> you can always try to delete the liens in tiki-index.php [20:05:02] <ReWoP> could it be permitions on the folder ?? [20:05:26] <ReWoP> i gave the web server all perms... [20:05:27] <sylvieg> I don't think so [20:06:30] <ReWoP> ... [20:06:37] <ReWoP> but i could be a server problem.. [20:07:15] <ReWoP> i tryed with polaris version and was woking [20:07:47] <ReWoP> then i have a DB problem and re-intalled it and this error occured.. [20:08:05] <sylvieg> yes it is a conflict between server/ and tiki [20:08:30] <ReWoP> now was trying it with -Sirius- version and not workig 2. [20:08:50] <ReWoP> the server is nt2003 server [20:09:38] <sylvieg> there is 2 lines I don't understrand in tiki-index.php (header("...404...") I am pretty sure there are the guilty ones [20:09:48] <ReWoP> i thing that there is error only on this part, because i can create/edit modules, menus pages premitions... [20:10:05] <ReWoP> mabe [20:11:01] <ReWoP> but dosnt answer why worked on my 1st polaris version, and dind on my 2nd and on 1st Sirius..... [20:11:14] <ReWoP> dont thing its code problem... [20:11:38] <ReWoP> if it was mabe it wold be random error [20:11:53] <ReWoP> after all it already worked once... [20:11:59] <red_adair> nt2003 ? what's that ? [20:12:20] <ReWoP> windows 2003 server :p [20:12:21] <sylvieg> you can try to put into comment the 2 line header"... 404..) in tiki-index.php Additional information: [18:56:51] <ReWoP> i wanted to add that there is other tiki installed on the same server but it works !
I'm closing this as invalid. IIS has settings to show its own page on a 404 error, but sending a 404 doesn't seem to be wrong. To set IIS 7 to send the HTTP reply's body, set existingResponse to PassThrough. Auto (the default) has the same behavior from IIS 7.5. Thanks to Wade Hildo.
[23:43:00] <mdavey> amette that is IIS behaviour - they need to set up an error page. For some bizarre reason by default IIS catches header 404 and replaces the http body with its own. Typical M$ behaviour - we know better than everyone else. [23:43:30] <amette> ah, damn... [23:43:49] <amette> mdavey : why did you add those lines there? [23:44:31] <amette> Because, if IIS users don't get the "Create Page - Similar Pages"-whatever tiki-page, that's contraproductive... imho... [23:47:07] <mdavey> because otherwise browsers and webcaches think that is a valid page and cache it, allow it to be bookmarked, etc. With the headers, if a page has been bookmarked then deleted then when you click on the bookmark smart browsers will know that the page has been deleted and do the right thing (prompt to delete the bookmark, search for the correct page, etc). [23:50:23] <amette> mdavey : hmm, well, that's a dilemma - I really can't suggest anything to do there.... :-/ [23:50:48] <amette> good change of yours... and though I don't like M$ supporters, it would be important to keep it running well for them... [23:51:56] <amette> can we make tiki set an error page? [23:52:02] <mdavey> who reported the problem? we could find out if configuring IIS's error page to be tiki-error.php (perhaps with a PATH_INFO) is okay for them. Otherwise, it is a case of having a whole bunch of options. [23:52:25] <mdavey> allow_404_header allow_410_header, etc. [23:52:32] <amette> It was a guy, jumping in here, telling it and promising to come back on monday... [23:53:18] <amette> Well, but the standard error page wouldn't help, right? We need the "Create this page" etc stuff - or am I not understanding something here? [23:54:08] <amette> standard error page == tiki-error.php [23:54:14] <mdavey> the standard error page doesn't send any header by default because it is a generic error. [23:54:33] <mdavey> although it should send the pragma no-cache headers at the very least. [23:55:09] <amette> pragma no-cache? - dunno what pragma means, but no-cache sounds very reasonable! :D [23:55:18] <mdavey> does abyone actually have IIS to test with [23:55:41] <luciash> maybe damian [23:55:43] <amette> I think ohertel is the only IIS test guy... and he hasn't been seen for a long time... [23:55:45] <luciash> :) [23:55:49] <mdavey> excuse the flood [23:55:52] <mdavey> header( 'Expires: Mon, 26 Jul 1997 05:00:00 GMT' ); [23:56:12] <mdavey> header( 'Last-Modified: ' . gmdate( 'D, d M Y H:i:s' ) . ' GMT' ); [23:56:13] <mdavey> header( 'Cache-Control: no-store, no-cache, must-revalidate' ); [23:56:16] <mdavey> header( 'Cache-Control: post-check=0, pre-check=0', false ); [23:56:17] <mdavey> header( 'Pragma: no-cache' ); [23:57:30] <amette> well, wouldn't it be pretty easy to put that into the tiki-error.php - or would that make problems? [23:57:47] <mdavey> It would be interesting to know if 410 causes the same problem: visit tiki-install.php after renaming the install directory - in IIS [23:58:23] <amette> hmmm..... we'll have to bug that guy a little to do some testing for us... ;) [23:58:41] <mdavey> yes it would be pretty easy. It shouldn't cause problems but would be nice to test.
Show.tiki.org snapshot creation is in progress... Please monitor http:///snapshots/ for progress. Note that if you get a popup asking for a username/password, please just enter "show" and "show".
Password reset was successful
Password reset failed
Show.tiki.org instance destruction is in progress... Please wait...
The public/private keys configured to connect to show2.tiki.org were not accepted. Please make sure you are using RSA keys. Thanks.
Unable to connect to show2.tiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is currently under maintenance. Sorry for the inconvenience.
Unable to get information from show2.tiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is in the progress of creating the new instance. Please continue waiting for a minute or two. If this continues on for more than 10 minutes, please let us know of the problem so that we can do something about it. Thanks.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
The URL for the show2.tiki.org instance that demonstrates this bug is at: http://. Note that if you get a popup asking for a username/password, please just enter "show" and "show". This is different from the initial login and password for a new Tiki which is "admin" and "admin".
For the install log, see http:///info.txt
Note that if you see PHP errors or a Tiki claiming to be missing third party software, the instance creation is probably not finished. Please wait a couple minutes and reload.
Snapshots are database dumps of the configuration that developers can download for debugging. Once you have reproduced your bug on the show2.tiki.org instance, create a snapshot that can then be downloaded by developers for further investigation.
Snapshots can be accessed at: http:///snapshots/. Note that if you get a popup asking for a username/password, please just enter "show" and "show".Create new snapshot
|No attachments for this item|