I'm having the same problem. New install of 2.0.15. New install of CBB 3.05. No data imported.

In ADMIN section:
If I try to create or edit a category I get a blank page.
If I try to edit a forum I get a blank page.

In forums as a user:
If I try to edit an existing message (there is one there by default) I get a blank page.
If I try to reply I get a blank page.
If I try to post a new message I get a blank page.

I have deleted all files from templates_c. Did not fix.

I have renamed plugin.dist.php to plugin.php and made a change to the editor line per Wizanda's recommendation. Did not fix.

I have turned on debug for the site per standard white page instructions. No errors are reported as noted at the top of the debug report:
When replying: errors (0) queries (31) blocks (5) extra (0) timers (5)
When posting new message: errors (0) queries (27) blocks (5) extra (0) timers (5)

I'm at a loss. What else can I do to fix this? Thanks in advance!!!

I recommend restoring your backup and starting the conversion over again. It may take a few tries to pinpoint where the problems might be. There are some table differences between the two trees that can cause great headaches....

Best of luck!

Very nice work here!

I'm playing with it but found that the horizontal menu doesn't work under 2.2.x. Regardless, it's very educational and I look forward to the merging of the two XOOPS so I can take advantage of your efforts!

This looks very promising. I'd recommend keeping all three implementations.

[ pagebreak ]
[ pagebreak:pagetitle ]
[ pagebreak:#:pagetitle ]

This ensures backwards compatibility and for sites that prefer a list of pages rather than a drop-down, they still have a choice.

Thank you very much!

I recently saw in a really good article on frxoops that mentioned that Giba had reworked the poll module. I went to XOOPS Brasil which is where it listed it being located, but that site only gives me a news release without a download link. I see that they have a downloads section but I can't figure out whether the poll module is one of the files there.... :(

Could a kind Spanish/Portuguese speaker point me in the right direction, please? Is the file in their downloads directory?

frxoops article:
http://www.frxoops.org/modules/news/article.php?storyid=1073

Giba article:
http://www.xoops.net.br/modules/news/article.php?storyid=511

The lack of permissions has prevented my use of polls for several years now. It's definitely needed.

This will become even more of a pressing issue if/when XOOPS become multi-site capable -- one install/database serving multiple communities. If you have sites on bikes, origami and cooking and are polling your users on a destination for a bike ride, you shouldn't need to bother the origami or cooking folks. Especially since their input isn't really relevant since they won't be attending those events.

I've considered cloning the polling module in the past but this is troublesome as some polls ARE intended for everyone....

Thanks for adding permissions to your to-do list!!!!!!!

Out of curiousity, will your modifications be made available for general XOOPS use? I'm interested in the interactive fiction functionality you are proposing and wouldn't mind seeing how you have approached it.

Thanks in advance for contributing back to the community!

The timeouts for posts is a good/bad thing. :)

You've just run across one of the things that makes XOOPS more secure. It closes sessions within reasonable amounts of time which are adjustable by the administrator. I presume it prevents session hijacking. I presume it also helps it to recover resources.

I frequently spend an hour or so writing responses on my own site. I like to be able to write in between other tasks and give myself some time to (re)consider what I've written. As a result, I've gotten into the habit of highlighting and copying my text before submitting. If I've timed out, I re-login and paste my text. Problem solved.

I've found that many very busy sites have short timeouts regardless of the forum or CMS software they use. This habit has helped me keep my sanity....

You will very likely find that XOOPS has a number of minor annoyances like this. They result in a more secure CMS with the cost being some inconvenience. Some of them have hacks to work-around them for those that don't mind a little less security. Use the search function here. And don't be afraid to ask whether something is possible/changeable/hackable to better suit your needs.

I ran phpnuke sites for several years. I left during one of the many forking sessions it has. The straw in my proverbial camel's back was when nuke deleted the support forums and shortly after went pay for updates including security fixes even though most of the fixes were provided by the public, not the developer. I don't know if things have changed since (and quite frankly, I don't care since I am a very happy XOOPS user). That decision split the nuke community (again) and made everyone angry at everyone else. In short, it wasn't fun to run a nuke site anymore.

I researched the options and settled on Xoops. It has several active developers, a supportive community, a main website where I can get information and ideas. And most importantly, it's secure and constantly monitored for holes which are patched quickly. Yes XOOPS has it's share of drama, but it's actually productive most of the time and the participants normally mean well even if they get heated -- that's a lot different from the Nuke dev tantrums....

Over the years, I've found the XOOPS php code to be easily mod'able even for a complete novice like myself. The themes are laid out clearly and are moving toward all css-based for layout.

Xoops has an upgrade path and a plan. I've never had any issues updating a site. I can update my sites remotely, adding and removing modules with a few clicks. I can almost taste the ability to easily run multiple sites from a single database.

I've tried several options. Anyone choosing a CMS should do so too. XOOPS works for ME. You need to decide if it works for you.