Category: Usability

Please see
http://doc.tikiwiki.org/Lost+edit


{FLASH(movie=files/FeatureRequest_BetterHandlingOfBackButtonWhileEditing.swf,width=>811,height=>708,quality=>high)}{FLASH}

Hello Dev Team;

A post for help was made to the Dev email list. It was suggested to make a wish sooooooo:
Would you make it possible to assign category ids during profile assembly using a wiki page template? More specifically:

1. Using a datachannel; wiki pages, blogs, file galleries, groups and categories are created and referenced in a wiki template with the “wikicontent:template_name” syntax.
2. This has been successfully done for both blogs and file galleries. (see respective code below)
For blogs in a wiki page template:
{bloglist Id="$profileobject:public_blog$" Items="1" author="$profilerequest:Login$Login$" simpleList="n" charCount="250" wordBoundary="y" ellipsis="y" more="y" showIcons="y" isHtml="n"}
For file galleries in a wiki page template:
{colorbox fgalId="$profileobject:public_gallery$" thumb="n" showallthumbs="y"}
3. This does not appear to work for categories.
{module module="categories" type="wiki page" deep="off" categId="$profileobject:state_category$" selflink="y" notitle="y" }

Thanks in advance for your consideration.

Take care,
Robert Rasgorshek


Please reference email to developers: Assigning category id using $profileobject: syntax

{syntax type="tiki" editor="plain"}
All wiki pages have the option to refresh them by clicking on their title. For a page e.g. ...&itemId=5, it does not work.

TW5.0Beta1

The register and forgot password link are barely visible at https://tiki.org/Community
{img fileId="2147" thumb="box"}

om: admin
To: admin
Cc:
Subject: Tiki User Registration Request
Date: Thu 07 of Sep, 2006 [13:32]

Hi,

gandalf < > has requested an account on www.domain.de

To validate that account, please follow the link:
http://www.domain.de/tiki-login_validate.phpuser=gandalf&pass=98d3eee5d2201c477b6066c28dac3bd2


best regards,
your Tikiwiki

The validation link should be something like this:

http://www.domain.de/tiki-login_validate.php?user=gandalf&pass=98d3eee5d2201c477b6066c28dac3bd2

When inserting the question mark manually validation is working.

Read on #wiki (freenode)

(10:47:42) TheSheep: marclaporte: don't want to be rude, but I have an implementation hint for tikiwiki -- make the registration url fit in 80 chars, it will be much easier to copy to the browser this way
(10:48:05) marclaporte: you mean the one you receive by email?
(10:48:17) marclaporte: (not rude at all, always like feedback, good or bad)
(10:48:45) TheSheep: marclaporte: yes
(10:49:19) TheSheep: marclaporte: the domain name is short, if only the php file name and the password were shorter, it would fit nicely
(10:49:38) TheSheep: just a small detail
(10:50:07) TheSheep: most people use graphical mail clients anyways probably


Below is an example:
Hi marclaporte2,
you or someone registered this email address at tikiwiki.org
If you want to be a registered user in this site you will have to use the following link to login for the first time:

http://tikiwiki.org/tiki-login_validate.php?user=marclaporte2&pass=de7fdd5c84dae05d133dc75948188b4c

Enjoy the site!

Hi,

Marc asked me to report these two bugs -

"Found two bugs while registering (www.tmukraine.com.ua):
http version: Request not from this host.
https version: recaptcha code is not showing and thus, it's blocking"

I also found that there are CAPTCHA issues when using Mozilla FF (v.31) (no problems with Opera) -
on FF + Ubuntu 12.04 wasn't showing the CAPTCHA phrase at all.

Thanks,
Mike

{syntax type="tiki" editor="plain"}
If you set the "login_is_user" flag, registration fails with the message "email_not_valid".

I couldn't find a related issue (registration / register => dogfood category) so I create this.

It is actually super hard to register at Tiki.org.
This is critical and should be fixed asap.

If you don’t enter correctly the captcha ''(this may also subject to a sub-bug because when I tested I paid attention to those too hard too read letters)'' you enter in a loop of error you can’t get out.

{img fileId="1276" thumb="box"}
{img fileId="1277" thumb="box"}
{img fileId="1278" thumb="box"}
{img fileId="1275" thumb="box"}

When the website was back I tried to login and got another error:
Error
Account requires administrator approval.

I had to validate and then to confirm email using tiki-adminusers.php.

This is very bad for new user willing to register and it ended with Tiki.org not being available.

{syntax type="tiki" editor="plain"}
I want to allow registration without E-Mail.
Even though I have disabled all E-Mail checking it reports a validation failure.
The function validate_email called in tiki-register.php does as first task a format check on the E-Mail and returns false if the format is wrong. Emptpy emails result in false too.
Is this a valid decision at this point?

{syntax type="tiki" editor="plain"}
Don't know what to call it:

{FLASH(movie="http://worldfreemansociety.org/tikimovies/Bug-5RC1-Registration-ValidEmail.swf")}{FLASH}

Quick sensation in a production site of mine:

A new page in a wiki structure doesn't inherit categ perms from structure parent but only object perms (unexpected for intranet type of sections of wiki structures)

It does inherit permissions from the parent when local permissions are applied to the parent wiki page. However, in my opinion, category permissions (when there are no object permissions but category permissions) should be either applied by default to the new child page from the parent in the structure, or at least offer/warn the user about it with a checkbox for the user to select to copy categ. permissions also.

Regression: 'Users accept internal messages by default' is not applied to new users, therefore, no one can write them internal messages until they go there to allow that one by one. This is not the expected behavior in places like education, where plenty of students are created each semester, but there is not an easy way to preset that you can write to them (or among themselves) by default with nor further tweaking their preferences one by one.

The "Remember me" feature of login on tw.o sites doesn't really work as it should. On tw.o, dev.tw.o and themes.tw.o it's set via Admin > Login to values "tikiwiki, .tikiwiki.org, /, 1 week" and it lasts only some hour or so and expires then. It's annoying to relogin many times a day.

Based on my research, it looks like this feature was supposed to be removed. See http://dev.tikiwiki.org/tiki-index.php?page=Hello+World&highlight=CSRF

dthacker

The "Allow HTML" button is a PITA.

because it is default unchecked EACH TIME you open the edit screen. therefore if anyone puts html in a page it is by default not parsed the next time somebody edits.

This feature has never worked well. There is no active development on it. Should be moved to mods or just removed.

But there is not unanimity on this yet :-)
http://dev.tikiwiki.org/Endangered+features

There has been no commits on this feature for a year. We will re-add it later on via mods or in a future version


Not sure if this is fixed but in the past:

Homework menu appear twice
:: Homework
Assignments
Grading Queue
Last Changes
:: Homework
Assignments
Last Changes

Since Tiki JukeBox will not be ready in time for 1.9, it needs to be removed from BRANCH-1-9. Damian has indicated he will make it available via mods when it is ready.

To be reproduced, see:
http://xavi-9794-5464.show.tikiwiki.org/tiki-index.php?page=D1+Cover
u: admin
p: 12345

And see the same page as user:
u: user1
p: user1
which has been granted local permission to view and edit that page, and global permission to edit structures. If you attempt to go to edit the structure,
http://xavi-9794-5464.show.tikiwiki.org/tiki-edit_structure.php?page=D1+Cover&page_ref_id=1

you get:
{QUOTE()}
Error: You do not have permission to use this feature: tiki_p_view
{QUOTE}

Potential Workaround:
Comment out the check for the permission to display any part of the edit strcutures interface. Line 22 from tiki-edit_structure.php should become:
{CODE()}
//$access->check_permission('tiki_p_view');
{CODE}

And line 123 from templates/tiki-edit_structure.tpl should change from:
{CODE()}
{if $editable == 'y'}
{CODE}
to
{CODE()}
{if $editable == 'y' && $tiki_p_edit == 'y'}
{CODE}

Should that be enough?

I couldn't test properly due to the interference of this other bug which prevents assigning object permissions:
https://dev.tiki.org/item5916

This has also been reproduced on the http://demo.opensourcecms.com site.

I created a user. Then I'm trying to remove the "Registered" group from the groups associated to that particular user. When I click on the little x next to the group it disappears from the user's groups. Then I created a group named "blocked". This group only inherits from the anonymous group. It is created basically to prevent a user from having more permissions than an anonymous user, without removing the account (in order to reactivate the permissions at a later time). What I actually want to do is to deactivate some accounts and reactivate them later. So limiting the permissions to that of an anonymous user seemed an appropriate course of action. After removing the "Registered" group from the user's list, I assign him the blocked group only. This blocked group include the anonymous group and that's it. But, when I go to see the blocked group's permission(it has none of its own), I see some permissions inherited from the anonymous group (which is what I asked for) but I also see the tiki_p_edit permission inherited from the "Registered" group (which is NOT what I asked for). So it seems to me that when you have a user, it belongs necessarily to the registered group. And when you remove that group from the user's group list, it doesn't seem to have any real effect aside from not showing that group in the list. It would be interesting to remove that registered group from some users to deactivate their account temporarily. In any case this seems a bug, either removing Registered should have the expected effect, or it should not be possible to remove that group at all. I would opt for the first alternative.

Related:
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=1124

Unassigning several users from a group fail, only one is removed.

Check the instance;
Go to : http://bsfez-11581-6534.show.tikiwiki.org/tiki-admingroups.php?group=The%20group#contenttabs_admingroups-3

Try to unassign more than on user from the "The group". Only the first one is removed.

It is possible to list all users in a given group. However, to remove them from the groups, we need to go to another page.

We should be able to remove users from groups on this page:
tiki-admingroups.php?group=Registered&show=1

Using 2.3, when some user renames a page that you were monitoring, you get an email message with a broken link to stop monitoring, because there is no hash at the url.

Example:
^
If you don't want to receive these notifications follow this link:
http://yourdomain/tiki-user_watches.php?hash=
^

When you are on a page of a wiki structure, you can click on the print icon, but you will only print that single page.

The icon and option to "__print this page and all the subpages__" (= in the the sub-structure) right from there (without going through all the clicks at "Wiki > multiprint > select structure > print") would be very welcome, since the base feature to rpint the full structure exists.

From the home of the structure, it would print the full structure (as it can be done with one click from a structure within a Workspace through ((doc:AulaWiki)) mod, or through many clicks as usual, as explained above).

If the user is on a subpage of the structure, that button would print that page and all subpages from the same structure.

Does it make sense?