1
eoviedo
Re: SOLVED
  • 2006/8/9 16:51

  • eoviedo

  • Documentation Writer

  • Posts: 6

  • Since: 2003/5/5 1


$last_character = substr($_SERVER['REQUEST_URI'], -1);

if ($last_character == "/" ) {
$xoopsTpl->assign('en', $_SERVER['REQUEST_URI'].'index.php?lang=english');
$xoopsTpl->assign('es', $_SERVER['REQUEST_URI'].'index.php?lang=spanish');
$xoopsTpl->assign('fr', $_SERVER['REQUEST_URI'].'index.php?lang=french');
}

if ($last_character == "p") {
$xoopsTpl->assign('en', $_SERVER['REQUEST_URI'].'?lang=english');
$xoopsTpl->assign('es', $_SERVER['REQUEST_URI'].'?lang=spanish');
$xoopsTpl->assign('fr', $_SERVER['REQUEST_URI'].'?lang=french');
}

if ($last_character != "/" && $last_character != "p") {
$xoopsTpl->assign('en', $_SERVER['REQUEST_URI'].'&lang=english');
$xoopsTpl->assign('es', $_SERVER['REQUEST_URI'].'&lang=spanish');
$xoopsTpl->assign('fr', $_SERVER['REQUEST_URI'].'&lang=french');
}

... using this way you can change the language if the url ends in '.php', '/' or a file with variables.



2
eoviedo
xlanguage v3.0 doesn't work under XooPS v2.014
  • 2006/8/6 11:18

  • eoviedo

  • Documentation Writer

  • Posts: 6

  • Since: 2003/5/5 1


Hi!

I have tried to run xlanguage v3.0 using XooPS v2.0.14 and only works with the theme -not with the content-. It doesn't matter if I use the language tags in blocks, news, etc. XooPS always ignores the tags and shows them with the content.

I tried EXACTLY THE SAME configuration under XooPS v2.0.13.2 and works fine with the theme and the content.

Maybe the way that XooPS v2.0.14 decode []?

... something that I don't know if is going to help you... xbs-tags v1.0 doesn´t work too with XooPS v2.0.14 and runs fine with XooPS v2.0.13.2 using EXACTLY THE SAME configuration.

Please forgive me for using capital letters but I only wish to be sure you don't spend time trying to guess a possible mistake in my tests.

Thanks in advanced.



3
eoviedo
Calling variables in the Menu
  • 2005/7/21 11:13

  • eoviedo

  • Documentation Writer

  • Posts: 6

  • Since: 2003/5/5 1


I would like to make a site more accesible using an access key combination (Alt key + number) for every link in the menu.

I need to define that access key for all modules and calling it in the template of the block menu.

I tried this for the news module:

.- In the xoops_version.php added the next line:

$modversion[\'config\'][1][\'accesskey\'] = \'3\';

'3' Is its position in the menu.

.- In the system_block_mainmenu.html, for building every link:

<a class="menuMain" href="<{$xoops_url}>/modules/<{$module.directory}>/" accesskey="<{$xoopsModuleConfig['accesskey']}>"><{$module.name}></a>

But it does not work. When I see the source in the web browser the parameter for the accesskey is empty.

Any help?



4
eoviedo
Re: Those Orange/White Module Logos
  • 2004/8/19 12:37

  • eoviedo

  • Documentation Writer

  • Posts: 6

  • Since: 2003/5/5 1





5
eoviedo
Re: Starting off the Roadmap discussion
  • 2004/3/3 9:49

  • eoviedo

  • Documentation Writer

  • Posts: 6

  • Since: 2003/5/5 1


Sorry, perhaps I did not explain myself very well, Herko. I wanted to say that mambo includes some nice features, like database back-up, restore, sql queries, information about the system, etc.

Only that. Personally I also think that XOOPS is better :)



6
eoviedo
Re: Starting off the Roadmap discussion
  • 2004/3/2 11:57

  • eoviedo

  • Documentation Writer

  • Posts: 6

  • Since: 2003/5/5 1


I love XOOPS... but perhaps Mambo makes somethings enough well -I am thinking only about the possibilities of the administration menu-.

I hope I am not being wrong saying that is util to check this in:

http://www.opensourcecms.com/mambo/administrator/index.php

login: admin
password: admin

What do you think?






TopTop



Login

Who's Online

266 user(s) are online (175 user(s) are browsing Support Forums)


Members: 0


Guests: 266


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits