Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not a problem... a suggestion #29

Open
GoogleCodeExporter opened this issue Jan 16, 2016 · 0 comments
Open

Not a problem... a suggestion #29

GoogleCodeExporter opened this issue Jan 16, 2016 · 0 comments

Comments

@GoogleCodeExporter
Copy link

I remember this from back in the day. I used it. Now I am looking for a simple 
yet robust website. There are some really annoying glitches (default realmID 
doesn't work, it always uses 1, among other glitches) but I am posting this 
issue because I have a simple question...

why is it that all CMS' assume the website and authserver are always on the 
same machine?

How hard would it be to have a seperate website DB, with different credentials 
for accessing the DB?

I did some grepping.. and "username" is in like 10 files. account is in like 
35. seems like a major rewrite, but I am not that great with php.

Thanks, and I hope you come back and continue working on this. 9 months is a 
long time...


another note: being a dev for mangos (which sadly is dying) I added 
account_access table, so the core could be more compatible with trinitycore. 
This simplifies things. no longer need a setting for mangos or trinitycore... 
(this only applies to the 4.3.4 core currently. will add it to 2.4.3 and 335a.)

Thanks for letting me vent.


Original issue reported on code.google.com by [email protected] on 27 Sep 2012 at 6:44

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant