If you mean:
http://dev.xoops.org/modules/phpwiki/index.php/CoreFunctions
The link works.

Macmend, I replied in the other SMF thread about this. I guess I don't understand your views. Do you not like the bridge developed by Orstio? Did you try it? I don't know simple-xoops or the "module" they are using, but Orstio's is very effective. I am using SMF wrapped in my XOOPS site, and I love it.
Can you clarify what you are searching for?

I clicked the link. I didn't read about the scam stuff though, because the five million ads on the page frightened me, and I found myself curled up in a fetal position sobbing uncontrollably.

Really, I aint never going back there no more.

Glad I could help! That number sounded familiar to that of my own php.ini default value for uploads.

Quote:
I don't see it that way. I don't think anyone is keeping us in the dark. We hear news (some may prefer more details and from specific people) periodically, which indicates life. If people want move by move commentary, they should probably be one of the people working on the project.
Just my commentary. Patience is a virtue.

Might that be related to your php.ini settings? Just a guess.

Exactly. That's what I have on my site.

Again, Orstio released the newest bridge (aka module by some) a few days ago, and the SMF discussion for it is HERE with the thread for the previous bridge version concluding HERE. People unfamiliar with the bridge might appreciate the recently locked topic for the information that still applies to the newest version.

It really does work well, with some of the webmaster's biggest concerns being:

• Making sure the sessions of XOOPS and smf are set to the same value so one does not expire while the other has them still signed in. Personally, I set my XOOPS custom session to a huge number like 3000 and make the default smf session also 3000. The "Minutes to stay logged in for" of SMF should simply be removed as an option.
Sessions issue virtually resolved.

• How to integrate comments within modules of the XOOPS site. One may choose to use the comments as they are but remove the post counts from the template so there is no confusion.

• Some XOOPS url's will need to be redirected to either point to their SMF equivalents or to something else like the homepage. Examples of these url's are /user.php, /userinfo.php, /viewpmsg.php, /register.php, and /pmlite.php

• Get rid of the XOOPS User Menu, meaning make it not visible to the public. There is next to no use for it if you have SMF, especially for registered members. Admin can easily get to the control panel without the User Menu if it is made not visible to webmasters, too. (/admin.php)

If you really want SMF, like I do, these issues are worth managing. No, the SMF bridge/module does not fully integrate like other forums used with Xoops, but it is very very close, and a little work ties up the loose ends.

Quote:
Macmend, I'm not sure why you think it is only for the "simple-xoops" branch. I have it installed on my site which is XOOPS 2.0.16. It is a BRIDGE that gets installed in your modules folder. I would invite you to stop by my site, but I do not have it open to the public yet.

The link mortuk posted above is useful, and I got help from the bridge developer Orstio in that thread. You'll also note that the newest link is actuallyhttp://www.simplemachines.org/community/index.php?topic=173730.0
The latest bridge was released just the other day.

-EDIT-
I see after looking through the SMF thread that you posted there sounding very discouraged, but then you are here praising what you see on that simple-xoops site, which is actually the very same bridge you said you were disappointed with, or at least it works nearly exactly the same.

Quote:
Sure. System Admin Preferences>General Preferences (same place you change the default theme). Under Default theme, you'll see "Check templates for modifications ?" (should check YES while testing) and under that you'll see "Selectable themes." You'll be able to select multiple themes you want to be able to view on the front end. You can choose any or all of the themes you have uploaded to your themes folder.

Next, you go to your admin for Blocks, and make the "Change Theme?" block visible and set the page(s) you want it on. To ensure users or anonymous viewers do not see the block while you are testing, change the permissions in your Groups so only webmasters have access to the block.

That should do it. As you experiment with themes or work on them, you'll want to have "Check templates for modifications ?" on, and turn it back off after you are finished testing. Also, sometimes, you'll have to clear all files except the index.html in your templates_c along with clearing your browser's cache. Even with my "check templates" setting set to YES, I have had instances when changes were not revealed until I cleared those things too. I'll also mention that you might want to "refresh view" when using an ftp app like Filezilla to be sure it is displaying everything in templates_c.

Quote:
Oh, okay, I see after rereading that you are familiar with this, so you just need to make the correct block visible and set permissions for who may see it(you).

Quote:
I think there are lots of newer themes to be found, and several credible sources making them. The only question is what kind of license they are using, whether we can use them however we want or if commercial use is prohibited.

Quote:
That doesn't make any sense, unless the theme.html file was either not present or did not have the proper permissions set.

When you try your new theme, to be safe, you can make the theme selectable in the "Change Themes" block and avoid making it your default theme until you are sure you like it.
Subsequently, you should always have access to your admin side regardless of the theme you are running.http://www.yourURL.com/admin.php should take you there if you can't get there the normal way.

Another reason for a blank screen could be related to protector and your ip being registered as a bad ip, in which case (I believe) you can go to /yourTRUSTPATHdirectory/modules/protector/configs/ and delete whatever is in the present file. I think this happens depending on settings and how many times you click on a link (like "Home") within the set period of time.

That's all I got. I'll be hoping to hear more details about this theme, too, if it really had anything to do with the trouble you ran into.

Good luck...