Close to next release: 2 bugs ...

Worker Joined: May 15, 2004 Posts: 119 Location: Germany

Hello again,
I lost lost you some posts ago ... Hope you get it fixed and the new release will be available this week because I have one week vacation Smile

Happy eastern, for the last 10 Minutes ....
Regards, Benson

Posted: Mon Apr 17, 2006 4:46 pm

Not a problem, on it now.

Posted: Thu Apr 20, 2006 10:46 am

Hi,
I am sitting here in front of my computer and I am waiting for the next release ... I think I make a lot of traffic to that page by updating it every hour just to to see if the new version is available ... Smile

Ok, make it a final release, not a new alpha beta or what ever ...

Just some last comment to the NSN group integration. I do not understand that module/function very well and I do not need it, but ok it might be good to have a more flexible access handling for the future. This integration seams to be the reason for some additional problems I have with my german translations. For example in the admin section for modules there is, if I change a existing module, the following text 'What Groups:' or 'View must be SET to Groups Only', that is not a problem, but the integration should be completely translated ... ?
Another problem for me is that I have the admin module Groups and NSNGroups, both are not talking to each other ...?

Also in the 'Groups Administration' there is a bug in 'Groups Configuration'. '# items in lists' (for what is it good for?) is allways emty ? Even if I select 10 it is empty the next time I load that page ...
The field 'Date Display Format:' is also a problem to me, if I key a invalid date format, no group is shown anymore in the 'View Groups' section ? I have to select again 10 for '# items in lists' and save it, then all groups are shown. Entering a date format, saving, all groups are not shown anymore .... ?

Ok, I do not understand that module, as I said, but it seams to be buggy ....

Best regards, Benson

... still waiting ...

Posted: Thu Apr 20, 2006 12:54 pm

Benson, I can just tell you that there a number of bright and dedicated people led by Raven trying to get this release out the door and have it be relatively bug free and stable. Given the starting point, which is a bug filled PHPnuke, it will not be absolutely bug free but it will be a lot better than any other Nuke distribution has ever been.

I don't think you need to be checking every hour, once a day would probably do you fine. Your bug report on Groups will be put into the process but, if I had to guess, resolving it will probably get pushed back to the next release. Others can speak more authoritatively to that though.

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

fkelly is right! I had to draw a line in the sand and it is done and released! Read the News item at [ Only registered users can see links on this board! Get registered or login! ]

Posted: Thu Apr 20, 2006 6:32 pm

I think it rocks myself.....

Posted: Sun Apr 23, 2006 1:00 pm

Quote:

For example in the admin section for modules there is, if I change a existing module, the following text 'What Groups:' or 'View must be SET to Groups Only', that is not a problem, but the integration should be completely translated ... ?

Did you already found the file for your translation ? This is in language/groups/lang-english
You need to copie the language file, rename it to lang-german.php translate this into German and upload the file. Afterthat your Block Navigation should be translated.
Maybe you need also to translate same parts in admin/languages/lang-german.php e.g. Visible to Subscribers only. Smile

We knew this procedure from phpBB language files right Benson ?

Posted: Sun Apr 23, 2006 2:06 pm

Hello Susann,
yes, I found it and I do not have problems to make my own lang-german.php file.

I already stressed Raven a lot with my 'hardcoded' language problem Very Happy

.

Posted: Sun Apr 23, 2006 2:40 pm

I know but I quess at the time he is stressed enough.
But feedback is always wise.
What do you mean ? Wouldn´ it be better to place the text 'What Groups:' or 'View must be SET to Groups Only', also in an other place meant language file instead of the groups or just add the missing language files also in the folder language/groups ?
I have that feeling that many users don´t search in this folder to translate "View must be set to Groups only" and "What Groups" into her language and they wonder why it´s always in English. Maybe I´m wrong.

Posted: Mon Apr 24, 2006 1:07 am

Hello Susann,
I think the translation should be in the language file for the related module. That will make it more easy!
I was confuded and I did not find it Embarassed

Regards, Benson

Posted: Mon Apr 24, 2006 7:31 am

Let me just add in that core Nuke and many addons are not conformed to a strict language file / script separation. This is one of the items on our agenda for v2.10.00. We wil try our best to clean up our own house before releasing the next version. We just ask for patience Wink

Posted: Mon Apr 24, 2006 11:35 am

Hi Raven,
I am totaly satisfied with the actual release, so don't hurry!

In general, you should give a statement about security, I mean if a new patch level is relesed (e.g. 3.3) I would like to know if my site must be updated or not, so maybe you can release a security update separtely to a new release ?
Regarding the language issue, for me it is difficult to handle it if it would be in one big language file. therfor it is a good thing to have the module depending things in a separate language file as it is almost now.
If the missing translation for e.g. the admin part of modules is located in the language file for the groups module, I can find it (search) but I will confuse.
So, if a module needs some patches/integrations to other parts of core Nuke, the language parts should be also splitted to the related language files, I think ...

Regards, Benson

Posted: Tue Apr 25, 2006 6:27 am

The problem is, as Raven has eluded to, each module writer can decide where to place the language defines. There are several different what I would call "banner nuke releases" where the basic architecture changed, such as the module admin in 7.5. This completely changed where the module's language files were placed (actually I think to separate them by module right?).

As a module writer, I can place it almost anywhere, but usually one of three places:

admin/language <-- if used in the system admin control panel area

language <-- typically for blocks and other system-wide defines, but could be almost anything.

modules/Module123/admin/language <-- for a specific module's administration tool language defines

modules/Module123/language <-- typically for a specific module's non-administration language defines.

These are all just core nuke placements of things.

Posted: Wed Apr 26, 2006 12:27 am

Hello,
please keep in mind. The good thing using language files is that nuke can be shown in different languages. The next advantage is that you can easy change terms to what you want to see on your site.
But, if you do so, changing some terms, you need to be carefull with every update to not overwrite your language files. Than it becomes a little bit difficult to find out if additional terms have been added, because you have to add it to your own files too. In that case, it would be the best to have it in individual files for each module.

If a module, like NSNGroups, need some changes in core modules, the language part should be also 'patched' into the corresponding language files for each patched module, that would make it more easy to find the missing/wrong terms. That is what I would prefer ...

Regards, Benson

Posted: Wed Apr 26, 2006 1:11 am

Yup - that is why you should always use a file comparison tool like 'Beyond Compare 2'.

Posted: Wed Apr 26, 2006 6:49 am

benson, as long as you are not suggesting changing where the defines are located (which is by usage and module writer's design), I completely agree with you. At least for the languages are "core" to nuke, each module should have a language file with the defines in them, even if they are still in English or whatever the "native language" is for that module.

You have just increased my module workload greatly! Wink

But, it is the right thing to do.