Thanks for pointing out that I had an old version of the module from the XOOPS 2.2.3 theme packs. That version was 1.4 and the current version is 1.44.

I downloaded the 1.44, uninstalled completely the old 1.4 and installed the current version.

No change. Still no display of "Recent News" on the Top Page.

I'm using the "Navigate Through Topics" block instead on my Top Page, but it would have been nice to have the latest news already displayed.

I'm also having an odd issue with News, using XOOPS 2.2

The Recent News block does not display on the Top Menu page, but it displays fine on the News module pages.

A couple of times I saw remnants of the news item that should have been displayed, so it looks like it's trying to post it to the Top (Home) page, but something is not correctly formatted, or is displaying too high, behind the banner. I don't know what's causing it.

Hi mOnty,

Quote:

Indeed. That's what it uncompressed as, and that's when it first crashed and damaged the mySQL database.

I tried changing the name to different things in an attempt to get XOOPs to recognize myReviews as a module.

It does not work as;

/myReviews
/myreviews
/myrev
/reviews
/rev

Any ideas?

Thanks,
-Lion

Hi mOnty,

I'm having difficulty with myReviews, and was wondering if perhaps you can help. Basically, it won't install at all. I'm running XOOPS 2.0.1, php 4.3, and the path to the myReviews is modules/rev (have tried modules/myReviews and modules/myreviews and other variations). Here's a screenshot of what I get when I pull up the module admin page;



It acts as if it can't see that it's a module at all. On reading the errors that were generated in php debug mode, it looks like something to do with permissions, so I tried changing permissions, eventually on everything, making everything in modules/rev to 777. Things looked better, the 'Module not found' error is gone, but it still won't install. The module admin page now looks like this;



At this point, I'm at a complete loss for what to try next...

Any ideas, or fixes, would be greatly appreciated.

Thanks!
-Lion

This is going to sound odd, but I am having the exact same problem with three different 'Reviews' modules; all three are breaking in the exact same way.

What happens is that when the folder is moved to the /modules directory, it says that there's no "modfile", it can't see the name of the module. All of the files are in the /reviews (or /myReviews, depending on which module) folder, not nested further down. The files are present, this I verified repeatedly. For some reason, XOOPs can't seem to see them.

If I try to install anyway, I end up with a bad installation which cannot be accessed, has no name, and can only be removed by going into MyPHPAdmin and directly removing the entries from the modules table.

My configuration is php 4.3.11, XOOPs 2.1.1. The problem is occuring with "Lykos Reviews 1.00", "My Reviews 2.1 RC1", and an earlier version of MyReviews.

I see that other people are using those modules without this problem, so I'm thinking the issue must be with my configuration somewhere. Any ideas would be welcome.

-Lion

Hi X-ception,

Quote:

I'm not going to knock anyone's hard work that they've done on whatever forum module they are partial to, I'm sure that each developer has his or her own excellent reasons for liking whatever package they're working on.

But you're right, there's a lot of choices of out there and it's a shame to be limited to very narrow selection. IPB is not palatable to me because it requires hacking core XOOPs files, which can render it inoperable when the next XOOPs or IPB update comes along. Let the XOOPs folks do what they do best, and the dedicated forum folks do what they do best, all I hope for is a bridge so that the packages work nicely together.

I'm willing to pay for a developer to write this bridge, and from the look of things, there are other people who might contribute also. Does any developer want to take up the challenge, and if so, how much would it cost to have such a product, a XOOPS<>SMF Bridge, to be produced? Or, if someone writes this as a commercial product, I would be willing to buy a copy if the price was reasonable.

-Lion

Catalin,

Thank you very very much!! That fixed the problem and showed me some other things to look at to fix other possible issues too! Just knowing where these functions are located is a huge help to me.

I wish you well.

-Lion

At this point, I just want to get rid of the bad module listing in the XOOPs Admin menu. I'm hoping there's a file that can be edited to do that.

