This component is great! When will you make one for Joomla 1.6? Or, how can I make the 1.5 version work with 1.6?

Thank you!

Hey,
Good question. I didnt have the time to try it on Joomla 1.6. So i really dont know
I will have a look at it soon. Ill let you know if it works. Did you try installing it on joomla 1.6 ?
Kim

Kim,

I have not tried to install it on 1.6. I don't want to run the risk of breaking something. From what I understand, there are different tables in the database.

Has anyone tried and was successful?
Can anyone help with upgrading it to 1.6?

I tried to install it on 1.6 and it was a fail. I so hope Kim gets some time for a 1.6 version, if you search for module to do this many forums are filled with people looking to do this. Thanks for developing it. I haven't needed it until I made my first 1.6 site so I haven't used it yet, but I am excited about the module non-the-less.

Hey Guys,
Well Joomla 1.6 is a big change i understand. I think there might be changes to the database. I installed Joomla 1.6 on my webhosting and it doesnt work very good. It is very slow! At least it is slow on my webhosting thow it meets all requirements for joomla 1.6.

I did read about the new joomla and i do see the advantages in it, like managing your own ACL. So it is easyer to configure permissions for each type of user in your joomla website. Also in Joomla 1.6 you can display modules on all pages but exclude modules from certain menu items! Which is a thing i always wanted!

But for now i am not to charmed of this new joomla version and i will keep using the old Joomla 1.5.22. But in a couple of months when Joomla 1.6 evolves to a more mature and trustable CMS. And when it runs on my webserver (Maybe needs upgrading after all?) i will make a joomla 1.6 version and post it here!
grtz Kim

I have come so close to getting your extension to work in Joomla 1.6. I am stuck at one point though, and can't really test it out to see if it is working or not, because I can not get the form to display on the front end.

I have changed everything else so that it will install into 1.6 without any problems, modified some other files so the the component options will display in the administrator side, added ACL support to the front end including a check to see if 1.6 is running, and reconfigured the call to get the user information for currently logged in user and pass that to the app.

I made appropriate changes to call the newer tables, and insert the users based on your scripting and reformatting for the newer tables in 1.6. I also am currently using ACL in my joomla 1.6 website, and have a test user with admin rights and a higher level of access.

At first all I got was the message on the screen "you must be a administrator or superuser...", but once I altered the file to include a call for user rights under the newer joomla that went away. Now all I get is a blank page with an error message on it "
Parse error: syntax error, unexpected $end in ..../public_html/components/com_adduserfrontend/views/adduserfrontend/tmpl/default.php on line 445"

I can't figure this part out. I don't know where it is coming from. Maybe you can take a look at what I have so far and get a release out to everyone for 1.6, without much work on your part. If you do a test install of Joomla 1.6.3, and install the zip I created, it will install just fine, and you can tie it to a menu item and try to launch it. Maybe it's a quick fix and we can finally have a 1.6 version of the best app on the market, in my opinion!

I could really use this for my project, as it required 1.6 for ACL functionality and some other requirements, but I need a way for people to add users securely from the front side as well (without giving them access to the back end).

Thanks so much!

Hey
Very nice work

After a couple of hours searching and recoding some stuff i got rid of the error. Now its working!

But there are a lot of things that need to be fixed. Security is gone, groups are not working as they should. emailadress validation, language strings ar missing and so on!

A lot of things dont work anymore. I also suspect that Joomla 1.6 is using another kind of password encryption.

So i will first fix as many stuff as i can. Then ill post a dev version of adduserfrontend for J1.6 for you so you can also have a look at it. We need to implement all setting you made in the new configuration tab backend.
Ill get back to you soon
Kim

Security and groups work completely different in 1.6, as a user can be a member of more than one group. The code I put in there is supposed to enable this functionality. As far as setting up your extension to use it, I have a feeling we're going to have to add a setting in the back-end config so that the front end automatically assigns that group(s) to the new user being created. As for password encryption, not really sure as I hadn't gotten that far. I did turn on the ability for the app to look for permissions on the user trying to access it, and I am not sure if it was fully working or not, as I couldn't get past the error message. I had my setup secured so that you must be logged in with certain privileges in order to use it. I would be more than happy to assist in any way that I can. I don't have that much php, xml, java coding experience, but could test and tweak existing to work out the kinks. Thanks for looking at it!

