Category: Accessibility

1) Column colapsing is not remerbered whenever I change from one page to another.

2) And also have had some problems with their navigators saying "cookies must be on" when they are on, no matter wich browser is being used. This happends as they attemp to login. After many tries the user can login.


Using:
Tiki 6.1 fresh code install, on past 6.0 db updated to 6.1.

There are many pages within t.o that have spaces. On the other hand, the WikiSyntax historically uses WikiWords. I also see that tiki supports aliases for pages. This led me to the following suggestion:

- Propose to render WikiWords as "Wiki Words" in the page. This makes it easier to read. Obviously this mean one control more ...
- When parsing a page, and there is no page for a specific WikiWord, look for the page 'Wiki Word' (adding a space before each capital).

Advantage : this would allow people coming from other wikis to make links with WikiWords, even for pages like ((Wiki Plugins)), without the need for clumsy parenthesis everywhere.

on the features selection page there is a checkbox for each feature with its name next to it. In normal Web UIs a checkbox is next to a <label> tag which contains the text referring to the setting the checkbox controls. If you set up the name= and title= for both the input and the label then clicking that text automatically selects the checkbox.

This is not always implemented properly across the web but it is the way forms are supposed to be used and it is easy and no one ever complains about it. It increases the effective size of the checkbox and cements the relationship with the word.

On the features selection page, however, the text instead links to the tikiwiki.org descriptions of the features. This confused me and happened several times before I retaught myself to not click the words.

access tiki data (like trackers, wiki pages, etc.) with webservices.

Add an additional option on trackers, wiki pages etc. to make them accessible by webservices (like choosing categories)

Administration UI where security can be configured (Password on specific webservices etc.)

No html links are shown for uploaded images in the file gallery. Only wiki display and download links appear in the "Additional Info" screen.

Users just have to "know" that to display in html you must use /displayFilenumber

Also, there is no direct way to get BACK to that Additional Info screen from the gallery once the file is uploaded. i.e. it does not appear in the image's 'tool' pop-up menu, which just lists for us Dowload, Replace, Properties, Open in WebDav, Email this, and Delete only. No way to get back to the "additional info" screen.

Also, the images don't have a suffix when the URI format is /display123 and this causes problems with some software which expects one.


The old image galleries had an html link for the images.

After a search (general by text) the beginning of text which is displayed is not decoded-re-encode for the context.
On the screenshot joined you can see parts of text with tiki tag (!! for h2), HTML tags, problem of encoding UTF8 probably or old text not re-encoded (not yet checked).

Similar to the special character tool (which it could replace) , this is useful when you are away from your usual keyboard... (or just have a mouse!)

Good against keyloggers, so it could part of the login screen too

Here is a BSD-licensed one:
http://www.greywyvern.com/code/javascript/keyboard

Dokuwiki has a plugin
http://www.dokuwiki.org/plugin:vkeyboard

!!!After upgrade the admin can't login anymore

!!!The failure sequence :
#Create a new directory or repository for the new version
#Update with your files (particularly images or icons)
#Site enable (example a sub-domain) on Apache
#Copy the database on new name
#Install manually .htaccess (compare and insert your valid options )
#Update "local.php"
#run <your new domain>/tiki-install.php. Goto the end (note an error occurs if your say at the end "run tiki" without locking or not because tiki-setup tries to re-open a session already automatically opened by installer). You just launch again (default tiki-index)
#~~#F00:__Try to login as admin : You will be rejected as wrong password __~~

!!Analysis - many possible reasons :
There are a lot of reasons to be in this situations. So to be successful a lot of conditions must be satisfied :

#If your new version uses the same current domain (after upgrade for my own I defines the same "servername" as current one and then keep the other when a particular name containng the version :
- The Cookies of session will try to reconnect an older version and a trace shows that the password is not the one you have given (generally empty). So the cookies of the site name must be cleared on your navigator

#The temp files or session table contain too wrong data : they must be cleared on server for your current copy (SVN update case)

#Your admin record in user_user record contains sessions data : they create a conflict which makes crash your login

#Be careful of the fact that you can have an open session in your navigator with the same site (sometimes we uses a lot of tab management which can create this : on firefox use showcase and search to clear your old sessions

#Generally avoid these problem is sufficient but at the end you will be prompt to update your password (as for the first login as admin with password admin). This can fail for the following reason : if the .htaccess is not set or modrewrite not well operational the <site name> will include the "port" used by your server. If your NAT translates the port address (i.e. 80-> 4397) you will get the following url <site>:4397/.... which fails

It is sure that if you use only one site close everything and upgrade you will get the minimum of problems but you will get someone anywhere.


!!~~#099:This situation is common and complex for whom have to manage product and data migration from one version (or several) of tiki to a new one.~~
It is not seen generally by developers, because it is not at all their common upgrade process nor test.

http://www.w3schools.com/tags/tag_abbr.asp
http://www.w3schools.com/tags/tag_acronym.asp


This is already possible via ((doc:PluginTag)) but dedicated plugins could be cleaner/simpler in certain cases

Android browser on Tiki8: It just says "Loading..." forever


[http://cksource.com/blog/CKEditor_3.6.2_released|Recent iPads and iPhones should be OK]

If browser is not supported, should Tiki revert to entering text (or manual HTML?)

After clicking "create new wiki page", i typed a name for this site containing a forbidden char (in this case "&"). I prompted this entry (not knowing this char is forbidden) to add content to this page.

the "invalid character" field popped up and forced me to rename the page. looked similar to the normal "rename page" input, but without a button to "save" the change.

unfortunately, the save button was also missing in the editor field for my new page and "previewing" the new site didn't change anything in this behaviour.

so in the end - content as well as the page were lost.

please add "save" buttons to this areas.

Contributors

Please see:
http://irc.tiki.org/irclogger_log/tikiwiki?date=2012-10-03,Wed&sel=483#l479

The log in "Remember me" option can be set to "User's choice". There are fine grained options up to one day, but there's a gap between one day and one week. I'd be helpful and convenient to offer two days and three days as well.

Another nice-to-have would be a menu for users to choose themselves how long to remember up to a maximum set by the administrator. The administrator's duration menu should include the "Always" option in this case, too.

The webinterface for bug reports and wishes can be submitted only without preview. It'd be an enhancement to have the opportunity to correct typos and check things before final submission.

Recently, I went into Admin and turned off one of the features in Admin at tiki-admin.php?page=features. The feature was Calendar in Global Features. But that brought up a problem that I was able to investigate in my host server's error logs:

.../tiki-calendar.php
PHP Warning: PDO::query(): SQLSTATE[42000]: Syntax error or access violation: 1226 User ... has exceeded the 'max_questions' resource (current value: 75000) in .../wiki/lib/core/TikiDb/Pdo.php on line 78

PHP Warning: Invalid argument supplied for foreach() in .../wiki/db/tiki-db.php on line 152

PHP Warning: PDO::query(): SQLSTATE[42000]: Syntax error or access violation: 1226 User ... has exceeded the 'max_que ...
... /wiki/tiki-lastchanges.php

Using a pretty tracker as registration form doesn't allow to de-activate the captcha.
Since one of the point of using a tracker for registration is to allow special questions which robots can't answer, what is the point of forcing the use of the captcha (through which robots can easily pass)?
Maybe a duplicate of bug #1818, I'm unsure.

SHOW admin password: 01234

Hi,

This bug affects version 9.x, but after having a short look at the 10.x source code, that version is probably also affected.

It happened after upgrading from version 3.9 to 9.3.

When accessing my.host or my.host/index.php, tikiwiki should redirect to tiki-index.php but gets stuck in an endless redirection loop by redirecting to my.host.

When accessing my.host/tiki-index.php directly,the following error message is displayed:
"Error
Required features: feature_wiki. If you do not have the privileges to activate these features, ask the site administrator."

Similar errors when accessing other features.

Bugs & Wish list

If you're editing a page and you fail the CAPTCHA or your session expires, your whole edit is lost. Most users expect their browser to have saved the form data, many would know enough to log back in then hit the back button to get back to the form (or at least, hit "back" and copy the data for later pasting after login). This does not work - after a "back" the form is empty!

I'm ranking this bug as priority 7 because it is very serious - data loss and angry users. I think the solution is trivial, too: see below.

Fatal error when trying to authenticate against an LDAP server on IIS6 Windowns 2003 Server:

Fatal error: Call to undefined method Net_LDAP2_Error::getEntry() in D:\WWWROOT\wiki60\lib\auth\ldap.php on line 257

New user is shown a red X with the title "Random Image" as the registration code.

User can't see the letters so can't register

Appeared in 1.9.10.1 while adding extra security checks

Hi there,

I want to nkow if it is possible to integrate the tikiwiki login process with another page, I want to create another secure page using the tikiwiki login process, Do you guys have any hint for doing that?

My page will be in php also, I know that I will probably have to do some inclusion but don't which file to include in my code and which function.

Any help will be much apreciated.

Thanks

Contributors

Noob here enjoying the site, enjoying the software and finding my way around. Thank you.

It means spending a *lot* of time at the Tiki sites.

I get the message already about the dogfood. Cool.

But every day, every page load, I must dismiss this notice to uncover what is underneath. Or scroll the viewport out from under it.

It is located on top of the navigation.

Can we not have it fixed in the page above the navigation, or permanently dismissable once logged in, or ...?

Can we just use the site now, and stop swatting at the javascript? :)

I'm just setting up svn etc now. And wouldn't have the balls to make such a visible change right off the hop anyway. It's not real important obviously. But if somebody is there and knows and can do, it would make surfing the sites more pleasant...

Cheers!!

Please see:
http://phplayersmenu.sourceforge.net/demo.php

phplayersmenu has 5 types.

$types['vert'] = 'layersmenu.inc.php';
$types['horiz'] = 'layersmenu.inc.php';
$types['tree'] = 'treemenu.inc.php';
$types['phptree'] = 'phptreemenu.inc.php';
$types['plain'] = 'phptreemenu.inc.php';

Tiki is only using 3.

"Two classes are provided to prepare also accessibility solutions, i.e. "server-side based" tree menus (that have just the same look of the above mentioned JavaScript-based tree menus, but require the PHP support on the web server) and plain menus that do not require the JavaScript support to the browser."

Related:
Menu items with link type options (framed, new window, replace)
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=521


We could also let the user determine an icon for each menu item.

Bugs & Wish list

Using the same IIS web site:
*You can install 6.0 and successfully login as admin.
*Install 6.1 and 6.2 but neither of them are able to login as admin.

Additional details, as per forum post (http://tiki.org/tiki-view_forum_thread.php?comments_parentId=40416&topics_sort_mode=lastPost_desc&forumId=6):
Trying to use TW on our IIS web site. Have followed all references I could find but have not been able to get 6.1 going.

As a test, I have managed to get 6.0 going, so not sure why 6.1 and 6.2 has issues. Any guidance on how to debug this is appreciated.

Thanks.

Details are:
- Win2003 SP2 and IIS6
- MySQL 5.1 (tried both local and remote server)
- PHP 5.2.17
- Firefox 3.6
- No tildes in the URL
- Tried placing TW in the root of the web site and as a virtual directory
- Have granted the EVERYONE user READ,WRITE & MODIFY access to the web root and all sub folders.
- No PHP errors recorded in the PHP error log

Symptoms:
- Install proceeds successfully.
- DB install states that is is successful (both local and remote DB scenarios)
- Prompted with admin change password screen and successfully change the password.
- Prompted with the Home page, then login as admin and new password, only to be presented with the Home page again, which states:
"Congratulations
This is the default homepage for your Tiki. If you are seeing this page, your installation was successful.

You can change this page after logging in. Please review the wiki syntax(external link) for editing details."

- Try clearing cookies, then logging in and are presented with "You have to enable cookies to be able to login to this site".

"And from version 5.6 onwards, HAWHAW supports special output for the Lynx text browser. This "archaic" browser is still used today, often by handicaped people with screen readers and other special equipment. HAWHAW's Lynx support allows to create barrierfree applications, which validate Bobby-AAA-approved out of the box and additionally are accessible from each telephone by means of HAWHAW's VoiceXML support."

[http://www.hawhaw.de/]



Todo: add the powered by HAWHAW logo in the tiki-bot_bar.tpl when tiki-mobile is activated.

{img src=images/code.png}%%% {CODE(wrap=1)}
(6:51:03 PM) The topic for #sumo is: irc channel for development of http://support.mozilla.com/ || see also mozilla.support.planning (newsgroup) || Next meeting: 2pm PST Dec. 4; http://wiki.mozilla.org/Support/Weekly_Meetings || If you'd like to help test the live chat software PM Lucy
(7:19:06 AM) MarcoZ: Hi there!
(7:19:29 AM) Tomcat: hi MarcoZ :)
(7:19:53 AM) MarcoZ: Hi Tomcat!
(7:20:23 AM) MarcoZ: Can anybody tell the new kid on the blog how to create an article on Sumo? I would like to get an article into the knowledgebase about what's new in the area of a11y in Firefox 3.
(7:20:36 AM) MarcoZ: But I can't find a way (at least none that is obvious to me) how to start an article.
(7:20:55 AM) Tomcat: Lucy: ^
(7:21:20 AM) Tomcat: in case you are awake :)
(7:57:08 AM) marclaporte: MarcoZH: I don't know what the editorial rules are, but just edit a page and change the name in the URL
(8:07:42 AM) MarcoZ: marclaporte, thanks, will give this a try. If I simply do something like support.mozilla.com/kb/MyNewTitle , I get a 404, and an option to create a new page, but with the hint in parentheses that "this page will be orphaned", but without any further explanation to what this implies.
(8:08:18 AM) MarcoZ: djst, hi! This is Marco, the a11y guy :-)
(8:09:44 AM) djst: MarcoZ: hey thre!
(8:10:00 AM) djst: MarcoZ: great to see you around
(8:11:02 AM) djst: MarcoZ: i missed your previous conversation with marclaporte, in case there's anything you're wondering about
(8:11:13 AM) djst: MarcoZ: is the sumo site usable at all as it is?
(8:12:22 AM) MarcoZ: djst, yes it is usable and has good markup. That's not a problem. I just can't figure out how to start a new article. I shot you an e-mail about it earlier, but if you know the answer from the top of your head, we can discuss it here.
(8:13:00 AM) djst: ah yeah, let me see if there's a fix for that. there was a quick edit form in the contributor home page before but i think it was removed
(8:13:02 AM) djst: let me check
(8:14:08 AM) djst: MarcoZ: http://support.mozilla.com/kb/Creating+articles
(8:14:27 AM) djst: that page is linked to from the contributor home page (which should be the page you see when you log in, but currently it's not)
(8:14:43 AM) djst: MarcoZ: this is not optimal, we should make this easier to see
(8:19:38 AM) MarcoZ: djst, thanks this is the starting point I needed.
(8:20:05 AM) djst: MarcoZ: ok. i'm here most of my work days so just ping me if you need any other info.
(8:21:24 AM) marclaporte: :-)
(8:22:04 AM) marclaporte: MarcoZ: are you using JAWS or something similar?
(8:31:45 AM) MarcoZ: marclaporte, yes, on Windows I'm using JAWS, on Linux I'm using Orca.
(8:33:40 AM) marclaporte: MarcoZ: I have a few questions about a11y and wikis if you don't mind
(8:34:53 AM) marclaporte: 1st off: an intro so you get an idea where I am coming from. My name is Marc Laporte and I am a project admin for TikiWiki CMS/Groupware
(8:35:25 AM) marclaporte: I took a course on a11y, but I never really had much real world experience
(8:36:12 AM) marclaporte: I would like TikiWiki to become more & more accessible, hopefully, eventually, fully accessible out of the box
(8:36:49 AM) marclaporte: I have a theory that wiki syntax maybe a positive thing for a11y, but I don't know really
(8:37:30 AM) marclaporte: (compared to standard html CMSs or the ones that use WYSIWYG/rich text editors)
(8:38:32 AM) marclaporte: We currently have no one helping/promoting/testing/etc a11y and I hope this could change.
(8:38:49 AM) marclaporte: so....
(8:39:08 AM) MarcoZ: marclaporte, thanks for your introduction! I started as the accessibility QA at Mozilla last week.
(8:39:28 AM) marclaporte: sweet
(8:41:07 AM) marclaporte: So what is global a11y status in FF as of now?
(8:41:24 AM) MarcoZ: marclaporte, so far what I've seen looks pretty good with JAWS on Sumo. The only real problem I ran into was actually signing up. The captcha system is not accessible at all. There is an accessible chaptcha system called ReCaptcha (http://www.recaptcha.net) that is accessible. That's the one improvement I definitely know Tiki could use. Unless of course, the captcha isn't standard, .
(8:42:01 AM) marclaporte: MarcoZ: I appreciate the feedback
(8:42:04 AM) MarcoZ: well, global a11y status in FF 3 will be a lot better than in 2, primarily because FF3 is also going to be accessible on Linux, not just Windows.
(8:42:18 AM) marclaporte: I see
(8:42:38 AM) marclaporte: Is wiki syntax better or worse for a11y?
(8:42:47 AM) marclaporte: (in general, not specifically TikiWiki)
(8:43:01 AM) MarcoZ: I made the switch from IE quite a long time ago, and there's only one site that I can't use with Firefox. And that's not because of a11y reasons, but because the music store I use here in Germany only works with IE, so every sighted person will also have this problem. :-)
(8:43:28 AM) MarcoZ: I mostly worked on MediaWiki so far, and the Wiki syntax was easy to grasp for me.
(8:43:59 AM) MarcoZ: It is appreciated to have these helper buttons/links available to insert the Wiki tags, so one doesn't have to memorize them all, but editing stuff, and having a feeling I know what I'm doing, is good with Wiki syntax.
(8:46:29 AM) marclaporte: MarcoZ: are you able to use the quicktags? or you type the syntax?
(8:51:33 AM) marclaporte: MarcoZ: I am going to log a feature enhancement request on dev.tikiwiki.org wishlist. May I copy/paste our current discussion in the tracker?
(8:51:33 AM) MarcoZ: The quicktags appear as links for JAWS, so i can simply select one and activate it to insert the quicktags. Works quite nocely actually. :-)
(8:52:26 AM) MarcoZ: marclaporte, sure!
(8:52:59 AM) marclaporte: MarcoZ: so you insert and after you find the text with wiki syntax and you go and change it?
(8:58:04 AM) MarcoZ: marclaporte, yes. For example, the heading level 1 notation is an exclamation mark followed by text, heading level 2 is two exclamation marks. I simply change the text after it.
(8:59:49 AM) marclaporte: Excellent.
(9:00:12 AM) marclaporte: ReCaptcha is very interesting!
{CODE}

http://validator.w3.org/check?uri=http%3A%2F%2Fdoc.tikiwiki.org%2FPluginmouseover&charset=%28detect+automatically%29&doctype=Inline&group=0

Result: 71 Errors, 55 warning(s)

Line 332, Column 75: character "<" is the first character of a delimiter but occurred as data.

…'link' onmouseover="return overlib('<table><tr><td><img src=\'tiki-show_user

✉

This message may appear in several cases:

* You tried to include the "<" character in your page: you should escape it as "<"
* You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
* Another possibility is that you forgot to close quotes in a previous tag.