Wiki source for SuggestionsArchive

Show raw source

=====Resolved Suggestions=====

''This is an archival page from the earlier time of development. Please use only the [[ | Tracker]] for everything related to bugs or feature requests.''

//this are older suggestions (from the SuggestionBox) which have been implemented or otherwise handled or replied to.//

===Font action===
I didn't know where to put this, so here goes.
I've been adapting a script that uses GD to make an image of some text using a specified font. I'll post it at FontActionInfo

BTW - The work you've done - especially with CSS styling - is very, very good. Keep it up ;-)

~&We have a nice page called CodeContributions and the "Category User Contributions" (without the space) -- NilsLindenberg

=== Typo correction in embedded Wiki Edit 2 ===

For the new ( release, line 645 of wikiedit2/wikiedit2.js should be fixed to say:
%% s += " Ctrl+Shift+Minus - Horizontal line\n";%%
not "horisontal." I've already fixed it in my local copy, but no sense in perpetuating errors. :) --MovieLady
~&Thanks to eagle-eyed JsnX it's //aready// fixed in beta4 :) but thanks for the note! --JavaWoman
~~& Marvelous, thanks! :) --MovieLady

=== Question: PHP 4.3 and "mysql_escape_string()"? ===

For the Wikka Wakka Wiki you need at least PHP 4.3 because the "mysql_real_escape_string()" in wakka.php is only available in PHP 4.3. A lot of hoster just offering PHP 4.1 or 4.2. Then you have to replace "mysql_real_escape_string()" with "mysql_escape_string()". What was the reason for the replacement in the new release? Again: Keep on the good work.
-- SkyWalk
~&The reason is that ##mysql_real_escape_string()## is more secure than ##mysql_escape_string()## so we want to take advantage of that; but as implemented this left users of older versions of PHP in the cold. A workaround for this will be in version (see above) - now avaliable as a [[HomePage | public beta]]. --JavaWoman

===Compatibility with PHP 4.1.x===
with Debian GNU/Linux 3.0 (woody) are installed PHP 4.1.2 and this version don't support "mysql_real_escape_string" function.
temporary fix on wikka.php head:

if ( ! function_exists("mysql_real_escape_string") )
function mysql_real_escape_string($string)
return mysql_escape_string($string);

~&This will be in version - now avaliable as a [[HomePage | public beta]]. --JavaWoman

===Don't let old pages get indexed===
//(moved to WikkaSpamFighting)//

===User page===
If someone registers as a new user and chooses a Wikiname, his wikinamepage is empty. I think it would be nice, if the page whould be created from the wiki, containing a text with perhaps a welcome, some (Wiki)rules and usefull pages (this text should be stored somewhere so that it could be customized from the WikiAdmin). The page should automatically belong to the category user. Regards, NilsLindenberg

===Non-breaking space in forced links===
Sometimes a forced link has a phrase as link description with spaces for readability but where these spaces should **not** cause wrapping in the middle of the string - in other words, the spaces really should be non-breaking spaces. Unfortunately, specifying ## ## will (unlike here) result in the entity becoming visible as an entity instead of as the character it encodes.

It should be possible to either specify ## ## where needed and have it result in the actual character (i.e., keep the actual entity rather than "escaping" it), or (less desirable) there should be another mechanism to indicate where link text should not be broken. It can't be automatic since non-breaking may not be desirable at every point either.

//**Note:** Actually, with the beta version running on this site, this demonstrates how the new htmlspecialchars_unicode() function is indeed buggy - as I pointed out on WikkaDevelopment. The solution is presented [[WikkaDevelopment | there]] now (look for **htmlspecialchars_unicode()**).//
~&Now found on HtmlSpecialChars - JW

===User Control===
Is there an easy way to not allow registration? I would like to have it so that I can control the registration process, not let just anyone sign-up.

... (Nils proposing a solution)
~&Look at UserRegistration for the first version, or [[ | try it]] --NilsLindenberg

A nice contribution Nils. If you want to go further with fiddling with the code for registration, I've thought it would be useful if there was a feature that required a password from an administrator to be able to register so that if you were going to register you put in your user info (as now) and a password you've obtained from the admin that allows you to register....for instance, in this way a teacher could set up a wikki with registration "on" and send a note to all of the parents with the registration password so that they could register....outsiders couldn't register, only those with the registration key. Possibly a quite useful feature to many potential user groups. -- GmBowen

===Cookies and logging out===
This issue issue moved to StayingLoggedIn!

==Page viewed counter==
It occurs to me that some kind of "counter" for how many times the wikipage has been viewed might be a useful "action" for somebody to be able to use...this way a page author would know how often somebody has gone to the page & this might help focus development (especially for those keeners that have multiple pages/projects). [and I agree with the contributor below....Wikkawiki is great software]
~&I completed altering a script and modifying the wikka code for this.....go to GmBowenCounter for the php script and the necessary alterations. --GmBowen

===Mod rewrite and a problem===
Hi there. First, I'd like to thank you all for your work with Wikka -- it's just great! I have some problems though. On my [[ | experimental wikka site]] I'm not able to use mod_rewrite, which is annoying by itself, but when I set the rewrite parameter in the config file to "0", the scripts add an <input> tag to the code at the beginning of the footer (which is a form if I'm correct). This input tag gets no close tag so I added a "/" at the end. Will this screw up things somehow or is this little fix enough? -- JockeAndersson
~&Good catch. Adding the end slash should be fine. It will be added by default in the next Wikka release. -- Jsnx

===Remove underline from links in footer===
Another thing. I feel a bit stupid for asking, but how do I remove the underline from the links in the footer. This is not set in the style sheet nor added in footer.php. Ot not in a place where I see at least. -- JockeAndersson
~&Jocke, in the style sheet [wikka.css by default], add "text-decoration: none;" to the smallprint style. Or am I not understanding the problem? %%(css)
.smallprint a {
color: #987;
text-decoration: none;
}%% -- JsnX

It doesn't really do it. I tried it before, and I added the code snippet again, but without the wanted result. Where in the code is the underlining set? The header link also has it's text underlined and I can't find where this is set. The stylesheet doesn't contain any such tags, and I can't seem to find them in the other files. -- JockeAndersson

The reason the above addition to smallprint doesn't work is that the links are visited meaning the pseudo-class a:visited must be defined as well with "text-decoration: none" in it. There is no definition for a:visited in the css by default. Perhaps this should be added to Wikka's code? -- JockeAndersson

~&Sure, I'll add it. Just curious though, what web browser are you using? Internet Explorer does not show underlined links as you have least not for me. -- JsnX

I'm currently using Mozilla Firefox, but I'm testing pages in IE as well. The underlines were only visible in Firefox. IE is usually the one to screw up page rendering, not being fully standards-compliant and all. Oh, and the code could use an a:active definition as well. Be sure to define them in correct order though: a visited hover active. W3C were specific about that for some reason. -- JockeAndersson

~&Thanks for the tip. By the way, your site looks awesome. -- JsnX
~~&You really think so? Thanks!! :) Much of the general layout comes from A List Apart's site, but adapted to my needs. I've had a site running for a while but can't find the time to update it properly. I believe Wikka will change all that and am seriously thinking of replacing my ordinary site with a Wikka wiki. The forum will still be phpbb, but the site itself could really benefit from the pros of Wikka. I second [[MarkHissinkMuller]]'s suggestions for improvement. Especially the possibility to manage ACLs based on user groups as well as individual users, would be great. -- JockeAndersson
~~~& I tried to do something like this at ACLsWithUserGroups. --ChristianBarthelemy

===Improved pageindex action===
I've provided the php code for a modification of the pageindex.php action which will improve showing the index in high-use sites. You can see the code at GmBowen. I'm not a programmer myself, but have one working for me and he modified the code to have it work like this. You can see it in action (LOL) if you go to (as it's set up it's defaulting to show "all", but you can set that to any single available letter if you wish by adding a parameter, e.g., ""{{pageindex start="C"}}""). -- Mike Bowen

===Show comments by default===
And isn't it possible to have the comments shown by default for every user?
-- TromboneFreakus

~&at the moment not. maybe if someone has time... do you mean every registered user, or every user? --NilsLindenberg
~&I don't understand the question. Can you please be more specific? --DarTar
~~&Oops, I thought they didn't show up by default, but it apperently does. -- TromboneFreakus

And will there be translations?
-- TromboneFreakus

~&An internalization/localization project is currently under discussion, but it requires a major overhaul of the code, so don't expect it to appear in the very next releases -- DarTar

===Missing Pages===
Is there a reason why missing pages are marked through ##<a href="..."><span class="missingpage">Page name</span></a>## instead of ##<a class="missingpage">Page name</a>##? This makes control on ##hover## behavior difficult.
-- DarTar

~&None that I know of. I made the change. Better now? -- JsnX

===Public ownership of pages===
I think defaulting to "Public" ownership would be more beneficial than Nobody. Nobody allows anyone to gain ACL rights to main pages if the proper setup steps are not taken. This is a major security issue and should have been addressed when the "Public" role was created.

~&This is not a security issue within the context of a wiki. Wikis are supposed to be open by design. In addition, admins can change ownership whenever they want. However, personally I agree with your point, and this will be considered for a future release. - JsnX

===Double-click event===
I'm being picky here (again!). I've noticed that the double-click edit event is used on the BODY tag. One issue I've experienced is that while entering a comment, I couldn't double-click a word (to highlight and replace it) without triggering the edit screen. My suggestion is to put it on the DIV class="page" tag. -- Sam
~&Added your suggestion in Wikka Thanks for pointing this out. -- JsnX

CategoryDevelopmentSuggestions CategoryDevelopmentArchive
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki