The long awaited SMF Module!

Well most of the softwares that I know use case-insensitive user names.

Getting case-sensitive names to work with MODx (Work Around)
In order to get MODx to support case-sensitive user names, you will need to run the following SQL script to modify your web users table. Please replace {dbase} with the name of your database and {prefix} with the name of your table prefix:

ALTER TABLE `{database}`.`{prefix}web_users`
MODIFY COLUMN `username` VARCHAR(100) BINARY NOT NULL DEFAULT ’’,
DROP INDEX `username`,
ADD INDEX `username` USING BTREE(`username`);

Note: To activate case-sensitive logins for SMF the module will use the “Match case” option found in the Members > Registration > Set Reserved menu.

Here’s the update to the module. See the readme document. This version will allow MODx to support case-sensitive user syncs
http://modxcms.com/forums/index.php/topic,2606.msg17794.html#msg17794

Is that a complete ready to roll distribution, or does it need the updated API put in there too?

Quote from: rthrash at Feb 09, 2006, 12:22 AM

Is that a complete ready to roll distribution, or does it need the updated API put in there too?

It’s ready to roll. If everyone can confirm that it works then we can release it as stable. The readme doc might need some editing.

Anyone seen anything that needs to be changed

That’s great Raymond !

I’ll download the latest and give it a testrun... anyway, a great thing to solve this before first release

Ditto on that David. I’ll give it a try this weekend.

Considering this server can handle it, maybe we should annouce the release date a day or two early to build hype!

Hi Raymond,

Just downloaded this and testing on a local copy of the current database for these forums and a fresh MODx install for the pending deployment.

Couple of things:

1) Password really needs to be obscured as a password field.
2) When installing, I don’t know of a default group I want them to join... is that required?
3) Can we autodetect things from the config file, like the path...
4) I can get the module to run, but when I select either of the options, I get a not found error:

Not Found

The requested document was not found on this server.

The version in the module is dated Jan 26... did I grab the wrong one?

FYI, this is on a PHP5 install running Apache.

Ahhhh... it’s a problem with Safari, actually. The module won’t run when clicking the actual module links. Is there a reason those links have to be triggered via JS and not via a regular HREF?

However, once in Firefox and testing, I get the following parese error registered:

« Execution of a query to the database failed - UPDATE command denied to user ’tattoocms’@’localhost’ for table ’smf_members’ »
      SQL: UPDATE tattoosmf.smf_members SET dateRegistered=’1139859122’,ID_GROUP=’4’, ID_POST_GROUP=’4’, showOnline=’1’, lastLogin=’1129049624’, gender=’0’, is_activated=’1’ WHERE ID_MEMBER=’3196’;

FYI, in checking the users after the error, I do notice that the users are imported into MODx. The one that errored out, is the single user exported from MODx to SMF (ID 3196). Also note that the database user and password for the forum and the CMS may not always be the same, as they aren’t in this case.

And one last report...

With PHP5 and the plugin installed, I get basedir restriction errors when the plugin is enabled:

PHP error debug
Error: logHandler::logError() [function.logError]: open_basedir restriction in effect. File(/usr/share/pear/error.class.inc.php) is not within the allowed path(s): (/home/httpd/vhosts/tattootheweb.com/httpdocs:/tmp)
Error type/ Nr.: Warning - 2
File: /home/httpd/vhosts/tattootheweb.com/httpdocs/manager/includes/log.class.inc.php
Line: 28
Line 28 source: include_once "error.class.inc.php";

When I disable the plugin and module and login, I don’t get the errors with one of the imported webuser logins.

Ok, I’ve installed the module but am not able to run it. I keep getting an invalid SMF path error but my path is correct! /forums/ (yes it works as a url as well)

Hi Ryan,

I think you have a very old version of the module. See the first post in this thread

Mark,

The path is the physical path. I think it’s mentioned somewhere inside the reade me doc.