292491
ibanez
Re: "Sorry, you do not have the permission to access this area...." Urgent!
  • 2003/7/15 22:07

  • ibanez

  • Just popping in

  • Posts: 33

  • Since: 2003/1/28


When I said Urgent perhaps I should have said EMERGENCY! I have things that I have to get!



292492
ibanez
Re: "Sorry, you do not have the permission to access this area...." Urgent!
  • 2003/7/15 21:42

  • ibanez

  • Just popping in

  • Posts: 33

  • Since: 2003/1/28


modules/system/admin says the same fatal error as before
modules/system/admin.php says no permissions



292493
netwize
Re: "Sorry, you do not have the permission to access this area...." Urgent!
  • 2003/7/15 21:34

  • netwize

  • Just popping in

  • Posts: 89

  • Since: 2002/1/20


you can go to /modules/systems/admin

to open and check the group permission again.




292494
ibanez
"Sorry, you do not have the permission to access this area...." Urgent!
  • 2003/7/15 20:58

  • ibanez

  • Just popping in

  • Posts: 33

  • Since: 2003/1/28


I removed module permissions from registered users and another group, but not Webmasters, to make sure no one can access the contents while I work. Only now I get "Sorry, you do not have the permission to access this area." when i go to my homepage, when I never removed permissions for webmaster.

It happened on XOOPS 1,3,10 and after installing XOOPS v2 I still get the same problem. How can I get back into my site. I have 50 members waiting for the site to get back up!



292495
patagon
Re: Autologin for Xoops 2.0.x
  • 2003/7/15 20:55

  • patagon

  • Quite a regular

  • Posts: 235

  • Since: 2002/1/8 0


Its actually in your control panel. System is usually the first item on the left menu and from there you have to choose templateset from the menu that appears when you mouse over. Then choose system on the template you are using, you will see the file in that list.



292496
john47
Re: Autologin for Xoops 2.0.x
  • 2003/7/15 20:48

  • john47

  • Just popping in

  • Posts: 24

  • Since: 2003/4/24


i cant find Control Panel->Administration->Template Editor->Sytem->system_block_login.html can somone help?



292497
WismeriL
Re: SOLVED - Making Xoops CONTENT Multilingual
  • 2003/7/15 20:23

  • WismeriL

  • Just popping in

  • Posts: 4

  • Since: 2003/7/7 1


I don't know if it's Chado website but this site :
http://peekaboo.s8.xrea.com:8080/
is using it, you can switch between english and japanese by clicking on the flags.

WismeriL



292498
patagon
Re: SOLVED - Making Xoops CONTENT Multilingual
  • 2003/7/15 20:10

  • patagon

  • Quite a regular

  • Posts: 235

  • Since: 2002/1/8 0


Chado,

that looks really interesting, thanks for sharing it. Do you have a site where we can see this? i would like to see it working...

Thanks



292499
Herko
Re: SOLVED - Making Xoops CONTENT Multilingual
  • 2003/7/15 19:57

  • Herko

  • XOOPS is my life!

  • Posts: 4238

  • Since: 2002/2/4 1


Excellent hack! Great work!

Herko



292500
Chado
SOLVED - Making Xoops CONTENT Multilingual
  • 2003/7/15 14:24

  • Chado

  • Not too shy to talk

  • Posts: 113

  • Since: 2003/6/6 7


This hack will work with news, forum, wf-sections, tinycontent or any module that uses the textsanitizer.
After searching the boards and posting a couple questions that never were answered, I had a go at this myself and well…necessity is the mother of invention….I discovered the module.textsanitizer.php file and messed with it till I got it to work. I am not a coder, so I am sure that someone can improve on this. (More on that later)
First things first:
This hack assumes that you are using the multi-lingual hack that can be downloaded here from ModsCentral.
To install it on Xoops2.x, follow the instructions I posted here.
That will get your XOOPS to be multilingual.

Now to make your content multilingual:
1. Open the module.textsanitizer.php file in the class folder. Around line 145 is the function “&xoopsCodeDecode” After the line
Quote:
$replacements = array();

and before the line
Quote:
$patterns[] = "/\[ code](.*)\\[\/ code\]/esU";

Place this code:
Quote:
//multi-lingual hack by chad--if japanese show japanese else show nothing
global $xoopsConfig;
$patterns[] = "/\[japanese](.*)\[\/japanese\]/sU";
if ($xoopsConfig['language'] == "japanese") {
$replacements[] = '\\1';
} else {
$replacements[] ="" ;
}
//if english show english else show nothing
$patterns[] = "/\[english](.*)\[\/english\]/sU";
if ($xoopsConfig['language'] == "english") {
$replacements[] = '\\1';
} else {
$replacements[] = "";
}
//end multi-lingual hack

Of course you will change the language ('english','japanese') to reflect the languages that you are targeting. The name in the brackets has to match the name of your language pack that you downloaded (or created). You could add more if you are targeting more than 2 languages.

To use this:
When you add your article just enclose the section you want shown in a particular language in brackets with that language name. This is very similar to adding a url or code to an article. For example: Quote:
[english]This is my English text.[/english][japanese]kore ha nihongo desu.[/japanese] This text (not enclosed in brackets) will show up in both (all) languages.


If you are just targeting European languages, you may not have to worry about this, but if you are targeting multi-byte languages like Japanese you may have to manually change the character encoding of your English global.php file to match your japanese one.

That’s it! Basically very simple – If you are having problems with the layout, you probably are putting spaces between the codes.
I hope this helps!
Chad







Login

Who's Online

198 user(s) are online (116 user(s) are browsing Support Forums)


Members: 0


Guests: 198


more...

Donat-O-Meter

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

Latest GitHub Commits