Wiclear

• View history

You are here :

• Wiclear
• Bugs

Feel free to enter here the bugs you just found.

Bug or missunderstanding?

I use lang slovenian and the wikki plugin. If I'm logged in, all's OK. When I log out my blog becomes a wiki and the site is english.

the language is set correctly to sl-SI in config.ini

Is this a bug or did I miss something in the installation/setup?

David : hard to say without more information. I think you're the only one (apart from me) who is using the wiki_blog plugin. So you set up wc_default_lang=sl in config.ini ? (I think sl-SI will not work unless the UTF-8 translation file is named sl-SI.lang but the one I know is named sl.lang (in i18n dir). Then make sure your default lang content is also sl. For that see section named "changing of master lang" in this page.
David : for the other issue, without a link is tough to say. You can send me privately if you want the adress of your site ? Basically, the wiki_blog plugin does not change the wiki into a blog. It just adds a handler to the default page to display the list of last changes in a blog way. It also adds new "widget" like the calendar and the categories, but this is part of the layout, and you could still add the calendar and the categories to the layout of the wiki without the wiki_blog installed. By the way, which theme are you using ? You should use the dokuwiki_blog theme that comes with the distribution. If you made your own custom theme then make sure you have activated the wiki_blog plugin by using the prepend.inc.php file in your theme directory and calling the wikiBlogSetup(); function. See the one in the theme dokuwiki_blog for that.

Thanks, I managed to get it working right now. Right: the sl-SI doesen't work, the language must be sl for my locale. I have swiched it manualy cos I was hoping the calendar will be translated but nothing happened anyway.

I have noticed that the blog on your page has the calendar translated in french (as well as the words Today, Yesterday ...) how did you do it? I know that php has locales built in and is abel to translate it (and the locale sl-SI exists and works on some of my pages ...)

David : each plugin have their own i18n translation files. So go to /tools/wiki_blog/i18n/ and copy fr.lang to sl.lang then starts translating. When you're happy with it send me the translation file for next release ! More information here.

Bugs in navigationBox()

Type error

Navigation box causes a "Trying to get property of non-object" notice.
Line 1383 sets

global $user_lang;

correct is

global $user;

Bug

