Search results
Jump to navigation
Jump to search
- ** dologin.cgi -- log in ** dologout.cgi -- log out3 KB (488 words) - 06:37, 5 December 2010
- Other than ''Log In'' you will need to be logged into ISFDB as an editor or moderator to use * [https://www.isfdb.org/cgi-bin/dologin.cgi?index.cgi+0 Log In]6 KB (910 words) - 20:02, 9 September 2022
- |Navigation after Log Out gives SQL errors in nav bar |Log in / log out does not redraw nav bar41 KB (5,830 words) - 22:11, 13 September 2022
- * 20068 OPEN If you log out of the ISFDB, you will still have the option to "Log out" displayed in the navbar. When you select it, you will see the followin ...PEN [http://www.isfdb.org/cgi-bin/ea.cgi?Dave%20Wolverton Dave Wolverton's Log Works biblio] currently lists the first two volumes of his ''Golden Queen''49 KB (7,728 words) - 11:07, 3 February 2008
- ...porarily disabled the new functionality pending the addition of a deletion log23 KB (2,973 words) - 21:49, 13 September 2022
- ...issue is that ISFDB does a case-sensitive compare and the editor could not log in using the all lower-case name he had entered initially. [[User:Marc Kupp ...is changed), and it does not perform a strictly caseless search (I can not log in as "AlvonRuff", for instance). Rather than try to guess the MediaWiki al40 KB (6,314 words) - 20:31, 20 August 2009
- ...of LCCN and the editor has not been PV'd. Most of the changes I see in the log I would not expect notice for - adding external IDs, cover credits (that cr ...the Talk page is an active communication. I'll read your arguments for the log as being for 'passive communication' unless you say that isn't your intenti125 KB (20,374 words) - 12:29, 28 September 2022
- ...06'''. Not sure if this is the right place to list it, but when I hit the "log out" on the isfdb page (not the wiki) I get an "Internal Server Error". [[U36 KB (5,466 words) - 19:27, 22 November 2006
- | Create a log of moderator actions which make tags private/public56 KB (7,647 words) - 21:59, 13 September 2022
- ...r who is considering approving the edit, and would be retained in the edit log, to whatever extent the other edit details are retained. Obviously this is ...run across publications where someone has added detailed notes. If an edit log was available then we'd be able to ask the last editor "Do you want to mark110 KB (17,630 words) - 20:24, 3 January 2020
- || <span id="Yu"></span>The Yule Log ...114031743/http://www.thisishorror.co.uk:80/read-horror/flash-fear/the-yule-log-by-william-meikle/ 2011-12-06]113 KB (12,818 words) - 20:11, 24 November 2018
- ...s like publication merges aren't supported yet (despite showing the proper log spew, after posting this same edit previously as [http://www.isfdb.org/cgi-59 KB (9,023 words) - 18:26, 26 December 2006
- ..., edit the help text and update the [[Rules and standards changelog|change log]]. --[[User:MartyD|MartyD]] 08:13, 21 April 2018 (EDT) ...to update the note at the bottom of the section that serves as an "update log". [[User:Anniemod|Annie]] 19:44, 5 July 2018 (EDT)376 KB (62,546 words) - 20:32, 27 June 2019
- .../ delete - you should be able to reference that rule. So to automate your log (generally the only hope of keeping it accurate and complete), you need to246 KB (40,297 words) - 20:05, 26 September 2017
- ::: In any case, I'm thinking the merge logic should be modified to at least log the old/new names for each publication so that someone can look back to see573 KB (97,958 words) - 17:23, 17 December 2015
- ...d truth is it is '''silly''' and the sad truth, no one will clear the back log, so I can finish the process. It amounts to '''blackmail''' over an opinion621 KB (105,414 words) - 17:25, 17 December 2015