Forum OpenACS Q&A: How to customize the login process

Collapse
Posted by Hérick Moniz on
Hi,

First of all, congratulation to all for the terrefic work you have done on this new release. I follow OpenACS since 2000 and I have made myself a few site using OpenACS 3.5 but I never succesfully installed OpenACS 4. The installation of this new release has simpler and I did it on OpenBSD 3.3 and MacOS X Server 10.3 !!!

So now I like to move to OpenACS 5.0 and I like to know what is the best way to customize only one module. I like to be able to put the login process adn the registration into a IFRAME.

Should I replace <master> for <master src="mytemplate"> in all ADP file of the register module or there is a a way to do with with the subsite function.

And also, how could I contribute to a french localization of OpenACS ???

Thank you

Herick

Collapse
Posted by Chris Davies on
I believe http://translate.openacs.org/ is the URL for helping the translation project, and it appears that French is about 1/3 done.
Collapse
Posted by xx xx on
I often have trouble to login at http://translate.openacs.org. It throws me back to http://translate.openacs.org/register/ forever.

I would use http://translate.dotlrn.collaboraid.net/ if you experience the same thing. Peter/Carl can give you permission.

French is an important language to add so please join.

Collapse
Posted by Hérick Moniz on
Hi again,

So if I understand correctly you prefer that I do the translation on translate.openacs.org but how could I use it in my own project after ? With CVS ???

For a look of what I am trying to do with the login process look at http://www.postedecoute.com/ and click on "Connecter"

This will display a hidden DIV containing a IFRAME with the /register/ page in it.

I have tried to make a custom site so I could apply a new template to register. But some files redirect to the main register page instead of my /subsite/register.

I like to know if I have taken the right approch to this problem.

Thanks for your help

Herick

Collapse
Posted by Joel Aufrecht on
One basic approach is that you do primary translation work on the public translation server, translate.openacs.org.  This work can be overseen by professional translators, both paid and volunteer, and by the community at large.  The work on the translation server is converted to "catalog files," which are XML files that are included with every package and loaded into the database on installation (for English) or when a locale is enabled (for everything else).

So step 1 is do the translations.  Step 2 is that the consensus translations get into the OpenACS CVS tree - this process is awaiting some final code fixes and an upgrade to the translation server to make it easy and automatable.  Step 3 is that new OpenACS releases provide the new translations.

Step 3a is a mechanism for existing sites to easily get new translations - this step hasn't been fully addressed that I'm aware of, because it's actually pretty complicated.  The first part is to get the new files - you can do this via CVS, which is not hard but not automatic either, and could be tedious if you have a lot of locales in a lot of packages.  The second part is to get the new locale data from catalog files into your system.  You can simply re-import the files (import is part of what's done automatically when you Enable an locale).  This will overwrite any existing translations on your site.  If you have none, great, you're done.

But if you have customized your own translations, then you have essentially the same problem as if you have customized some of the standard code - you have to do a merge when you get new translations or new code.  Fortunately, acs-lang in 5.0.0 includes a merge mechanism for this.

So the bottom line is, if you have time to wait 1-2 months while this process is ironed out, do the work on the translation server and then import it back to your server with the next dot release.  If not, do it on your server and we'll figure out how to get it to the translation server.

Collapse
Posted by xx xx on
But some files redirect to the main register page instead of my /subsite/register.
You'll have to track down why this happens for example change: https://openacs.org/api-doc/proc-view?proc=ad_redirect_for_registration&source_p=1

Also, you may want to share thoughts with Cathy to make subsites work as independent sites. Don suggested: 'We might want to parameterize the toolkit so you can install it in a "each subsite is its own world" mode.'

(It's another example of a project that would benefit from creating a bazar at OpenACS, IMO)