Hey Man,
Thanks for your help. It gave me a jumpstart getting the component to work with Joomla 1.6

I Fixed all problems and everything works as far as i can see. But i changed some stuff you did because i didnt understand it completely, so to keep it simple i deleted it and did it my way. It now works with the usergroups.

You can donwload the package at: http://www.ghanja.be/en/downloads/components/add-user-frontend/details.html
Tnx a lot, Kim

Hey man, Great Job!

Most of it works like a charm. There is, however, a small problem. You took out some functionality on the administration part that was needed in order to fully take advantage of the ACL functionality in 1.6.

You removed my "access.xml" file in the admin/components folder, as well as took out the "tab" for permissions in the "config.xml" file that I had inserted.

In Joomla 1.6, both of these settings are needed in order for ACL to work properly. If you look at the screen shot "adduserfront1.jpg" that I have attached, you will see that an error comes up stating I don't have view rights, even though it seems to function fine anyways.

To make this go away, you need those 2 items above, and to enable the permissions as you want them. This makes that error message go away, as it gives you rights to view and use it. As seen in screen shot "adduserfront2.jpg".

I have included those two files in a .zip attached so that you can review. These two files and the code they contain, came right off the Joomla 1.6 website under the documentation, if you wanted to look it up.

I think if you repackage those two components back in, and don't forget to change your installer file to include the "access.xml" file as I had it when I sent it to you, then everything will work perfectly after that!

Great job on this, and thank you so much for getting a new version for 1.6 out for all of us to enjoy! You are awesome!

Here are the screen shots, they got cut off due to some size limitation in your posts.

Only one image at a time I guess.

Here is the "adduserfront1.jpg" that shows the error message. This image above is the one after the error is fixed.

Hey,
Yeah i didnt understand the purpose of that code. And somehow i didnt get that error. But i will have a look at it anyway.
Tnx Kim

Yeah, every application now, whether built into 1.6 or outside, has this ACL permissions code in there.

Your app isn't very complex, so there isn't really a need to make it complicated.

Here is the link to the documentation on where I found that info: http://docs.joomla.org/Upgrading_a_Joomla_1.5_extension_to_Joomla_1.6#ACL_changes

I also changed that a little bit from what I just sent you again. There are 3 files in use here, "access.xml", "config.xml", and the sites "controller.php". I have changed these around a bit more to make more sense, and to try and actually get the ACL permissions to work like they should, ie disable use of the frontend if no permissions are assigned to that login group based on the users groups settings.

I am not sure how you are calling permission to use this object. If by number for admin or super user, you may want to look at the documentation on how to call all available groups for each user in an array, and then test against that.

There is some more documentation at and good links to others from there: http://docs.joomla.org/JUser::authorise/11.1

Hey man, what do you think all of this is about? It started a couple of days ago. Everything was working fine with the adduserfrontend, and all of a sudden these error messages started appearing above the form.

"Notice: Undefined index: firstname in /home7/peoplep3/public_html/components/com_adduserfrontend/views/adduserfrontend/tmpl/default.php on line 1073

Notice: Undefined index: lastname in /home7/peoplep3/public_html/components/com_adduserfrontend/views/adduserfrontend/tmpl/default.php on line 1081

Notice: Undefined index: email in /home7/peoplep3/public_html/components/com_adduserfrontend/views/adduserfrontend/tmpl/default.php on line 1109

Notice: Undefined index: username in /home7/peoplep3/public_html/components/com_adduserfrontend/views/adduserfrontend/tmpl/default.php on line 1125"

Any ideas on where this could be coming from? It references the lines that have the field names and types of test with the "$_Cookie" part.

Hey
I have no idea what could cause that.
Kim

QUOTE:
Yeah, every application now, whether built into 1.6 or outside, has this ACL permissions code in there.

Your app isn't very complex, so there isn't really a need to make it complicated.

Here is the link to the documentation on where I found that info: http://docs.joomla.org/Upgrading_a_Joomla_1.5_extension_to_Joomla_1.6#ACL_changes

