Category: User Administration (Registration, Login & Banning)

When logging into my site under various accounts the Apache web server intermittently crashes with the following error in the error log:

[Thu Oct 26 00:20:05 2006] [notice] Parent: child process exited with status 3221225477 -- Restarting.
[Thu Oct 26 00:20:05 2006] [notice] Apache/2.0.59 (Win32) SVN/1.3.1 PHP/5.1.6 DAV/2 configured -- resuming normal operations

I have not made any modifications to the TikiWiki code (1.9.6) or changes to my server configuration. Everything was working normally for several months before the error started to appear.

I am able to force a similar crash to occur every time throught the Community -> User List feature (tiki-list_users.tpl). I debugged the template code and found that userlink in the following caused the crash:

{section name=changes loop=$listusers}
<tr>
<td class="odd"> {$listusers[changes].login|userlink} </td>
<td class="odd"> {$listusers[changes].realName} </td>
{if $feature_score eq 'y'}

Any help?

-Anthony

See video:

{FLASH(movie="tiki-download_item_attachment.php?attId=62",width=>876,height=>677,quality=>high)}{FLASH}

One cannot assign permissions on individual FAQs. This prevents from creating FAQ for different level of users.

A number of users in the [https://tiki.org/forumthread59532?topics_offset=29|forum] liked my suggestion of an "auto delete unverified user feature." Often times spammers attempt to create accounts with fake email accounts. These accounts accumulate over time creating a nightmare to clean up after a while.
A feature to delete users matching this status after a specified period of time will help reduce the need to search through the user lists to purge invalid accounts.

''Reviewed with Tiki25''

--If the auto-assign is set to "Creator" and the admin edit an existing item with a null username (creator deleted, error with duplicate feature, etc), the admin username will be assigned and saved. This can happen even if admin doesn't see the field (if he use a modal to modify some preferences or part of the item).--
''Not able to reproduce anymore, may have been fixed''


If the admin duplicate an item that has a another user selected in a user selector field, the new item (the clone) will be saved with the admin for user.

{FADE(label="Instance")}
__Tiki show trunk and Tiki show 24 are not working as expected__ but I could reproduce the bug on a Tiki24 instance:
http://bsfez-11581-7751.show2.tiki.org/tiki-view_tracker.php?trackerId=1

If you want to reproduce you can log as admin/12345 go to the tracker a duplicate an item from a different user using:
http://bsfez-11581-7751.show2.tiki.org/tiki-tracker-clone_item?trackerId=1&itemId=1&modal=1
{FADE}
{img fileId="2021" thumb="box"}

Hi, I've just added a new banning by ip rule at tw.o:

Title User/IP Sections Action
IP_dedes151_81.18.70.166 81.18.70.166 blogs, categories, cms, directory, faqs, featured_links, file_galleries, forums, galleries, gmaps, mytiki, poll, user_messages, wiki page

but I got message
^
Notice: this variable may not be empty: user
^
On a tiki screen as if I was not logged (and I was, as user xavidp with admin rights).
But below, after the footer section, a new tiki header and the rest of another tiki page appeared, and it looked as if Tiki recognized me as logged on the header (my picture is shown), but the login module was also shown for anonymous to log in, on the right column.

See html attached.

The rules seemed to be saved.

{syntax type="tiki" editor="plain"}
Rule activated by dates
Rule active from
Rule active until
Upgraded tiki: Shows years 1969 till 2010
Clean install: Only gives the year 2010 to chose from
This year is almost over so whould be nice to have some later years to chose from.

It would be useful to extract all permissions of File Galleries or Wiki pages or Forums, etc

This would provide a way for admins to know who actually has access to what.

Right now, group expiry just removes the user from the group.
In use cases of membership management in associations, or business, in which members pay a fee per year, this feature is needed for an easier setup without so much intervention of the admin in so many steps.

Scenario: NGO with 3 levels of users:
* A) "regular members", needing tyo pay fee FA
* B) "associated members" , needing tyo pay fee FB
* C) "students", needing tyo pay fee FC

2 levels of time-dependent fees for each group:
* first year you pay feee F*1
* from second year onwards you pay a different fee F*2

When the membership payment for a year is over, that user should be automatically re-assignable to another group defined in the group transitions, which should allow to set conditions for the trigger to happen:
* when group expiry happens
* when freeperiods frmo ((doc:PluginMemberPayment)) expire
* when some tracker field = some value, higher/lower than some date or other tracker field, etc. (this one is just brainstorming; it should be thought more {sign user="xavi" datetime="2016-05-27T10:51:06+00:00"})

This way, they can be requested to pay for the fee F*2, knowing that they have to pay FA2, FB2 or FC2. With current codebase, after gruop expiry, you do not know which group that user belonged to, and you can't offer that user the right fee to be payed for with plugin MemberPayment.


HTH

It would be great to be able to bind arbitrary actions to user creation.

For example, I would like to have a blog created on user registration, named after the username.
Then I might want to have only that user with permissions for some items.
Maybe point the user's group homepage to something user-specific.

And et cetera :)

Discussion over at ((Spam Protection))

http://www.wikimatrix.org/wiki/feature:Blacklist

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))

{syntax type="tiki" editor="plain"}
The number count in a password is rated using this piece of code in lib/tiki-js.js:

