The preloader folder will be found in the pm module folder.

I'm not quite sure that you will be able to do it from the way you are suggesting, but it is worth a try.

You should however be able to add another tab quite easy by adding one by editing the '/module/pm/admin/menu.php' file:

and

$adminmenu = array();
$adminmenu[1]['title'] = _PM_MI_INDEX;
$adminmenu[1]['link'] = "admin/admin.php";
$adminmenu[2]['title'] = _PM_MI_PRUNE;
$adminmenu[2]['link'] = "admin/prune.php";
$adminmenu[3]['title'] = 'Newtabconstant;
$adminmenu[3]['link'] = "newtabfile.php";

Easypeasy huh

Quote:

All posts are checked for spam ratings before they are saved to the database. That way, even if they are using bots and they are marked as spam, they hit the moderator queue long before they will be visible on your website and shown to the world.

Of course this is not fool proof, but it should go a long way to reducing spam.

Quote:

When you come across a bod bot, you can submit this to the Akismet database, and this way it will be shared with the rest of the Xoops community. plus, you have many other CMS's using this system as well, so it will be well maintained and kept up to date.

Quote:

Yes, I have more or less completed this. While most of the work will be done automatically, webmasters will have the ability to ban users suspected of spamming or mass postings without them having to make an actual spam post.

Hope that helps?

Hey Jim,

I have already done what you asked in the new version, which I will be releasing next week and I have a few surprises in store ;)

Once I have the module as a full release I will add all the plug-ins for different modules, because I am not quite sure how I will have the plug-in system until then.

ATB

Catz

The pmlite (which should have been taken out when the PM module was created) is 'overloaded' with the new preloader system. Look in the PM module Preloader and that should give a good understanding of how this is done.

I also think that there is a smarty plugin somewhere, I might be wrong.

Module: Spammer v.1.00b Alpha
Xoops: v2.45
PHP: V5+

**WARNING ALPHA VERSION**

Change Log

=>version 1.00 Beta 29 July 2010
Fixed: Fatal error: Call to a member function getVar() on a non-object in /html/Mysite/modules/spammer/plug-ins/comments.php-line 57 (grosdunord)
This was due to anonymous posting being allowed and $GLOBALS['xoopsUser'] would not be an Object.
Fixed: Spammer was using the IP address of the spammer instead of the spammers Referrer url.
Changed: The title was not being checked for spam, now both title and body will be checked for spam.
Changed: Moved much of the plug-in code into the spammer class, and made it easier to create plug-ins (less confusing)
Added: The ability to add extra search params whilst doing a spam check. If any of these extra words are found, then this would trigger a spam alert.
Added: Spammer will not check for a valid key before submitting to the akisment severs. Spammer will fail if no valid key is found.
Added: Added the ability to log each spam post, users can view who which users are spamming their websites.

Known bug: There seems to be some bottlenecking when displaying in the admin area when there shouldn't be. I am looking into this.
Todo: Add the ability to ban users who spam frequently.
Todo: Add an about us page in the admin area.
Todo: Add Help documents.

Description:

Spammer is exactly the opposite of what its name suggests. Spammer is an Anti-Spam module that helps fight against Spam using the Akismet API. Akismet FAQ.

Spammer requires a key to function correctly. You can create one from this website.

Commercial website wishing to use this service must buy a license.

How does Spammer work?

Spammer checks each post against the Akismet database to see if a post has elements of spam contained within the content. Spammer can deal with this spam in a number of ways.

1. Ignore it and let it bybass.
2. Delete it.
3. Mark the post as spam.
4. Mark the post for moderation.
5. Mark the post for moderation and mark it as spam.

(4+5) will probably be combined in a future release.

Spammer requires no hacks to the system at any level. You just install the module and it should work. This is possible through using the pre-loader system and plug-ins.

So far, Only a comments plug-in has been created, but this can easily be developed to include many other modules very easily. Please let me know which modules you believe should its own plug-ins.

As this module is only Alpha, it is only for testing but should work correctly with the comments system. (Famous last words).

What is not working yet
1. The logging system: This will be in the next release of Spammer.
2. Email to Administrators: as above.