I also changed that a little bit from what I just sent you again. There are 3 files in use here, "access.xml", "config.xml", and the sites "controller.php". I have changed these around a bit more to make more sense, and to try and actually get the ACL permissions to work like they should, ie disable use of the frontend if no permissions are assigned to that login group based on the users groups settings.

I am not sure how you are calling permission to use this object. If by number for admin or super user, you may want to look at the documentation on how to call all available groups for each user in an array, and then test against that.

There is some more documentation at and good links to others from there: http://docs.joomla.org/JUser::authorise/11.1

Well i dont see the purpose of implementing those features. I just want Superadmins and Admins to add users. Not the rest....

I think it's a very useful extension. I have the same issues that mstarr68 and I agree that this extension should allow their use in accordance with the ACL group JL16. For example, I want to be used by the publishers group, for that reason I modified the code. I know that modification it isn't perfect, rather it is a workaround to used it. I have cleaned (tab, comments, send email as html without special character error code) and some change code to eliminate the error messages (some variable initialization, delete S_COKIES,..., as mstarr68 indicated previously). Exactly \components\com_adduserfrontend\views\adduserfrontend\tmpl\default.php file (see attachment).

I need to have an extensions to create/delete users from Front-End by Publishers (no admin). For the moment, I can create new users from FrontEnd with a publisher user and delete user extension from Front-End .... I'm looking for I

mstarr68 wrote:

QUOTE:
Yeah, every application now, whether built into 1.6 or outside, has this ACL permissions code in there.

Your app isn't very complex, so there isn't really a need to make it complicated.

Here is the link to the documentation on where I found that info:
http://docs.joomla.org/Upgrading_a_Joomla_1.5_extension_to_Joomla_1.6#ACL_changes

I also changed that a little bit from what I just sent you again. There are 3 files in use here, "access.xml", "config.xml", and the sites "controller.php". I have changed these around a bit more to make more sense, and to try and actually get the ACL permissions to work like they should, ie disable use of the frontend if no permissions are assigned to that login group based on the users groups settings.

I am not sure how you are calling permission to use this object. If by number for admin or super user, you may want to look at the documentation on how to call all available groups for each user in an array, and then test against that.

There is some more documentation at and good links to others from there:
http://docs.joomla.org/JUser::authorise/11.1

Bijlage:
Bestandsnaam: samplefiles.zip
Bestandsgrootte: 2606

Hey Guys,
Thanks to both of you for your work. I compared your codes with each other and my code and i merged the 3 of them. Now we ve got the ACL working in Joomla 1.6. Thanx to mstar68 who put me on the right path. I didnt found the errors you were talking about at first. But as i got deeper in to it i saw them except from the cookie errors

So i found how to implement the ACL in the component. mstar68 already did his part in the controller. But in the component file we needed to add:

