Comparing revisions for WikkaBugs
- [6884] 2005-03-24 17:47:58 by NilsLindenberg (unregistered user) [add delayed messages]
- [20755] 2009-08-17 09:46:45 by JeyRey (unregistered user) [over 5 year old resolved issue removed]
Additions:
{{lastedit show="3"}}
<<**Related pages**:
-for resolved bugs/issues see: WikkaBugsResolved
-workarounds for unusual problems and temporary fixes for known bugs listed at WikkaWorkarounds
-for issues related to Wikka layout refer to: WikkaCSS
-for feature suggestions rather than bugs, go to the SuggestionBox
-looking for help? check the [[WikkaDocumentation Wikka Documentation]]
<<>>==Attention:==
For problems with **foreach** in PHP version **4.3.10**:---See WikkaBugsResolved>>::c::
**Please post recently discovered bugs on the //top// of this page (just below this note).**---
::c::
====Messages delayed====
====Extreme extreme slowness====
Not being registered makes no difference. There are users reporting Wikka pages taking several minutes to load!
The guys on the Puppy Linux Forum (SimpleForumPro, a Perl script on the same host, runs real fast), have been analysing the problem, discussion here (look further down the page):
http://www.goosee.com/puppy/sforum/simpleforum_pro.cgi?fid=07&topic_id=1111215715&page=2
...anyone got any thought what the cause could be?
===Spaces in uploaded files===
//Thanks to MrTrick for pointing out this problem//
It is possible to upload files with a space in the file name. However, when trying to download such a file things don't work as expected: in Mozilla browsers (Mozilla, Firefox, etc.) the suggested filename for the download is truncated at the first space.
Two possible solutions:
~1) Prevent that file names are //stored// with spaces in the name; simply replacing all spaces with underscores would do the trick and keep the file name recognizable. This has the advantage that no assumptions are being made about the server OS //or// the user's OS as to whether spaces in file names are valid.
~2) Mozilla seems to pick up the suggested file name from the Content-Disposition header. (raw)urlencoding the file name here works, but then displays the name with the encoding; enclosing the file name in (double) quotes works better, showing the full file name with spaces. This has the advantage that the original file name is preserved - //provided// both the server OS and the downloading user's OS can handle such file names.---
Take your pick ;-) -- JavaWoman
If you edit the ACL on a page, click "Store ACLs", then edit the ACL and click "Cancel", it still reads "Access control lists updated.", even though the changes were canceled. This is due to the "Cancel" button causing the browser to navigate backwards, and a javascript popup. --BarkerJr
===Alzheimers for Wikka?===
This is not a bug specifically - it is really a potential implentation weakness, but if a user specifies a page purge time in wikka.config: "pages_purge_time" => "100" and if that page is not edited for a while, then when that page is edited, the last copy will be deleted, leaving no archived copies at all. I think purge pages should delete old pages, but there should always be a minimum number of old copies preserved, otherwise the wiki becomes highly vulnerable to a content deletion attack. Would it be better to remove this feature, or modify it? --IanAndolina
~&Instead of removing or modifying it (the configuration parameter, rather) we could refine it by introducing an extra parameter name something like "pages_keep" to set a maximum number of pages to be kept regardless (maximum, since it could be less if there are not that many versions in the first place). Setting one or the other to 0 could disable purging altogether. --JavaWoman
~~&Sounds good to me - can you think of an elegant way to modify the SQL query to only delete pages older than X that are also more than Xth on a list of revisions. I'm sure I can come up with something ugly ;) --IanAndolina
~~~&I'm good enough at SQL that I need the manual for that. ;-) As far as I can determine, you need two statements (semi pseudo code): 1) a ##select count(*) from pages where ...## to determine the current number of records; and 2) ##delete from pages where ... order by [timestamp] limit [$count - $pages_keep]##. You can't do a subquery in delete (yet) so the count must be a separate step (but it should be very fast). --JavaWoman
//reported in IRC while I was asleep, sorry - JW does have to sleep sometimes//
(Potential) User extremely frustrated when at installation he's entering a real and valid email address and the Installer rejects it with "Email appears incorrect". This is caused by the extremely brain-dead Javascript in the installer that accepts **nothing but lowercase letters** to appear before the '@'. To be anywhere like realistic it should be corrected to accept numbers, dots, hyphens and underscores as well.
--JavaWoman //(hoping the reporter shows up again so I can help him with a workaround)//
~& Gosh, this is //really// annoying. JW, any news from your general-purpose [[WikkaEmailToolkit email validation]] functions ;-) -- DarTar
~~&The basic problem is that the installer does not use any system routines but instead JavaScript for validation. And the RE it uses for email validation is really, really braindead. Yes, very annoying as I've not seen the user back in #wikka either - we may have lost a user. I could have given a workaround if only I'd not been sleeping. --- Email library is not quite ready but getting close (needs some restructuring, basically); it will be a class, with several abstract methods so the installer should be able to use it as well (provided it can find the class file). And I'm learning some good tricks working on the sessions module (which might also be useful for Wikka). But the installer needs a major overhaul in any case. Sigh... --JavaWoman
===Comments in formatted PHP code===
GeSHi has a habit of adding a trailing line if the PHP code contains a comment using ""//"" or ""#"".
For example %%(php) echo "hello world"; // How do you do?%% This does not happen if ""/* */"" is used for comments. For example %%(php) echo "hello world"; /* How do you do? */%%
-- FreekDijkstra
~&Sounds also like a GeSHi problem rather than a Wikka bug. If anyone is installing (or has installed) GeSHi 1.0.6 I'd appreciate feedback on whether this cosmetic problem is solved as well. --JavaWoman
My default installation of Wikka 1.1.6.0 did display the error
htmlentities(): charset `646' not supported, assuming iso-8859-1 in /home/www/WWW/files/research/air/wiki/3rdparty/plugins/geshi/geshi.php
on the FormattingRules page. I was able to fix this by adding the "set_encoding" line in the GeSHi_Highlight() function in wikka.php:
$geshi =& new GeSHi($sourcecode, $language, $this->config['geshi_languages_path']); # existing code
$geshi->set_encoding('UTF-8'); # set encoding (new line)%%
-- FreekDijkstra
~&This is actually not a Wikka bug, but a problem in GeSHi itself - which only appears in rare cases. See CharsetNotSupportedWorkaround for more information. I think the latest GeSHi version (1.0.6) has addressed this problem. If you'd like to try this, make sure you remove the workaround code in Wikka when installing the new GeSHi version. --JavaWoman
===User name matching===
(related to the //Category name matching// item below)
While [[RegisterActionTest testing]] the beta RegisterAction, I realized that using a username like **""DarTartar""** results in a //"Sorry, username already exists"// error. Looks like a problem in the RE used by the ##""LoadUser()""## function. I'll take a look at it ASAP.
-- DarTar
===Multiple wikka installations on one host: Login security hole?===
Okay. Say that I've installed multiple seperate installations of wikka on one host. If I do a login on wikka A, I can also
reach the pages of wikka B, whereas wikka B has an authentication table where the user account of wikka A does not exist!
My guess is that this behaviour occurs because the login cookies are set with path root. And as long the login cookies exist
Wikka doesn't care about authentication anymore??
-- JeroenJansen
~&Same problem. Is it possible to include in wikka.config.php a line in which you specify the default cookie prefix? I guess this could solve the problem. --YanB
===Category name matching===
Yes, I know the category system needs to be revamped, but I figured I'd report this anyway. If you have a category name that is a substring of another category name, pages referencing the second category will also appear in the first. In other words...I have a category named '""CategoryBookOne"", and another named ""CategoryBookOneJournal"". Pages that reference ""CategoryBookOneJournal"" also show up in the list of pages for ""CategoryBookOne"", which is not the behavior I expected or wanted.
-- TammyCravit
Gathered from error reports in different places (including comments on WikkaInstallation, #wikka and IM) - neither new, but worth repeating and putting together, I think:
~-In at least some cases the "detected" base path misses a closing slash (resulting in links that don't work); the installer should check if the derived path has a final slash, and if not, add one, before presenting that to the user.
~-If PHP (and thus Wikka) cannot connect to MySQL the installer just "hangs" after the first screen and printing "Testing configuration"; this seems to be (at least partly) the result of having error messages from the MySQL statements suppressed with a @, which would be OK if the error message were handled afterwards - but this doesn't happen. Other mysql_xxx() calls in the installer also have the @ suppressing error messages. That should either be removed, or all error messages should be picked up and handled by the installer, at the very least by showing the message to the user. ---
~This is especially a problem for users new at MySQL or new even at PHP+MySQL for whom it won't be obvious where to start troubleshooting when the installer simply hangs.
--JavaWoman
===mod_rewrite issue===
When in edit mode using IIS if you click the help button the program doesn't take you to the FormattingRules page, but tries to go to the ""FormattingRules"" Directory, which does not exist.
===Bug in Textsearch (expanded)===
As DotMG has pointed out, the input for this two actions isn't validated, making it a security-hole.
You can fix it by changing the line
$phrase = stripslashes($phrase);
into
$phrase = preg_quote($this->htmlspecialchars_ent(stripslashes($phrase)), "/");
You have to change both files (textsearch and textsearchexpanded). --NilsLindenberg
**Advanced search results reveal confidential info**
Results should be hidden or not shown if the user doesn't have read access to page IMHO. --PolVazo
===Recent[ly]Comment[ed|s] actions should check for permission===
Comments are being previewed even if users do not have access. A simple check needs to be added. -- JsnX
if ($this->HasAccess("comment"))
===tags in the edit-notes===
I made a edit note: "removed a <?php (to much)" and got "removed a". Perhaps replacing <> would be the better option? --NilsLindenberg
~&Funny - I just stumbled over the same problem - only in the RecentChanges newsfeed: the <?php causes imbalanced tags there, and thus a syntax error: until that post has "aged" off of the feed, it can't be loaded any more! The [[http://feedvalidator.org/check?url=http%3a%2f%2fwikka.jsnx.com%2fRecentChanges%2frecentchanges.xml validation result]] clearly shows what the problem is. So yes, edit notes should be fed threough htmlspecialchars[_ent]() everywhere they're presented, and that includes the RSS feed! --JavaWoman
~~&And the WikiPing, too :) --NilsLindenberg
~&Oh is **that** what you removed Nils. I couldn't figure out using history what you did. Where did you take it from? And why? Did I have one more <?php than was necessary? In which code block? --GmBowen
~~&It was at the beginning of mail.php: %%(php) <?php <?php%%. I guess you overlooked it when you copied your new version to the page. Happent to me in another case, too. --NilsLindenberg
===Opera and layer===
(copied from the sandbox --NilsLindenberg)
Opera browser doesn't like a right layer a the end of a page :(
~&A "layer" is nothing but a div; Wikka's "float" boxes are floated divs. When a floated block is longer (vertically) than the section it precedes, it will (vertically) overlap with the next section. This is just standard CSS (the effect isn't limited to Opera either). To prevert this overlap happening at the end of a page (or section), add ""::c::"" at the end of the page (or section), which will create an empty div a with clear: both style. **Not a bug** - just standard CSS for which Wikka markup provides an appropriate mechanism. --JavaWoman
(copied from the sandbox --NilsLindenberg)
not support 2byte language in the Code formatters!!!!
%%(c)
// 한글이 깨지겠지
// 진짜 깨지네.. 흑흑.. 에디터창에서 깨지는 것도 열받는데..
...
Line 46 :
- Code generates a double </a> for links.
- & in URL should be replaced by &
=> %%(php) print("<td valign=\"top\">" . (($site != "unknown") ? "<a href=\"http://".$this->htmlspecialchars_ent($site)."\">".$this->htmlspecialchars_ent($site)."</a>" : $site) . /*"</a> ".*/($IsAdmin ? "[<a href=\"".$this->href("delete_referrer", "", "spam_site=").$this->htmlspecialchars_ent($site)."&redirect=".$this->GetMethod()."\">Blacklist</a>]" : "")."</td>");%%
Note: You cannot see this error by validating directly a page because W3C is not registered and it will not have the same output as you, in other words, code on line 46 won't be executed. But you can save the page on your hard disk and validate it.
--DotMG
**Not really bug, but should be corrected for respect & compliance to RFC2616**
If a browser sends the header
Accept-Encoding: gzip;q=0, deflate
Which should be interpreted as : "I don't support gzip encoding, but I prefer deflate", Wikka will understand "The browser supports gzip-encoding", as it just searches for the text gzip in $_SERVER['HTTP_ACCEPT_ENCODING']. An example I use to treat it correctly is :
%%(php) function ParseHeaderLine($hl, $token=null)
{
$ar_hl = explode(',', $hl);
foreach ($ar_hl as $dotmg_idx => $val)
{
if (preg_match('/^\s*(.*?);\s*q\s*=\s*([0-9\.]*)/i', $val, $match))
{
$res[strtolower($match[1])] = doubleval($match[2]);
}
else
{
$res[strtolower($val)] = 1;
}
}
if ($token) return(isset($res[$token]) && ($res[$token] > 0)); #if $token is set, we return true or false
return ($res); # else we return the header parsed.
}%%
and
%%(php) if ($this->ParseHeaderLine($_SERVER['HTTP_ACCEPT_ENCODING'], 'gzip')) ...%%
Note : This function might be useful to deal also with Accept-Language, when Wikka will be made effectively multilingual.
--DotMG
A page contains unicode characters looks OK when viewed but displays ""''&#*****;''"" while edited in WikiEdit
Simplified Chinese Test:
中文是一种美丽的语言，除了具有音节上的美感，同样拥有视觉上的美感
In 1.1.5.3, I solved this problem by changed some line in ./handlers/page/edit.php
#from
"<textarea onKeyDown=\"fKeyDown()\" id=\"body\" name=\"body\" style=\"width: 100%; height: 500px\">".$body."</textarea><br />\n"
#to
"<textarea onKeyDown=\"fKeyDown()\" id=\"body\" name=\"body\" style=\"width: 100%; height: 500px\">".$this->htmlspecialchars_ent($body)."</textarea><br />\n"
Wikka is wonderful! ZhuangYuyao
~&This workaround you outlined will work as well in Wikka 1.1.6.0. A real solution wil take some more investigation though, so we were unable to fix this for the current release. This is now under investigation. --JavaWoman
I noticed: Turning off DoubleClick-editing does not work (double-clicks still go to edit-window) in IE 6.0 or Firefox 1.0.
Keep up the good work!
Cheers, MarkHissinkMuller
~&Yes, I noticed the same thing. This is a bug as of 1.1.6.0. --RyanKnoll
~~&Heres the fix:
~~&add as **first** line in handlers/page/show.php:
~~&%%(php)
<?php $user = $this->GetUser(); ?>
~~&and change the second line to:
~~&%%(php)
<div class="page" <?php echo ((!$user || ($user["doubleclickedit"] == 'Y')) && $this->GetMethod
() == "show") ? "ondblclick=\"document.location='".$this->href("edit")."';\" " : "" ?>>
~~&--NilsLindenberg
DarTar and I have recently created some test pages, testing page names related to how Wikka evaluates 'valid' page names: ,My,Page and ÄhnLich (yes, they both exist, even if they don't show up as such in this sentence!). Now look at where they show up on PageIndex... surely there shouldn't be **two** '#' indices??
--JavaWoman
~&I think that this is due to the encoding of the MySQL tables. I can't see how that would be fixed with a small touch on the code. If this is the matter then I hope that it also rings the i18n bell too. //Translation to Greek is my bussiness ;)//
~&""--""GeorgePetsagourakis
~~&Yes, my i18n bells were already loudly ringing... but you bring up a good point with MySQL. I hadn't thought about a real cause yet, just wanted to record what I saw before I got distracted again ;-). Sort order is a whole subject of its own within i18n .... --JavaWoman
First, this may applied to my ISP only. When I installed, I have to use
the ?wakka= options. However, I have to add a / to the end of the
default Basic URL before append ?wakka= to it. So I think it maybe
helpful to modify the instruction to '... so it should include
the "/?wakka=" parameter...'
~&ArpY: Maybe this is caused by a config error. Please have a look at your config - is there a slash at the end of the base_url?
http://gmbowen.educ.unb.ca/wikitest/bug.jpg
http://gmbowen.educ.unb.ca/wikitest/bug3.jpg
~&''I've never seen anything like it and can't reproduce your screenshots - can you tell us exactly which browser/version/OS (all three!) you are using? To me it feels more like a browser problem than a Wikka problem... Also: given the spacing they look as if they belong to the "small print" line "Valid XHTML 1.0 Transitional? :: Valid CSS? :: Powered by Wikka Wakka Wiki 1.1.6.0?" in the footer - can you maek a screen shot that includes that line? --JavaWoman''
~~&''Sure. Win 98, IE 6.0.2800.1106 (most recent updates of both as far as I know). I've closed and rebooted several times since leaving this note and it's still there (but farther up the page now, in the middle of the second code block, but with the same spacing). You're right that it's "from" that small print line....those images (and you cannot right-click and get properties on them....they're visible, but NOT there, if you get what I mean) are NOT on that line as a matter of fact and the spacing corresponds exactly. I've never seen it at any other site, but have noticed it a few times at wikka recently...but not always. It persistently (which means ALMOST always) shows up on the bannermaker page when I go there. -- GmBowen''
~~~&''Further questions: Does it depend on whether or not you are showing comments on the/a page? And which stylesheet are you using for viewing this site? Any difference when you choose a different stylesheet (TestSkin)? (BTW, that 'infinity' symbol is not an image, it's just a character.) --JavaWoman''
~~~~&''No, showing comments or not has no effect. I just looked NOT showing comments and the symbols were halfway up the page in the code block. I'm using the default stylesheet as far as I know (I've not changed it)...and when I do switch to yours they're still there (on a different vertical part of the page, but it varied before anyways. Oh, right, that's a character. Well, what's weird is you can't highlight it either. It's like a ghost image. Weird. --GmBowen''
~~&''TEST: Please try with my stylesheet again, to see if that makes any difference now (I tweaked it). --JavaWoman''
~~&''Answer: Sorry to say, the floaters are still there in IE even using your stylesheet. (FYI....I tried using your stylesheet in Netscape 4.7 & it crashed the TestSkin page. I can go to other pages with your stylesheet in Netscape, but I get the WSOD on the TestSkin page and can't change to anything else. Later...closing & re-opening NS allowed me to re-set it to the wikka.css....and it "crashed" the page again. Obviously there are broader NS problems....wikka's homepage doesn't load at all using any skin in NS 4.7.) --GmBowen''
~~~&''Forget about NS 4.x - it doesn't really support stylesheets. The only solution for that would be detecting it and not giving it a stylesheet at all. I'd like to trace the problem with IE6 though ... even though I cannot reproduce it with my IE6 on Win2K. It may not be standards-compliant, but there's still an awful lot of people using it, even when FireFox is taking market share from it now. I have to think about another approach but I still suspect it's something to do with the (valid) stylesheet that trips up IE6. Thinking... --JavaWoman''
~~~~&''Any chance it's a videocard memory issue? It's a new ATI card, but that the images jump around on re-loads is interesting to me. It's like the video driver is doing something as video memory fills in different ways. --GmBowen''
~~~~~&''Sounds unlikely to me - and they're not images, remember? Just text, but bits of text **positioned** by means of a stylesheet. Any chance of testing with a different machine, different video card, but same Browser+OS? Meanwhile, I'll sleep on it. :) --JavaWoman''
~~&''Another idea just struck me: are you using some security software (like Norton security) or a proxy (like The Proxomitron or Privoxy) that sits between your browser and the Internet? That might "do" things to the page to cause a different display. I'm asking because I know The Proxomitron can cause display problems - and the problem seems to be unique to your machine/browser... Another thing to try would be to get Mozilla or Firefox and see if that shows the same problem on your machine. --JavaWoman''
~~~~&''I'm out of ideas, Mike, except that it's //probably// something to do with the stylesheet and IE (more likely since you don't see it with FF) - plus something else... Try to find a pattern, is all I can suggest. Note down at which pages it happens. See what shakes out. --JavaWoman''
Um, I don't know how to describe this really. Put ""{{include page="CategoryDocumentation"}}"" on the SandBox page....I can't figure out why it gives that output as Sandbox doesn't own anything.
~&''Looks like the weirdness is caused by the ""{{Category}}"" action which assumes the "current page" represents the category - and find pages "belonging to" a category by finding a mention of that page name. Good sign our category system does need an [[CategorySystemOverhaul overhaul]]! --JavaWoman''
~&Include pulls in a page that itself has the category action on it; the "official" version of this action assumes that the page it occurs on **is** a category. The "//experimental//" category action that is now active on this site no longer makes this assumption but recognizes that SandBox isn't a category page and defaults to the top category. See Sandbox for a an example (at this moment). --JavaWoman
~~&I can see that it now works, but what do you mean that it "recognizes that Sandbox isn't an action".....do you mean target page? --GmBowen
~~~&Oops, sorry (corrected now) - I meant the new category action sees whether the page it's "sitting" on is a category page or not - if not it defaults to showing the list for the top-level category. --JavaWoman (aka IamBack)
===Backlinks / ""LoadPagesLinkingTo()""===
I just discovered that the ##""{{backlinks}}""## action may list pages that don't "exist" any more, in the sense that they (apparently) still are in the database but without any active version (seemingly as a result of a rename action. I added an example on [[JavaWoman my own page]] where you can see a supposed backlink from ReleaseNotes (which was replaced by WikkaReleaseNotes).
~&The cause is apparently in the ""LoadPagesLinkingTo()"" method which is used by ##""{{backlinks}}""## action. It currently is implemented like this:
~& %%(php) function LoadPagesLinkingTo($tag) { return $this->LoadAll("select from_tag as tag from ".$this->config["table_prefix"]."links where to_tag = '".mysql_real_escape_string($tag)."' order by tag"); }
%% I think replacing this by:
~& %%(php) function LoadPagesLinkingTo($tag) { return $this->LoadAll("select from_tag as tag from ".$this->config["table_prefix"]."links where to_tag = '".mysql_real_escape_string($tag)."' and latest = 'Y' order by tag"); }
%% might do the trick to avoid deceased pages - but please test!
~&--JavaWoman
====GetEnv is not a good idea!====
At ./wikka.php, you will see a line %%(php)<?php if (!$configfile = GetEnv("WAKKA_CONFIG")) $configfile = "wikka.config.php";?>%%
In the most cases, a website is hosted in a machine as a VirtualHost, this means that a number of websites share the same environment variables. If someone knows where your site is hosted, he can put his site at the same server, and use a script containing %%(php)<?php putenv('WAKKA_CONFIG=/home/hacker/config.php');?>%%. And all wikka sites on the same server will use his configuration file. The rest actions to take to hack your site will be as easy as eating sandwich.
Php doc says that an environment variable is altered only during the life of the script, but with my dev Easyphp's on windows, that is false. (I think a "new" environment variable keep its value, even on Linux).
I wanted to make a unique Wikka interface used by 3 sites on the same server. The best secure solution I found is to alter ./wikka.php like this :
%%(php)<?php
if (file_exists("wakka.config.php")) rename("wakka.config.php", "wikka.config.php");
#if (!$configfile = GetEnv("WAKKA_CONFIG")) $configfile = "wikka.config.php";
if (!$configfile && isset($GLOBALS['wikka_config'])) $configfile = $GLOBALS['wikka_config'];
if (!$configfile) $configfile = "wikka.config.php";
if (file_exists($configfile)) include($configfile);
and put the 2 files sitenumber2.php and .htaccess below at the root of the server number 2:
__sitenumber2.php:__
%%(php)<?php
$GLOBALS['wikka_config'] = "/path/to/altered_config.php";
chdir("/path/to/basewikka");
include('wikka.php');
?>%%
__.htaccess:__
%%<IfModule mod_rewrite.c>
RewriteRule ^(css|images|wikiedit2)/(.*)$ /path/to/basewikka/$1/$2 [L]
RewriteRule ^(.*)$ sitenumber2.php?wakka=$1 [QSA,L]
</IfModule>%%
--DotMG
~&''I've now written up my thoughts about a [[WikkaSecureConfig more secure way to handle Wikka's configuration]] (which should also provide also more flexibility). --JavaWoman''
===Expanded Text Search fails===
I tried an expanded Text-Search after [[http://wikka.jsnx.com/TextSearchExpanded?phrase=%2Bparameter+%2Blink +parameter +link]] and got the following error:
''Warning: Compilation failed: nothing to repeat at offset 1 in /.../actions/textsearchexpanded.php on line 33''
for every page.
--NilsLindenberg
~&''In my recent RE exploits I have found that a warning of this type comes up when a regular expression isn't quite correct (though not every attempt to match may bring up teh warning); haven't investigated further in textsearchexpanded.php though. --JavaWoman''
~&Php has a function : preg_quote that may help us. Or try this solution : DotMGTextSearchExpanded
Looking at **formatters/wikka.php** to find the cause of the two bugs listed below (found one), I notice to my horror that a **lot** of the regular expressions used there are actually incorrect. They allow such things as using a comma to indent a line (in addition to a tab, or ~, at the start of a line: **demo** in the SandBox, and in the list **below**!), or a comma in a WikiName (even at the start) or in an InterWiki link. That can't have been the intention - it's simply a matter of incorrect RE syntax. I'd become sort of "sensitized" to this phenomenon looking at DarTar's RE on ValidPageNames earlier today - now I see where he found an example (see my comment on that page on his RE!).
,''Note: see also [[,My,Page]] - yup, that's a real page now. ;-)''
~&Rather than simply fixing all the REs (and other REs all over the place...) I'd like to propose a more fundamental solution:
~&-create a "library" of RE building blocks to be used in the Wikka core (for an example of what I mean with building blocks see my propopsal for an alternative RE on ValidPageNames); simply create a separate file with define()s for these building blocks, and include them at the start of the main wikka.php file;
~&-gather all RE used in the Wikka core here (extensions/plugins could have their own set of defines - as long as they don't have conflicting names);
~&-now use **only** these building blocks when using REs anywhere in the Wikka core.
~&This should make it much easier to create both //correct//, and //consistent// regular expressions; any (near)duplicates will be much easier to discover, and fix.
~&
~&Probably best to leave this to just **after** the coming release, so we have a stable code base again. I volunteer to undertake this work. (Unlike some people, I happen to like REs.) :)
~&--JavaWoman
Have a look at the source of WikkaDevelopment, you will see that tabs and unordered lists for some reasons are not correctly parsed (actually after one edit, tabs were added at the beginning of each line). I'll try to figure out why this happens...
-- DarTar
~&Possible clue:
~&I just stumbled over the fact that the little list of "Useful pages" at the end of the default (installation-generated) ""HomePage"" had incorrect coding: The last list item (li) was not terminated, nor was the list itself (no closing ul tag). It took me a bit of trial and error to reproduce this - but have a look at my test code at the end of SandBox (now). Originally I thought that any list at the end of a page would be unterminated, but that turned out not to be the case. Then I hit on something else: the last list element on that default ""HomePage"" (not the one here) ands with a period. My test version on SandBox now also has the last element ending in a period ... and if you look at the (HTML) page source, you'll see it is indeed an unterminated list. Somehow that ending period (maybe in combination with end-of-page?) causes the Formatter never to close the list; take that ending period away, and it works normally. I tried a few variants, to check whether it might be an odd-even problem, but no: whether the number of list items is odd or even, if the last one ends in a period, the list isn't terminated.
~&
~&No difference whether it's anordered (ol) or unordered (ul) list, the formatter behaves the same way.
~&
~&And, BTW, if you look at the preview when editing, the HTML source of the **preview** actually contains a lot of Wiki code that shouldn't be there!
~&
~&I haven't dug in the Formatter yet to find the cause or whether end-of-page makes a difference...
~&--JavaWoman
MySQL 5+ isn't supported as it requires PHP to use the mysqli extension instead of plain old mysql. I hoped there would be a single file to change this, but there seems to be no database abstraction in this project at all.
-- DavidCarrington
~&I do not have access to a MySQL 5 server for testing. And judging by the feedback that I see here on Wikka, most other Wikka admins are using older versions of MySQL. However, I do like progress, so I looked at the documentation for the mysqli extension. I don't see any major issue here. It looks like the function calls are the same, they just have a different name. Instead of calling mysql_connect, you call mysqli_connect. Instead of calling mysql_query, you call mysqli_query. So on and so forth.
~&
~&It seems that we would just have to do a simple version check and call "mysql" functions for older versions, and "mysqli" functions for newer versions.
~&
~&Please correct me if I'm missing something. -- JsnX 26 Nov 2004
~~&I'm running MySQL 5 fine with the mysql_* functions. When you compile PHP, it's your choice to compile the mysql_* or mysqli_* functions. I chose to compile it with mysql_*, which is working fine for me. --BarkerJr
==Login Problem==
==User search - should be case-sensitive==
===Problem with "History"??===
I ran across this on another wikka implementation....
http://elvito.sv-city.de/wikka.php?wakka=RecentChanges
if you look at Sun, 22 Aug 2004 the second item down says
"" [ (20:46 CEST?) [history?] - TextSearch?phrase=ElVitoWakkaWiki? ? ppp-82-135-6-82.mnet-online.de ]"" which seems kinda wrong. -- Mike (aka GmBowen)
==Email Addresses==
Found several issues with how email addresses are validated / accepted / used; outlined on WikkaAndEmail - and I'm working on solutions. (Email is //complicated// and there's a whole bunch of standards (RFCs) involved.)
First part of the solutions now in WikkaEmailToolkit; while the toolkit is still incomplete, what's there now can be used as presented there (no dependencies on later components).
-- JavaWoman
Bugs I've found:
- Security: I was wondering whether it would be possible to store IPs for registered users as well. That way you can ban them via .htaccess if necessary.
- ''Last known IP or every IP they ever connect from? I'd be willing to store one last known IP per user. '' - JsnX
- ''Last known IP please :) Thanks.'' - Sam
- ''I'd suggest adding *two* distinct fields to ##wikka_users##: Last Login IP/Hostname + Last Login Time'' - DarTar
- ''I was also thinking of a way to ban users directly from the wiki (much in the same way as referrers are added to the blacklist of spammers). This might turn out easier to implement than a //user deleting action// (which was one of the ideas discussed [[UserAdmin here]])'' - DarTar
- Security: Single-click restore of previous versions (without copying/pasting).
- ''Yes, this will be implemented at some point.'' - JsnX
- I should point out that there is an alternative to copying/pasting.
- Go to the revisions page.
- Click the date and time link that you would like to revert back to.
- Click the 'Re-edit this old revision' button.
- Click the 'Store' button.
Thanks - Sam
- Mod_rewrite : take a look at FaviconDotIco and RobotsDotTxt
====Logout problem====
With Wikka Wakka Wiki 1.1.6.0. Php5
Login.
Go to Preferences/Logout, click the logout button
=> it goes to:
%%[[mypath]]/wikka.php?wakka=UserSettings?action=logout%%
So, it tries to find the "UserSettings?action=logout" page, doesn't and propose to create it.
The path should be:
%%[[mypath]]/wikka.php?wakka=UserSettings&action=logout%%
::c::
CategoryDevelopment
<<**Related pages**:
-for resolved bugs/issues see: WikkaBugsResolved
-workarounds for unusual problems and temporary fixes for known bugs listed at WikkaWorkarounds
-for issues related to Wikka layout refer to: WikkaCSS
-for feature suggestions rather than bugs, go to the SuggestionBox
-looking for help? check the [[WikkaDocumentation Wikka Documentation]]
<<>>==Attention:==
For problems with **foreach** in PHP version **4.3.10**:---See WikkaBugsResolved>>::c::
**Please post recently discovered bugs on the //top// of this page (just below this note).**---
::c::
====Messages delayed====
====Extreme extreme slowness====
Not being registered makes no difference. There are users reporting Wikka pages taking several minutes to load!
The guys on the Puppy Linux Forum (SimpleForumPro, a Perl script on the same host, runs real fast), have been analysing the problem, discussion here (look further down the page):
http://www.goosee.com/puppy/sforum/simpleforum_pro.cgi?fid=07&topic_id=1111215715&page=2
...anyone got any thought what the cause could be?
===Spaces in uploaded files===
//Thanks to MrTrick for pointing out this problem//
It is possible to upload files with a space in the file name. However, when trying to download such a file things don't work as expected: in Mozilla browsers (Mozilla, Firefox, etc.) the suggested filename for the download is truncated at the first space.
Two possible solutions:
~1) Prevent that file names are //stored// with spaces in the name; simply replacing all spaces with underscores would do the trick and keep the file name recognizable. This has the advantage that no assumptions are being made about the server OS //or// the user's OS as to whether spaces in file names are valid.
~2) Mozilla seems to pick up the suggested file name from the Content-Disposition header. (raw)urlencoding the file name here works, but then displays the name with the encoding; enclosing the file name in (double) quotes works better, showing the full file name with spaces. This has the advantage that the original file name is preserved - //provided// both the server OS and the downloading user's OS can handle such file names.---
Take your pick ;-) -- JavaWoman
If you edit the ACL on a page, click "Store ACLs", then edit the ACL and click "Cancel", it still reads "Access control lists updated.", even though the changes were canceled. This is due to the "Cancel" button causing the browser to navigate backwards, and a javascript popup. --BarkerJr
===Alzheimers for Wikka?===
This is not a bug specifically - it is really a potential implentation weakness, but if a user specifies a page purge time in wikka.config: "pages_purge_time" => "100" and if that page is not edited for a while, then when that page is edited, the last copy will be deleted, leaving no archived copies at all. I think purge pages should delete old pages, but there should always be a minimum number of old copies preserved, otherwise the wiki becomes highly vulnerable to a content deletion attack. Would it be better to remove this feature, or modify it? --IanAndolina
~&Instead of removing or modifying it (the configuration parameter, rather) we could refine it by introducing an extra parameter name something like "pages_keep" to set a maximum number of pages to be kept regardless (maximum, since it could be less if there are not that many versions in the first place). Setting one or the other to 0 could disable purging altogether. --JavaWoman
~~&Sounds good to me - can you think of an elegant way to modify the SQL query to only delete pages older than X that are also more than Xth on a list of revisions. I'm sure I can come up with something ugly ;) --IanAndolina
~~~&I'm good enough at SQL that I need the manual for that. ;-) As far as I can determine, you need two statements (semi pseudo code): 1) a ##select count(*) from pages where ...## to determine the current number of records; and 2) ##delete from pages where ... order by [timestamp] limit [$count - $pages_keep]##. You can't do a subquery in delete (yet) so the count must be a separate step (but it should be very fast). --JavaWoman
//reported in IRC while I was asleep, sorry - JW does have to sleep sometimes//
(Potential) User extremely frustrated when at installation he's entering a real and valid email address and the Installer rejects it with "Email appears incorrect". This is caused by the extremely brain-dead Javascript in the installer that accepts **nothing but lowercase letters** to appear before the '@'. To be anywhere like realistic it should be corrected to accept numbers, dots, hyphens and underscores as well.
--JavaWoman //(hoping the reporter shows up again so I can help him with a workaround)//
~& Gosh, this is //really// annoying. JW, any news from your general-purpose [[WikkaEmailToolkit email validation]] functions ;-) -- DarTar
~~&The basic problem is that the installer does not use any system routines but instead JavaScript for validation. And the RE it uses for email validation is really, really braindead. Yes, very annoying as I've not seen the user back in #wikka either - we may have lost a user. I could have given a workaround if only I'd not been sleeping. --- Email library is not quite ready but getting close (needs some restructuring, basically); it will be a class, with several abstract methods so the installer should be able to use it as well (provided it can find the class file). And I'm learning some good tricks working on the sessions module (which might also be useful for Wikka). But the installer needs a major overhaul in any case. Sigh... --JavaWoman
===Comments in formatted PHP code===
GeSHi has a habit of adding a trailing line if the PHP code contains a comment using ""//"" or ""#"".
For example %%(php) echo "hello world"; // How do you do?%% This does not happen if ""/* */"" is used for comments. For example %%(php) echo "hello world"; /* How do you do? */%%
-- FreekDijkstra
~&Sounds also like a GeSHi problem rather than a Wikka bug. If anyone is installing (or has installed) GeSHi 1.0.6 I'd appreciate feedback on whether this cosmetic problem is solved as well. --JavaWoman
My default installation of Wikka 1.1.6.0 did display the error
htmlentities(): charset `646' not supported, assuming iso-8859-1 in /home/www/WWW/files/research/air/wiki/3rdparty/plugins/geshi/geshi.php
on the FormattingRules page. I was able to fix this by adding the "set_encoding" line in the GeSHi_Highlight() function in wikka.php:
$geshi =& new GeSHi($sourcecode, $language, $this->config['geshi_languages_path']); # existing code
$geshi->set_encoding('UTF-8'); # set encoding (new line)%%
-- FreekDijkstra
~&This is actually not a Wikka bug, but a problem in GeSHi itself - which only appears in rare cases. See CharsetNotSupportedWorkaround for more information. I think the latest GeSHi version (1.0.6) has addressed this problem. If you'd like to try this, make sure you remove the workaround code in Wikka when installing the new GeSHi version. --JavaWoman
===User name matching===
(related to the //Category name matching// item below)
While [[RegisterActionTest testing]] the beta RegisterAction, I realized that using a username like **""DarTartar""** results in a //"Sorry, username already exists"// error. Looks like a problem in the RE used by the ##""LoadUser()""## function. I'll take a look at it ASAP.
-- DarTar
===Multiple wikka installations on one host: Login security hole?===
Okay. Say that I've installed multiple seperate installations of wikka on one host. If I do a login on wikka A, I can also
reach the pages of wikka B, whereas wikka B has an authentication table where the user account of wikka A does not exist!
My guess is that this behaviour occurs because the login cookies are set with path root. And as long the login cookies exist
Wikka doesn't care about authentication anymore??
-- JeroenJansen
~&Same problem. Is it possible to include in wikka.config.php a line in which you specify the default cookie prefix? I guess this could solve the problem. --YanB
===Category name matching===
Yes, I know the category system needs to be revamped, but I figured I'd report this anyway. If you have a category name that is a substring of another category name, pages referencing the second category will also appear in the first. In other words...I have a category named '""CategoryBookOne"", and another named ""CategoryBookOneJournal"". Pages that reference ""CategoryBookOneJournal"" also show up in the list of pages for ""CategoryBookOne"", which is not the behavior I expected or wanted.
-- TammyCravit
Gathered from error reports in different places (including comments on WikkaInstallation, #wikka and IM) - neither new, but worth repeating and putting together, I think:
~-In at least some cases the "detected" base path misses a closing slash (resulting in links that don't work); the installer should check if the derived path has a final slash, and if not, add one, before presenting that to the user.
~-If PHP (and thus Wikka) cannot connect to MySQL the installer just "hangs" after the first screen and printing "Testing configuration"; this seems to be (at least partly) the result of having error messages from the MySQL statements suppressed with a @, which would be OK if the error message were handled afterwards - but this doesn't happen. Other mysql_xxx() calls in the installer also have the @ suppressing error messages. That should either be removed, or all error messages should be picked up and handled by the installer, at the very least by showing the message to the user. ---
~This is especially a problem for users new at MySQL or new even at PHP+MySQL for whom it won't be obvious where to start troubleshooting when the installer simply hangs.
--JavaWoman
===mod_rewrite issue===
When in edit mode using IIS if you click the help button the program doesn't take you to the FormattingRules page, but tries to go to the ""FormattingRules"" Directory, which does not exist.
===Bug in Textsearch (expanded)===
As DotMG has pointed out, the input for this two actions isn't validated, making it a security-hole.
You can fix it by changing the line
$phrase = stripslashes($phrase);
into
$phrase = preg_quote($this->htmlspecialchars_ent(stripslashes($phrase)), "/");
You have to change both files (textsearch and textsearchexpanded). --NilsLindenberg
**Advanced search results reveal confidential info**
Results should be hidden or not shown if the user doesn't have read access to page IMHO. --PolVazo
===Recent[ly]Comment[ed|s] actions should check for permission===
Comments are being previewed even if users do not have access. A simple check needs to be added. -- JsnX
if ($this->HasAccess("comment"))
===tags in the edit-notes===
I made a edit note: "removed a <?php (to much)" and got "removed a". Perhaps replacing <> would be the better option? --NilsLindenberg
~&Funny - I just stumbled over the same problem - only in the RecentChanges newsfeed: the <?php causes imbalanced tags there, and thus a syntax error: until that post has "aged" off of the feed, it can't be loaded any more! The [[http://feedvalidator.org/check?url=http%3a%2f%2fwikka.jsnx.com%2fRecentChanges%2frecentchanges.xml validation result]] clearly shows what the problem is. So yes, edit notes should be fed threough htmlspecialchars[_ent]() everywhere they're presented, and that includes the RSS feed! --JavaWoman
~~&And the WikiPing, too :) --NilsLindenberg
~&Oh is **that** what you removed Nils. I couldn't figure out using history what you did. Where did you take it from? And why? Did I have one more <?php than was necessary? In which code block? --GmBowen
~~&It was at the beginning of mail.php: %%(php) <?php <?php%%. I guess you overlooked it when you copied your new version to the page. Happent to me in another case, too. --NilsLindenberg
===Opera and layer===
(copied from the sandbox --NilsLindenberg)
Opera browser doesn't like a right layer a the end of a page :(
~&A "layer" is nothing but a div; Wikka's "float" boxes are floated divs. When a floated block is longer (vertically) than the section it precedes, it will (vertically) overlap with the next section. This is just standard CSS (the effect isn't limited to Opera either). To prevert this overlap happening at the end of a page (or section), add ""::c::"" at the end of the page (or section), which will create an empty div a with clear: both style. **Not a bug** - just standard CSS for which Wikka markup provides an appropriate mechanism. --JavaWoman
(copied from the sandbox --NilsLindenberg)
not support 2byte language in the Code formatters!!!!
%%(c)
// 한글이 깨지겠지
// 진짜 깨지네.. 흑흑.. 에디터창에서 깨지는 것도 열받는데..
...
Line 46 :
- Code generates a double </a> for links.
- & in URL should be replaced by &
=> %%(php) print("<td valign=\"top\">" . (($site != "unknown") ? "<a href=\"http://".$this->htmlspecialchars_ent($site)."\">".$this->htmlspecialchars_ent($site)."</a>" : $site) . /*"</a> ".*/($IsAdmin ? "[<a href=\"".$this->href("delete_referrer", "", "spam_site=").$this->htmlspecialchars_ent($site)."&redirect=".$this->GetMethod()."\">Blacklist</a>]" : "")."</td>");%%
Note: You cannot see this error by validating directly a page because W3C is not registered and it will not have the same output as you, in other words, code on line 46 won't be executed. But you can save the page on your hard disk and validate it.
--DotMG
**Not really bug, but should be corrected for respect & compliance to RFC2616**
If a browser sends the header
Accept-Encoding: gzip;q=0, deflate
Which should be interpreted as : "I don't support gzip encoding, but I prefer deflate", Wikka will understand "The browser supports gzip-encoding", as it just searches for the text gzip in $_SERVER['HTTP_ACCEPT_ENCODING']. An example I use to treat it correctly is :
%%(php) function ParseHeaderLine($hl, $token=null)
{
$ar_hl = explode(',', $hl);
foreach ($ar_hl as $dotmg_idx => $val)
{
if (preg_match('/^\s*(.*?);\s*q\s*=\s*([0-9\.]*)/i', $val, $match))
{
$res[strtolower($match[1])] = doubleval($match[2]);
}
else
{
$res[strtolower($val)] = 1;
}
}
if ($token) return(isset($res[$token]) && ($res[$token] > 0)); #if $token is set, we return true or false
return ($res); # else we return the header parsed.
}%%
and
%%(php) if ($this->ParseHeaderLine($_SERVER['HTTP_ACCEPT_ENCODING'], 'gzip')) ...%%
Note : This function might be useful to deal also with Accept-Language, when Wikka will be made effectively multilingual.
--DotMG
A page contains unicode characters looks OK when viewed but displays ""''&#*****;''"" while edited in WikiEdit
Simplified Chinese Test:
中文是一种美丽的语言，除了具有音节上的美感，同样拥有视觉上的美感
In 1.1.5.3, I solved this problem by changed some line in ./handlers/page/edit.php
#from
"<textarea onKeyDown=\"fKeyDown()\" id=\"body\" name=\"body\" style=\"width: 100%; height: 500px\">".$body."</textarea><br />\n"
#to
"<textarea onKeyDown=\"fKeyDown()\" id=\"body\" name=\"body\" style=\"width: 100%; height: 500px\">".$this->htmlspecialchars_ent($body)."</textarea><br />\n"
Wikka is wonderful! ZhuangYuyao
~&This workaround you outlined will work as well in Wikka 1.1.6.0. A real solution wil take some more investigation though, so we were unable to fix this for the current release. This is now under investigation. --JavaWoman
I noticed: Turning off DoubleClick-editing does not work (double-clicks still go to edit-window) in IE 6.0 or Firefox 1.0.
Keep up the good work!
Cheers, MarkHissinkMuller
~&Yes, I noticed the same thing. This is a bug as of 1.1.6.0. --RyanKnoll
~~&Heres the fix:
~~&add as **first** line in handlers/page/show.php:
~~&%%(php)
<?php $user = $this->GetUser(); ?>
~~&and change the second line to:
~~&%%(php)
<div class="page" <?php echo ((!$user || ($user["doubleclickedit"] == 'Y')) && $this->GetMethod
() == "show") ? "ondblclick=\"document.location='".$this->href("edit")."';\" " : "" ?>>
~~&--NilsLindenberg
DarTar and I have recently created some test pages, testing page names related to how Wikka evaluates 'valid' page names: ,My,Page and ÄhnLich (yes, they both exist, even if they don't show up as such in this sentence!). Now look at where they show up on PageIndex... surely there shouldn't be **two** '#' indices??
--JavaWoman
~&I think that this is due to the encoding of the MySQL tables. I can't see how that would be fixed with a small touch on the code. If this is the matter then I hope that it also rings the i18n bell too. //Translation to Greek is my bussiness ;)//
~&""--""GeorgePetsagourakis
~~&Yes, my i18n bells were already loudly ringing... but you bring up a good point with MySQL. I hadn't thought about a real cause yet, just wanted to record what I saw before I got distracted again ;-). Sort order is a whole subject of its own within i18n .... --JavaWoman
First, this may applied to my ISP only. When I installed, I have to use
the ?wakka= options. However, I have to add a / to the end of the
default Basic URL before append ?wakka= to it. So I think it maybe
helpful to modify the instruction to '... so it should include
the "/?wakka=" parameter...'
~&ArpY: Maybe this is caused by a config error. Please have a look at your config - is there a slash at the end of the base_url?
http://gmbowen.educ.unb.ca/wikitest/bug.jpg
http://gmbowen.educ.unb.ca/wikitest/bug3.jpg
~&''I've never seen anything like it and can't reproduce your screenshots - can you tell us exactly which browser/version/OS (all three!) you are using? To me it feels more like a browser problem than a Wikka problem... Also: given the spacing they look as if they belong to the "small print" line "Valid XHTML 1.0 Transitional? :: Valid CSS? :: Powered by Wikka Wakka Wiki 1.1.6.0?" in the footer - can you maek a screen shot that includes that line? --JavaWoman''
~~&''Sure. Win 98, IE 6.0.2800.1106 (most recent updates of both as far as I know). I've closed and rebooted several times since leaving this note and it's still there (but farther up the page now, in the middle of the second code block, but with the same spacing). You're right that it's "from" that small print line....those images (and you cannot right-click and get properties on them....they're visible, but NOT there, if you get what I mean) are NOT on that line as a matter of fact and the spacing corresponds exactly. I've never seen it at any other site, but have noticed it a few times at wikka recently...but not always. It persistently (which means ALMOST always) shows up on the bannermaker page when I go there. -- GmBowen''
~~~&''Further questions: Does it depend on whether or not you are showing comments on the/a page? And which stylesheet are you using for viewing this site? Any difference when you choose a different stylesheet (TestSkin)? (BTW, that 'infinity' symbol is not an image, it's just a character.) --JavaWoman''
~~~~&''No, showing comments or not has no effect. I just looked NOT showing comments and the symbols were halfway up the page in the code block. I'm using the default stylesheet as far as I know (I've not changed it)...and when I do switch to yours they're still there (on a different vertical part of the page, but it varied before anyways. Oh, right, that's a character. Well, what's weird is you can't highlight it either. It's like a ghost image. Weird. --GmBowen''
~~&''TEST: Please try with my stylesheet again, to see if that makes any difference now (I tweaked it). --JavaWoman''
~~&''Answer: Sorry to say, the floaters are still there in IE even using your stylesheet. (FYI....I tried using your stylesheet in Netscape 4.7 & it crashed the TestSkin page. I can go to other pages with your stylesheet in Netscape, but I get the WSOD on the TestSkin page and can't change to anything else. Later...closing & re-opening NS allowed me to re-set it to the wikka.css....and it "crashed" the page again. Obviously there are broader NS problems....wikka's homepage doesn't load at all using any skin in NS 4.7.) --GmBowen''
~~~&''Forget about NS 4.x - it doesn't really support stylesheets. The only solution for that would be detecting it and not giving it a stylesheet at all. I'd like to trace the problem with IE6 though ... even though I cannot reproduce it with my IE6 on Win2K. It may not be standards-compliant, but there's still an awful lot of people using it, even when FireFox is taking market share from it now. I have to think about another approach but I still suspect it's something to do with the (valid) stylesheet that trips up IE6. Thinking... --JavaWoman''
~~~~&''Any chance it's a videocard memory issue? It's a new ATI card, but that the images jump around on re-loads is interesting to me. It's like the video driver is doing something as video memory fills in different ways. --GmBowen''
~~~~~&''Sounds unlikely to me - and they're not images, remember? Just text, but bits of text **positioned** by means of a stylesheet. Any chance of testing with a different machine, different video card, but same Browser+OS? Meanwhile, I'll sleep on it. :) --JavaWoman''
~~&''Another idea just struck me: are you using some security software (like Norton security) or a proxy (like The Proxomitron or Privoxy) that sits between your browser and the Internet? That might "do" things to the page to cause a different display. I'm asking because I know The Proxomitron can cause display problems - and the problem seems to be unique to your machine/browser... Another thing to try would be to get Mozilla or Firefox and see if that shows the same problem on your machine. --JavaWoman''
~~~~&''I'm out of ideas, Mike, except that it's //probably// something to do with the stylesheet and IE (more likely since you don't see it with FF) - plus something else... Try to find a pattern, is all I can suggest. Note down at which pages it happens. See what shakes out. --JavaWoman''
Um, I don't know how to describe this really. Put ""{{include page="CategoryDocumentation"}}"" on the SandBox page....I can't figure out why it gives that output as Sandbox doesn't own anything.
~&''Looks like the weirdness is caused by the ""{{Category}}"" action which assumes the "current page" represents the category - and find pages "belonging to" a category by finding a mention of that page name. Good sign our category system does need an [[CategorySystemOverhaul overhaul]]! --JavaWoman''
~&Include pulls in a page that itself has the category action on it; the "official" version of this action assumes that the page it occurs on **is** a category. The "//experimental//" category action that is now active on this site no longer makes this assumption but recognizes that SandBox isn't a category page and defaults to the top category. See Sandbox for a an example (at this moment). --JavaWoman
~~&I can see that it now works, but what do you mean that it "recognizes that Sandbox isn't an action".....do you mean target page? --GmBowen
~~~&Oops, sorry (corrected now) - I meant the new category action sees whether the page it's "sitting" on is a category page or not - if not it defaults to showing the list for the top-level category. --JavaWoman (aka IamBack)
===Backlinks / ""LoadPagesLinkingTo()""===
I just discovered that the ##""{{backlinks}}""## action may list pages that don't "exist" any more, in the sense that they (apparently) still are in the database but without any active version (seemingly as a result of a rename action. I added an example on [[JavaWoman my own page]] where you can see a supposed backlink from ReleaseNotes (which was replaced by WikkaReleaseNotes).
~&The cause is apparently in the ""LoadPagesLinkingTo()"" method which is used by ##""{{backlinks}}""## action. It currently is implemented like this:
~& %%(php) function LoadPagesLinkingTo($tag) { return $this->LoadAll("select from_tag as tag from ".$this->config["table_prefix"]."links where to_tag = '".mysql_real_escape_string($tag)."' order by tag"); }
%% I think replacing this by:
~& %%(php) function LoadPagesLinkingTo($tag) { return $this->LoadAll("select from_tag as tag from ".$this->config["table_prefix"]."links where to_tag = '".mysql_real_escape_string($tag)."' and latest = 'Y' order by tag"); }
%% might do the trick to avoid deceased pages - but please test!
~&--JavaWoman
====GetEnv is not a good idea!====
At ./wikka.php, you will see a line %%(php)<?php if (!$configfile = GetEnv("WAKKA_CONFIG")) $configfile = "wikka.config.php";?>%%
In the most cases, a website is hosted in a machine as a VirtualHost, this means that a number of websites share the same environment variables. If someone knows where your site is hosted, he can put his site at the same server, and use a script containing %%(php)<?php putenv('WAKKA_CONFIG=/home/hacker/config.php');?>%%. And all wikka sites on the same server will use his configuration file. The rest actions to take to hack your site will be as easy as eating sandwich.
Php doc says that an environment variable is altered only during the life of the script, but with my dev Easyphp's on windows, that is false. (I think a "new" environment variable keep its value, even on Linux).
I wanted to make a unique Wikka interface used by 3 sites on the same server. The best secure solution I found is to alter ./wikka.php like this :
%%(php)<?php
if (file_exists("wakka.config.php")) rename("wakka.config.php", "wikka.config.php");
#if (!$configfile = GetEnv("WAKKA_CONFIG")) $configfile = "wikka.config.php";
if (!$configfile && isset($GLOBALS['wikka_config'])) $configfile = $GLOBALS['wikka_config'];
if (!$configfile) $configfile = "wikka.config.php";
if (file_exists($configfile)) include($configfile);
and put the 2 files sitenumber2.php and .htaccess below at the root of the server number 2:
__sitenumber2.php:__
%%(php)<?php
$GLOBALS['wikka_config'] = "/path/to/altered_config.php";
chdir("/path/to/basewikka");
include('wikka.php');
?>%%
__.htaccess:__
%%<IfModule mod_rewrite.c>
RewriteRule ^(css|images|wikiedit2)/(.*)$ /path/to/basewikka/$1/$2 [L]
RewriteRule ^(.*)$ sitenumber2.php?wakka=$1 [QSA,L]
</IfModule>%%
--DotMG
~&''I've now written up my thoughts about a [[WikkaSecureConfig more secure way to handle Wikka's configuration]] (which should also provide also more flexibility). --JavaWoman''
===Expanded Text Search fails===
I tried an expanded Text-Search after [[http://wikka.jsnx.com/TextSearchExpanded?phrase=%2Bparameter+%2Blink +parameter +link]] and got the following error:
''Warning: Compilation failed: nothing to repeat at offset 1 in /.../actions/textsearchexpanded.php on line 33''
for every page.
--NilsLindenberg
~&''In my recent RE exploits I have found that a warning of this type comes up when a regular expression isn't quite correct (though not every attempt to match may bring up teh warning); haven't investigated further in textsearchexpanded.php though. --JavaWoman''
~&Php has a function : preg_quote that may help us. Or try this solution : DotMGTextSearchExpanded
Looking at **formatters/wikka.php** to find the cause of the two bugs listed below (found one), I notice to my horror that a **lot** of the regular expressions used there are actually incorrect. They allow such things as using a comma to indent a line (in addition to a tab, or ~, at the start of a line: **demo** in the SandBox, and in the list **below**!), or a comma in a WikiName (even at the start) or in an InterWiki link. That can't have been the intention - it's simply a matter of incorrect RE syntax. I'd become sort of "sensitized" to this phenomenon looking at DarTar's RE on ValidPageNames earlier today - now I see where he found an example (see my comment on that page on his RE!).
,''Note: see also [[,My,Page]] - yup, that's a real page now. ;-)''
~&Rather than simply fixing all the REs (and other REs all over the place...) I'd like to propose a more fundamental solution:
~&-create a "library" of RE building blocks to be used in the Wikka core (for an example of what I mean with building blocks see my propopsal for an alternative RE on ValidPageNames); simply create a separate file with define()s for these building blocks, and include them at the start of the main wikka.php file;
~&-gather all RE used in the Wikka core here (extensions/plugins could have their own set of defines - as long as they don't have conflicting names);
~&-now use **only** these building blocks when using REs anywhere in the Wikka core.
~&This should make it much easier to create both //correct//, and //consistent// regular expressions; any (near)duplicates will be much easier to discover, and fix.
~&
~&Probably best to leave this to just **after** the coming release, so we have a stable code base again. I volunteer to undertake this work. (Unlike some people, I happen to like REs.) :)
~&--JavaWoman
Have a look at the source of WikkaDevelopment, you will see that tabs and unordered lists for some reasons are not correctly parsed (actually after one edit, tabs were added at the beginning of each line). I'll try to figure out why this happens...
-- DarTar
~&Possible clue:
~&I just stumbled over the fact that the little list of "Useful pages" at the end of the default (installation-generated) ""HomePage"" had incorrect coding: The last list item (li) was not terminated, nor was the list itself (no closing ul tag). It took me a bit of trial and error to reproduce this - but have a look at my test code at the end of SandBox (now). Originally I thought that any list at the end of a page would be unterminated, but that turned out not to be the case. Then I hit on something else: the last list element on that default ""HomePage"" (not the one here) ands with a period. My test version on SandBox now also has the last element ending in a period ... and if you look at the (HTML) page source, you'll see it is indeed an unterminated list. Somehow that ending period (maybe in combination with end-of-page?) causes the Formatter never to close the list; take that ending period away, and it works normally. I tried a few variants, to check whether it might be an odd-even problem, but no: whether the number of list items is odd or even, if the last one ends in a period, the list isn't terminated.
~&
~&No difference whether it's anordered (ol) or unordered (ul) list, the formatter behaves the same way.
~&
~&And, BTW, if you look at the preview when editing, the HTML source of the **preview** actually contains a lot of Wiki code that shouldn't be there!
~&
~&I haven't dug in the Formatter yet to find the cause or whether end-of-page makes a difference...
~&--JavaWoman
MySQL 5+ isn't supported as it requires PHP to use the mysqli extension instead of plain old mysql. I hoped there would be a single file to change this, but there seems to be no database abstraction in this project at all.
-- DavidCarrington
~&I do not have access to a MySQL 5 server for testing. And judging by the feedback that I see here on Wikka, most other Wikka admins are using older versions of MySQL. However, I do like progress, so I looked at the documentation for the mysqli extension. I don't see any major issue here. It looks like the function calls are the same, they just have a different name. Instead of calling mysql_connect, you call mysqli_connect. Instead of calling mysql_query, you call mysqli_query. So on and so forth.
~&
~&It seems that we would just have to do a simple version check and call "mysql" functions for older versions, and "mysqli" functions for newer versions.
~&
~&Please correct me if I'm missing something. -- JsnX 26 Nov 2004
~~&I'm running MySQL 5 fine with the mysql_* functions. When you compile PHP, it's your choice to compile the mysql_* or mysqli_* functions. I chose to compile it with mysql_*, which is working fine for me. --BarkerJr
==Login Problem==
==User search - should be case-sensitive==
===Problem with "History"??===
I ran across this on another wikka implementation....
http://elvito.sv-city.de/wikka.php?wakka=RecentChanges
if you look at Sun, 22 Aug 2004 the second item down says
"" [ (20:46 CEST?) [history?] - TextSearch?phrase=ElVitoWakkaWiki? ? ppp-82-135-6-82.mnet-online.de ]"" which seems kinda wrong. -- Mike (aka GmBowen)
==Email Addresses==
Found several issues with how email addresses are validated / accepted / used; outlined on WikkaAndEmail - and I'm working on solutions. (Email is //complicated// and there's a whole bunch of standards (RFCs) involved.)
First part of the solutions now in WikkaEmailToolkit; while the toolkit is still incomplete, what's there now can be used as presented there (no dependencies on later components).
-- JavaWoman
Bugs I've found:
- Security: I was wondering whether it would be possible to store IPs for registered users as well. That way you can ban them via .htaccess if necessary.
- ''Last known IP or every IP they ever connect from? I'd be willing to store one last known IP per user. '' - JsnX
- ''Last known IP please :) Thanks.'' - Sam
- ''I'd suggest adding *two* distinct fields to ##wikka_users##: Last Login IP/Hostname + Last Login Time'' - DarTar
- ''I was also thinking of a way to ban users directly from the wiki (much in the same way as referrers are added to the blacklist of spammers). This might turn out easier to implement than a //user deleting action// (which was one of the ideas discussed [[UserAdmin here]])'' - DarTar
- Security: Single-click restore of previous versions (without copying/pasting).
- ''Yes, this will be implemented at some point.'' - JsnX
- I should point out that there is an alternative to copying/pasting.
- Go to the revisions page.
- Click the date and time link that you would like to revert back to.
- Click the 'Re-edit this old revision' button.
- Click the 'Store' button.
Thanks - Sam
- Mod_rewrite : take a look at FaviconDotIco and RobotsDotTxt
====Logout problem====
With Wikka Wakka Wiki 1.1.6.0. Php5
Login.
Go to Preferences/Logout, click the logout button
=> it goes to:
%%[[mypath]]/wikka.php?wakka=UserSettings?action=logout%%
So, it tries to find the "UserSettings?action=logout" page, doesn't and propose to create it.
The path should be:
%%[[mypath]]/wikka.php?wakka=UserSettings&action=logout%%
::c::
CategoryDevelopment
Deletions:
<p>If you have something to report:<br/>
<strong>First</strong> check if your issue is already being discussed on this page:</p><ul>
<li>If so: check if it has a link to a ticket:<ul>
<li>If so: <strong>follow that link</strong> and add your comment there</li>
<li>If not: add your comment to the issue <strong>on this page</strong></li></ul></li>
<li>If not: please use the <strong><a href="http://wush.net/trac/wikka/" target="_blank">issue tracker</a></strong> to report your <strong>new</strong> bug or issue. Again, <a href="http://wush.net/trac/wikka/search?ticket=on">search first</a> to make sure your issue has not been reported yet.</li></ul>
</div>""
<<==Read this first==
~-workarounds for unusual problems and temporary fixes for known bugs are listed at WikkaWorkarounds
~-general help can be found on the [[Docs:WikkaDocumentation Wikka documentation page]]
<<::c::
===== {{done}} Bugs reported on the tracker =====
===Wakka formatter: Indenting on first line===
[[Ticket:13]]
===No Registration Wikki===
[[Ticket:79]]
===Valid Email Addresses===
[[Ticket:80]]
[[Ticket:13]]
=== Indenting not working properly in handlers/page/edit.php ===
[[Ticket:85]]
[[Ticket:88]]
[[Ticket:1]]
[[Ticket:34]]
[[Ticket:80]]
See CharsetNotSupportedWorkaround
[[Ticket:90]]
===Purging should not remove the whole history of a page===
[[Ticket:93]]
===RSS feed action hangs or crashes browser if feed does not exist===
[[Ticket:95]]
[[Ticket:97]]
===Purging of pages not always happening===
[[Ticket:100]]
[[Ticket:104]]
[[Ticket:108]]
[[Ticket:231]]
[[Ticket:232]]
===Code tag % % ... % % problems===
[[Ticket:783]]
===== {{todo}} Bugs still to be checked/migrated =====
===the Blank on IE browser===
i just tested it on IE,firefox,opera;but only on IE it sometimes got blank page,nothing displaed,no code on it(so i think it's not coz the insert ads host,and my host don't gave ads).this not happened always,when you click the links,go to the new page,got a blank,then refresh it,it displayed.no this problem on firefox or opera.
but which is interesting,on your official site of Wikka,there is no this problem with IE blank.is there something wrong with the File permission?(exhausted with it),but when refresh the blank page,it displayed.
~&Details like the versions of your IE, your webserver and Mysql (and perhaps a link to the page) would be helpfull! NilsLindenberg
===remote (or local) won't load Wikka===
I just installed Wikka and it works fine on the localhost.
But if I want to access it from another machine, being it on the LAN or internet, I got an error message saying "connection refused when attempting to contact localhost."
my config setting is
"base_url" => "http://localhost/wikka/wikka.php?wakka=",
"rewrite_mode" => "0",
If I change the localhost to mydomain.com, I can access it from internet, but I can't load it on my localhost.
It's one or the other. Is there anything I did wrong?
~& Hi, this is a problem that depends on your server configuration and how it resolves virtual hosts. It is in no way a Wikka bug. You should contact your network administrator to address this issue -- DarTar
~~& I don't think so. I tried MediaWiki and it works fine. I can serve my web pages and that's fine. My server is behind a cable modem and a router. All ports are forwarded correctly. But I really think that the "base_url" syntex caused this problem.
~~~&Since you say you can access your site from the Internet if you use "base_url" => "http://mydomain.com/wikka/wikka.php?wakka=", you could simply edit your hosts file on your local machine and map mydomain.com to 1.0.0.127 - that way you can access the site on your local machine the same way as from the Internet. For accessing it from other machines on your LAN you may need to add a similar mapping (to the hosting machine's local IP address) to access it from there. -- JavaWoman
The following is a solution copied from comments of WikkaInstallation that I think resolves this issue (have not tested it though) --GiorgosKontopoulos 16/03/2006
The following solution will allow Wikka to work for a site that can be reached by multiple domain names (for example, a server that has one address when accessed via an intranet and a different address when accessed from the Internet):
Edit wikka.php.
//After
$wakkaConfig = array_merge($wakkaDefaultConfig, $wakkaConfig);)
//add the following line:
$wakkaConfig[base_url] = "http://".$_SERVER["SERVER_NAME"].($_SERVER["SERVER_PORT"] != 80 ? ":".$_SERVER["SERVER_PORT"] : "").$wakkaConfig[base_url];
Then, edit wikka.config.php and set base_url to contain just the path of your Wikki instead of the full URL
"base_url" = "/wikka/",
I may be reinventing the wheel here. It would be good if Wikka actually had a config option to autodetect the domain or require it in base_url. --Vincent -- 65.242.114.226 (2006-02-06 18:52:54)
===Wikka and WebDAV===
I've found that the .htaccess file (i think) prevents me from accessing a wikka folder using MacOS X's in built webdav client. I imagine that if the Rewrite stuff was less catch-all it might not have this effect, letting me edit wikka templates with ease rather than the terminal... thanks tom
Now.. and I don't get this... THIS has fixed it.. and it doesn't even seem to make sense (my install is in a folder called Wikka)... but when I try and change it ... it stops working again... My .htaccess file looks like this...
""RewriteEngine"" on
# ""RewriteCond"" %{REQUEST_FILENAME} -d
# ""RewriteRule"" ^(.*/[^\./]*[^/])$ $1/
""RewriteCond"" %{REQUEST_FILENAME} -f [OR]
""RewriteCond"" %{REQUEST_FILENAME} -d
""RewriteRule"" ^(.+) - [PT,L]
""RewriteCond"" %{REQUEST_URI} !/(Wikka/css|/Wikka/files|actions|dav|handlers|pages)
""RewriteRule"" ^(.*)$ wikka.php?wakka=$1 [QSA,L]
..... I don't get this... but hey, if it works...
===Wrong Links===
I get Links like
http://localhost/~ckl/Wikka/wikkaHomePage
http://localhost/~ckl/Wikka/wikkaCategoryCategory
and so on, instead of
http://localhost/~ckl/Wikka/wikka/HomePage
http://localhost/~ckl/Wikka/wikka/CategoryCategory
~& Open ##wikka.config.php## and check the value for ##base_url##: it should be ""http://localhost/~ckl/Wikka/wikka/"". BTW, you may also want to read ModrewriteInSubdirectoryWorkaround. Hope this helps -- DarTar
~~& Thank you for the help.
~~& If I use http://localhost/~ckl/Wikka/wikka/ the links are correct,
~~& but the css file is not found and I get messages like //Unknown method "page/HomePage.php"//. ModRewrite is off.
~~& If I use http://localhost/~ckl/Wikka/wikka the links are not correct and if I click HomePage I get
~~& Not Found The requested URL /home/ckl/public_html/Wikka/wikka.php was not found on this server.
===Logout fails silently or takes long time on ""SourceForge"" hosted site ===
Here are the symptoms :
When you click on the **logout** button, it returns to UserSettings page but does nothing.
You can browse other pages, it keeps saying 'You are XXXX' even after logging out.
IMHO, I think it may be a problem with the ""SourceForge"" hosting space as I've tried logout/login on different Wikka sites already hosted by ""SourceForge"" -> same issue.
On my local LAMP, it works fine so I suggest there are some PHP, MOD_PHP, APACHE issues on ""SourceForge"".
--PhilippeVincent 10 Aug 2005
~& it may not be a bug since i noticed there are some problems with mysql on sourceforge.
~& when a query takes too long, the server just cut the connection.
~& So, if the logout process takes a bit too long according to the short mysql latency, it fails over...silently.
~& --PhilippeVincent
===.htaccess settings yields consistent error 403 on Apache===
Original issue: running Apache 2.0.54, with the presence of .htaccess file I kept getting error 403. Originally I moved .htaccess and set the base page in the conf to using the long url. After looking around I realized that the fix, in some instances (see requirements below) is to set the option ##""FollowSymLinks""## to on in your .htaccess file.
Problem: your Apache configuration files don't have ##""FollowSymLinks""## on
Solution: use the .htaccess below IFF (if, and only if) you have the following options set in the configuration file for the directory: ##""AllowOverride Options""## or ##""AllowOverride All""##, because you're going to need to override the settings in your local .htaccess file.
%%(apache)
### STOP REFERRER SPAM
SetEnvIfNoCase Referer ".*(adultsite|picturesplace|learnthebiz|pi-o|erotica|ghettoinc|port5|bulk-email|camgirls|paris-hilton|modelos|kredit|handyflirt24|versicherung|wwww|erotower|krank|x-1000|flirtnet|blowjob|agedwife|in-the-vip|boysfirsttime|milf|captain-stabbin|tranny|Kontakt|erotik|fetish|frauen|hardcore|fick|krankenversicherung|jinnan-cross|8thstreet|xxx|XXX|ficken|fuck).*" BadReferrer
order deny,allow
deny from env=BadReferrer
<IfModule mod_rewrite.c>
Options +FollowSymLinks
RewriteRule ^(.*)$ wikka.php?wakka=$1 [QSA,L]
</IfModule>
The + is optional, but I chose to put it in since I'm overriding default settings.
--KoG
~& I'm also get the same error 403. I tried KoG workaround but it gives error 500 (Internal Server Error). The only solution that works with me to delete .htaccess file. Is this implies security risks? I don't know till now. --Ikhnaton2
~~&There is no //security// risk with removing .htaccess. In fact, only the Apache web server can do anything with it but Wikka can function just fine running on other webservers (even IIS :)). Also, there are hosting plans where Apache is used but the use of .htaccess is not allowed - which might result in it either being ignored, or possibly a 403 error. So, while a .htaccess file (with Apache) may make life with Wikka easier (some spam defense, and pretty URLs) it's safe to remove it.---That said, if adding ##""Options +FollowSymLinks""## changes the 403 error into a 500 error, you might want to check the ServerErrorWorkaround page (and look at ModrewriteInSubdirectoryWorkaround as well). --JavaWoman
~~~&IIS7 is supposed to support something akin to htaccess. But yes, some apache installations don't allow for overriding either. I those cases you'll need to speak with your administrator, or find a different/better host. Of course, Wikka works fine without mod_rewrite. As for the other portion of .htaccess, it's for stopping spambots. Of course, if you set your Wikka ACLs so only registered users can post/comment (as necessary and appropriate to your purpose), you should be ok. If you find yourself hammered by Wiki-attacking bots, adjust your security as needed (or talk to JW - she's been dealing with spammers I think) --KoG
~~~~The .htaccess should probably be removed or renamed in the distribution. Once upgrading to 1.1.6.2 i wasn't able to use wikka untill i removed the htaccess file that it comes with.-BrendonB
~~~~~&Can't confirm that, as the 1.1.6.2Alpha, 1.1.6.2Beta, and the 1.1.6.2-released all worked without the .htaccess file being an issue on my system. --WazoO 11Jul06
===Messages delayed===
===Using compression===
//Moved here from a comment so it won't get "lost". --JavaWoman//
Wikka doesn't work with zlib.output.compression = On, it would be nice if it did.
-- 81-178-214-34.dsl.pipex.com (2005-01-06 22:31:13)
~&''The screenshots no longer seem to exist --JavaWoman
""http://gmbowen.educ.unb.ca/wikitest/bug.jpg
http://gmbowen.educ.unb.ca/wikitest/bug3.jpg""''
~&I've never seen anything like it and can't reproduce your screenshots - can you tell us exactly which browser/version/OS (all three!) you are using? To me it feels more like a browser problem than a Wikka problem... Also: given the spacing they look as if they belong to the "small print" line "Valid XHTML 1.0 Transitional? :: Valid CSS? :: Powered by Wikka Wakka Wiki 1.1.6.0?" in the footer - can you maek a screen shot that includes that line? --JavaWoman
~~&Sure. Win 98, IE 6.0.2800.1106 (most recent updates of both as far as I know). I've closed and rebooted several times since leaving this note and it's still there (but farther up the page now, in the middle of the second code block, but with the same spacing). You're right that it's "from" that small print line....those images (and you cannot right-click and get properties on them....they're visible, but NOT there, if you get what I mean) are NOT on that line as a matter of fact and the spacing corresponds exactly. I've never seen it at any other site, but have noticed it a few times at wikka recently...but not always. It persistently (which means ALMOST always) shows up on the bannermaker page when I go there. -- GmBowen
~~~&Further questions: Does it depend on whether or not you are showing comments on the/a page? And which stylesheet are you using for viewing this site? Any difference when you choose a different stylesheet (TestSkin)? (BTW, that 'infinity' symbol is not an image, it's just a character.) --JavaWoman
~~~~&No, showing comments or not has no effect. I just looked NOT showing comments and the symbols were halfway up the page in the code block. I'm using the default stylesheet as far as I know (I've not changed it)...and when I do switch to yours they're still there (on a different vertical part of the page, but it varied before anyways. Oh, right, that's a character. Well, what's weird is you can't highlight it either. It's like a ghost image. Weird. --GmBowen
~~&TEST: Please try with my stylesheet again, to see if that makes any difference now (I tweaked it). --JavaWoman
~~&Answer: Sorry to say, the floaters are still there in IE even using your stylesheet. (FYI....I tried using your stylesheet in Netscape 4.7 & it crashed the TestSkin page. I can go to other pages with your stylesheet in Netscape, but I get the WSOD on the TestSkin page and can't change to anything else. Later...closing & re-opening NS allowed me to re-set it to the wikka.css....and it "crashed" the page again. Obviously there are broader NS problems....wikka's homepage doesn't load at all using any skin in NS 4.7.) --GmBowen
~~~&Forget about NS 4.x - it doesn't really support stylesheets. The only solution for that would be detecting it and not giving it a stylesheet at all. I'd like to trace the problem with IE6 though ... even though I cannot reproduce it with my IE6 on Win2K. It may not be standards-compliant, but there's still an awful lot of people using it, even when FireFox is taking market share from it now. I have to think about another approach but I still suspect it's something to do with the (valid) stylesheet that trips up IE6. Thinking... --JavaWoman
~~~~&Any chance it's a videocard memory issue? It's a new ATI card, but that the images jump around on re-loads is interesting to me. It's like the video driver is doing something as video memory fills in different ways. --GmBowen
~~~~~&Sounds unlikely to me - and they're not images, remember? Just text, but bits of text **positioned** by means of a stylesheet. Any chance of testing with a different machine, different video card, but same Browser+OS? Meanwhile, I'll sleep on it. :) --JavaWoman
~~&Another idea just struck me: are you using some security software (like Norton security) or a proxy (like The Proxomitron or Privoxy) that sits between your browser and the Internet? That might "do" things to the page to cause a different display. I'm asking because I know The Proxomitron can cause display problems - and the problem seems to be unique to your machine/browser... Another thing to try would be to get Mozilla or Firefox and see if that shows the same problem on your machine. --JavaWoman
~~~~&I'm out of ideas, Mike, except that it's //probably// something to do with the stylesheet and IE (more likely since you don't see it with FF) - plus something else... Try to find a pattern, is all I can suggest. Note down at which pages it happens. See what shakes out. --JavaWoman
~&Mike, was this ever resolved? --JavaWoman
===Login Problem===
===User search - should be case-sensitive===
CategoryDevelopmentSuggestions
