OK. I solved the situation on my own.
Solution? Open it in a binary editor and save everything in the lower ASCII
table (only save pure text). I have taken the liberty of correcting grammer
and punctuation. Please see attached if in need of the PLAIN TEXT version
of the installation and configuration guide for the SMF_bridge.
Thanks to all whom have taken the time to respond to my post(s).
P.S. If someone can post the images that accompany the MS DOC version
of this. I would be more than happy to create a PDF document.
After installing the bridge you should allow users to login via the MODx WebLogin snippet.
Modx will now handle all logins and signups.
so how would that work if you have the smf forum how could a user login using the modx snippet if they are at the SMF board, or do you have to let them know to only login at modx to access the forum, it’s somewhat confusing, most people will sign on at the forum I would think.
would you disable sign ups at the forum in order to make use of the bridge
Curious about something, if we want to wrap SMF that’s on a different domain into another domain
both being complete 2 different modx installs, could the SMF bridge still work for both ?
ie
site one mydomain1
SMF <----
site two mydomain2
wrap SMF
will the connector work on mydomain2 with the wrapped smf located on another domain ?
@bugsmi0 Pure speculation. But I see a couple of possible issues
with your purposed situation. 1) Communication with the database; In an effort to keep your
data consistent, you’re going to need to communicate with the *same* database and work
with the same table information on both domains.
2) If your links aren’t the equivilent to roughly: href=/mydomain/site target=_top you run
the risk of having your content being hijacked. That is to say, if you wrap your pages;
whats to stop someonelse from posting your *live* content within ther own and claiming
it as theirs? That *used* to happen to me alot until I created and inserted a javascript or
PHP location enforcer in the HEAD section of all my documents that breaks them out of a
frameset container.
Just thought you might want to consider these possible scenerio’s.
--Chris
not sure I follow you, the two domains are both owned by me and the main thought to have a single SMF as opposed to 2 was to keep it simple, having 2 is more difficult to maintain then just one.
My concern was how the SMF connector plugin would work since both domains have separate DB and modx installs would it get messed up with people logging on from one site or another, the goal being to control the new user accounts created on modx and to make sure the users are logged into the right modx site.
not sure if this is possible
Ahhh, I see what your goal is. I’m pretty sure that’s not going to be possible.
Pretty much every forum I’ve ever evaluated, required working from one
database (or table, depending on it’s layout). So it wouldn’t be possible for
SMF to decern which domain (MODx install) you wanted to work with for any
given user. There might be another solution. But I can’t imagine how.
Best wishes.
--Chris H.
so how would that work if you have the smf forum how could a user login using the modx snippet if they are at the SMF board, or do you have to let them know to only login at modx to access the forum, it’s somewhat confusing, most people will sign on at the forum I would think.
In the SMF-bridge documentation show’s you how you can redirect logins and signup request to a modx page. This means that once a user clicks on login from your SMF page they will be taken to a MODx page.
would you disable sign ups at the forum in order to make use of the bridge
The module will redirect the SMF request to a MODx signup page.
Quote from: bugsmi0 at May 17, 2006, 04:52 PM
Curious about something, if we want to wrap SMF that’s on a different domain into another domain
both being complete 2 different modx installs, could the SMF bridge still work for both ?
ie
site one mydomain1
SMF <----
site two mydomain2
wrap SMF
will the connector work on mydomain2 with the wrapped smf located on another domain ?
Yes it should providing that the domain names are different. for example, www.domain1.com, www.domain2.com
both SMF and MODx will get different cookies for the two separate domains.
Quote from: bugsmi0 at May 18, 2006, 02:39 AM
not sure I follow you, the two domains are both owned by me and the main thought to have a single SMF as opposed to 2 was to keep it simple, having 2 is more difficult to maintain then just one.
My concern was how the SMF connector plugin would work since both domains have separate DB and modx installs would it get messed up with people logging on from one site or another, the goal being to control the new user accounts created on modx and to make sure the users are logged into the right modx site.
not sure if this is possible
Let me see if I can get this right. It’s 2 MODx DB/Install with 1 SMF DB/Install, correct?
example:
MODx A -
|
--->-- SMF A
|
MODx B -
The problem here is which modx will SMF redirect request for signups/logins to?
PS. Not to worry. There are plans to solve things like this in some future release of MODx
