|
Hi there,
I have a pretty demanding client with some fairly interesting expectations, so bear with me...
There are four sites for this client, all in different languages, all
with different domains (abc.com, abc.pl, abc.pt, abc.fr). I want all
of these sites to be able to share the same database. The user should
have the option of seeing just forum activity for their language (or
domain whichever is easiest to set up) or for all languages. Each of
these sites will share groups, but the content is filtered by thread
language. So, for example, a user registers in Poland and
automatically assigned a language id of polish. They go to the forums
and see three groups with x threads in each group. They go to their
profile and change a custom field which changes their default viewing
language to "All", go back to the forum home page and see three groups
with x+y threads, in mulitple languages. Does this make sense?
Also, the groups that will be set up, can we have different names for
each group based upon their natural language? So, someone from the UK
sees "Videos, Photos, News", while someone from Poland sees "Klipy,
Foty, Niusy". The content could be language filtered or all, as
specified above.
I guess now is also an opportune moment
to ask if you have translations for Polish, French and Potuguese. This
may be expanded even further in the future, so perhaps a full
translation list would be smarter, with a description of how we go
about translating it. If we come up with a language which you haven't
got a language file for, can we do our own?
On a slightly
different track, we intend to bring forum content into each site to
some extent (latest postings, comments on an article looking like a
standard list of comments, but actually being a forum post). Is this
possible, and how easy? I guess what I'm asking is do you supply
scripts (which can be understood and modified) for this type of thing.
Its not going to be much fun if I have to figure out the database table
and data structure to be able to do these bits and pieces.
With the "member online" facility, how exactly are you able to
determine if a user is online? If its session based (IIS, db,
whatever), don't you have the issue of the user closing their browser
and the system being unaware they've gone until their session times
out? Its not actually "live", is it? If it is, can we use it
elsewhere in the sites?
And finally, licenses. We would probably get the multi-site
developer license to remove the copywrite and ads. Does this give
us the flexibility to run unlimited versions of the forum without ads
and the link? Or is there a per/site, per/server license that I
haven't found?
Hope this all makes sense. If its daunting for you, guess how my brain feels?!
Kitster
|
|
First as to your licensing questions you should use the Contact Us section of the site to contact us directly as licensing questions of this nature can not be answered on a public forum.
As to your question on language translation, to translate the forum to another language edit the files in the language_files folder using notepad. If you look in the language file forum on this site you may find someone has already translated the files for you and have posted links to their translation.
For your question on displaying posts etc. in your site you should checkout the mods forum to see if someone has written a mod to do what you require.
The active users (members online) is not 100% accurate as HTTP is a stateless protocol meaning that as soon as the page has finished downloading the connection to the server is dropped, at which point it's impossible to tell if the user is just reading a page or has actually left the site completely. Instead the active users list traces users by IP address and places them into the active users array, this entry in the active users array is dropped 20 minutes after the last activity. I may look into updating this in future to use AJAX to ping the server every so many seconds or minutes which would make it more accurate, but performance and bandwidth issues will need to be looked into before implementing such a feature.
|