Quote:
Are you sure you don't just need a custom block?
That would be a whole lot easier than creating a module.

If you really need to create a module, go get one of the smaller ones and start hacking.

Dennis

Quote:

What is the licensing on IPB vs. phpBB ?
It looks like the Invision S/W is commercial, right?

Also, what features of IPB that phpBB doesn't have are you using?

Thank!
Dennis

There have been some similar requests made often in the past. You can find them if you search the forums. To sum them up, lots of people would like this, but no one has actually written any code to support it (lots of wishing - no doing).

My ideal would be a member or subscriber module that would replace the existing registration, view, edit pages and allow them to add customized attributes. Many (but not all) of the existing attributes could be removed from the main code and made into these extended attributes. This is a pretty ambitious idea and I'm not sure I want to tackle it as my first XOOPS module.

I'd be really cool if an experienced module dev could take this on as a sort of project leader. I'm sure a lot of us would pitch in with ideas and code.

Dennis

I just got a chance to try this out on my testing site, and I'm very impressed !!

I've only explored the admin pages so far, but this module looks like it will be fantastic for my sites. Consider this a virtual pat on the back.

I know you're quite busy, but I think moving this to a final release and making it part of the default XOOPS install will be a huge step forward for XOOPS.

Is there a place in a Wiki where people like me can add some howto and "use case" material about the new wfsections? The only drawback I see in this module is an overwhelming sense of complexity with all the admin options. I love complexity, but a first time user might want some help setting this up for various types of use, hence good docs in a wiki or something like that.

Thanks for all your effort, Catswolf!

Dennis

There is nothing like this available now, but it sure would be nice to allow "user defined" fields. Perhaps a better implementation would be a subscriber module that would store it's data in a separate table and provide an enhanced view/edit account page to replace the current ones.

I've thought about doing this, but it's only gotten that far, unfortunately

If you look at the licensing/pricing of commercial apps, I think you will be pleasantly surprised by what you find. The initial software costs are always a fraction of the actual startup costs. These used to be "baked in" to the selling price, but competition has forced them to make the sales price lower and add extra line items for installation, customization, configuration, support, and maintenance. These are the items that you can (and should) always charge for. Giving away the initial product is no big deal if you can make your money with the services you provide.

There might be a few organizations that will implement your product without paying for any services, but they probably have very limited needs (and no budget) anyway. Even those places may need to hire you in the future, and if they are using your code, you have a huge marketing advantage over other companies when they go looking for help. OTOH, if you decide to bail and not provide any more support or updates sometime in the future, the code you worked so hard to create is not wasted, but can be picked up by others if it's worthwhile for them to use it. That's the value proposition of open source software.

If the non-profits understand the value your code provides and the added value that you bring, I expect most all of them will want to hire you for the services you provide, knowing that their needs will figure prominantly in future upgrades and they will be benefiting other NPO's in addition to the value the receive. This seems like an especially easy sell to a non-profit, as they are less concerned about their expertise being re-used by their "competitors".

And as another benefit, if your code is open sourced, you will automatically get a lot of good will from experienced PHP/XOOPS coders who you might need help from in the future. It's always nicer to have friends than competitors, IMO.

Good luck with your project!

Dennis

You can add a custom block and put it in the center column. Or you might try the TinyContnet module, it works well for this, and gives you a menu block for accessing the pages.

HTH,
Dennis

You could "chop" it however you want manually if you know HTML (or pay someone to do it if you don't).

As far as putting it inot XOOPS, why would you want to?
It's just a bunch of static pages. The only advantage of XOOPS would be for security (and it's hardly secret content) or searchability, which can be done with htdig or a link to Google once it indexes the pages.

Is there something I'm missing about this?

Dennis

Quote:

I think I had the same issue you are having. I turned on PHP debugging and found an error (extraneous <tr>'s inside a <{'s if I recall correctly). After I fixed that, the threads came back OK. I had to turn off the debugging, because it showed so many bugs the site became unusable. It's working OK, but I think the code still needs a bit more "polishing". Even as it is, I like it better than the original NewBB (so don't take this as harsh criticism).

The file I mod'ed was: modules/newbb/templates/newbb_thread.html
The line now reads:
<{if $viewer_is_admin == true}>

I also found a naming conflict with xf-sections that I fixed, if anyone experiences diffculty posting to a private forum when xf-sections is installed.

Dennis

Quote:

The answer is yes!

To make the notifications send the contents, edit the template files in the modules/newbb/language/english/mail_template directory. Use the one called global_newfullpost_notify.tpl as a guide for modifying the others. You might need to change the order of some lines in post.php also to get it to work in some places.

Hope this helps someone else!

Dennis