Quoted from the Dokuwiki site:
"2005-04-24 I finally upgraded to the devel version. We’re officially in pre-release state Please report all bugs and oddities you may encounter."

I have not upgraded my version yet so I'm not sure if anything broke. Looks like a pre-release version is available and a new release should be coming soon.

What language of XOOPS are you installing Dokuwiki in?

Administrator is the the name for Administrator in English. If your install uses a different word for Administrator, that needs to be changed in one of the Dokuwiki files.

In a project this size, communication is essential. So is willingness to embrace change.

I'm just a user. I don't ask many support questions primarily because I can search the forums and find most of my answers. If a private forum is created, there will be a lot less people there to answer questions and the vast majority of users (people like me) will never see the answers. That seems like a very big step in the wrong direction....

I see talk of informing the local support sites of upcoming changes. That is a very good thing. That allows everyone to be prepared when changes happen. It allows local translations to be available on release days.

I really appreciate the open discussions around the recent patches. Those posts gave a lot of insight into the development process. I'm hoping that this process becomes more commonplace.

Mith mentions updated road maps. I think they are essential. EVERYONE needs to know what is happening and what to expect. We don't need specific dates, but rather concepts and general time frames. If things get pushed back, change the time frame. If there is ongoing discussion DURING the development and testing processes, then everyone will be understanding and aware of delays.

I see a lot of progress being made. Communication is something that seems really obvious but is actually hard to accomplish. It's a constant challenge.

There was a really good conversion script that I used about a year ago. The only thing that didn't convert was BB code. But all users, PM's and forums converted without a hitch.

I think the script I used was by bd_csmc. If you search on NUKE and CONVERSION you should get quite a few hits. There might be more recent scripts available but I figured any starting point is better than none.

NOTICE: For those of us using this module, a serious regex error was recently discovered in Dokuwiki. A fix is posted on the Dokuwiki site.

-----

What do I prefer about Dokuwiki? It's clean, well-integrated, simple to use, text file-based and super simple to maintain or upgrade. Most importantly, it is still under development even though it is a mature application. Garbellini did a fantastic job on the installation documentation and on tying it into XOOPS totally seamlessly -- my sincere thanks!

I could never get Wiwimod to work properly. It might be a good module but it failed miserably for me. I have not seen an update for it in months.

I couldn't find phpWiki when I was looking for a wiki module. It seems to be even older than Wiwimod.... It does not integrate searches with Xoops.

Your mileage may vary. Use the module that works for you and meets your needs.

You'll need to do it by hand.

Most (if not all?) themes have a style.css file. Some have styleNN.css and styleIE.css as well.

The style.css file is where most of your theme's css is located. The site logo, left/center/right columns, header, footer, and many more general css settings are here. Many of the standard modules use css settings from this file. The most common are odd, even, blockTitle, blockContent, etc.

The styleNN.css and styleIE.css files are for css changes that specifically affect Netscape and Internet Explorer respectively. These are exceptions. There are some known rendering issues with IE for example and some workarounds to make it render the same as NN (and vice versa). These files allow you to make those fine tuning changes.

Some modules also include css files. Their filenames can vary. This is especially true of modules that are ported from outside of XOOPS or that were developed as stand-alone programs before being brought into Xoops. Integrating this css into XOOPS can sometimes be challenging if the module redefines classes.

Thanks for the continuing development! Great module!

I'll post to your site as a feature request. I'd find it useful if when using buttons and you choose to not show the title, the line the title would normally appear on would be eliminated. This would allow the buttons to appear closer together. Right now the two rows of buttons have a large gap between.

Using the search function in the upper right with keywords of either "Warcraft Theme" or "WOW Theme" gave hits to themes that might interest you.

Quote:

The menu title choice was intentional. Since there is only one menu, the title "User Menu" seemed cumbersome. It also allows for further expansion of that menu for other items should I wish to add them without adding buttons. This allows for Admin, News Submissions, News Moderation, etc.

One item that wasn't mentioned in the first post was that there is a second row of buttons for administrative and "second tier" users. This allows access to subscribed services. That row isn't visible to anonymous users.

The primary design choice that influenced this theme was that the website will be run on a home PC that is used for other things as well. It has limited DSL bandwidth. As such, I was aiming for a fast-loading, low graphic theme that wouldn't impact either normal use or web visitors unduly.

Thanks for the feedback!