Login, forgot password, signup and other tpls...

Hi Guys..

Which files actually update the main JR tpls for Login, forgot password, signup? Are the files in the skins templates folder or module jrUser templates folder?

Thank you!

Marla
updated by @sweet: 08/07/26 12:31:30PM

check your skin, if it has jrUser_user_login.tpl, then thats it otherwise the one in the module.

I tried that and reset the cache but the new changes wont show. I dont see any erros in the dashboard.

if you've changed the .tpl file on the server by changing it then re-uploading it and then resetting the caches and it doesn't change then it could be that there is an over-ride in the ACP skins -> templates tab that's active OR there might be changes to the user modules template as an override in the ACP.

There's a few methods to make changes and sometimes making changes to a site where differnt methods have been used it can be hard to locate the source.

check
ACP -> SKINS -> (your skin) -> TEMPLATES -> the template your intereste in .tpl
ACP -> MODULES -> USERS -> USERS -> TEMPLATES -> the template your intereste in .tpl

Still trying to figure this out. I did a fresh install and still unable to edit the tpls for Login, forgot password, signup.

how are you trying?

--edit--
Make sure that if you are using a local server you must be using a domain name, jamroom wont work off of 127.0.0.1/ or localhost/

you can give local sites a domain name using /etc/hosts to use a somthing.test domain.
updated by @michael: 07/21/26 11:32:02PM

these docs are 2 ways to make adjustments

Docs: altering a module's template
https://www.jamroom.net/the-jamroom-network/documentation/module-developer-guide/1051/altering-a-modules-template


Docs: Using the Template Editor
https://www.jamroom.net/the-jamroom-network/documentation/jamroom-admin-handbook/3183/using-the-template-editor

Which you should use is most likely determined by how you like to build. If you use an IDE then you probably wont use the Template Editor.

I'm using localhost/mysite. Everything seems to be working fine but just these few tpls wont update. I've tried editing the tpl's directly and in: ACP -> SKINS -> (your skin) -> TEMPLATES ->
ACP -> MODULES -> USERS -> USERS -> TEMPLATES ->.

I'll take a look at the guides.. thank you!

make sure you go to the TEMPLATES page, check the checkbox then SAVE to activate the over-ride, then reset the caches
ACP -> MODULES -> CORE -> SYSTEM CORE -> TOOLS -> RESET CACHES.

OR you can go to the DEVELOPER module then to GLOBAL CONFIG and turn on "Run in Developer Mode" to turn caching off while you build.

If you want to use .tpl files in you skin directory for login and signup, you'll want to enable them in your ACP > Users > Users > Site Options and check the Enable Templates checkbox then click the Save Changes button. Be sure to reset caches too.


--

Douglas Hackney
Jamroom Team - Designer/Developer/Support
FAQ-Docs-Help Videos

Hi Douglas,

That page does not exist in my Jamroom.

user/admin/global/section=site+options

This page does not exist

Would you like to create this page in Site Builder?

What should I do now?

Thank you,

Marla

You should be able to go to your ACP > USERS > Users > Global Config > Site Options; it is a built-in feature for the User module. If you don't see that tab under the Global Config tab, you may need to update your install. ACP > CORE > Marketplace > System Updates.

If you don't need to update, and you still are not seeing that setting, you'll want to send us your admin login to support_at_jamroom_dot_net so we can check it out.


--

Douglas Hackney
Jamroom Team - Designer/Developer/Support
FAQ-Docs-Help Videos

I'm working on my laptop. I'll try to update because I'm seeing a lot of pages with this: This page does not exist. Would you like to create this page in Site Builder?

I'll try that. Thank you!

It can be confusing as to why there are multiple locations to edit stuff. Here's a short 'why'.

In the beginning Jamroom was not editable by the end user, there was no way to extend it without asking for a feature. It was also only for music websites. With version 4 (I think) we got a way to add modules to extend the ability of the system. Making a module meant building in php and uploading via FTP to your server.

With jamroom 5 the architecture changed to make 'jamroom' just a core set of modules of which even the core was a module of itself. Skins became a way to take advantage of the modules that existed in the system. So if you built a skin you might make it general and able to use ANY module or you might make the skin require X modules and not work with some modules. How the site looks is pretty much controlled by how the skin designer chose to build.

To allow the skin designers a way to customize things like the login page 'template overrides were added'. That meant that a skin could take the template a module used and copy it to the skin, then the system would prefer that template over the one the module has. ie jrUser_login.tpl.

Docs: Altering a modules template
https://www.jamroom.net/the-jamroom-network/documentation/module-developer-guide/1051/altering-a-modules-template

That flow worked well for a while, and is still the flow that most developers will use as it allows for module updates without needing to re-add the changes.

Then the request came in from non-developers to be able to make 'just small tweaks'. The system built for them was the TEMPLATES tab in the ACP in the MODULES and the SKINS section. Its supposed to be a one-or-the-other setup but if you use both it can be really hard to figure out if where the over-ride is.

After all these years of using JR I still find it hard to navigate the ACP... so I've created a simpler ACP for my site that works for my needs.