i need to remove the registration link inside the login view http://bartenders4hire.net/index.php/login without completely disabling the registration functionality.
We are using js Jobs on the site and the regular registration is not providing all fields, therefore i need to find the code where i simply can delete the registration link.
I looked inside the modules and plugins, but couldn't find it
Anyone has an idea where i can find that code?
You'll find the registration-link in /components/com_users/views/login/tmpl/default_login.php on the bottom of the file. You can override this file in your own template by copying it to /templates/yourtemplate/html/com_users/login/default_login.php. Then you can remove the registration-line from the file in your template,
regards Jonas
Related
I'm new to joomla and have got a problem with a website.
I need to modify a view and I've been told it is in
http://www.example.com/index.php?option=com_user&view=register&Itemid=68
It has a registration form and i need to modify its field. I've access to FTP only. I need to know where are these files to modify the registration form. If one can describe the meaning of this url structure then it would be very helpful.
You will find the template files in /components/com_user/views/register/tmpl.
However, you should create an html/com_user folder in your template directory with a copy of those files and use a template override ("never" edit core files).
Here are a couple resources that will point you in the right direction:
http://docs.joomla.org/J2.5:Developing_a_MVC_Component/Introduction
http://docs.joomla.org/How_to_override_the_component_mvc_from_the_Joomla!_core
com_user means use the user component register view.
Itemid 68 refers to the id of the menu item it is linked from.
You don't want to directly modify any joomla files.
If you want to add a field to registration activate the user plugin or create your own user plugin along the same design but with the fields you want.
It is advisable not to modify the core files directly, they will get overridden whenever the Joomla is updated.
However what you are looking for is available at components\com_users\models\forms\registration.xml file. you can change the default fields of the registration form in this file.
If you would like to add additional fields to registration form, there is a better way:
http://docs.joomla.org/Creating_a_profile_plugin
I installed an extension to add custom fields to customer registration form.I want to add some option value in dropdown menu box of input validation in backend admin page..could you plz tell me the path of the folder where can I find the phtml file which is responsible for that part ?
-Thanks.
The files you are looking for are in:
app/design/adminhtml/default/default/template
But just changing the .phtml file won't do the job. The customer model itself should be extended to provide for your extra field. Therefore i highly recommend you to write a module for this instead of altering Magento core code. This to make sure that you can still use updates in the future.
Writing such an module requires more in depth knowledge of Magento. For more information on custom adminhtml see here.
For information on extending the core functionality look here.
If you don't feel like programming this all yourself take a look at customer attribute modules on Magento Connect.
I tried to override profile.xml file along with edit.php (view file) by placing them within templates/template_name/html/com_users/profile folder, and also made sure the edit.php file know about new profile.xml ($this->form->loadFile( dirname(__FILE__) . DS . "profile.xml");) but i cant seem to make it work while updating custom fields from profile editing page at the front end. Also i can see that custom fields are not in order as it should be with respect to profile.xml. Please somebody help me...
You can't override an Joomla xml file. You need to create a user plugin to install separately for the form fields to appear. There is a profile plugin that comes with the default Joomla installation. Further details on this can be found here.
I would like to override my joomla registration component in the way to have next to it the login form as well. As first step I made in my template folder the registration call but from here I don't know how to include the login form.
thanks
fefe
Is this roughly the idea you're looking for?
http://zebiangroup.markmurphy.ca/component/users/?view=login
If so, I'll be packaging it up as an extension shortly. If you need it asap leave me a message at markmurphy.ca and I'll get in touch.
I'll be back to update this post when I have the extension finished and uploaded.
[Edit:]
I'd hate to leave you totally in the dark and keep you searching for an answer so I'll point you in the right direction.
I was able to write a system plug-in that overrides the user components' controller.php only if that component was the one being requested and if the requested view was for the login or registration and if the task was only to display.
From there I had the new controller.php override the requested view name substituting my own and adding the appropriate models, references and variables to the view.
After that all I had to do was add the layout to my active themes "html" folder under com_users.
I am loading the Joomla login module in an article using {loadposition xxx}.
when cache is on it doesn't works and give the error of Invalid Token.
What I figured out is that it is taking value of hidden field of the Joomla token from the cache which is usually generated randomly differently every time login module is loaded.
Can anybody have some idea to make it works?
First you cannot remove the hidden field of the token because this way the form will never work ... It's a required parameter so you have to restore it back and follow these steps
Go to the Module manager
One the module
The first item on the parameters is called "Caching" set it to never.
EDIT
You better use the plugin Modules Anywhere by Nonumber.nl
It fix 99$ of the issues that occur because of {loadposition} in regards to module title, content, caching ... etc