New Features for next version
1. Plug-ins for the following modules: News and NewBB/CBB.
2. Ban users by IP.
3. Set a posting limit by IP
4. Add this is not Spam/Ham. Not sure how to go about this yet.
5. New Name for Spammer, I don't like this one, so your welcome to suggest a new one.

Download the alpha from: Here.

Please use this forum for feedback, bugs and features

ATB

Catz

Module: Spammer v.1.00 Alpha
Xoops: v2.45
PHP: V5+

**WARNING ALPHA VERSION**

Description:

Spammer is exactly the opposite of what its name suggests. Spammer is an Anti-Spam module that helps fight against Spam using the Akismet API. Akismet FAQ.

Spammer requires a key to function correctly. You can create one from this website.

Commercial website wishing to use this service must buy a license.

How does Spammer work?

Spammer checks each post against the Akismet database to see if a post has elements of spam contained within the content. Spammer can deal with this spam in a number of ways.

1. Ignore it and let it bybass.
2. Delete it.
3. Mark the post as spam.
4. Mark the post for moderation.
5. Mark the post for moderation and mark it as spam.

(4+5) will probably be combined in a future release.

Spammer requires no hacks to the system at any level. You just install the module and it should work. This is possible through using the pre-loader system and plug-ins.

So far, Only a comments plug-in has been created, but this can easily be developed to include many other modules very easily. Please let me know which modules you believe should its own plug-ins.

As this module is only Alpha, it is only for testing but should work correctly with the comments system. (Famous last words).

What is not working yet
1. The logging system: This will be in the next release of Spammer.
2. Email to Administrators: as above.

New Features for next version
1. Plug-ins for the following modules: News and NewBB/CBB.
2. Ban users by IP.
3. Set a posting limit by IP
4. Add this is not Spam/Ham. Not sure how to go about this yet.
5. New Name for Spammer, I don't like this one, so your welcome to suggest a new one.

Download the alpha from: Here.

Please use this forum for feedback, bugs and features

ATB

Catz

Upload all your files again to the server, seems you might have some that either didn't upload or got corrupted during the upload.

My Advice to you all that would even dare to use an alpha on a production site, is this.... ROLL BACK TO A STABLE VERSION OF XOOPS! Or wait till it is more a late RC (if you HAVE to use a non production version).

If you are going to test this then fine, do so on a test server and report bugs that you have found while testing and help Xoops in the long run.

I never ever give any help to anyone using my modules on a live site, because that is not the purpose of an Alpha version.

Go back to 2.45 until 2.5 is ready.

I fear this will lead to more problem in the long run.

I really do not understand this approach when this should have been handled by the template class? Really, xoTheme should check whether or not the file has been added before and take the required steps to prevent compatibility issue.

Instead we create another file and class to do this and thus instead of making the process simple we begin to complicate the issue further.

Doing this is simple:
$xoTheme->addScript('somescript.js');

Doing this begins to create problems:

$xoTheme->addScript('browse.php?Frameworks/jquery/jquery.js');

Why? Because we could have easily did a check to see whether the javascript was 'JQuery.js' and used the correct version from xoTheme or template class and this way compatibility wouldn't have been affected in the short or long run.

Or better still:

$xoTheme->addJQuery();
$xoTheme->addJQueryUI();

Again we complicate things when there is no need to.

Hiya Xoopers,

One thing is clear, Xoops is clearly lacking with the ability to use OpenID and Facebook (google/yahoo etc) for login and I believe that this could easily be added to Xoops using Xoops native login (with a few minor core changes I guess).

Mainly, Xoops uses a class that could easily be extended to add new features like this and it shouldn't be that big a problem coding this once I get enough information on the subject.

Now the problem is that while I could easily code the required changes, I am not an expert in this field, but I am willing to learn and 'I need help' (lol like I haven't heard that before).

I am looking for others who have a better understanding and knowledge that could work with me to help create this for Xoops.

If you think you can help, please PM me with your expertise and how you would like to help.

I would also like to know which API's for openID would be best used etc etc.

Many thanks,

Catz