tamplan

File Name: [T] Developpers Tools File Submitter: tamplan File Submitted: 25 Jul 2009 File Category: Applications This little admin application can help you making all the necessary xml files for your application you write. All the xml files are exported in one step. You can make the xml files for severals applications in one step too. Click here to download this file

More than 40 views and none comment ? May I report an issue for the record ?

It is not necessary here to report an issue but to propose an improvement. In the 'cp_skin_restrictions.php' line 327, you use this string 'Grant access to System application?' using two entries from a language file: <div class='tablesubheader'>{$form} {$this->lang->words['r_grantto']} {$application['app_title']} {$this->lang->words['application_bit']}?</div> For the module is in line 341: <div class='tablesubheader'>{$form} {$this->lang->words['r_grantto']} {$module['sys_module_title']} {$this->lang->words['module_bit']}?</div> Is there a way to use only 2 entries and not 3 for example nammed: 'r_grantto_application' => "Grant access to '%s' application?", 'r_grantto_module' => "Grant access to '%s' module?", In French and maybe in others languages, application and module have not the same 'gender' and the words the same places in the sentences. The final strings in French would be: 'r_grantto_application' => "Donner l'acc

Since version 2.3.x of IPB, the ibf_posts and the ibf_topics don't have the same type for the icon_id field. Let's imagine this situation, a member can use 127 (tinyint(2)) icons message in a post but much more in a topic (smallint(3)). We can use API to write topic with a incorrect icon message number we can not change later editing the first post of the topic. Not really a bug but using the same type for the icon_id field should be better not?

This is only possible from version 3.0.2 of IPB. All interventions are my sole purpose as the improvement of IPB that I am a strong advocate and passionate... :wub: Not sure it is properly translated from French. :)

In the 'core_public_global.php ' language file, you must have: 'discussion' => "Forums", 'tb_mlist' => "Members", Because "forums" and "members" are two applications of the IP.Board core and are not applications addons... :cool:

For the skin issue of 'active content', in 'activePostsView', search: {$app['app_public_title']} Replace twice by: {IPSLib::getAppTitle($app['app_directory'])} And for the skin issue of 'new content', in 'newPostsView', search: {$app['app_public_title']} Replace twice by: {IPSLib::getAppTitle($app['app_directory'])} Hope this help, regards :thumbsup:

Language files CAN and must be translated in the ACP.

There is no problem :thumbsup:

This is false and not correct !! Read this code: static public function getAppTitle( $app ) { if ( ! $app ) { return ''; } return isset( ipsRegistry::getClass('class_localization')->words[ $app . '_display_title' ] ) ? ipsRegistry::getClass('class_localization')->words[ $app . '_display_title' ] : ( IN_ACP ? ipsRegistry::$applications[ $app ]['app_title'] : ipsRegistry::$applications[ $app ]['app_public_title'] ); } So, Vesperala, I presume you must add some entries in the romanian language file core_public_global.php: 'blog_display_title' => "Blogs", 'calendar_display_title' => "Calendar", 'chat_display_title' => "Chat", 'downloads_display_title' => "Downloads", 'gallery_display_title' => "Gallery", 'portal_display_title' => "Portal",

I don't understand, this is correct with my boards, the tab names are depending of the language's user.

Have you seen this issue I have reported?

Remember your point of view when IP.Subscriptions will be finalized and completely stable... :thumbsup:

$app is the folder application name. To translate the CCS tab, you add an entry with the following informations :

Completely agree with this point. A week for an user can start on Monday and on Sunday for another one => an entry in language files not in settings. All the messages like the board offline's one => an entry in language files Boards rules ditto Anything that can be translated via PCA and depending on the language of a member should be in language files including date, time and number format. There is always a default language so we can image a 'date_short', 'date_long'... entries in language files not in settings.