If you are looking for a workaround, there is an option in modversion to execute a script after installation. It may be possible to run the module's update right at the end of installation, silent to the user.

(Though I have never tried it)

I have never worked with IPBM, but since it is a XOOPS module, my hope is that it would use the XOOPS user table. If this isn't the case, that would make things a lot more complex. I will look at IPBM this weekend if I get a chance and see what comes up.

If you are feeling gutsy, you could always try it. It doesn't modify your IPB at all, so worst case scenario you have to clean up XOOPS and try again.

This is just from personal experience, but I always seem to have an easier time getting NetPBM to work than I do ImageMagick. There are precompiled binaries for Win32 from the main Gallery SourceForge page.
http://prdownloads.sourceforge.net/gallery/netpbm1.1-gallery1.0-win32.tgz?download

If this works, then the problem is pinned down to something strange with the ImageMagick installation. If it still generates errors, it might go deeper than that.

Either way, I reccomend keeping these just below your site root in something like:
C:\Program Files\Apache Group\Apache2\NetPBM\

Let me know how it goes, and good luck!

I let the XOOPS table just assign a new ID (in order to prevent screwups with auto-numbering). I thought for a while about making it carry the same ID over, but I had an issue with some users registering on the new XOOPS site to set things up (and so the member IDs didn't match).

For the IPB member table, I did use ibf_members since it contained the most complete user settings, including the all-too-valuable username and MD5 password hash.

I hope this helps

Ah, but those all seem to go to the Invision Module. ^_^ I'm actually working on migrating everything into XOOPS from various other mediums. Thank you for the link though, I think the information on NEWBB -> IPB will worth looking into as far as what needs to be done to create an IPB -> NEWBB one.

(Note: Not really sure what kind of hack this is, or if it even is. Ultimately, it will become a forum migrator too, which I guess is a hack-tool-thing. ... sorta)

No, this isn't flawless, and no it doesn't move your posts (working on something like that), but if you are like me and had a site whose uses and functions exploded without warning (jumping from 200 views per day to 4,000+), you needed a way to get your data into a good CMS like Xoops.

I was running IPB 1.3, and needed to get my data into XOOPS as fast as possible, the most important data being my user database. Nobody wants to re-register. So here it is, a user DB migration tool, hopefully the first of a few.

Note: things are hard coded, and I am not fond of the "exempt" users method, but I couldn't think of an easier way. If anyone has one, more power to you, and please post so we all can learn.

Without any more rambling, the code:
http://www.felocity.org/files/xoops_2.0.5.x/ipb1.3-users-to-xoops2.5.2.zip

Please let me know if there are any questions, etc. Good luck!

Quick note: This does NOT put the user into the registered users group. An Insert statement to drop the new UID into group 2 would be helpful, and once I finish on a few sites, I will come back and correct this.

That does make a bit more sense, especially since a module would technically (in a perfect object-oriented world) be a derivation of a XOOPS Object (or more precicely, an instance of a XOOPS Module).

Given the amount of data that goes in and out of Xoops, it only made sense there be some sort of validation functions in the core, it's just been a matter of finding them.

Thank you very much for the help! I'll start digging and see what I can find about how to use those two examples in my code. Anything's worth a try, some things worth 2-3.

(Edit: I could not see anything in the RFI forum for some strange reason, so I have no idea if these functions have been discussed )

Xoops ate my session, so this is going to be a lot more abbreviated than before. After looking through the class files, the forum, the news, and other modules, I have tried to put together a helpful reference on using the Text Sanitizer. If some other people in the mod community can verify these, it would be a huge help both to the mods and to the wiki. I do believe though that these functions (as used now) are marked "depreciated" in CVS, but I couldn't for the life of me find the new revised function names.

Get the instance of the MyText Sanitizer
Must do this first.


Sanitize Data to save in a DB



Prepare Data from DB to display on page
second option is to show smilies or not (optional)



Prepare data from DB to put back into a textbox



Prepare data from DB to put into a "preview" section
second option is to show smilies or not (optional)



Prepare data from DB to put into a "preview" section that is contained in a form? (anyone actually use this?)



Sanitize Text Area Data to save in a DB



Prepare Data from DB to display on page
1st option: convert html code (optional)
2nd option: convert smilies (optional)
3rd option: convert XOOPS code (optional)



Prepare Data from DB to put back into a text area



Prepare Data from DB to display in a Preview
1st option: convert html code (optional)
2nd option: convert smilies (optional)
3rd option: convert XOOPS code (optional)



Prepare Data from DB to display in a Preview and that preview is contained in a form? (anyone actually use this?)



Prepare Data from DB to display in a "quote" format? (anyone actually use this?)

Yeah, it is!
I don't think it would be too hard, although it would be independant of the profile field (which would be an awesome touch if that ever happened).

Another option would be to integrate a ping to GeoURL
(http://geourl.org/ ) and then track out of that. While probably not the best solution, it is still a pretty awesome thing.

Incidentally, the Flash Script took far too long on my computer and caused it to hang. It might be simply because of the sheer number of dots it was trying to mark.

Once again though, a very cool module, and would be a nice addition to Xoops, though I'm not sure if we would need anything quite so ... flashy. (Forgive the bad pun)

This is hard because I actually use MT on my personnal site and a few others. Here is the rule I use when deciding platforms.

A) What will it do?

B) Is that all it will ever do?

C) What is the most important feature for you?

Usually theres three questions help when I am weighing Nuke against XOOPS against Movable Type against B2 (etc).

If you know all you will ever have (or ever will have) is blog-centric data, then Movable Type will probably be your number 1 option. RSS, Collaborative Blogs, HTML page generation (for non google bots), and it's use of PERL instead of PHP all make it a better choice if (and only if) you are going to be doing just blogs.

The instant you start adding other things such as calendaring, profiles, and the all important forums, it starts becoming a lot trickier to decide what's best. I strongly encourage you in the planning stages to install a copy of each and see which one will better meet you and your user's needs. Sometimes the clients just like posting interface X over Y.

Give XOOPS a shake, and it might be just what you need! Good luck enjoy Xoops!