If navigationBox() is called without $node being instantiated as object it causes an error. This tipically happens, when you try to use it with the blog plug-in on the home page, or in some modes (ie. new article creation). You can solve that simply by inserting the following line in the file /wiclear/inc/lib/content.lib.php after the line 1384 (function navigation box)

 function navigationBox()
{
  global $node;
  global $wiki;
  global $user;
 
  if(!is_object($node)) return;
  .
  .
  .
  etc.

David : OK, thank you I'll have it fixed.

Make a new root

I created a new page, originally the child of my root. I decided to click on "make root" to test this feature. It is now the root - good (although there was an error reported when I did this - "clearall" function does not exist). However, I cannot make the original page the root again now (no "make root" button).

Any way around this?

Ahh - found it and fixed it - it was a bug in wiki.classes.php

You need to amend the line:

$cacheLite->c l e a n A l l (); (no spaces)

to read:

global $cacheLite;
$cacheLite->w c c l e a n A l l (); (no spaces)

(sorry spam filter will not let me post this)

David : thanks. Corrected. Yes spamSimpleFilter rejects the content because wcClean All contains a n a l

Easy to get an XML parsing error if you include an ampersand symbol

WiClear needs to change ampersands before storing them in the SQL database - change to & Particularly if they are placed in a section title you will get an XML parsing error when you try to view the page.

David : please provide an example (even if that breaks XHTML validity of this page)

Try this & cry out

Hmm - does not affect this one, but it does on my wiki - http://www.rwapadventures.com/ql_wiki

In fact I am having problems with a few XML parsing errors - see the ql_wiki at the moment.

Is it the fact I am running on a Linux server?

David : I've browse several pages without encountering any XML validation issue. Can you point me with a link to a page that has this problem please ?

Ok try: Sandbox on QL Wiki

David : OK, reproduced. This is because you are using the "allow html" option in your preferences. (well, I reproduced it in this mode, and it works ok without it. Like in this site, so I guess this is the likely explanation). If you allow html content and your html don't validate you will get that error because wiclear is served as xhtml. So your html must validates or xhtml capable browser like firefox will report those kind of errors. Perhaps in that case, wiclear should be modified to serve the page as html instead of xhtml...

Rich : Or perhaps wiclear could store ampersands and other special characters in a different way to overcome this. Unfortunately, even using & does not pass the test at present.

David: I've modified wiclear to be served as html when allow html content is used. It prevents the page from not validating in FF. You can then use & now...

Also, I see my version of WiClear lacks the controls boxes for editing text and also sub nodes is not working - am I missing something on the install?

David : for your nodes, I guess this is you who entered the page Tools (especially Nodes) not working. This is already fixed.

Rich : Yes thankyou - it was also down to me running an early MySQL (pre v4.1).

David : for the toolbar I don't know, do you have the plugin SimpleToolBar installed ? If you have it, and if you have created a custom theme, have you left the call to simpleToolbarSetup(); in prepend.inc.php in your theme ? As your page are not opened for edition, I cannot have a look to the javascript during edition to see if I can find something...

Rich: You need to register to edit. However we based the theme on WiClear - that does not include a prepend.inc.php reference or even file in the theme folder. Only Dokuwiki does that. I obviously need to add this to my theme.

MySql charset problem during install

Alas, I do not know how to resolve this one ?

• how can I detect if MySql supports charset or not !
• how do I know which charset is installed ?
• how can I change my sql requests to include or not charset information ?

David : should be fixed in latest snapshot. Install program has been modified to list available charsets when first connecting to database. If none are available, then installation proceed without using them. This needs to be polished but should do the trick. Nice side effect : it is now possible to choose charset at install, instead of having to use the UTF-8 converter later on.

All other reproductible and known bugs resolved

ACLS possible improvement

display the list of sub nodes of a particular node that do not have the same acl than current node.

Hide sub nodes if people doesn't have the right to see them

I think there is no use showing nodes that cannot be read.

David (03/02/07) : done (was possible after all)

Inherit ACL from parent node

Pages should have the same ACL as the parent node when creating/attaching a page to a node.

I think it should be great to automatically recurse apply ACL of the new parent node to the node (and it's sub nodes).

David (03/01/07) : done

Show and respect ACL in the site plan

At least show if a page is readable/writeable by anonymous. It will help detecting possible problem in the wiki. Pages that cannot be read, should not be shown in the plan.

David (03/02/07) : also done (was not that hard finally). Read protected pages are shown with a non clickable flag and a lock icon right aside

Button preview/publish/cancel should be at the same level

They act on the same part of the form. They should be at the same level. (it is UI things)

David (02/27/07) : done

Add a link wiki syntax help

Replace the wiki syntax help at the end of the edit page by a link which pops a new window. Because it is useless to have this explanation in most of the case and in other case, it is more useful to have it in a separate window that you can look into when you need it. In the current situation you must go to the end of the page and then go back to the textarea...

David (02/27/07) : done

Notification mail contains HTML entities

I am notified with �

David (02/27/07) : done

Remove the content at the beginning of the page

At least when people hit on edit, they should not see the content at the beginning of the page. It is long to scroll through the entire content (which people just have read before).

However, the content should appear again when people hit the "preview" button...

David (02/27/07) : done

Separate the parent/sub node tree functions

I have rewritten this function and the subnode function to get a simple li list not containing the current node. It helps me building my theme.

Patch is available for this

David (03/01/07) : waiting for patch

Some russi an symbols gets corrupted in v.1.0

Hi, i using php 5 and MySQL 5.2 I successfully installed Wiclear but found, thats anytime i using "ш" symbol in content or title it gets corrupted and showing as ?? I viewed my DB (in HEX mode) and found, that Wiclear write "D13F" bytes instead "D188" in DB I checked - my tables is in utf8_general_ci collation Moreover - i have no troubles with any other russi an symbols and have no troubles with Drupal (also UTF8) installation in same DB Interesting thing: If i type line of "ш" symbols and push preview button - page updates and i see valid result - row of "ш", but if i push Submit button - symbols gets corrupted.

David : Unfortunately, I'm no expert in UTF-8. Most of the time I'm only using latin-1. Patch appreciated : if you have the skills or know somebody who have the skill to fix the problem, let me know.

Errors in the NodeParents results.

I'm using the content id's here.

1 is parent of 6, which is parent of 7, According to the website, siteplan and MYSQL database : wc_content_hierarchy

When I get on the 6 content, I get this result from the getNodeParents : you are here : 1 > 6 But when I get on the 7 content, I get this : you are here 1 > 44(?) > 6 > 7

I try to move this page to another parent, this is working, when I put the 6 parent back, I still get the 1 > 44 > 6 > 7 sheme...

I tryied to figure how the request was working, and maybe the problem comes from the n_left and n_right parameters ... They were crossing between the 44 content and the 6 ...

I changed ( by hand ) the n_right value of 44 to the higher value used by its children, and this seems to work again. how comes that it got a higher value, then included the other contents in it ?

Thank you in advance

David: Sorry for the delay I missed the page update. Yes this problem happens from time to time but unfortunately I have no easy way to reproduce it. Anyway, there is a simple way of fixing it : See Database maintenance, and use "verify and repair". If you have a simple way to make this happen let me know I'll have it fixed asap.

No trackbacks yet

To make a trackback, use ping url http://wiclear.free.fr/tools/trackback/trackback.php?id=3

If your client support ping url auto discovery, you can also try it using directly this page's url

Comments are closed

Comments

• Login
• Register

• 
• 
• Powered by Wiclear

• PHP execution time : 0.151 seconds

• SQL execution time : 0.013 seconds