Is a problem that I'm having, I think that will be resolved when ?trabis have finished updating all the files that contain this class 'XoopsLocale', hopefully soon, otherwise it's a mess without being able to test the new features ?

tatane wrote:

Quote:

trabis wrote:
1 - I think we can add some axaj yes. By 'we' I mean some other core developer that has more experience with jquery than me!

Yes, but everyone does not know the language ajax or another, we must think of the people who come on Xoops beginners wanting this option. If he sees that he must seek the help of a developer to add this option they will go elsewhere.

irmtfan wrote:

after 10 years i still cannot understand why core team always think we must have one field for login?
we can login with both "uname" and "email" fields.

tatane wrote:
I have two question: when someone creates an account in the field "nickname" would it be possible to have a system which is where the nickname is already taken him that it can not be used?

Because currently the member must validate their registration to whether or not the name is used similarly for the e-mail address

you go to integrate the system account creation by email and not by nickname?

Thank you

timgno wrote:

A question, the same XoopsLocale class and translate function is only for the modules?

timgno wrote: Quote:

Fatal error: Class 'XoopsLocale' not found in C:\wamp\www\2.6.0\htdocs\class\module.textsanitizer.php on line 481

Parse error: syntax error, unexpected '<<' (T_SL) in C:\wamp\www\2.6.0\htdocs\modules\notifications\index.php on line 69

irmtfan wrote:
@Trabis:
I review your updates. they are really fantastic.
Now all local needs are covered include isRtl and isMultiByte.

just 2 point:
1- will you add strtotime in the future?

2- a bug in your example pt_BR in xoops26/locale/pt_BR/locale.php

class XoopsLocale extends XoopsLocaleEn_US{

should be XoopsLocalePt_BR

Cesag wrote:

Standardize everything and have (") everywhere, it will be less ugly and prevent errors with (')..

flipse wrote:
Troubleshooting xoops modules or looking for updates is time consuming now. You have to search in all kinds of forums or it seems websites from developers don't exist anymore. Most frustrating is the fact the information you need is divided on many pages and websites, or is gone...

I love the way all information around a WP plugin can be found on a single page. Updates can be found there, latest version downloads, support questions asked, bugs reported, there is a link to the developer site and so on... We could also add links to all module translations.

Why not develop such a concept for xoops.org?