Here's the file listing of what's in the /wfsection1 module directory (which has since been relocated outside of the modules directory altogether - putting it back in doesn't fix the problem);

-bash-2.05b$ ls -la
total 144
drwxr-xr-x 13 lionheart lionheart 1024 May 24 12:48 .
drwxr-xr-x 4 lionheart lionheart 512 May 24 12:48 ..
drwxr-xr-x 2 lionheart lionheart 512 Nov 2 2003 admin
-rw-r--r-- 1 lionheart lionheart 9821 Jun 28 2003 article.php
drwxr-xr-x 2 lionheart lionheart 512 Nov 2 2003 blocks
-rw-r--r-- 1 lionheart lionheart 4051 Jun 2 2003 brokenfile.php
drwxr-xr-x 3 lionheart lionheart 512 Nov 2 2003 cache
drwxr-xr-x 2 lionheart lionheart 512 Nov 2 2003 class
-rw-r--r-- 1 lionheart lionheart 2106 Jan 7 05:16 comment_delete.php
-rw-r--r-- 1 lionheart lionheart 2102 Jan 7 05:16 comment_edit.php
-rw-r--r-- 1 lionheart lionheart 2100 Apr 11 09:28 comment_new.php
-rw-r--r-- 1 lionheart lionheart 2102 Jan 7 05:16 comment_post.php
-rw-r--r-- 1 lionheart lionheart 2104 Jan 7 05:16 comment_reply.php
-rw-r--r-- 1 lionheart lionheart 2446 Jun 15 2003 download.php
-rw-r--r-- 1 lionheart lionheart 2050 May 24 2003 footer.php
-rw-r--r-- 1 lionheart lionheart 286 Jun 11 2003 header.php
drwxr-xr-x 2 lionheart lionheart 512 Nov 2 2003 helper
drwxr-xr-x 2 lionheart lionheart 512 Nov 2 2003 html
drwxr-xr-x 6 lionheart lionheart 512 Nov 2 2003 images
drwxr-xr-x 2 lionheart lionheart 512 Nov 2 2003 include
-rw-r--r-- 1 lionheart lionheart 15653 Jul 1 2003 index.php
drwxr-xr-x 5 lionheart lionheart 512 Nov 2 2003 language
-rw-r--r-- 1 lionheart lionheart 2882 Jun 20 2003 print.php
-rw-r--r-- 1 lionheart lionheart 6070 Jul 2 2003 ratefile.php
drwxr-xr-x 2 lionheart lionheart 512 Nov 2 2003 sql
-rw-r--r-- 1 lionheart lionheart 9736 Jun 17 2003 submit.php
drwxr-xr-x 3 lionheart lionheart 512 Nov 2 2003 templates
-rw-r--r-- 1 lionheart lionheart 4739 Jun 3 2003 topten.php
-rw-r--r-- 1 lionheart lionheart 25774 Jun 19 2003 wfsupdate.php
-rw-r--r-- 1 lionheart lionheart 4980 Jul 2 2003 xoops_version.php
-bash-2.05b$

Thanks for your time, David!

-Lion

I am having trouble with the module installation page of the Admin section. Basically, there are three modules which will not install properly;

myReviews
wfsection 1.01
wfsection 2.0.1

The installations (I suspect it was caused initially by myReviews, since I have had no luck installing any version of that) failed, and the display showed an unnamed module in the installed section. It looks like this;



Trying to get info or uninstall did not work. I tried removing the directories, that didn't work either. As far as I can tell, the section is not linked to anything at all, and that's why it doesn't respond. The original installation error was, I think, something to the effect of a module file not being found. Subsequent attempts to re-install one of those modules will fail, and leave me with another bad entry in the table (I renamed it to 'bad1', and now I have a 'bad2' and a 'bad3' as well). Rebaming the entry, or setting it active/inactive, are the only things I can do with them.

How do I fix this? Any suggestions would be greatly appreciated.

Thanks!

-Lion

I'm getting the same error, apparently a conflict between WF-Section, WF-FAQ, and WF-Quotes. I also have WF-Links installed, but it doesn't seem to have the issue. When I turn PHP Debug on, this is what I get when I attempt to access the admin.php file in either WF-Quotes or WF-FAQ;

Fatal error: Cannot redeclare listgroups() (previously declared in /cms/modules/wfsection/include/groupaccess.php:14) in /cms/include/groupaccess.php on line 13

Part of the installation for the FAQ and Quotes modules said to copy the /include file (which was groupaccess.php) over to the XOOPS ROOT /include, which I did. One overwrote the other, but they were the exact same size, so I thought it was just a common-use php file. I think both modules do use the same file, and they actually conflict.

So. My question, if I understand all that's happened so far, is this;

Which .php files need to be modified, and how do they get modified, in order to let the WF modules co-exist peaceably?

In advance, thanks!

-Lion