11
johny
Xoops ML package
  • 2003/11/14 13:11

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


I've put my site on-hold till the multi-language package comes out since there is just too much hardcoding, and correcting that hardcoding involved.

I look forward to the ML pack. I hope it will be available soon

The authors of it are kindly asked to post it here (or with instructions how to get it).

-a grateful member-



12
johny
Re: Contact module hack
  • 2003/11/11 13:34

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


Thanks for the instructions. I actually know that already since that is the case with all such systems. The problem is that usually these strings are called from one file and are defined in language files. That's easy to modify and I can do that with no fuss.

If you take a look at the Contact module files, however, you'll see that they are not so easily configured. I believe I added the string to the template file and updated the module but I only got the string displayed, not the actual text defined in the language files. If I enter - hardcode - normal text in the file, it gets displayed but I'd really need that to work multilingual.

I might have called the string incorrectly; I used several types of calling it. I took a look at other files and copy-pasted those, modified that, and it still didn't work. Please take a look at this particular module and try to advise which file needs modifying and how to call the language variable.

Please help - I'm still confused here



13
johny
Re: Contact module hack
  • 2003/11/8 16:58

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


I've done that but the problem is that I don't know how (and in which file) to call it.

I just switched to XOOPS (from Nuke) and I need to adjust



14
johny
Contact module hack
  • 2003/11/7 15:40

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


I have reaally a simple wish but I can't figure it out by myself.

I'd like to tweak the standard Contact module that comes with Xoops. All I want is to display additional information (instructions and alternate ways of contacting) below the form. If I simply edit the templates/contact_contactusform.html I get the desired result BUT I'd like to offer that information in two languages - depending on the language selected by the user.

That's where it gets trickier. It seems that I cannot call a translation directly from that file. I might also be wrong. I'd really appreciate if someone helps me out here.



15
johny
Re: Language selection
  • 2003/11/7 12:59

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


(the upper message got posted twice and since I can't delete it, I edited the content out in this message)



16
johny
Re: Language selection
  • 2003/11/7 12:59

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


Hello.

I've installed the module and tweaked the include/common.php file, and it works great. If I turn on debugging feature, though, I get this message displayed:

Quote:
Notice [PHP]: Undefined index: sel_lang in file modules/language/common/functions.php line 2


Any idea what that is all about?



17
johny
Re: theme problem ?
  • 2003/10/24 22:49

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


One more...

If I turn on the 'site closed' function, I get this displayed:

Warning [PHP]: fopen("/MY_PATH/cache/db%3Asystem_siteclosed.html""r") - No such file or directory in file class/smarty/Smarty.class.php line 1998
Notice 
[PHP]: Undefined indexxoops_sitename in file templates_c/db%3Asystem_siteclosed.html line 12


OK I do know that I can turn them off (and when the new site will be ready for public I will do that) but I really do want to eliminate any problems first...



18
johny
Re: theme problem ?
  • 2003/10/24 22:23

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


I also got the following messages displayed and I'd like to get rid of them so I can troubleshoot the real problems later.

Notice [PHP]: Undefined indexdefault_theme in file class/smarty/plugins/resource.db.php line 17
Notice 
[PHP]: Undefined indexdefault_theme in file class/smarty/plugins/resource.db.php line 23
Notice 
[PHP]: Undefined indexdefault_theme in file class/smarty/plugins/resource.db.php line 71
Notice 
[PHP]: Undefined indexdefault_theme in file class/smarty/plugins/resource.db.php line 77
Notice 
[PHP]: Undefined variablefile_path in file class/smarty/plugins/resource.db.php line 96
Notice 
[PHP]: Undefined indexlang_rememberme in file templates_c/db%3Asystem_block_login.html line 7
Notice 
[PHP]: Undefined indexsslloginlink in file templates_c/db%3Asystem_block_login.html line 10
Notice 
[PHP]: Undefined indexxoops_lblocks in file class/smarty/Smarty.class.php line 626
Notice 
[PHP]: Undefined indexdefault_theme in file class/smarty/plugins/resource.db.php line 17
Notice 
[PHP]: Undefined indexdefault_theme in file class/smarty/plugins/resource.db.php line 23
Notice 
[PHP]: Undefined indexdefault_theme in file class/smarty/plugins/resource.db.php line 71
Notice 
[PHP]: Undefined indexdefault_theme in file class/smarty/plugins/resource.db.php line 77
Notice 
[PHP]: Undefined variablefile_path in file class/smarty/plugins/resource.db.php line 96
Notice 
[PHP]: Undefined indexmodules in file templates_c/db%3Asystem_block_mainmenu.html line 10
Notice 
[PHP]: Undefined indexxoops_module_header in file templates_c/default^theme.html line 35


After downloeading the latest resource.db.php (http://cvs.sourceforge.net/viewcvs.py/xoops/xoops2/class/smarty/plugins/resource.db.php) I only have three errors left.

Notice [PHP]: Undefined indexxoops_lblocks in file class/smarty/Smarty.class.php line 626
Notice 
[PHP]: Undefined indexmodules in file templates_c/db%3Asystem_block_mainmenu.html line 10
Notice 
[PHP]: Undefined indexxoops_module_header in file templates_c/default^theme.html line 35


Any ideas how to get rid of those?



19
johny
Re: SOLVED - Making Xoops CONTENT Multilingual
  • 2003/10/24 13:52

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


I think very highly of Xoops. I was using PhpNuke before, and now I'm trying to adapt to Xoops.

Xoops indeed has better functionality, but lacks multi-language support. I think you guys are doing a great job and I'll stard hardcoding the files using this forum topic.

Thank you for sharing this, and I would like to urge the developers to at least offer multi-language versions of XOOPS in the future, if not switching completely to this functionality.

I could hardly say I'm a newby when it comes to hardcoding modules and other files, but I have to admit that this kind of tweaking certainly requires a lot of energy and attention.

My congratulations and thanks to the brave and bright people who started coding this




TopTop
« 1 (2)



Login

Who's Online

760 user(s) are online (79 user(s) are browsing Support Forums)


Members: 0


Guests: 760


more...

Donat-O-Meter

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

Latest GitHub Commits