Comparing revisions for SuggestionBox
- [6347] 2005-02-26 19:53:14 by FernandoBorcel (unregistered user)
- [19976] 2008-05-25 13:26:47 by NilsLindenberg (unregistered user) [replaced old discussion with link]
Additions:
{{lastedit show="3"}}
Feedback is welcomed and appreciated. Use the form or edit this page.
**Please help to keep this page readable: add new entries at the //top// (right below the form) and add a header!**
>>=== Bugs vs. feature suggestions ===
Please post issues/bugs to the appropriate page:
~-General bugs/issues: WikkaBugs
~-CSS layout issues: WikkaCSS
**See also:**
~-WikkaSpamFighting for spam-related issues
~-WikkaWorkarounds for specific platforms
~-WikkaOptimization
>>{{feedback}}::c::
%% RewriteCond %{REQUEST_URI} !=/favicon.ico
===Section Editing Redux===
Instead of a full blown section editing implementation why not just implement a tag like '<WikiPage>' which inserts the contents of WikiPage (no comments) at the markers location. <WikiPage x> would insert the first x lines of the WikiPage into the current page. And/or <WikiPage Header> would pull just the section of the page which is demarked by Header and EOP or next header. Such sections can be inserted in a special color/block/font/whatever and automatically link back to the original page for editing. The goal is to provide better editing granularity and readability on pages which have lots of information density. Could also be used to mimic blog functionality. -KarmaTester
----
Right now (1.1.6.0), if a non-existant page is requested, the wiki returns status code 200, which will cause the page to be indexed by search engine spiders. It'd probably be better to return 404 (not found) or 410 (gone) or include robots exclusion meta tags in the pages that don't exist. --BarkerJr
~&Ah, maybe this is why a now non-existent page that I deleted 2 months ago is still getting 50hits or so a day from the porn/vicodin/viagra sites that linked to it (don't ask //me// why...it was a completely inoccuous page)...at least according to the referrers database table. --GmBowen
~&See RobotFriendly. --DotMG
=== //Kant-en-klaar// code blocks ===
A micro-idea before going to bed. We all know it's a bad idea to copy code blocks from the formatted version of a page.
If I want to test some freshly posted code, here's what I have to do:
~1) open a ##/raw## version of the page;
~1) scan the page for the chunk of code I want to save (this can be pretty difficult on long source pages with no syntax highlighting);
~1) open a text editor;
~1) copy the code block;
~1) paste it in the text editor;
~1) save the file.
Wouldn't it be nice to have at the end of each code block a small link pointing to a handler allowing the user to download the code block with the right name and the right extension just //with one click//?
See GrabCodeHandler for a first proposal -- DarTar
(The following was copied from a comment on ModRewrite -- JavaWoman)
//Hi, I discovered that the default .htaccess included did not work for my setup up. I needed to include ""RewriteBase"" /directory/ as well since Wikka is installed in a subdirectory. I hope this helps anyone having trouble getting Wikka to work.
-- h-67-102-97-191.mclnva23.covad.net (2005-02-11 04:49:37)//
The installer **correctly** deduces the base path for the configuration; it could conceivably also detect if it's sitting in a subdirectory, and if so, dynamically change the .htaccess file and include the correct ""RewriteBase"" statement to take care of this. --JavaWoman
I use wikka as wiki engine of [[http://diantn.free.fr my page]].
IMO, the wikka.php file is too big to be one single file. I suggest that we separate the Wakka class into new file, say Wakka.class.php
And then in the wikka.php, e.g at line where the Wakka class previously located, simply we put:
include ('Wakka.class.php');
-- DiN
~&DiN, this is a //very// good idea. I fact, the idea had crossed my mind already, but thanks for the reminder. :) Indeed, a class belongs in a file of its own. --JavaWoman
~~&Maybe a folder called classes? the handlers/page/diff has a bunch of classes inside, too. --NilsLindenberg
~~~&With my current proposed structure on WikkaCodeStructure, it would go into the library folder; classes that are shared, into library/common. I prefer a //functional// separation rather than one based on coding format. --JavaWoman
===phpMyEdit in Wikka===
I've set up a demo of [[http://www.jsnx.com/wikka-dev/SuggestionBox phpMyEdit running within Wikka]]. This would be useful for anyone wanting to directly interact with MySQL tables from a Wikka page. -- JsnX
~&I assume this is meant for admins only but ... Could you add some explanation? I looked but don't have a clue how to use it. What are the radio buttons for, for instance? What's the "V" button at the top? The UI is very confusing. --JavaWoman
~~& Jsnx, that's interesting. I think the idea is worth consideration. I have used phpMyEdit as an interface to allow my users to store their profiles in the DB when I still was a MySQL newbie :) and it's true that it allows a number of tricky things (especially cross-reference between tables). So I think a plugin for integrating phpMyEdit within Wikka pages might be a nice extension. You probably know though that all the interface options can only be set by editing the source, or were you thinking of allowing some kind of admin access to the interface options? And be honest, are you thinking of phpMyEdit as a sort of replacement for my baby admin actions, aren't you?! In a sense this might be interesting, but it would really be unnecessary compared to what we can do by creating direct calls to the DB using core functions. Why heavily tweak an external script to do something wikka-like if we can already use something that only needs core functions? --- Moreover, when you perform operations on pages (like 'add', 'copy' or 'delete') you generally want to do something more complicated than just modify single records of the page table. Using phpMyEdit as a sort of proxy for a page admin action can lead to major inconsistencies in the page structure. --- And, JW, the "v" button is for filtering the table ;-) -- DarTar
~~~&DarTar, that's silly. The admin actions that you have developed are looking fantastic! I was never thinking of using phpMyEdit to replace your actions. I'm using phpMyEdit to interface with non-Wikka tables; I like to see the data shown from Wikka, and I also like being able to use Wikka formatting within the data. It might help if I gave an example of how I use phpMyEdit. [... I'll write an example later on ...] -- JsnX
~~~&Filtering? Well first it's not obvious, nor explained; but I just went back and tried pressing the "v" button - and I get three other mystifying buttons in return. Frankly, I don't want to use something as badly-designed as this. Shudder. DarTar, your Admin functions may need some refinement, but mystifying they are not. Let's stick with those, and build on them. Sorry, JsnX, but this doesn't get my vote. --JavaWoman
~~~~&Thanks for the comments. I expected there would be some reservations about including this in Wikka. I too have some reservations about phpMyEdit. However, with that said, I also find it to be a **very useful** tool which I will continue to use. It doesn't matter to me whether phpMyEdit is ever an official Wikka component because using it requires zero modifications to the Wikka code -- there will be no ongoing maintenance when upgrading to new Wikka versions. It's not my intention to support this, but if someone wants to use it, I'm happy to make my modified phpMyEdit version available. I'm proposing this as an official "unofficial Wikka add-on". :) -- JsnX
~&I am interested by the idea to interact with MySQL tables from a Wikka page. Would you please share the updated phpMyEdit code? --ChristianBarthelemy
~~&Yes, I plan to play around with it for a few more days, then I'll upload the code and some instructions. -- JsnX
~~~&Hi Jason, I am still interested to know more about this... --ChristianBarthelemy
~&Well, Jason, I do think it would help I you would explain what you are using this **for** (especially if not for Wikka administration); I'd also like to know then why you chose phpMyEdit and not another browser-based client - and why a browser-based client in the first place. I've only ever tried phpMyAdmin and found it lacking because it tends (tended) to work on single tables only. I quickly switched to "real" clients that are more powerful and allow me to build queries involving several tables if needed, so consistency can be maintained. I have a bunch of handy tools (for Windows), all free: for design, administration and maintenance. And though I do have phpMyAdmin available, I don't intend to use it. --JavaWoman
~~&My bet is that Jason's using it to fix the pages where I've (inadertently) submitted double percent signs as part of submitted code so that the history feature works properly. {grin} --GmBowen
~~~&LOL! But - "inadvertently"? Using double percent signs should be possible in code - and if not, that's a bug in Wikka, not your fault! (Not that I have a solution for that yet, though I have been thinking about that problem.) --JavaWoman
===Support for (Technorati) tags===
I think it might be interesting to provide Wikka support for (Technorati) "**tags**". "Tags" in this context are simple keywords that help identify and categorize web content, in particular blog posts. Such keywords coupled with a ping system can be used by remote servers to retrieve fresh content for specific topics. See for instance how technorati.com aggregates fresh information about [[http://www.technorati.com/tag/wiki wikis]] from a number of sources.
[[http://www.technorati.com/help/tags.html More information on Technorati tags]]
~&Seems like we need to update our RSS (feed) implementation first... --JavaWoman
Page output to an Adobe pdf file using FPDF.
(copied from WikkaDevelopment --NilsLindenberg)
==Signature==
(copied from WikkaFaq, but perhaps better at WantedFormatters? --NilsLindenberg)
Does Wikka support automatic user signatures in pages (not comments)? I need some code so that users don't need to enter their username and time/date when they are working on a page in ThreadMode. I've searched in the docs, but I could not find anything about this, any ideas?
-- JeroenJansen (2005-01-28 11:35:43)
~& Jeroen, there is a hack for automatically adding a user's signature in WakkaWiki posted by NickK on his [[http://wakkawiki.de/NickK homepage]]. It should be easy to adapt to Wikka. -- DarTar
~~& Dartar, just saw your reply. Thanks for the hint! --JeroenJansen
== Easy way of adding links ==
MatthewLangham
== Create rewrite rules on install ==
~//copied from comment on WikkaInstallation --JavaWoman//
Since I installed wikka in a subdirectory under the domain root I needed to add the following to the .htaccess file just under """RewriteEngine on""":
""RewriteBase"" /subdirectory/
Devs, how about writing the .htaccess rules at the same time you write out the wikka.config.php file since you automatically pickup the wiki base location at that point?
-kt
-- KarmaTester (2005-01-26 06:52:07)
== Image dimensions ==
The [[AddingImages image]] action really needs the ability to specify image height and width. :) --MovieLady
==Clearing ACLs==
There should be a button on the ACL page to "Reset ACLs to Default". What this would do is delete the record for the current page from the acls table. There is a distinction between setting the ACLs to the sites default values and not having ACLs defined for a page. If the ACLs are set and the default values get changed, the page will remain at the set values. However, if no ACLs are defined, the page will always use the default values.
To help show the distinction, there should be a visual indicator on the ACL handler page which states whether the page has ACLs defined or is using the site's default values. Basically, just check for a record in the acls table for the current page, and display a message accordingly. -- JsnX
It would nice to have the registration function check to make sure there isn't another account with the same email already registered so that one person doesn't clutter up the db with multiple accounts. (Or at least the configurable option to check for only one email/one account.)
It should also then be easier (I would think) to use it to essentially ban by email address; if the registration process checked for an email in the user table, found that it was already in use and didn't let the person create a new username, one could use the wonderful ACLsWithUserGroups hack that Christian created to make a list of banned users by username. Yeah, yeah, folks who want to abuse the system could always create new email addresses on the various free sites, but that's an awful lot of work, and this would at least slow down some of it. --MovieLady
~&You know how many TestUsers my Wikka already has? *g* This should do the job (this time no config option, sorry jw :)
~&%%(php)
function ExistsEmail($email)
$count = 0;
$query = "SELECT COUNT(email)
FROM ".$this->config['table_prefix']."users
WHERE email='".mysql_real_escape_string($email)."'";
if ($r = $this->Query($query))
{
$count = mysql_result($r,0);
mysql_free_result($r);
}
return ($count > 0) ? TRUE : FALSE;
~&Place this function in wikka.php right after function UserWantsComments(). And change in actions/usersettings.php the following line: %%(php)
else if (strlen($password) < 5) $error = "Password too short.";
%% to %%(php)
else if (strlen($password) < 5) $error = "Password too short.";
else if ($this->ExistsEmail($email)) $error = "You already have a username.";
~&--NilsLindenberg
~~& LOL I can imagine. Thanks so much for this - I'll try it out this evening. --MovieLady
~& Speaking of registration control, note to self: make a configuration option to turn off new account registrations. Some sites might be private and not want people registering. Admin privilege should override this and still show the registration fields in usersettings, to save the admin from having to go into the database manually to add acounts or some other hack. -- JsnX
~~& (you saw UserRegistration by Nils? I think it, or something like it, should be standard. mike)
~~~& Doh! I somehow missed that. That's pretty much what I had in mind. Nice job, Nils! :) -- JsnX
~~~~&Thank you. About your Admin-adding-user case: that's an addition to UserAdmin, not for usersettings. --NilsLindenberg
~~~&there's also code around that uses GD & that could be built onto Nils' code that generates a "registration password" automatically and outputs it as a distorted graphic image.....the code is intended to befuddle auto spam registers & thus stop open-registration sites from being hit by spam bots that register themselves as users. Ultimately, as the bots become more sophisticated I think we'll have to use something like that or else sites like this one (with open registration) will be victimized. [[http://www.bluecopia.com/form.php Here]] and [[http://www.horobey.com/demos/codegen/ here]] are examples of what I mean (I like the simplicity of the first version in the second example). -- GmBowen
~~~~&Yes, "Captcha" is an old trick - it will keep out some bots (but not all) and it will keep many people out, too, like those who are visually handicapped (not just people who are totally blind - being colorblind may be enough to be defeated by such tricks). Add a sound equivalent? Well, there are people who are deaf **and** blind. Are we going to deny them access to our wikis? I'm not in favor of making Wikka **in**accessible when we should be working towards making it **more** accessible. --JavaWoman.
== RSS options ==
It would be wonderful to be able to choose what kind of RSS feed is created for a page. For example, ""{{rss}}""/""{{rss show="1"}}"" could show only the headlines and the update field (current setting), ""{{rss show="2"}}"" could show a blurb of the updated info, ""{{rss show="3"}}"" could show the whole update. --MovieLady
== Embed a blurb from a news page into another page? ==
==Logging-out==
== Backlinks ==
== Language file ==
I would be nice to see all phrases put into a single file. This would allow to translate the wiki in a few hours without changes every single file.
~&Look at DotMgs approach at WikkaInternationalization. But at least it should work for languages in the range of the "normal" (ascii?) code. If you are interested, you should start a page in where we can collected the hard-coded sentences (would wait for the .6 relase, anyway). --NilsLindenberg
~~&The most flexible and powerful way to support i18n is still Gettext which is supported by PHP. If we go in that direction (likely), manually creating a "language file" is needless work since Gettext does all that automatically for you. And it supports options for handling plurals and such which simple string-to-string language files cannot handle. The problem is that code needs to be written in a way to properly be able to use Gettext, so that translatable strings **do** contain whole phrases with punctuation and **do not** contain any HTML markup (actually this is true for simple laguage files as well). Currently our code is not "in shape" for i18n though, so that's the first job we'll have to tackle. --JavaWoman
== User names ==
==Finally using CVS?==
I apologize since this idea has been suggested before, and I believe the developers are working to implement it already. However, with the beta of 1.1.6.0 released, I think it would be a good time now to start using CVS. This allows for better collaboration and as each bug fix or feature is implemented, developers and testers can grab new copies and work out further bugs. In addition, this allows more outsiders to participate in the code development process and not wait as long from the transition of releases.
Also, I am willing to help with the CVS migration process if needed and help anyone who is interested in learning how to use CVS.
~&There is a cvs version of wikka at [[http://sourceforge.net/projects/wikka/ sourceforge]]. Just has to be updated --NilsLindenberg
~~&Actually, Nils, we need a lot more than "just updating" the CVS at Sourceforge. We need to integrate CVS in our development process - and develop a process for doing so. That requires a bit of planning... :) And while at least some of us have experience with source control systems, at the same time some of us **don't** have experience with CVS specifically, so a bit of study will be required before we can start planning. Help with learning how to use CVS //well// from someone who has experience with it would certainly be welcome, Mike! Thanks for the offer. --JavaWoman ''(reading manuals....)''
~~~& The "just was meant as an addition to existing ("Of course" would have been better, though :). I just wanted to point out the existing (or better non-existing ;) usage of sourceforge, in case Mike does not no. It is obviously to me that you have to integrate it into your development-process, otherwise it would not be out of date (*duck & run* ;) --NilsLindenberg
~~~~& Hi Nils. Actually, I did find Wikka's CVS repository at SF weeks ago, but I forgot to mention it in my above post. JavaWoman pretty much echoed my thoughts. We need to actively use CVS/update it constantly as changes are made. I run a project called [[http://xcomic.sourceforge.net Xcomic]] that uses Sourceforge's CVS a lot, so I have some experience with that. In addition, I recently set something up for my project that I think will be pretty cool if Wikka decides to really use CVS: a commit mailing list. Anytime someone makes a change to the CVS (modification, addition, or deletion), an automatically generated email will be sent to anyone on the suscribers list detailing the files changed and the areas changed (a diff). In any case, version 1.1.6.0-beta4 should be committed and access should be given to a few main developers. Then smaller contributors (like me) can send code changes to the main developers who subsequently commit. --MikeXstudios
~~~~~&Mike, I for one would welcome your insights in using CVS. Both DarTar and I have some ideas about how we want it set up - but no experience in doing so (in CVS). May I suggest you join our [[http://lists.sourceforge.net/lists/listinfo/wikka-developers developers mailing list]]? For this type of thing I think that would be the best medium to discuss thoughs and methods. I like the idea of a commit mailing list. --JavaWoman
==Stopping Spammers getting Google Juice==
//(moved to WikkaSpamFighting)//
==List of special actions?==
==Give control over HTML==
It would be nice to see a template engine in Wikka to give the users the full control over the HTML source. Smarty is always a good choice.
~& I would love to see Wikka adopt some type of template system. I think that its is sorely needed. Changing the look of Wikka requires tedious editing of php files, and alot of the time it is non-obvious where you need to go to edit such files. Another alternative to [[http://smarty.php.net Smarty]] could be [[http://wiki.ciaweb.net/yawiki/index.php?area=Savant Savant]]. --KickTheDonkey
~~&While I use and like Smarty very much (and it's quite fast), it's rather "heavy" for Wikka, I think. I just had a look at Savant2 which I hadn't heard of before. It looks like a good fit, is lightweight and easy to use. A templating system like this would also provide much more flexibility for Wikka admins to have control over page structure and layout. I'll want to play with it some (in combination with Wikka), but my first impression based on documentation and code is very favorable. More when I've had a chance to exercise it. --JavaWoman
~~~&I'm sorry JW, but what do you mean by Smarty being rather "heavy" for Wikka? Resource-wise? Hard to use / implement? Difficult for the end user? -- FernandoBorcel
==Allow spaces in pagetitle==
==User-defined formatting rules==
==Local links==
It would be nice if a link to the same host as the wikka install was not flagged as 'external'. I've added a 'hack' to my personal page: KickTheDonkey. Works fine here.
==Idea for Category Support==
moved to CategorySystemOverhaul, it is the better place, thanks DarTar
--ArpY
~& ArpY, take a look at CategorySystemOverhaul for an open discussion on how to improve the category system -- DarTar
A "compile category" action. Right now, if I go to CategoryDocumentation I can see a list of all of the pages in this category...but it still requires a lot of snooping to find what I want. As an administrator I'd like to provide a pdf "booklet" of all of that output for users to download. To make this now would mean going to and printing each and every page (using a software tool, TO a pdf file). Ugh. An action that let me go ""{{compile category="CategoryDocumentation"}}"" to generate a single web page of all of that documentation would be quite useful because then I could just print it to a pdf file once.....then I could provide a link to the PDF file so users could download it and print it off.
==Section Editing ==
- http://c2.com/cgi/wiki?SectionEditing
- It makes allows you to flow and edit much quicker.
- Each topic should have a corresponding edit button. This allows your to edit each section with out breaking your flow.
- http://www.splitbrain.org/dokuwiki/wiki:section_editing
==Compatibility & Installer==
==Standard date and time format==
Although I'm all for using the ISO date/time format as we see in the timestamp of the footer of every page, I note that several other parts of Wikka use different date/time formats. I'd like to see an approach where this is standardized.
Proposal:
~-Define date-time format (or separately date and time, as well as a way to combine them) in the configuration; use the ISO format as a default (in the initial configuration, as well as when no format is defined in the config).
~-Use this format wherever date and/or time are formatted.
~-Make using the configured formats a requirement for every Wikka extension (that displays date/time information) to be included with the distribution.
I realize that in principle it's possible to pick up formats from a locale but for a Wikka targeted at an international audience this may not be the best approach, and for a Wikka with a "local" audience it may not be either if it's hosted on a (public) server outside that country - hence the idea to define a format in the configuration.
--JavaWoman
~''Agreed -- DarTar''
==Handling the config==
==Markup for code not to be shown==
==Online editing of mindmaps would be great==
(copied from Sourceforge.net --NilsLindenberg)
It would be great, if users should work together on mindmaps.
Maybe by downloading/ Open With FreeMind and then having a possiblity to save changes in FreeMind directly back to the online mindmap.
==Tables ==
For the discussion on tables in Wikka, take a look at WikkaTables.
~&See also TableAction for a preliminary solution. --JavaWoman
==Wikka Exporting/Importing ==
Just added a few thoughts [[WikkaFilters here]]
-- DarTar
==how to format code to get two % characters without space together?==
I want to produce a code sample page in wikka with DOS batch code. The code syntax requires two percent characters together to markup a variable. Example: % %variable% % (without the spaces). Wikka always tries to format the text as code, even if I format the DOS code inside a code block, even if I %% marked it as code with two percent characters like this here%%
Is there a solution? I could not find a literal entity for "percent"
''You could use % which is the numerical entity reference for the percent sign: % - but *within* a code block an entity is "escaped" - a problem by itself, and so it wouldn't help. See: %%some text with %% embedded in it%%
But it should be possible to just plug in a piece of code without having to worry about which characters and strings to somehow escape - maybe the double percent isn't such a happy choice for Wiki markup of "code"; should we find a character combination that is less likely to be a syntactical meaning in an artificial language? (And how do you markup Wiki markup as **code**?) -- JavaWoman''
How about the € (euro) Symbol? Or is it to new? --NilsLindenberg
''The main problem with the € (euro) symbol is not that it's new, but that it's hard to type: most keyboards don't have the symbol. And it might occur in code as well (imagine a sample conversion routine). Wiki markup should be easy to type. So we need a symbol (or sumbol combination, maybe), that's:
~1) easy to type
~2) not likely to occur in any programming code (note "likely" - you can never completely exclude it; think of APL!)
The **exclamation mark** still seems to be "free", and although a single exclamation mark often is used for negation in programming languages (and in comments, of course) a double one isn't (just don't use rows off exclamation marks in your code comments); or else a combination of an exclamation mark with something else (that is not itself an "operator" in languages). Maybe we should do a search (Google?) to check whether **!!** or a combo is actually an operator in any language.
-- JavaWoman''
==markup of diff pages==
==showing comments==
Working on a test installation, I found the user setting "Show comments by default" did not work. Testing it here, I found it doesn't work here, either.
Haven't dug in the code yet to find where this should happen (but will).
I'm quite happy with Wikka's capabilities out of the box - good starting point! :) I'll likely stay with it - but I'll probably make some extensions... (such as an option to require confirmation of a registration before allowing edit access - validates email).
Great work! JavaWoman
It does work.... just not as might be expected. Comment preference is stored for each page as you browse the wiki. So, if you browse a few pages with comments not showing, it remembers this. Then if you update your preferences and return to the same pages, it still remembers that your previous preference was not to see comments on those pages.
Try this:
- Browse to UserSettings and check off "Show comments by default" and click "Update Settings".
- Now **close all browser windows**
- Open back up your browser and go to the same pages......
- Comments are now showing by default, right?
- JsnX
Right. I see it does work. ;) Somewhat, um, counterintuitive, though. So I guess my suggestion then becomes that when a user configuration is changed, this change should immediately be stored in the user session/cookie so it's active right from that moment (without closing the browser). That would, I think, be more in line with expected behavior. Possible? (I haven't looked at that area of the code yet.) --JavaWoman.
==Language support==
I was searching almost whole site to check what kind of languages are supported by this wiki. I was unsuccessful. Is it possible to put somewhere (main page, release note, futures section…) some information about languages they are supported?
Thanks MDD
== Problem: Scrolling in the search - field ==
It is me again! What is the function of the "Please add a note on your edit" - field? Again and again: Keep on the good work.
this note is shown in some lists like the RecentChanges and the page revisions. it's just a little helper to keep the wiki organized and has no effect on the page itself. use it whenever you can to drop a short abstract of what has changed, even if you have corrected some typos to let others know that no essential changes were made. it is a really useful feature --DreckFehler
maybe we could have a level switch on that feature, constituting it obligatory, optional, or off... an addittion to the conf will be neccessary thought.. --GeorgePetsagourakis
== Problem: Five Line Breaks ==
== DB Export ==
==Code block formatting==
==Various suggestions==
==Other method to attach files==
==Installation problem - UTF-8?==
==Add page link & other suggestions==
==Using FPDF with Wikka==
Not so much a suggestion, more a request although it may be useful to others.
I have been using FPDF from [[http://www.fpdf.org FPDF ]] to export content from a database to pdf files.
I would like to extend my usage of FPDF to wikka by adding a hyperlink to the top of my wikka pages which would allow me to post the page tag or page id to the FPDF script for exporting the content into a pdf file.
The link would be in the form similar to
http://www.mysite.com/script.php?id=
Can anyone tell me how I can extract the page tag or page id from the wikka_pages table in order to do this.
====Resolved Suggestions====
== Question: PHP 4.3 and "mysql_escape_string()"? ==
For the Wikka Wakka Wiki 1.1.4.0 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.
~&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 1.1.6.0 (see above) - now avaliable as a [[HomePage public beta]]. --JavaWoman
== Typo correction in embedded Wiki Edit 2 ==
For the new (1.1.6.0) 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 1.1.6.0 beta4 :) but thanks for the note! --JavaWoman
~~& Marvelous, thanks! :) --MovieLady
==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 1.1.6.0 - 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 1.1.6.0 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()**).//
--JavaWoman
==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.
--BooYa
... (Nils proposing a solution)
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
~Look at UserRegistration for the first version, or [[http://www.niehle.info/UserSettings try it]] --NilsLindenberg
==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
- I think it would be nice if you could use wikka markup (""**bold**, //italics//, __underline__, etc."") inside of tables. - RichardTerry
~&Richard, thanks for the feedback. It is on my agenda to look at another solution for tables. My plan is to allow straight HTML table syntax after running it through the "safehtml" checker. But I need to check that there are no security risks with this first. Also, I'll take a peak at your suggestion too. -- JsnX
~&Check out my proposal for an extended TableAction which does provide this. (TableAction is intended as a preliminary solution until we have table markup.) --JavaWoman
==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 [[www.bronzeworks.org/Wikka/ 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?
''Good catch. Adding the end slash should be fine. It will be added by default in the next Wikka release. -- Jsnx''
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? -- JsnX''
~~~.smallprint a {
~~~color: #987;
~~~text-decoration: none;
~~~}
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 described...at 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 MarkHissinkMullers]] 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.
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 http://bowen4-srv.lakeheadu.ca/wikitxt/wakka.php?wakka=PageIndex (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
CategoryWikka
CategoryDevelopment
Feedback is welcomed and appreciated. Use the form or edit this page.
**Please help to keep this page readable: add new entries at the //top// (right below the form) and add a header!**
>>=== Bugs vs. feature suggestions ===
Please post issues/bugs to the appropriate page:
~-General bugs/issues: WikkaBugs
~-CSS layout issues: WikkaCSS
**See also:**
~-WikkaSpamFighting for spam-related issues
~-WikkaWorkarounds for specific platforms
~-WikkaOptimization
>>{{feedback}}::c::
%% RewriteCond %{REQUEST_URI} !=/favicon.ico
===Section Editing Redux===
Instead of a full blown section editing implementation why not just implement a tag like '<WikiPage>' which inserts the contents of WikiPage (no comments) at the markers location. <WikiPage x> would insert the first x lines of the WikiPage into the current page. And/or <WikiPage Header> would pull just the section of the page which is demarked by Header and EOP or next header. Such sections can be inserted in a special color/block/font/whatever and automatically link back to the original page for editing. The goal is to provide better editing granularity and readability on pages which have lots of information density. Could also be used to mimic blog functionality. -KarmaTester
----
Right now (1.1.6.0), if a non-existant page is requested, the wiki returns status code 200, which will cause the page to be indexed by search engine spiders. It'd probably be better to return 404 (not found) or 410 (gone) or include robots exclusion meta tags in the pages that don't exist. --BarkerJr
~&Ah, maybe this is why a now non-existent page that I deleted 2 months ago is still getting 50hits or so a day from the porn/vicodin/viagra sites that linked to it (don't ask //me// why...it was a completely inoccuous page)...at least according to the referrers database table. --GmBowen
~&See RobotFriendly. --DotMG
=== //Kant-en-klaar// code blocks ===
A micro-idea before going to bed. We all know it's a bad idea to copy code blocks from the formatted version of a page.
If I want to test some freshly posted code, here's what I have to do:
~1) open a ##/raw## version of the page;
~1) scan the page for the chunk of code I want to save (this can be pretty difficult on long source pages with no syntax highlighting);
~1) open a text editor;
~1) copy the code block;
~1) paste it in the text editor;
~1) save the file.
Wouldn't it be nice to have at the end of each code block a small link pointing to a handler allowing the user to download the code block with the right name and the right extension just //with one click//?
See GrabCodeHandler for a first proposal -- DarTar
(The following was copied from a comment on ModRewrite -- JavaWoman)
//Hi, I discovered that the default .htaccess included did not work for my setup up. I needed to include ""RewriteBase"" /directory/ as well since Wikka is installed in a subdirectory. I hope this helps anyone having trouble getting Wikka to work.
-- h-67-102-97-191.mclnva23.covad.net (2005-02-11 04:49:37)//
The installer **correctly** deduces the base path for the configuration; it could conceivably also detect if it's sitting in a subdirectory, and if so, dynamically change the .htaccess file and include the correct ""RewriteBase"" statement to take care of this. --JavaWoman
I use wikka as wiki engine of [[http://diantn.free.fr my page]].
IMO, the wikka.php file is too big to be one single file. I suggest that we separate the Wakka class into new file, say Wakka.class.php
And then in the wikka.php, e.g at line where the Wakka class previously located, simply we put:
include ('Wakka.class.php');
-- DiN
~&DiN, this is a //very// good idea. I fact, the idea had crossed my mind already, but thanks for the reminder. :) Indeed, a class belongs in a file of its own. --JavaWoman
~~&Maybe a folder called classes? the handlers/page/diff has a bunch of classes inside, too. --NilsLindenberg
~~~&With my current proposed structure on WikkaCodeStructure, it would go into the library folder; classes that are shared, into library/common. I prefer a //functional// separation rather than one based on coding format. --JavaWoman
===phpMyEdit in Wikka===
I've set up a demo of [[http://www.jsnx.com/wikka-dev/SuggestionBox phpMyEdit running within Wikka]]. This would be useful for anyone wanting to directly interact with MySQL tables from a Wikka page. -- JsnX
~&I assume this is meant for admins only but ... Could you add some explanation? I looked but don't have a clue how to use it. What are the radio buttons for, for instance? What's the "V" button at the top? The UI is very confusing. --JavaWoman
~~& Jsnx, that's interesting. I think the idea is worth consideration. I have used phpMyEdit as an interface to allow my users to store their profiles in the DB when I still was a MySQL newbie :) and it's true that it allows a number of tricky things (especially cross-reference between tables). So I think a plugin for integrating phpMyEdit within Wikka pages might be a nice extension. You probably know though that all the interface options can only be set by editing the source, or were you thinking of allowing some kind of admin access to the interface options? And be honest, are you thinking of phpMyEdit as a sort of replacement for my baby admin actions, aren't you?! In a sense this might be interesting, but it would really be unnecessary compared to what we can do by creating direct calls to the DB using core functions. Why heavily tweak an external script to do something wikka-like if we can already use something that only needs core functions? --- Moreover, when you perform operations on pages (like 'add', 'copy' or 'delete') you generally want to do something more complicated than just modify single records of the page table. Using phpMyEdit as a sort of proxy for a page admin action can lead to major inconsistencies in the page structure. --- And, JW, the "v" button is for filtering the table ;-) -- DarTar
~~~&DarTar, that's silly. The admin actions that you have developed are looking fantastic! I was never thinking of using phpMyEdit to replace your actions. I'm using phpMyEdit to interface with non-Wikka tables; I like to see the data shown from Wikka, and I also like being able to use Wikka formatting within the data. It might help if I gave an example of how I use phpMyEdit. [... I'll write an example later on ...] -- JsnX
~~~&Filtering? Well first it's not obvious, nor explained; but I just went back and tried pressing the "v" button - and I get three other mystifying buttons in return. Frankly, I don't want to use something as badly-designed as this. Shudder. DarTar, your Admin functions may need some refinement, but mystifying they are not. Let's stick with those, and build on them. Sorry, JsnX, but this doesn't get my vote. --JavaWoman
~~~~&Thanks for the comments. I expected there would be some reservations about including this in Wikka. I too have some reservations about phpMyEdit. However, with that said, I also find it to be a **very useful** tool which I will continue to use. It doesn't matter to me whether phpMyEdit is ever an official Wikka component because using it requires zero modifications to the Wikka code -- there will be no ongoing maintenance when upgrading to new Wikka versions. It's not my intention to support this, but if someone wants to use it, I'm happy to make my modified phpMyEdit version available. I'm proposing this as an official "unofficial Wikka add-on". :) -- JsnX
~&I am interested by the idea to interact with MySQL tables from a Wikka page. Would you please share the updated phpMyEdit code? --ChristianBarthelemy
~~&Yes, I plan to play around with it for a few more days, then I'll upload the code and some instructions. -- JsnX
~~~&Hi Jason, I am still interested to know more about this... --ChristianBarthelemy
~&Well, Jason, I do think it would help I you would explain what you are using this **for** (especially if not for Wikka administration); I'd also like to know then why you chose phpMyEdit and not another browser-based client - and why a browser-based client in the first place. I've only ever tried phpMyAdmin and found it lacking because it tends (tended) to work on single tables only. I quickly switched to "real" clients that are more powerful and allow me to build queries involving several tables if needed, so consistency can be maintained. I have a bunch of handy tools (for Windows), all free: for design, administration and maintenance. And though I do have phpMyAdmin available, I don't intend to use it. --JavaWoman
~~&My bet is that Jason's using it to fix the pages where I've (inadertently) submitted double percent signs as part of submitted code so that the history feature works properly. {grin} --GmBowen
~~~&LOL! But - "inadvertently"? Using double percent signs should be possible in code - and if not, that's a bug in Wikka, not your fault! (Not that I have a solution for that yet, though I have been thinking about that problem.) --JavaWoman
===Support for (Technorati) tags===
I think it might be interesting to provide Wikka support for (Technorati) "**tags**". "Tags" in this context are simple keywords that help identify and categorize web content, in particular blog posts. Such keywords coupled with a ping system can be used by remote servers to retrieve fresh content for specific topics. See for instance how technorati.com aggregates fresh information about [[http://www.technorati.com/tag/wiki wikis]] from a number of sources.
[[http://www.technorati.com/help/tags.html More information on Technorati tags]]
~&Seems like we need to update our RSS (feed) implementation first... --JavaWoman
Page output to an Adobe pdf file using FPDF.
(copied from WikkaDevelopment --NilsLindenberg)
==Signature==
(copied from WikkaFaq, but perhaps better at WantedFormatters? --NilsLindenberg)
Does Wikka support automatic user signatures in pages (not comments)? I need some code so that users don't need to enter their username and time/date when they are working on a page in ThreadMode. I've searched in the docs, but I could not find anything about this, any ideas?
-- JeroenJansen (2005-01-28 11:35:43)
~& Jeroen, there is a hack for automatically adding a user's signature in WakkaWiki posted by NickK on his [[http://wakkawiki.de/NickK homepage]]. It should be easy to adapt to Wikka. -- DarTar
~~& Dartar, just saw your reply. Thanks for the hint! --JeroenJansen
== Easy way of adding links ==
MatthewLangham
== Create rewrite rules on install ==
~//copied from comment on WikkaInstallation --JavaWoman//
Since I installed wikka in a subdirectory under the domain root I needed to add the following to the .htaccess file just under """RewriteEngine on""":
""RewriteBase"" /subdirectory/
Devs, how about writing the .htaccess rules at the same time you write out the wikka.config.php file since you automatically pickup the wiki base location at that point?
-kt
-- KarmaTester (2005-01-26 06:52:07)
== Image dimensions ==
The [[AddingImages image]] action really needs the ability to specify image height and width. :) --MovieLady
==Clearing ACLs==
There should be a button on the ACL page to "Reset ACLs to Default". What this would do is delete the record for the current page from the acls table. There is a distinction between setting the ACLs to the sites default values and not having ACLs defined for a page. If the ACLs are set and the default values get changed, the page will remain at the set values. However, if no ACLs are defined, the page will always use the default values.
To help show the distinction, there should be a visual indicator on the ACL handler page which states whether the page has ACLs defined or is using the site's default values. Basically, just check for a record in the acls table for the current page, and display a message accordingly. -- JsnX
It would nice to have the registration function check to make sure there isn't another account with the same email already registered so that one person doesn't clutter up the db with multiple accounts. (Or at least the configurable option to check for only one email/one account.)
It should also then be easier (I would think) to use it to essentially ban by email address; if the registration process checked for an email in the user table, found that it was already in use and didn't let the person create a new username, one could use the wonderful ACLsWithUserGroups hack that Christian created to make a list of banned users by username. Yeah, yeah, folks who want to abuse the system could always create new email addresses on the various free sites, but that's an awful lot of work, and this would at least slow down some of it. --MovieLady
~&You know how many TestUsers my Wikka already has? *g* This should do the job (this time no config option, sorry jw :)
~&%%(php)
function ExistsEmail($email)
$count = 0;
$query = "SELECT COUNT(email)
FROM ".$this->config['table_prefix']."users
WHERE email='".mysql_real_escape_string($email)."'";
if ($r = $this->Query($query))
{
$count = mysql_result($r,0);
mysql_free_result($r);
}
return ($count > 0) ? TRUE : FALSE;
~&Place this function in wikka.php right after function UserWantsComments(). And change in actions/usersettings.php the following line: %%(php)
else if (strlen($password) < 5) $error = "Password too short.";
%% to %%(php)
else if (strlen($password) < 5) $error = "Password too short.";
else if ($this->ExistsEmail($email)) $error = "You already have a username.";
~&--NilsLindenberg
~~& LOL I can imagine. Thanks so much for this - I'll try it out this evening. --MovieLady
~& Speaking of registration control, note to self: make a configuration option to turn off new account registrations. Some sites might be private and not want people registering. Admin privilege should override this and still show the registration fields in usersettings, to save the admin from having to go into the database manually to add acounts or some other hack. -- JsnX
~~& (you saw UserRegistration by Nils? I think it, or something like it, should be standard. mike)
~~~& Doh! I somehow missed that. That's pretty much what I had in mind. Nice job, Nils! :) -- JsnX
~~~~&Thank you. About your Admin-adding-user case: that's an addition to UserAdmin, not for usersettings. --NilsLindenberg
~~~&there's also code around that uses GD & that could be built onto Nils' code that generates a "registration password" automatically and outputs it as a distorted graphic image.....the code is intended to befuddle auto spam registers & thus stop open-registration sites from being hit by spam bots that register themselves as users. Ultimately, as the bots become more sophisticated I think we'll have to use something like that or else sites like this one (with open registration) will be victimized. [[http://www.bluecopia.com/form.php Here]] and [[http://www.horobey.com/demos/codegen/ here]] are examples of what I mean (I like the simplicity of the first version in the second example). -- GmBowen
~~~~&Yes, "Captcha" is an old trick - it will keep out some bots (but not all) and it will keep many people out, too, like those who are visually handicapped (not just people who are totally blind - being colorblind may be enough to be defeated by such tricks). Add a sound equivalent? Well, there are people who are deaf **and** blind. Are we going to deny them access to our wikis? I'm not in favor of making Wikka **in**accessible when we should be working towards making it **more** accessible. --JavaWoman.
== RSS options ==
It would be wonderful to be able to choose what kind of RSS feed is created for a page. For example, ""{{rss}}""/""{{rss show="1"}}"" could show only the headlines and the update field (current setting), ""{{rss show="2"}}"" could show a blurb of the updated info, ""{{rss show="3"}}"" could show the whole update. --MovieLady
== Embed a blurb from a news page into another page? ==
==Logging-out==
== Backlinks ==
== Language file ==
I would be nice to see all phrases put into a single file. This would allow to translate the wiki in a few hours without changes every single file.
~&Look at DotMgs approach at WikkaInternationalization. But at least it should work for languages in the range of the "normal" (ascii?) code. If you are interested, you should start a page in where we can collected the hard-coded sentences (would wait for the .6 relase, anyway). --NilsLindenberg
~~&The most flexible and powerful way to support i18n is still Gettext which is supported by PHP. If we go in that direction (likely), manually creating a "language file" is needless work since Gettext does all that automatically for you. And it supports options for handling plurals and such which simple string-to-string language files cannot handle. The problem is that code needs to be written in a way to properly be able to use Gettext, so that translatable strings **do** contain whole phrases with punctuation and **do not** contain any HTML markup (actually this is true for simple laguage files as well). Currently our code is not "in shape" for i18n though, so that's the first job we'll have to tackle. --JavaWoman
== User names ==
==Finally using CVS?==
I apologize since this idea has been suggested before, and I believe the developers are working to implement it already. However, with the beta of 1.1.6.0 released, I think it would be a good time now to start using CVS. This allows for better collaboration and as each bug fix or feature is implemented, developers and testers can grab new copies and work out further bugs. In addition, this allows more outsiders to participate in the code development process and not wait as long from the transition of releases.
Also, I am willing to help with the CVS migration process if needed and help anyone who is interested in learning how to use CVS.
~&There is a cvs version of wikka at [[http://sourceforge.net/projects/wikka/ sourceforge]]. Just has to be updated --NilsLindenberg
~~&Actually, Nils, we need a lot more than "just updating" the CVS at Sourceforge. We need to integrate CVS in our development process - and develop a process for doing so. That requires a bit of planning... :) And while at least some of us have experience with source control systems, at the same time some of us **don't** have experience with CVS specifically, so a bit of study will be required before we can start planning. Help with learning how to use CVS //well// from someone who has experience with it would certainly be welcome, Mike! Thanks for the offer. --JavaWoman ''(reading manuals....)''
~~~& The "just was meant as an addition to existing ("Of course" would have been better, though :). I just wanted to point out the existing (or better non-existing ;) usage of sourceforge, in case Mike does not no. It is obviously to me that you have to integrate it into your development-process, otherwise it would not be out of date (*duck & run* ;) --NilsLindenberg
~~~~& Hi Nils. Actually, I did find Wikka's CVS repository at SF weeks ago, but I forgot to mention it in my above post. JavaWoman pretty much echoed my thoughts. We need to actively use CVS/update it constantly as changes are made. I run a project called [[http://xcomic.sourceforge.net Xcomic]] that uses Sourceforge's CVS a lot, so I have some experience with that. In addition, I recently set something up for my project that I think will be pretty cool if Wikka decides to really use CVS: a commit mailing list. Anytime someone makes a change to the CVS (modification, addition, or deletion), an automatically generated email will be sent to anyone on the suscribers list detailing the files changed and the areas changed (a diff). In any case, version 1.1.6.0-beta4 should be committed and access should be given to a few main developers. Then smaller contributors (like me) can send code changes to the main developers who subsequently commit. --MikeXstudios
~~~~~&Mike, I for one would welcome your insights in using CVS. Both DarTar and I have some ideas about how we want it set up - but no experience in doing so (in CVS). May I suggest you join our [[http://lists.sourceforge.net/lists/listinfo/wikka-developers developers mailing list]]? For this type of thing I think that would be the best medium to discuss thoughs and methods. I like the idea of a commit mailing list. --JavaWoman
==Stopping Spammers getting Google Juice==
//(moved to WikkaSpamFighting)//
==List of special actions?==
==Give control over HTML==
It would be nice to see a template engine in Wikka to give the users the full control over the HTML source. Smarty is always a good choice.
~& I would love to see Wikka adopt some type of template system. I think that its is sorely needed. Changing the look of Wikka requires tedious editing of php files, and alot of the time it is non-obvious where you need to go to edit such files. Another alternative to [[http://smarty.php.net Smarty]] could be [[http://wiki.ciaweb.net/yawiki/index.php?area=Savant Savant]]. --KickTheDonkey
~~&While I use and like Smarty very much (and it's quite fast), it's rather "heavy" for Wikka, I think. I just had a look at Savant2 which I hadn't heard of before. It looks like a good fit, is lightweight and easy to use. A templating system like this would also provide much more flexibility for Wikka admins to have control over page structure and layout. I'll want to play with it some (in combination with Wikka), but my first impression based on documentation and code is very favorable. More when I've had a chance to exercise it. --JavaWoman
~~~&I'm sorry JW, but what do you mean by Smarty being rather "heavy" for Wikka? Resource-wise? Hard to use / implement? Difficult for the end user? -- FernandoBorcel
==Allow spaces in pagetitle==
==User-defined formatting rules==
==Local links==
It would be nice if a link to the same host as the wikka install was not flagged as 'external'. I've added a 'hack' to my personal page: KickTheDonkey. Works fine here.
==Idea for Category Support==
moved to CategorySystemOverhaul, it is the better place, thanks DarTar
--ArpY
~& ArpY, take a look at CategorySystemOverhaul for an open discussion on how to improve the category system -- DarTar
A "compile category" action. Right now, if I go to CategoryDocumentation I can see a list of all of the pages in this category...but it still requires a lot of snooping to find what I want. As an administrator I'd like to provide a pdf "booklet" of all of that output for users to download. To make this now would mean going to and printing each and every page (using a software tool, TO a pdf file). Ugh. An action that let me go ""{{compile category="CategoryDocumentation"}}"" to generate a single web page of all of that documentation would be quite useful because then I could just print it to a pdf file once.....then I could provide a link to the PDF file so users could download it and print it off.
==Section Editing ==
- http://c2.com/cgi/wiki?SectionEditing
- It makes allows you to flow and edit much quicker.
- Each topic should have a corresponding edit button. This allows your to edit each section with out breaking your flow.
- http://www.splitbrain.org/dokuwiki/wiki:section_editing
==Compatibility & Installer==
==Standard date and time format==
Although I'm all for using the ISO date/time format as we see in the timestamp of the footer of every page, I note that several other parts of Wikka use different date/time formats. I'd like to see an approach where this is standardized.
Proposal:
~-Define date-time format (or separately date and time, as well as a way to combine them) in the configuration; use the ISO format as a default (in the initial configuration, as well as when no format is defined in the config).
~-Use this format wherever date and/or time are formatted.
~-Make using the configured formats a requirement for every Wikka extension (that displays date/time information) to be included with the distribution.
I realize that in principle it's possible to pick up formats from a locale but for a Wikka targeted at an international audience this may not be the best approach, and for a Wikka with a "local" audience it may not be either if it's hosted on a (public) server outside that country - hence the idea to define a format in the configuration.
--JavaWoman
~''Agreed -- DarTar''
==Handling the config==
==Markup for code not to be shown==
==Online editing of mindmaps would be great==
(copied from Sourceforge.net --NilsLindenberg)
It would be great, if users should work together on mindmaps.
Maybe by downloading/ Open With FreeMind and then having a possiblity to save changes in FreeMind directly back to the online mindmap.
==Tables ==
For the discussion on tables in Wikka, take a look at WikkaTables.
~&See also TableAction for a preliminary solution. --JavaWoman
==Wikka Exporting/Importing ==
Just added a few thoughts [[WikkaFilters here]]
-- DarTar
==how to format code to get two % characters without space together?==
I want to produce a code sample page in wikka with DOS batch code. The code syntax requires two percent characters together to markup a variable. Example: % %variable% % (without the spaces). Wikka always tries to format the text as code, even if I format the DOS code inside a code block, even if I %% marked it as code with two percent characters like this here%%
Is there a solution? I could not find a literal entity for "percent"
''You could use % which is the numerical entity reference for the percent sign: % - but *within* a code block an entity is "escaped" - a problem by itself, and so it wouldn't help. See: %%some text with %% embedded in it%%
But it should be possible to just plug in a piece of code without having to worry about which characters and strings to somehow escape - maybe the double percent isn't such a happy choice for Wiki markup of "code"; should we find a character combination that is less likely to be a syntactical meaning in an artificial language? (And how do you markup Wiki markup as **code**?) -- JavaWoman''
How about the € (euro) Symbol? Or is it to new? --NilsLindenberg
''The main problem with the € (euro) symbol is not that it's new, but that it's hard to type: most keyboards don't have the symbol. And it might occur in code as well (imagine a sample conversion routine). Wiki markup should be easy to type. So we need a symbol (or sumbol combination, maybe), that's:
~1) easy to type
~2) not likely to occur in any programming code (note "likely" - you can never completely exclude it; think of APL!)
The **exclamation mark** still seems to be "free", and although a single exclamation mark often is used for negation in programming languages (and in comments, of course) a double one isn't (just don't use rows off exclamation marks in your code comments); or else a combination of an exclamation mark with something else (that is not itself an "operator" in languages). Maybe we should do a search (Google?) to check whether **!!** or a combo is actually an operator in any language.
-- JavaWoman''
==markup of diff pages==
==showing comments==
Working on a test installation, I found the user setting "Show comments by default" did not work. Testing it here, I found it doesn't work here, either.
Haven't dug in the code yet to find where this should happen (but will).
I'm quite happy with Wikka's capabilities out of the box - good starting point! :) I'll likely stay with it - but I'll probably make some extensions... (such as an option to require confirmation of a registration before allowing edit access - validates email).
Great work! JavaWoman
It does work.... just not as might be expected. Comment preference is stored for each page as you browse the wiki. So, if you browse a few pages with comments not showing, it remembers this. Then if you update your preferences and return to the same pages, it still remembers that your previous preference was not to see comments on those pages.
Try this:
- Browse to UserSettings and check off "Show comments by default" and click "Update Settings".
- Now **close all browser windows**
- Open back up your browser and go to the same pages......
- Comments are now showing by default, right?
- JsnX
Right. I see it does work. ;) Somewhat, um, counterintuitive, though. So I guess my suggestion then becomes that when a user configuration is changed, this change should immediately be stored in the user session/cookie so it's active right from that moment (without closing the browser). That would, I think, be more in line with expected behavior. Possible? (I haven't looked at that area of the code yet.) --JavaWoman.
==Language support==
I was searching almost whole site to check what kind of languages are supported by this wiki. I was unsuccessful. Is it possible to put somewhere (main page, release note, futures section…) some information about languages they are supported?
Thanks MDD
== Problem: Scrolling in the search - field ==
It is me again! What is the function of the "Please add a note on your edit" - field? Again and again: Keep on the good work.
this note is shown in some lists like the RecentChanges and the page revisions. it's just a little helper to keep the wiki organized and has no effect on the page itself. use it whenever you can to drop a short abstract of what has changed, even if you have corrected some typos to let others know that no essential changes were made. it is a really useful feature --DreckFehler
maybe we could have a level switch on that feature, constituting it obligatory, optional, or off... an addittion to the conf will be neccessary thought.. --GeorgePetsagourakis
== Problem: Five Line Breaks ==
== DB Export ==
==Code block formatting==
==Various suggestions==
==Other method to attach files==
==Installation problem - UTF-8?==
==Add page link & other suggestions==
==Using FPDF with Wikka==
Not so much a suggestion, more a request although it may be useful to others.
I have been using FPDF from [[http://www.fpdf.org FPDF ]] to export content from a database to pdf files.
I would like to extend my usage of FPDF to wikka by adding a hyperlink to the top of my wikka pages which would allow me to post the page tag or page id to the FPDF script for exporting the content into a pdf file.
The link would be in the form similar to
http://www.mysite.com/script.php?id=
Can anyone tell me how I can extract the page tag or page id from the wikka_pages table in order to do this.
====Resolved Suggestions====
== Question: PHP 4.3 and "mysql_escape_string()"? ==
For the Wikka Wakka Wiki 1.1.4.0 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.
~&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 1.1.6.0 (see above) - now avaliable as a [[HomePage public beta]]. --JavaWoman
== Typo correction in embedded Wiki Edit 2 ==
For the new (1.1.6.0) 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 1.1.6.0 beta4 :) but thanks for the note! --JavaWoman
~~& Marvelous, thanks! :) --MovieLady
==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 1.1.6.0 - 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 1.1.6.0 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()**).//
--JavaWoman
==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.
--BooYa
... (Nils proposing a solution)
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
~Look at UserRegistration for the first version, or [[http://www.niehle.info/UserSettings try it]] --NilsLindenberg
==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
- I think it would be nice if you could use wikka markup (""**bold**, //italics//, __underline__, etc."") inside of tables. - RichardTerry
~&Richard, thanks for the feedback. It is on my agenda to look at another solution for tables. My plan is to allow straight HTML table syntax after running it through the "safehtml" checker. But I need to check that there are no security risks with this first. Also, I'll take a peak at your suggestion too. -- JsnX
~&Check out my proposal for an extended TableAction which does provide this. (TableAction is intended as a preliminary solution until we have table markup.) --JavaWoman
==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 [[www.bronzeworks.org/Wikka/ 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?
''Good catch. Adding the end slash should be fine. It will be added by default in the next Wikka release. -- Jsnx''
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? -- JsnX''
~~~.smallprint a {
~~~color: #987;
~~~text-decoration: none;
~~~}
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 described...at 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 MarkHissinkMullers]] 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.
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 http://bowen4-srv.lakeheadu.ca/wikitxt/wakka.php?wakka=PageIndex (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
CategoryWikka
CategoryDevelopment
Deletions:
<p>Meanwhile, if you have something to report:<br/>
<strong>First</strong> check if your feature suggestion is already being discussed on this page:</p><ul>
<li>If so: check if it has a link to a tracker ID:<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> feature suggestion.</li></ul>
<p>Thanks for your understanding.</p></div>""
::c::
**Issues often asked for**
~-[[CategorySystemOverhaul Categories]]
~-[[WikkaFolksonomy (Technorati) tags & related]]
~-[[WikkaInternationalization Internationalization/Localisation]]
~-[[DateAndTimeFormat Date/Time]]
~-[[WikkaFilters Wikka Exporting/Importing]], [[WikkaToPdf PDF-Export]]
~-[[WikkaOptimization Optimization]]
~-[[TableofcontentsAction Table of contents (TOC)]]
~-[[SectionEditing Section Editing]]
~-[[WikkaSpamFighting Spam (and related issues)]]
~-[[WikkaTables Tables]]
~-TemplateSystem
~-[[WikkaWorkarounds Workarounds for uncommon problems]]
**see also:**
~-UserMap
===Language support===
[[Ticket:340]]
===Highlight text searched in a page ===
[[Ticket:281]]
[[Ticket:230]]
===Is There a way to consolidate a bunch of page updates (the actual content that is) onto one page?===
[[Ticket:259]]
===Static HTML for offline browsing===
[[Ticket:177]]
===Link en- and disabling in respect to user rights===
[[Ticket:175]]
===Edit comments displayed by user rights===
[[Ticket:180]]
===Please provide a way to add formatters, that don't get placed in '<div class = "code">'===
[[Ticket:176]]
===Note on edit, mandatory field===
[[Ticket:114]]
===Order of comments===
[[Ticket:115]]
===Own comments editing===
[[Ticket:116]]
===versioning of attachments===
[[Ticket:118]]
===Making PageIndex go faster===
[[Ticket:117]]
===Single-click restore of previous versions===
[[Ticket:119]]
===Signature===
[[Ticket:121]]
===Preview===
[[Ticket:123]]
===Generate ID in forms; allow class===
[[Ticket:21]]
===Accesskeys for the footer functions===
[[Ticket:73]]
===Exclude certain CamelCase words from formatting===
[[Ticket:191]]
===Import WikiPedia database===
[[Ticket:192]]
===Color Formatting===
[[Ticket:193]]
[[Ticket:161]]
[[Ticket:190]]
===showing comments===
[[Ticket:195]]
===Local links===
[[Ticket:196]]
=== RSS options ===
[[Ticket:197]]
===wikiwyg===
[[Ticket:44]]
===Google Sitemap===
[[Ticket:210]]
===Clearing ACLs===
[[Ticket:211]]
===Online editing of mindmaps would be great===
[[Ticket:212]]
===""%%"" in code blocks: a possible workaround===
===How to format code to get two % characters without space together?===
[[Ticket:213]]
===Sending 403 headers===
(related to the //Search engine results inflation// item below)
[[Ticket:258]]
===The access-key for "re-edit ===
[[Ticket:234]]
===LinkTails===
[[Ticket:35]]
===Search within the textbox===
[[Ticket:578]] (see also WikkaEdit)
===Numbers as page names?===
[[Ticket:8]]
===Improved code for error messages in Action() method===
[[Ticket:202]]
=== Language files ===
[[Ticket:340]]
[[http://wush.net/trac/wikka/ticket/604 Ticket: 604]]
=== Create rewrite rules on install ===
[[http://wush.net/trac/wikka/ticket/604 Ticket: 604]]
=====Suggestions to be checked/migrated to the tracker=====
====making user uploaded images more useful====
have a look at my suggestion at FilesAction
=== Automatic conversion from HTML to WakkiWiki syntax ===
Does such thing exist? For a number of other Wikies, it does.
It should be nice (one could say, essential) to have this here, too.
--CsillagKristof
~&Try out http://diberri.dyndns.org/html2wiki.html (Won't work with tables yet). --NilsLindenberg
===Files Management===
//copied from FilesManagementSolution --JW//
**Link** to files, rather than upload? Would it be possible to add the functionality so that rather than store the files within the Wikki, there was an option box for 'link' as well as upload. This would be useful on internal wikki deployments where you want to avoid file duplication by allowing users to point at the file to create a link to that file on a separate internal server. - RogerD
===Automatic summary===
//copied from [[http://sourceforge.net/tracker/index.php?func=detail&aid=1150914&group_id=118997&atid=682795 Sourceforge]] --NilsLindenberg//
Is it possible to display through an action a little summary of the categories and sub categories available from the page we are in ?
===Improving Wikka===
A nice list of suggestions can be found at: [[http://smackaroo.net/by-blood-and-bone/MyNextWiki By Blood and bone]].
===Login using retrieved password===
The password retrieved from forgotten password does not work for me. Is there some setting in php4 or mysql that would allow ""md5(md5(password)) == md5(password)"" to return true? Since the password sent is the hash of the clear-text password, the current line in usersettings.php compares a hash of the hashed password to the hashed password, I think. I've found the correct code elsewhere in usersettings.php.
// usersettings.php line 130 fixed
if ($existingUser["password"] == md5($_POST["password"]) || $existingUser["password"]==$_POST["password"])
This is the current version:
// usersettings.php current line 130
if ($existingUser["password"] == md5($_POST["password"]))
The first one works for me. Is there a problem with security in using that version?
-CharlotteFischer
~&Charlotte, you are correct in that the code doesn't work as is. We are working on splitting up the whole (confusing) login/usersettings form into separate actions and forms; logging in with a "temporary" password should then not only be separate, but also force the user to immediately choose a new password since sending a password by email is inherently insecure. Until we have that in place in a future release, your workaround is a good one (I came up with the same ;-)); but it's up to you to decide how acceptable it is in your application to let the user continue to login with an emailed password. --JavaWoman
===Hiding anonymous host/IP from non-administrators===
On the Wiki I run, it is not desireable for the IP/hostname of anonymous users to be displayed to just anyone. I've made a small modification to hide the IP/hostname of anonymous users to users that (a) Are not administrators, and (b) not themselves. In handlers/page/show.php, around line 80 you can find: %%(php)print("\t<div class=\"commentinfo\">\n-- ".$this->Format($comment["user"])." (".$comment["time"].")\n");%% I modified this to: %%(php)if ($this->IsAdmin() || $current_user == $comment["user"] || $this->LoadUser($comment["user"]))
print("\t<div class=\"commentinfo\">\n-- ".$this->Format($comment["user"])." (".$comment["time"].")\n");
else
print("\t<div class=\"commentinfo\">\n-- Anonymous#".str_pad(dechex(crc32($comment["user"])), 8, "0", STR_PAD_LEFT)." (".$comment["time"].")\n");
}%% And in actions/recentlycommented.php: %%(php)if (!$this->LoadUser($comment_by)) $comment_by .= " (unregistered user)";%% was changed to: %%(php)if (!$this->IsAdmin() && $this->GetUserName() != $comment_by && !$this->LoaderUser($comment_by))
$comment_by = "Anonymous#".str_pad(dechex(crc32($comment_by)), 8, "0", STR_PAD_LEFT);
}%% And in actions/recentcomments.php: %%(php)if (strlen($comment["comment"]) > 120) $comment_preview = $comment_preview.".... ";%% after this add: %%(php)if (!$this->IsAdmin() && $this->GetUserName() != $comment["user"] && !$this->LoaderUser($comment["user"]))
$comment["user"] = "Anonymous#".str_pad(dechex(crc32($comment["user"])), 8, "0", STR_PAD_LEFT);
You will probably need to also update the XML handlers and the history page handler, but right now anonymous users cannot edit pages on my Wiki. (actions/recentchanges.php, handlers/page/*xml*.php, handlers/page/history.php). --Rick
===Storing the IP-adress for registered users===
//copied from WikkaBugs - this is a suggestion, not a bug --NilsLindenberg//
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. -Sam
~& 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
===Global Access Control Lists===
How about a global ACL that allows you to pick a prefix to a wikka word that automatically has an ACL applied? E.g. PrivatePage1, PrivatePage2 -- so the word Private is the trigger, anything prefixed with that has an ACL applied. -- JeremyCoates
===Integration into existing site===
==plus more on non-wikiname formatted usernames==
I'm trying to integrate wikka into an existing site auth system. I have wikka already successfully running with the includes of my main site, thus requiring main site login to access the wiki. i fig the best way to deal with wikka logins is to read the main sites "current user" info. when someone access' the wiki for the first time, their username obviously won't exist in the wikka userdb, so rather than making them create a login, i'll want to quietly query it into the wikka db. the problem is that wikka depends on wikiname formatted names. I don't care if people have their own page (may have it for a special few) password resets won't be an issue as stated below. While we may use comments (on the pages for the special few) they will prob remain off.
I'd like to do this as above to keep vandalism down. I've got almost 200k members and i know there are some jokers just waiting to anon deface crap just cuz they can. With an auto login like this, showing ppl their username as soon as they hit the wiki, it'll immediately cut that factor.
-- MonstoBrukes
~&I am interested in doing something very like this as well. I would like to integrate wikka into an existing phpBB site. I don't mind if my users have to log in twice - but I **//really//** don't want them to have 2 seperate usernames/ passwords. Therefore ideally I would like the wikka to use the usertable from phpBB... Has anybody else done something like this? -- KiltanneN
~~&One solution that I've used is to set up a registration page that registers the user into both the bulletin board and the wiki user tables. I've then removed the registration screens from each of the two. Users can then log into either of them using the same username and password. Of course, this only works when registering "new" users...one would have to write a script to copy existing users from the bulletin board into the wiki user tables for current users. --GmBowen
~~~& Not a bad idea - but breaks down for password changes and also name changes... I am going to try and build what I have described. I will make notes over here: UseThephpBBUserTable -- KiltanneN
~&See also WikkaWithphpBB --JavaWoman
===Pages linking to nonexisting pages===
As MovieLady pointed out somewhere, it could be usefull to see if there are pages linking to a non existing page (for example when you have renamed the page and have to update the links).
The following solution just prints out the links, without any other text ("the following pages link here") - which should be better placed in the backlinks action.
Change in ##handlers/page/show.php## the lines with if (!this->page) to:
%%(php;1)
if (!$this->page)
print("<p>This page doesn't exist yet. Maybe you want to <a href=\"".$this->Href("edit")."\">create</a> it?</p>");
print $this->Action("backlinks")."</div>";
~&What's the </div> for? I see no opening <div>. --JavaWoman
~~&it closes the <div class="page">. --NilsLindenberg
~~~&But I don't //see// an opening <div> - and this closing </div> is within an if clause. So when/where is that div opened, and when/where does it get closed when the condition is //not// true? Something wrong with the logic here, or you're not showing enough of the logic. --JavaWoman
~~~~&Ok, I was a littler bit short here :) the show handler opens a <div class="page"> before doing anything else (like the "has access"/page is existing check). So it has to be closed (and actually is closed) in every one of the three cases (1. no access to the page 2.pages is not existing 3.pages is displayed). In the official version it is closed after the "create it". I just moved it to have the backlinks inside the page-class (should have written that earlier :) --NilsLindenberg.
~~~~~&All right :) I guess the show handler is just sloppily written. If you open a div no matter what conditions apply, then you also close it no matter what, i.e., opened //outside// the if statement, then close it also //outside// the if statement. Whatever you do inside the if statement should have no influence at all: if opened, you must close it, no ifs and buts. I guess it's not wriiten like that (yet...). One for the code cleanup list. ;-) --JavaWoman
~&I think I've suggested before that the SandBox should not be indexed - the way to avoid this would be to add the appropriate meta tag to the page's head. That concept could easily be extended by allowing a WikiAdmin (not the WikiUser!) to define a list of pages where such a meta tag would be inserted. Generating a little text note to the effect for //all// these pages could also go some way to discourage spammers. --JavaWoman
%%(apache)RewriteCond %{REQUEST_URI} !=/favicon.ico
~&It can be done more generically by simply preventing rewiting happening when the requested URL matches an existing file or directory: %%(apache)RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f%% --- The first line excludes any directory, the second any existing file (which would include robots.txt and //any// icon file - you do not necessarily have to use favicon.ico). --JavaWoman
~~~& IE7 does support PNG's, IE6 and IE5.5 support it with a javascript solution, look in SmiliesAction for more on IE, PNG, image actions, icons etc.
~& The above code places paragraph tags throughout the page, including //within// code blocks, which seems undesirable. If ##\n## were treated as markup which wakka.php needs to transform into paragraph tags, code blocks wil not be changed, I think. I'll try it and post the code changes if it works. --PaulP
~~& No, that doesn't completely work either. It leaves code blocks unchanged, but keeps text from returning to left margin after indented paragraphs. --PaulP
//(copied from WikkaDevelopment --Nils)//
//(copied from WikkaDevelopment --Nils)//
//(copied from WikkaDevelopment --NilsLindenberg)//
~& Yeap, use this directly within the wikka page you are working on
~& %%(htmlstrict) <A href="http://google.com" TARGET="_blank">Google</A> %%
~& It will show up a normal link "" <A href="http://google.com" TARGET="blank">Google</A> ""
~& In this case the **TARGET="_blank"** bit is what does the trick.
~& Assuming this is what you were originally after, it has the advantage of no code changes. NickDamoulakis
~~& I assume you meant the above code to be put in double quotes like this:
~~& %%(htmlstrict) ""<A href="http://google.com" TARGET="_blank">Google</A>"" %%
~~& Since I use Wikka inside an iframe I need to use target a lot, so I modified the forced links section in wakka.php from:
~~& %%(php)//if ($url!=($url=(preg_replace("/@@|££||\[\[/","",$url))))$result="</span>";
if (!$text) $text = $url;
//$text=preg_replace("/@@|££|\[\[/","",$text);
return $result.$wakka->Link($url, "", $text);%%
~~& To this:
~~& %%(php)//if ($url!=($url=(preg_replace("/@@|££||\[\[/","",$url))))$result="</span>";
if (!$text) $text = $url;
if ($pos=stripos($text, ' target=')) {
$target = substr($text, $pos);
$text = substr($text, 0, strlen($text)-strlen($target));
//$text=preg_replace("/@@|££|\[\[/","",$text);
return $result.$wakka->Link($url, "", $text);%%
~~& I can now do forced links like this:
~~& %%[[http://www.google.com Google target="_top"]]%%
~~& What I don't like is target within imagelinks, the way it is now you have to write like this:
~~& %%{{image url="whatever.gif" link="http://www.google.com" target="target='_top'"}}%%
~~& This would have been better looking:
~~& %%{{image url="whatever.gif" link="http://www.google.com" target="_top"}}%%
~~& /AndreasHeintze
=== Easy way of adding links ===
-- MatthewLangham
~& MatthewLangham, I propose AddLinkAction as solution for adding links on a page in a structured way. I also added (under the Beta section at the end) a ""JavaScript""-link that you need to bookmark to fast add a link in two mouse clicks... (Works with Firefox and IE under XP, still needs testing with other browsers) -- OnegWR
=== Image dimensions ===
The [[Docs:AddingImages image]] action really needs the ability to specify image height and width. :) --MovieLady
now available as URUniqueEMailModule
=== Embed a blurb from a news page into another page? ===
===Logging-out===
=== Backlinks ===
backlinks.php
if ($pages = $this->LoadPagesLinkingTo($this->getPageTag())) {
foreach ($pages as $page) {
$links[] = $this->Link($page["tag"]);
// #MW:commented print(implode("<br />\n", $links));
// #MW: Ja, här ska jag fixa stöd för kolumner via parametern col
if (!isset($col)) $col=1;
$out = "<table width='100% border='0''><tr>";
$count = 0;
while (list($key, $val) = each($links)) {
if($count == $col) { $out .= "</tr><tr>"; $count = 0; }
$out .= "<td>" . $val . "</td>";
$count++;
$out .= "</tr></table>";
print $out;
=== User names ===
===List of special actions?===
===Allow spaces in pagetitle===
~& Wikka already uses the SmartTitle formatter, which displays the highest-level header present in the page (like: ##""===== This is the main heading""##) as a HTML title. See for instance the title of FormattingRules. -- DarTar
===User-defined formatting rules===
A "compile category" action. Right now, if I go to CategoryDocumentation I can see a list of all of the pages in this category...but it still requires a lot of snooping to find what I want. As an administrator I'd like to provide a pdf "booklet" of all of that output for users to download. To make this now would mean going to and printing each and every page (using a software tool, TO a pdf file). Ugh. An action that let me go ""{{compile category="CategoryDocumentation"}}"" to generate a single web page of all of that documentation would be quite useful because then I could just print it to a pdf file once.....then I could provide a link to the PDF file so users could download it and print it off.
===Compatibility & Installer===
===Handling the config===
''See also [[http://wush.net/trac/wikka/ticket/603 Ticket 603]] --JavaWoman''
===Markup for code not to be shown===
===markup of diff pages===
=== Problem: Scrolling in the search - field ===
=== Problem: Five Line Breaks ===
=== DB Export ===
===Code block formatting===
===Various suggestions===
===Other method to attach files===
===Installation problem - UTF-8?===
===Add page link & other suggestions===
===Disable CamelCase===
While I understand the arguments in favor of CamelCase, I prefer not to use it. Given how incredibly simple it is to modify Wikka for non CamelCase use (remove one line in formatters/wakka.php, and replace a regex in wikka.php, wouldn't it be simple just to add an admin option to turn it on and off?
===Rename Pages===
It would be nice to be able to rename pages and automatically update all backlinks to point to the right page.
Example: I have a ""HomePage"" which has a link to ""MyIdeas"" on it. Let's say I realized that all these ideas are Wikka related, so I want to rename the page to ""MyWikkaIdeas"". Any link to ""MyIdeas"" (such as that on ""HomePage"") should now be changed to point to ""MyWikkaIdeas"".
- JonathanMitchem
~& Yeah, so I found this... RefactorWiki which supposedly does exactly that (I haven't tested it personally) - JonathanMitchem
===Star Rating System===
I think that maybe usefull a star rating system for a page or for an image or other .
~& LuxiO, what criteria would you suggest for such a ranking system? --BrianKoontz
~~& BrianKoontz, first i think that the rating system should have an extra table in the main database so that every item we want rate should have a unique identification number. Then we manipulate this extra table from an internal action... maybe? --LuxiO
~~~& That sounds like a suitable approach...but my question is, how would users be expected to "rank" a page? Are we looking for a measure of suitability, quality or aesthetics, or maybe popularity? Is it really possible to assign a relative ranking to pages with dissimilar content? --BrianKoontz
~~~~&It would depend on the use of the wikki... for example, [[http://www.RantThisSpace.com Rant This Space!]] is purely for entertainment and therefore people would be encouraged to vote based on how entertaining the page was. In a corporate setting it might denote importance, or relevance to the project. Then the home page could display a list of all pages with 5 stars, and new members would know to read them first. Icons other than stars could also be used.
I have found this simple javascript for page rating:
%%(javascript)
<div class="js-kit-rating" starColor="Golden" path="ABSOLUTE-PAGE-URL"></div><script src="http://js-kit.com/ratings.js"></script>
but i don't know how implement single file rating --LuxiO
CategoryDevelopmentSuggestions