// Numbers
var nNumberCount = countContain(strPassword, m_strNumber);
// -- 1 number
if (nNumberCount == 1)
{
nScore += 10;
}
// -- 3 or more numbers
if (nNumberCount >= 3)
{
nScore += 20;
}

This causes a password with 1 number to get 10 points extra, a password with 2 numbers extra points, and a password with 3 or more numbers 20 extra points.

EDIT @joel.magene 2026/06/02:
Current master still miscalculates password number scoring, but differently from the original report.

In lib/tiki-js.js, the current fallback branch gives +10 points when nNumberCount is less than 3, including when it is 0. This means passwords with no digits are overrated.

Expected:
0 digits = +0
1-2 digits = +10
3+ digits = +20

Fix: only apply the +10 fallback when nNumberCount > 0.

When logging in wrongly with LDAP (no such user or wrong password), will get:

Fatal error: Call to undefined method Net_LDAP2_Error::getEntry() in /var/www/html/watwiki/lib/auth/ldap.php on line 257

(or white screen unless Error reporting is turned on for all)

Strangely this only happens if you key in a password 5 characters or longer. A shorter password will just show "Invalid password" or "Invalid username" as the case may be.

Hi:
For some reason I can't get login popup to *.t.o sites from android smartphone.
* t.o/forums: I can't see the "Log in" part on the top horizontal bar of the site, that I see using a desktop computer.
* dev.t.o: I can see indeed the "Log in" part on the top horizontal bar of the site, but clicking on it does nothing (apparently) for me.
* dev.t.o: clicking on the icon to display the contents of the top horizontal bar of the site does nothing for me.

:-/

We need improvements to that *.t.o site-bootstrapification maybe?

Xavi

Hi

When logging in, the "Remember me" checkbox seems to have no effect. After what appears to be half an hour, I need to login again.

I've done these settings in the "Log in" control panel:

* Remembe me: User's choice
* Duration: 1 Week
* Refresh the remember-me cookie expiration: off
* Cookie name: tikiwiki
* Path: /tiki/

Hey there,

talking about tiki-adminusers.php

Just recently tere was a new dialogue added to apply users. Today a popup opens and you can choose respectively multiselect groups to apply the users to or to remove users from.

I could not really test this good looking feature if it works spot on, or is tere would appear objections, because on save the user is not applied to the group - the setting is just ignored.

So on a site already having this update, I have to apply users to groups from tiki-admingroups.php tab 'members', which is a workaround, but not a good UX for te released system (thus a blocker).

I will look into it for a more detailed description lateron and try to find out who committed tis. Anyway, it would be nice, if someone of the coders could check and maybe fix ... I recon, that only a very little bit is missing.

{syntax type="tiki" editor="plain"}
When you have a group name like "Finance and Marketing Departments" and you create another group called "Finance and Marketing Departments Moderators". You will not be able to add users into the latter group if that user is already in the first group. This is caused by "duplicate key" error in the attempt to add the user, because the key length limitation is 32 chars.

This bug might probably be Mysql settings dependent.

There seems to be a button broken in tiki-admin_users.php, after changing the users's password, the confirmation screen appears and the "confirm" button does nothing.

Tested in three different installs in 5.3, including after svn up.
Tested in FF and IE8.

When using LDAP External authentication, I am unable to create a new user on the user administration page.

It does not require a password to create the user, but when you click Add, you receive the error message "Password should be at least characters long"


Users are created when they login the first time, but I need to configure permissions before they login.

We recently upgraded from Tiki-4.X to Tiki-5.X. We are running Tiki-5.3.

There seems to be a bug when trying to modify a user under the administration page (tiki-adminusers.php). When trying to click on a user, one is asked to confirm (which is a new workflow) and then taken to the Edit User page. However, when one tries to modify something (e.g. password, email address), you are asked to confirm again, but it never completes.

Here is a set of detailed steps to reproduce the problem:
# Go to admin users (tiki-adminusers.php)
# Click on user "demo"
# Click "Click here to confirm your action"
# Change email address from demo@demo.com to demo@demo.org
# Click "Save"
# Click "Click here to confirm your action"
* Nothing happens. The page address is "tiki-adminusers.php#", but it never changes from the confirm action page. "Go Back" does not work, but "Return to Home Page" does.

I installed Tiki 5.3 from Fantastico and then ran the setup script.

I was able to create some new users and assign them to groups.

The problems manifested when I attempted to change the default admin password and the password that I forgot for one of the new users.

Upon clicking "Edit Account Settings" next to the user, tiki-adminusers.php is displayed with the user number (e.g. tiki-adminusers.php?user=3).

There are three buttons, clicking the one to "confirm" the action causes tiki-adminusers to display a form for editing the password, email, etc. for the user.

"Saving Changes" causes tiki-admin users to again present the three buttons, this time without any user number on the URL.

Clicking to "Confirm" adds a "#" sign to the end of the URL, but nothing seems to happen.

The original password is unchanged and other values entered on the form are unchanged.

I have encountered a few snags after upgrading from Tiki 1.9.11 to 2.0

One of the problems is that I am unable to register / add users, because of the following error message:

An error occured in a database query!
Unknown column 'email_confirm' in 'field list'

This happens on
tiki-register.php (registration) and tiki-adminusers.php (batch upload / add)

Is there a fix for this?

Seems like Tanzania keeps falling out of the country list. This was the case some years ago. Might as well add Swahili as a language option if applicable.