Jump to content

tamplan

Clients
  • Posts

    193
  • Joined

  • Last visited

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by tamplan

  1. Open 'admin/applications_addon/ips/portal/modules_public/portal/portal.php' and delete : //----------------------------------------- // Make sure the portal is installed an enabled //----------------------------------------- if( ! IPSLib::appIsInstalled( 'portal' ) ) { $this->registry->output->showError( 'no_permission', 1076 ); } I consider this like a bug because the portal is installed. I have open a bug report.
  2. Follow the 'Edit Application Details...' link. (see screenshot)
  3. To hide all the tabs and hide the first link in navigation. Open 'SkeletonTemplate' in Portal templates, search : <div id='portal_articles' class='left'> Add before : <script type="text/javascript"> $$('li.first').invoke('hide'); $('search').next().hide(); </script> That's all folks :)
  4. You must change in 'globalTemplate'. Search : {parse variable="forumActive" default="" oncondition="IPS_APP_COMPONENT == 'forums'" value="active"} Add before : {parse variable="portalActive" default="" oncondition="IPS_APP_COMPONENT == 'portal'" value="active"} Then, search : <li id='nav_discussion' class='left {parse variable="forumActive"}'><a href='{parse url="act=idx" seotitle="false" base="public"}' title='{$this->lang->words['go_to_discussion']}'>{$this->lang->words['discussion']}</a></li> Add before : <li id='nav_portal' class='left {parse variable="portalActive"}'><a href='{parse url="app=portal" seotitle="false" base="public"}' title='{$this->lang->words['go_to_portal']}'>{$this->lang->words['portal']}</a></li> Edit the application public title to hide the original tab.
  5. In the portal skeleton, you can add this code : <script type="text/javascript"> $$('li.first').invoke('hide'); </script> That hide the first link in the navigation.
  6. I totally agree with what has been written. Take the example of the 'Online/offline' message. This setting key is 'offline_msg'. There is no reason to change this message very often. So, we can use it with a language file like: $this->lang->words['offline_msg'] It is almost the same principle for the management of the dates with a little function to translate days and months : $lang = array( 'ipb_calendar_mon' => "1", 'month_january' => $this->lang->words['M_1'], 'day_monday' => $this->lang->words['D_1'], ... To translate days and months depending on the user's language choice: function translate_date($my_timestamp, $type='long') { $my_date = strftime($this->lang->words['clock_'.$type], $my_timestamp); $day = strftime('%A', $my_timestamp); $key_day = strtolower($day); $translated_date = str_replace($day, $this->lang->words['day_'.$key_day], $my_date); $month = strftime('%B', $my_timestamp); $key_month = strtolower($month); $translated_date = str_replace($month, $this->lang->words['month_'.$key_month], $translated_date); return $translated_date; } Everything that depends on the user's language should be in language files. There is no need for another system that already used to translate the input language in the ACP. Hope this help :)
  7. Hello, Are you speaking about a page like this one ?
×
×
  • Create New...