// Access check.
if (!JFactory::getUser()->authorise('adduserfrontend.createuser', 'com_adduserfrontend') {
return JError::raiseWarning(404, JText::_('');
}

I changed my code like mckillo did to fix the errors. But i did put back the cookies. I need them for some functions! But i tried putting ISSET's around them. I hope this will fix it:

if(isset($_COOKIE['cookiename'])) {

$savedcookiename = $_COOKIE['cookiename'];

}

So guys please let me know if this works for you.
You can find the new version of add user frontend here: http://www.ghanja.be/en/downloads/components/add-user-frontend/details.html

mckillo wrote:

QUOTE:
I think it's a very useful extension. I have the same issues that mstarr68 and I agree that this extension should allow their use in accordance with the ACL group JL16. For example, I want to be used by the publishers group, for that reason I modified the code. I know that modification it isn't perfect, rather it is a workaround to used it. I have cleaned (tab, comments, send email as html without special character error code) and some change code to eliminate the error messages (some variable initialization, delete S_COKIES,..., as mstarr68 indicated previously). Exactly \components\com_adduserfrontend\views\adduserfrontend\tmpl\default.php file (see attachment).

I need to have an extensions to create/delete users from Front-End by Publishers (no admin). For the moment, I can create new users from FrontEnd with a publisher user and delete user extension from Front-End .... I'm looking for :-) I

Bijlage:
Bestandsnaam: default.zip
Bestandsgrootte: 4879

Tnx a lot i fixed it. See the other message i posted in reply of mstar68

With v.1.2.6 for JL16, the error message come back, for example for savedemail variable "Notice: Undefined variable: savedemail in /var/www/vhosts/xxx.es/httpdocs/web/components/com_adduserfrontend/views/adduserfrontend/tmpl/default.php on line 424".
The issue is because savedemail doesn't exist, the condition of this if is false:
if(isset($_COOKIE['email'])), then the savedemail variable (into if) doesn't create.

For the moment, my 424 line in components/com_adduserfrontend/views/adduserfrontend/tmpl/default.php is:
<td><input type="text" name="email" value="" /></td>
and so on for 409, 413, 418, 430 and 437 lines.

Why do you want to use both cookie for these fields?. When you create a new user name, email, ... are different for each user.

New feature: Define the contents of fields in size and content type. For example, username, less than 5 characters and numeric type.

When a double email or username check is done and the username or email already exist in the joomla system the component will bring you back to the form with all fields filled in like you have done before. Because the values are saved in cookies.

I finally found that these errors by turning on error_reporting = E_ALL in the php.ini file in my hostingaccount. I have fixed it with:

if(isset($_COOKIE['name'])) {

$savedname = $_COOKIE['name'];

} else {

$savedname ="";

}

I think this solves the problem

I updated the files at: http://www.ghanja.be/en/downloads/components/add-user-frontend/details.html

Now, it's working, but with your explanation I try to understand and make sense, but I can not find it or at least I do not see the objective.

I try to explain my point of view with my case:

1. My Con_adduserfrontend_configuration are:
Mode: Only Joomla
Namemode: Name
Username: Choose username
Check username: Choose another username
Check email: Check for double emails
Choose password: Dont choose password
Choose email address: Fill in email address
Email notification: Send notification email
Usertype: Registered
Custom Group: <nothing>

2. When I want to create a new user, I have to write 3 fields: name, email, username
Name is only one word.
email is particular email (gmail, hotmail,...) for each user.
username: membership number (5 digit numbers)

3. Only if I fill the 3 fields, I can press the button to create a new user, otherwise a warning message I have to fill the field that is empty.

4. If the field name or email is already registered in the database, the fields have the same data I have previously written, regardless of the code you have developed with cookie.

Then, in my opinion, I think you do not need any treatment through the Cokie. In my case, all data is written before I press the button and also in the case of username or email already registered, why I want the data from the previously registered user? I suppose it could be useful for other settings in the component.

Thank you for your support and quick reply.

Hey,
Well in reply to point 4. This is not true in all browsers. For some browsers we need the cookies. Otherwise the user needs to fill in all fields again!

QUOTE:
why I want the data from the previously registered user?

We dont want the data of the previously registered user. Cookies just save temp data on the computer of the user. If the username or emailadres already exist people will get redirected to the add user screen where the cookies fill out the fields again. These cookies only last 3 seconds and then are deleted so it will only work on redirection. It will not show the data again if you add multiple users one after another...

Ok, I don't know that your compoment needs cokies, but I suppose that old browsers. I tested my previuos modification with IE 8.0 & 9.0, FX 4.0 y 5.0, Chrome 12.0 and It's working without cokies.

Besides, I discovered another error the combination of component options and in my case is when the username is registered in the database. I try to explain with the line number of /components/com_adduserfrontend/views/adduserfrontend/tmpl/default.php file

Line 101: If $namemode == 0 //by configuration
and
Line 110: If $xname[1] == 0 //name is one word
Then
Line 222: lastname not defined

You can see in your web page the message error:
"Notice: Undefined variable: lastname in
/var/www/vhosts/xxx.es/httpdocs/web/components/com_adduserfrontend/views/adduserfrontend/tmpl/default.php on line 222".

Hey,
I dont get it completely because the line numbers you give dont match with mine. Anyway just turn of error reporting on you server and all will work fine

I can only see these errors when i change the settings on my webserver by php.ini. You can turn error reporting of and is fixed.
Kim

I don't want to hide the errors, I prefer to debug them. Here you are the capture with the line code. Now, default.php file is the same (last version 1.2.6).

Well I did change some stuff now. I updated the files on the download page. I hope this time it will be fixed

Thanks, it works without error.

Super