I'm not sure if this is the right forum to post this in, so move if needed.

I've been running an EQ guild website on XOOPS now for 8 or so years and just recently in the past 6 months or so have upgraded to 2.3.3. As a guild we use a point system for bidding on loot in guild raids and keeping track of who is on, and when, etc. is a big part of this.

I would like to write a module to help keep track of all this and should be able to handle all the logic and display stuff in php as well as the database stuff in MySQL (I have a bit of experience with php/mysql, but am by no means an expert). When trying to get it into an XOOPS module format, and tying it into existing XOOPS membership data and dealing with XOOPS variables I'm at a bit of a loss. Is there any basic beginner documentation on getting started with this?

the basic idea I have is:
I would like to have a 'guild member' table that ties into the XOOPS membership table that holds data such as main in game character, available raid points, alternate character info etc. It would have a record for each character, with a 'flag' for main or alt that is only modifiable via administrator access after creation. Regular site members would have the ability to add new 'characters' to their profile only, and after that not really be able to modify anything.

There would also be another table for attendance records that would generate most of the statistics that would be viewable by the membership base and would be where point totals and attendance data come from for the main membership table. I haven't worked all the details out about that, but have some ideas. Most of the logic etc. would use this table, and I'm ok with all of that and the parsing of data files to populate it. Most of the direct access to this table would be through an administrative section of the module.

So mainly, I'm looking for info on how I would go about creating a module, and what I would need to tie into the main membership table of xoops, and how all that works.

Any direction would be VERY much appreciated.

anyone have any idea?

I recently went from 1.3 to 2.3.3.

you can jump from 2.0.13.2 or better by using the upgrade option that comes with the full 2.3.3 download. Read the release notes for specific instructions but basically you make a modified html/htdocs directory, copy it on to your existing XOOPS file structure and run the upgrade script (in /upgrade) you need for the version you are upgrading from.

was pointed at this thread when asking about re-enabling HTML in sigs. Any pointers/directions on how/where this filtering is done so it can be disabled?

I just recently upgraded XOOPS from v1 to 2.3.3 and I have a lot of users that use html (some fairly elaborate) in our private forums that can't be duplicated with bbcode.

I've seen several posts mentioning that HTML sigs have been disabled for 'security reasons' but no pointers or direction to how to re-enable. Somewhere there is a filter that is taking the HTML stored in sql and spitting it out as 'code' and not letting the browser format it. It would be great if I could get a little guidance on how to reverse that.

bbcode will not do tables.

where is the code that disables html code in signatures?

I understand the security issues but I don't need to allow signatures in public forums and those posting in the private forums should be allowed to use HTML in signatures.

bbcode is not robust enough to be an option.

upgrading to 1.22 did not solve the problem. I'm not sure if the image thing is theme related or something that has to do with cbb itself.

I am assuming that the html in signatures is something in the base XOOPS package since it shows up as html code in the signature itself in the user profile editor.

The main functionality is working now after finding a theme that works (default does not). Forums are visible, permissions are settable, etc.

Having some signature problems now (to be clear, I'm talking about signatures, tacked on to the bottom of a post, set in user profiles... not avatars that appear at the side of a post). People that have working images in their signatures are having them 'thumbnailed' is there somewhere where this can be turned off? Or the size of signatures adjusted?

The other issue is that HTML in signatures isn't working, it's showing up as html code. I have checked the user table in the database directly and it is stored as straight HTML there so it is getting filtered somehow. Where is that happening and is there a way to stop that?

I have been able to dig up a few posts on this here but no real answers other than 'use bbcode' which is not an option, as far as I know you can't do tables in bbcode, and a reference to re-installing frameworks (I am using 1.20 because that's what I've been able to find, trying to track down 1.22 that I've seen mentioned now). Hopefully the frameworks 1.22 will solve it but posting now in case it doesn't and it's something else, and someone can point me in the right direction.

Thanks for suggesting the frameworks, I believe I've gotten it all straightened out now.

I did some digging and found that the version I installed the first go around was 1.10 (it was what I got when hitting the link I found after dloading cbb3.08). I found 1.20 and installed that and the fatal errors went away.

After that I was back to where the forum index wasn't showing up, but I wasn't getting errors. I had been playing around with Themes yesterday and noticed some of the issues I was seeing with the forums, when using different themes.

I copied over the themes from XOOPS 2.3.3 and while the default theme still showed no forums, some of the others did so it seems to be an issue with the default theme (which may be from 2.0.13 still).

Anyway, I think all is well now! yay1

I thought I did as I saw the Frameworks directory etc. included with the 2.3.3, but looking a bit more closely I guess not.

I grabbed the latest (I think) and did the entire upgrade process over again including frameworks before I upgraded to XOOPS 2.3.3.

When I tried upgrading from newbb 2.02 to 3.0.8 this time (with inline error checking on) I found that the upgrade was having a fatal error with php scripts timing out, so I upped that from 30 seconds to 120 in php.ini and tried again, that time it looked like it ran ok however now I am seeing some different errors when I try to either access the forum modification area or go to the forums directly from the home page.

this is what I see when I try to 'modify' a forum in the admin section.


This is what I see now when actually trying to go to the forums:


I am assuming the E_STRICT is from using an older version of MySQL but that in itself doesn't seem to be an 'error'

what exactly is the 'sanitizer' doing and does it really need to be doing it?