Osclass forums
Support forums => old => Topic started by: Pathfinder on February 01, 2014, 02:45:36 pm
-
As I have said in my other posts, I am very new to osclass and have limited knowledge and ability, but I am trying to 'think ahead'.
At the moment I am working on developing a site - www.caravancleaningservices.co.uk - using V3.3.2 and Twitter theme.
What I would like to know is;
Is it possible to 'link' this site with others I will be developing in the future?
Let me explain what I am looking for.
I would like users to register just once on any of my sites and that registration be valid on all the others. The problem with that is that whilst the other sites will be using the same osclass versions they will be using different themes and layouts.
My site 'Caravan Cleaning' uses parent categories 'Butlins', 'Haven',etc. with sub categories. I want to develop a General Classifieds site where I would probably use the default Bender theme and the parent categories in 'Caravan Cleaning' site would be sub categories under a parent category 'Caravan Cleaning' in the new classified ads site.
I would like it so that if a user places and ad on one site it automatically appears on the other. eg. on site 'Caravan Cleaning Services' place an ad in 'Allhallows' (a sub category of 'Haven') and have it also appear in the 'Classified' site in 'Allhallows' (which would be a sub category of 'Haven' which would be a sub category of 'Caravan Cleaning').
I do hope that makes sense and somebody can tell me if it's possible.
I'm asking this now in case I have to make changes to my current site 'Caravan Cleaning Services' now in preparation for 'linking' with my new sites in the future.
-
Hi Pathfinder,
I am also interested in this, but no step-by-step solution exists that I know of. I am still learning MySQL and so far, you can achieve this with sql triggers within a single db. All your installations should share same db (could be risky if you get into trouble with db for any reason), and use different prefixes. Then create sql triggers to sync some tables.
But, that is as far as I got, thing is - what tables are safe/should be synced? Because, there are foreign and primary keys, and so you have to know how to do it.
Regards
-
You need one database for multiple styled sheets, hosted on one domain, with sub domains, and then in your config files on each sub domain you would need to link it to the main database.
Therefore if someone registered on one site they would be registered on all sites.
Think the best thing for you today for arguments sake is have one osclass install. with multiple sub domains, so the user can choose at the front point of call where to go. Hope this helps a little
-
Hi aide2001,
using same db (with same prefix) for several installations effectively means you are cloning each instance, because you are limmited to theme and plugins settings, which are stored in the very same db. Simple solution with very limmited possibilities and not really the solution to the problem.
Regards
-
Only real way I know is data Integration.
This has a huge learning curve, at least for me..... :o
http://en.wikipedia.org/wiki/Data_integration
Tom
-
Gotta love those wiki articles - say a bunch and yet nothing :D
Regards
-
Maybe that was a poor choice of samples but the idea of database combining looks sound.
Long ago I tried, failed and abandoned the idea.
Here is a link discussing similar. If I had a clue I would sure like to try something.
http://msdn.microsoft.com/en-us/library/bb510625.aspx
Tom
-
Corrected
Hi,
An idea that should be more effective than using MySQL triggers:
1.- Choose one of your databases to work as "users_manager" (let's call it so).
2.- Intercept all queries before they reach the DB and redirect all mentions to [PREFIX]t_user and [PREFIX]t_user_description to users_manager.[PREFIX]t_user and users_manager.[PREFIX]t_user_description. You can do that with MySQL Proxy if you have root access to install it or simply slightly altering a core file:
oc-includes\osclass\classes\database\DBCommandClass.php
function query($sql) {
if($sql == '') {
return false;
}
// MySQL Proxy simulation mod
require_once('mysql_proxy.php');
$sql = mysql_proxy_out($sql); // end mod
if( OSC_DEBUG_DB_EXPLAIN && $this->isSelectType($sql) ) {
$this->query_debug($sql);
}
Create a new script mysql_proxy.php in oc-includes\osclass\classes\database (or wherever you want, just remember to adjust the require_once line)
Corrected:
<?php
function mysql_proxy_out($sql) {
return str_replace('[PREFIX]t_user', 'users_manager.[PREFIX]t_user', $sql);
}
// Replace [PREFIX] with your real prefix, i.e. oc_
?>
Now, this may be a very powerful feature, because in this new script you may alter each and everyone of the Osclass queries, and that is why I've created this script (mine has a lot of tweaks to accelerate things), but if you only want this users manager feature, you can just insert
$sql = str_replace('[PREFIX]t_user', 'users_manager.[PREFIX]t_user', $sql);
in DBCommandClass.php, instead of the three lines starting with // MySQL Proxy simulation mod.
Regards
-
Hi teseo,
another hit from you again :)
This idea could be indeed a better solution for simplicity and possibly regarding concurency (always 'in sync', table/raw locks..).
1.- Choose one of your databases to work as "users_manager" (let's call it so).
So, do we create a new blank db users_manager with tables oc_t_user, oc_t_user_description, oc_t_user_email_tmp (?) and some plugins' specific tables like oc_t_user_log (?) or I didn't understand this right?
Regards,
dev101
-
No need, just choose one of your normal databases to be what will manage user related affairs. The rest of the databases will keep their user tables but they will be empty and unused.
If things were to complicate (don't know, plugins specifities or some unfathomable circumstances ???), remember that you always may introduce conditions inside the mysql_proxy script, so some things might be database specific if that suits you.
Regards
-
This has always been an interest of mine and currently working with another forum member trying to have 2 sites. Just tried Teseo solution but for some reason (My abilities) it is not working.
Anyone have a simpleton suggestion cause that's me.
Strange thing is for quite some time I have been able to do this on localhost but not live. Now lost it on localhost.
Tom
-
Hi Tom, what exactly have you implemented based on teseo's solution?
I think the ONE line in "DBCommandClass.php" should do the trick as long as you do this for all other site "DBCommandClass.php" as well. The trick is to have them all POINT to the one 'user database' and that line of code is just doing that.
teseo, correct me if I am wrong.
Regards,
Eric
-
Hi,
Well, I have to confess that I haven't tested this myself. :D It occurs to me now that the procedure assumes that the script has authorization to access all the databases involved (same MySQL user, same MySQL password). Maybe your problem, Tom? ???
Regards
-
The more I think about this idea, the farther I get from it, for various reasons. Yes, it would be nice, 'cool', with clear advantages and so on, but it would have some drawbacks, too. So, complete separation might not be so bad after all.
Regards
-
I am going to show my ignorance but have to ask - Why am I getting this error in the test file, mysql_proxy.php. Screenshot attached.
Seems no matter what I do I cannot correct it. I can introduce more errors, I'm pretty good at that.... :o
Tom
-
Well, this is too important to go giving advice happily and with no personal testing. :D
So just done: Two installations with two databases that I'll call "users_manager' and 'users_slave', both with the same MySQL user and password.
I've skipped the mysql_proxy auxiliar script to avoid complicate things in the fundamental test, so that one-line modification only on DBCommandClass.php of users_slave installation:
$sql = str_replace('oc_t_user', 'users_manager.oc_t_user', $sql);
Now I login on users_slave installation with credentials of an user that only exits on users_manager, and voila:
SELECT * FROM (users_manager.oc_t_user) WHERE pk_i_id = '5'
SELECT * FROM (users_manager.oc_t_user_description) WHERE fk_i_user_id = '5'
SELECT dt_access_date, s_access_ip FROM (users_manager.oc_t_user) WHERE pk_i_id = 5 AND dt_access_date <= '2014-02-18 13:21:55'
UPDATE users_manager.oc_t_user SET dt_access_date = '2014-02-18 14:21:55', s_access_ip = 'XXX.XXX.XXX.XXX' WHERE pk_i_id = 5
...logged in. As you can see not only read queries (SELECT) are succesful, but also writing (UPDATE).
The more I think about this idea, the farther I get from it, for various reasons. Yes, it would be nice, 'cool', with clear advantages and so on, but it would have some drawbacks, too. So, complete separation might not be so bad after all.
Well, we are experimenting here, my friend, if you see drawbacks I would like to know what they are. If serious and unsurmountable, I'll give up, of course I don't want to cause problems but solve them. ???
Regards
-
My apologies, the problem with the method using the external script mysql_proxy.php was a missing semicolon to close the line:
Corrected
<?php
function mysql_proxy_out($sql) {
return str_replace('[PREFIX]t_user', 'users_manager.[PREFIX]t_user', $sql);
}
// Replace [PREFIX] with your real prefix, i.e. oc_
?>
Regards
-
Just tried the one liner. No errors but no login on master.
Here is what I have:
Two v.3.3.2's
One database
Master has oc_
Slave has db_
Can log in just one but not the other. I'll go back to the "Corrected" method because that has a lot of potential. Funny I tried a semi-colon about everyplace and way I could think of including where you placed it.
I learn near nothing doing it this way but could you send your files for this so I could compare?
Tom
-
Hmm... Yes, seems there might problems with the master installation (anyway, master doesn't require modification of DBCommandClass.php, only slaves).
Folks, please put on hold all of this until I have the time to check all this thoroughly. :-X
Regards
-
Update to my last post.
Only login is for the "site" I created user in...... :'( :-[
Other install says I don't exist...... >:(
Tom
-
Tom, the problem I've just detected is the contrary, everything went well on the slave installation with the user only referenced on the master DB, but problems with login on the master. ??? As I just told you, this will need more study (an possibly clean installations to start with).
Anyway, I'm going to stress what I told you all in the first place;
An idea that should be more effective than using MySQL triggers:
An idea to put to testing by the ones really interested in this feature (not my case, or what I would have presented here would be much more solid or not presented at all), now I'm yet more interested in the somewhat cryptic remarks of @dev101. Please buddy, elaborate to see if we should discard this idea of mine. ;)
Said that, I would like to separate the multisite matter (barely an idea) from the mysql_proxy pseudo-hook thing, this I have it working live for many months now with remarkable results. (See this thread for instance: http://forums.osclass.org/general-help/mysql-views/msg82975/#msg82975 ).
Regards
-
I understand. I posted exactly as you were posting the one about holding off. The forum system said someone was also posting but I chose to post anyway. Yours appeared just before mine.
I am and have been trying for many, many months as time permits so always interested in a thread on this topic. It just so happened that at this same time I and another forum member are working on this very thing but your idea is so superb we decided to try it.
Thanks so much for posting because this opens a nice dialog.
Tom
-
Hi again,
Progresses at least. It's not enough to share user tables on master database, you have to share sessions too to login on master or slave and be logged in both. Take this with a pinch of salt, but if you set he same session path for two installations, this seems to work at least for login/logout.
Master installation config.php:
session_save_path ( ABS_PATH . 'oc-content/uploads/' );
Slave installation config.php:
session_save_path ( '[path-to-master-installation]/oc-content/uploads/' );
And your cookies must be valid for the whole domain (mine are like that, but I couldn't recall if this is by default or I did something at some time) :D
CSRF token problems might arise, but then I've seen this only once, and my two testing installations are running Osclass 3.1.1, where CSRF errors are thrown seemingly randomly anyway, issue that I haven't seen at least on 3.1.2 installations. ???
Well, more food for testing, waiting for other bold explorers to share their experiences. ;)
Regards
-
Originaly I was testing with 3.0.2 just to get away from all those CSRF errors. Thinking if it works with a simple version no reason to not work with newer versions but then got it in my head maybe newer versions have some magic code that could help so bypassed 3.1 and when for 3.3. No CSRF's but 3.3 sure is picky about theme display and plugins.
Anyway, I have wasted so much time trying this with sql and now feel dumb(er) because your idea is so much more straight forward. Never occurred to me to capture/Re-direct PRIOR too... :o
Been going over the database files hoping something jumps out of the code at me and wondering what exactly was the plan for define('MULTISITE', 0); in config and just how can this be used for this...
Curious that there seems to be enough existing code to allow this but I have not been able to do it.
Has anyone ever set the config- define('MULTISITE', true);
When I do I get this and can't get past it (Brain dead):
Fatal error: Class 'SiteInfo' not found in K:\wamp\www\osclass33\oc-includes\osclass\helpers\hDatabaseInfo.php on line 85
Call Stack
Thanks for the updated post. I'm off to play some more.
Tom
-
Curious that there seems to be enough existing code to allow this but I have not been able to do it.
Has anyone ever set the config- define('MULTISITE', true);
As every big mansion, Osclass has its hidden doors and closed rooms... :D This is what I know of this:
http://forums.osclass.org/development/where-is-this-constant-is-used-define('multisite'-0)-in-config-php/msg2602/#msg2602
Take that into account, likely this might be more complicated than just share sessions and user tables, only full testing will say.
Fatal error: Class 'SiteInfo' not found in K:\wamp\www\osclass33\oc-includes\osclass\helpers\hDatabaseInfo.php on line 85
Did you set define('MULTISITE', true)? All that is incomplete, better to keep the default and try and find another path. ;)
One more thing, I said 3.2.2 when I wanted to say 3.1.2 (never have the time to go further, a busy period for me). :D
Regards
-
now I'm yet more interested in the somewhat cryptic remarks of @dev101
Hi teseo,
sorry for not responding sooner, I do really appreciate your efforts, you are the only one here contributing some real work :)
There was nothing cryptic, I just think when you put some plugins like PM messages and few other ones (exotic), this might get into trouble. This was not a factual statement, just a precaussion.
As you said, this would require detailed testing -- and I was wondering, should I spent that [limited] time [lately] on this, or something more creative like separated themes, functionalities, plugin integration, corrections and all?
That is all what I meant, really.
I will try to find time and test your 2nd solution (as I haven't proper time to test 1st at all).
Regards and thank you!
-
Thanks, buddy :)
I want to clarify that I think those maybe aren't alternative solutions, but complementary. As you say (and may be seen by that Garcia de Marina's post), this surely is more complicated than all this. Unfortunately, right now I just can barely point directions for those really interested and comment about their findings).
Regards
-
and may be seen by that Garcia de Marina's post
hmmm, what post - can you point me to it? (I feel really tired lately and exausted on my job; trying to spend my half/one hour per day for the forum to see interesting topics and help others if I can :-[ )
Testing is on my 'red' to-do list (top priority), and I would really like it (I cried for it how many times already?), but also started thinking [that] maybe separate domains or subdomains could be better/enough.
Regards teseo!
-
Yes, in all this, I forgot to explain why I suddenly started changing my mind about integration. I discovered dynamic pages in Osclass, which I didn't know about untill recently (always some new trick under the hood in this script!) and so started thinking about that direction. Instead of integration, I could create different 'main' pages with items and search limited only to few categories. So, you do not install X scripts and domains/subdomains, but just use single instance and divide them this way. What do you think of this idea?
Regards
-
I can completely relate to your situation regarding time and fatigue, believe me. :-\ But in my case I think I find some relief in setting my real job aside for a little while to study a bit things like this (and you never know when anything could be useful for you personally, so...) :D
This is the Garcia's post:
http://forums.osclass.org/development/where-is-this-constant-is-used-define('multisite'-0)-in-config-php/msg2602/#msg2602
And the other thing, alwaysmore than one way to skin a cat, it depends on your current objective. For instance, the site I'm currently working for has a completely compartmentalized structure based on countries, but in the beginning I prefered to keep them all on the same installation/database. Maybe if this multisite feature was been completed at the time, I would have chosen another path, but seems we have no time for what-if's in this business of ours... :D
Kind regards
-
Hi Teseo,
Is this still a valid method to connect 2 databases? From the thread it appears that others could not make this work and the thread ended abruptly.
If anyone else besides Teseo has been successful in getting this to work, appreciate your reply and any suggestions. TIA!
-
Hi,
No. Definitely the ideas in this thread won't achieve a full synchronization of users management between two databases. Main problem would be that of plugins related to users, no way to have a standard for that. :(
Regards
-
Hi Teseo,
Thanks for your reply. I am sure you know what I am trying to do but just to clarify - I won't have any plugins in the main installation ie "users_manager" (it will only have user information and nothing else, no listings or plugins). The second installation that will tap into the "user_manager" will have the listings and plugins. Thanks!
-
Frankly, I think this would require much more, no way to foresee all the problems that would arise.
Regards