1
pfaulkne
Re: End of installation?
  • 2005/3/16 6:35

  • pfaulkne

  • Just popping in

  • Posts: 32

  • Since: 2004/2/14


During installation, at the screen where you are asked for the DB information, change the 'prefix' from the default 'xoops_' to something else.

This is also a good security practice.



2
pfaulkne
Re: PROTECTOR and DB prefix.
  • 2005/3/14 3:46

  • pfaulkne

  • Just popping in

  • Posts: 32

  • Since: 2004/2/14


All,

The documentation team is currently working on a detailed guide for the protector module. It contains explanations suggested setting, best practices and operations.

As you some of you have seen, V2.37 is out. in the Prefix manager once you have renamed your tables, there is now a button on the right side of the *OLD* tables to allow you to delete them.

Also be aware, that if you have multiple sites running on the same DB, there is also a delete button next to the other prefix tables. So what Protector looks at is the prefix in mainfile, and then places a delete button next to any other prefix set in the same database.



3
pfaulkne
Re: How customizable is XOOPS?
  • 2005/3/2 5:03

  • pfaulkne

  • Just popping in

  • Posts: 32

  • Since: 2004/2/14


Have a look at "A Visual Introduction to Xoops" link on the left under the documentation section. That will give you an idea of what is possible. Also have a look in the Themes Library for what's available there. That will give you the basic idea of what you can do to make XOOPS personal, i.e. look.
If you don't like what you find, then go get the "Anatomy of the Default Theme". This will give you a start on how to build your own theme.

The look in the modules Repository to see what additional functionality you can add onto the core.

Then download the ones your interested inand start playing.

So the asnwer to your question is: VERY. It's all up to you.



4
pfaulkne
Restaurant Guide
  • 2005/3/2 4:55

  • pfaulkne

  • Just popping in

  • Posts: 32

  • Since: 2004/2/14


There was a thread back in 2003https://xoops.org/modules/newbb/viewtopic.php?topic_id=12536&forum=4&post_id=54890#forumpost54890 about a Restuarant Guide module. I can't find anything after that. Did the module stop dev work? Renamed? Ended up in the bit bucket?



5
pfaulkne
Re: Two Sites using one Database - Possible?
  • 2005/2/25 3:08

  • pfaulkne

  • Just popping in

  • Posts: 32

  • Since: 2004/2/14


Have a look at this thread. It was not long ago and I'm currently working on it for myself. As I said in the thread, if I get it working perfectly then I'll post it. So far it works sometimes.... :(

<a href="https://xoops.org/modules/newbb/viewtopic.php?topic_id=31035&viewmode=flat&order=ASC&start=10">here is the thread</a>

Mithrandir is also working on it and it looks like we are doing similar things. When I have more time to work on this, I'll try to sync up with him so reinventing the wheel is avoided.



6
pfaulkne
Re: problems running xoops on local host
  • 2005/2/24 12:41

  • pfaulkne

  • Just popping in

  • Posts: 32

  • Since: 2004/2/14


Now if we could just build a RPM for the common Linux boxes, we'd all be a LOT happier



7
pfaulkne
Re: Double Standards
  • 2005/2/14 0:59

  • pfaulkne

  • Just popping in

  • Posts: 32

  • Since: 2004/2/14


Sorry. Did I miss something here? The original post didn't mention AMS and I had to go find out what this was to understand the remaining posts.
Are we even sure the the original post is talking about this module or does he/she have a complaint about omething else?

Did he/she find XOOPS on the www somewhere and was asked to 'donate' fo download it?

Or did I miss an earlier post that references this one?
Confused...again.



8
pfaulkne
Re: Install two xoops sites and share users
  • 2005/2/11 6:58

  • pfaulkne

  • Just popping in

  • Posts: 32

  • Since: 2004/2/14


Thanks. Looks like that road is definateely the right one. Cheers.



9
pfaulkne
Re: Creating a bilingual site
  • 2005/2/10 8:00

  • pfaulkne

  • Just popping in

  • Posts: 32

  • Since: 2004/2/14


I did this the hardway, but it does work perfectly. In my case, I did a standard install. The I downloaded the Japanese version and expanded onto disk, Then I opened the language files for every module,
e.g. \html\modules\system\language\english\modinfo.php.
I then added the second langauge translation immediately after the English in the constant definition. So it looks like this
define("_MI_SYSTEM_BNAME2","User Menu :ウサ メニウ");

Did that for almost everthing. It took a while but works perfectly. You have to make sure your theme has enough width to handle this and there are some other minor issues of look and feel of the site, but it does work.
Have a quick look here.

This way users don't have to choose one or the other. Both are there. Just takes a little design planning. I'm still working on this so some of it is still in English only and some is both.

Hint: If you want to admin the site in English, then don't change the admin language files. Or just over right them with the other language files.

Upgrades are going to be a nightmare if they add next entries, but hey, I knew that when I started.



10
pfaulkne
Install two xoops sites and share users
  • 2005/2/10 7:31

  • pfaulkne

  • Just popping in

  • Posts: 32

  • Since: 2004/2/14


I started looking into this (through the code) and was wondering if I'm on the right path. Please remember I'm new to this and am trying to understand how XOOPS works.

Basically I think this will work. There is most likely an easier way to get the end result but,...

I install a new XOOPS into any directory and have the installer create the tables. Let's have these have a prefix of 'common' for ease of understanding.

Then I install two sites that I actually want to use and to share users/groups. Let's call these prefixes 'site1' & 'site2'.

I found that in mainfile the db prefix is stated. I also found that in \html\kernel\user.php in the function &get(&id) there is a reference to prefix

$sql 'SELECT * FROM '.$this->db->prefix('users').' WHERE uid='.$id;


There are several like this. I'm assuming that instead of using this constant, if I hardcode 'common' inplace of the prefix, this would then direct the query to the 'common' tables where I want the users to be. If I changed this in both 'site1' and 'site2' file, then both sites would share the users.

I say assume because I haven't try this yet. (Still building a test box).
Just wanted to know if this was the right road or should do a U-Turn and take that left folk in the road.

Cheers




TopTop
(1) 2 3 »



Login

Who's Online

193 user(s) are online (94 user(s) are browsing Support Forums)


Members: 0


Guests: 193


more...

Donat-O-Meter

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

Latest GitHub Commits