XOOPS Web Application System

A new HTML 5 and Responsive Theme for XOOPS!

Sun, 17 Mar 2013 04:00:00 -2300

Car Owners Manuals

Sat, 16 Mar 2013 20:19:26 -2300

Common Utilities RC and xThemes RC available

Tue, 12 Mar 2013 02:16:22 -2300

Sports Pack (Football/Soccer, Cricket, Darts) converted to XOOPS 2.5.5 Admin GUI

Sun, 10 Mar 2013 07:50:00 -2300

French Website for Mountain Biking powered by XOOPS

Sun, 10 Mar 2013 06:20:00 -2300

MyLinks 3.11 RC2 Ready for Testing

Thu, 07 Mar 2013 08:10:00 -2300

This is an RC release, please do not use it on a production site!

Mylinks is a XOOPS module that allows an administrator to create a series of website links. The module provides the ability for other users to submit sites for inclusion in the list which can be monitored by the administrator and then approved if desired.

Features:

Category support to put links into a logical order

Uses XOOPS search to search the title and description

Can screen shots stored locally or automatically create them using a 3rd party service

Create QrCodes for links (requires QrCode module)

Create link PDF

Print link Information

Tell-A-Friend feature to email information about a link to someone else (uses XOOPS Captcha)

Users can rate links

Links can be bookmarked using various 3rd party services

RSS / ATOM feeds

Flexible display of page headers, menus, etc

XOOPS blocks - Display random link, most recent links, Display most popular links

Supports usage of XOOPS Comment and Notification systems

User can report broken links

User can submit link for inclusion in the list

Code changes since v3.11 RC:

Added:

added templates to xoopsversion for rss, atom and pda templates

added missing files for template administration

Corrected:

addSlashes issue for a link's description and title

link count per category calculation routine

frontside admin link to modify a link (from ./admin/index.php to .admin/main.php)

do not allow voting on inactive links

approve/edit/ignore action buttons on listModReq form(s) in Admin panel

form title on Modified Links page in Admin panel

missing '< / div >' in ./templates/mylinks_link.html

incorrect url to view category in Random Link block

incorrect category displayed when listing Modified Links in Admin panel

Removed:

admin templates from xoopsversion. They did not exist and were not being used

"Make this my Homepage" link, security risk and was only supported in IE

Improved:

html template(s)

html rendering by moving hard coded English strings to language file(s)

security in forms - many forms now use XoopsSecurity tokens

Changed:

Tell-A-Friend to use server mailer form instead of user's email client

ereg_replace to str_replace in bookmark_qrcode_encoding() function

revision to RC2

System Requirements:

PHP 5.2.0

MySQL 5.0.7

XOOPS 2.5.0

Modulesadmin Class 1.1

Special appreciation to Cifug for his assistance in testing and invaluable suggestions for this release. Without his help the time it would have taken to get this release ready would have been increased significantly.

Important Notices:
Please read the INSTALL.TXT file for installation and configuration information. Mylinks 3.11 will be the last release supporting folder relocation.

Backup your existing site before installing/upgrading any new XOOPS module.

Download: XOOPS Mylinks 3.11 RC2

Bugs/Feedback: Please post in this thread on our Forums

XOOPS Module Packs Overview- Draft 1

Tue, 05 Mar 2013 11:20:00 -2300

Tutorial: How to update tables to follow XOOPS' new naming scheme?

Tue, 05 Mar 2013 04:20:00 -2300

As you might already know, there is an effort to standardize our module development - from using the same module Admin GUI structure, to using the same icons across all modules, from using the same pagination structure for each table, to naming the tables and fields in a consistent way (see this thread).

This tutorial will show you how to modify your module so it can rename the tables on the user site, when the user updates the module. This will follow the scheme suggested by alain01

The new table naming scheme is:

mod_AAA_BBBB

where AAA is the name of the module, and BBB is the name of the table.

For example, when we have in the News module a table called "topics", in the new updated version of News, it will become:

mod_news_topics

Here are few steps to follow, as used recently in the Pedigree module called "animal":

1) The new version should have the tables defined properly in the SQL file, so new installation have the right tables installed right away

2) In the existing installation the users normally copy files over, and then run "update" in the Admin. Therefore we'll need to add a file with the updates. We'll call it "update_function.php" and will place it in /include folder

3) In order for XOOPS to call this file, we'll add in xoops_version.php file following:


$modversion['onUpdate'] = 'include/update_function.php';

4) In that file, we start by adding a function to check if the table that we want to rename, does actually exist. This is done by using a function created by Hervet:


function tableExists($tablename)

{

    global $xoopsDB;

    $result=$xoopsDB->queryF("SHOW TABLES LIKE '$tablename'");

    return($xoopsDB->getRowsNum($result) > 0);

}

5) then we add a following function that will be executed when we click on the Update button:


function xoops_module_update_animal()

{

    global $xoopsDB;



    if (tableExists($xoopsDB->prefix('eigenaar'))) {

        $sql    = sprintf(

            'ALTER TABLE ' . $xoopsDB->prefix('eigenaar') . ' RENAME ' . $xoopsDB->prefix('mod_pedigree_owner')

        );

        $result = $xoopsDB->queryF($sql);

        if (!$result) {

            echo '<br />' . _AM_PED_UPGRADEFAILED . ' ' . _AM_PED_UPGRADEFAILED2;

            $errors++;

        }

    }

    return TRUE;

}

In this code above, we are checking if the "eigenaar" does exist, and if it does, then we're renaming it to "mod_pedigree_owner'". Of course, this is done for each table that we want to rename.

6) We also have to rename all occurrences of the tables in the code as well.

a) as a first step, it's easy to just run search & replace using as part of the search the word "prefiix", so in our example, we'll replace:

prefix("eigenaar")

with:

prefix("mod_pedigree_owner")

This is for cases where we call the tables in a conventional way.

b) But people are creative, and it might happen that they do it differently, so nothing will save us from testing, and eventually searching for the word "eigenaar" in all files, and then making a judgment call if it is meant as a table and therefore has to be renamed.

The new naming scheme will make it easier two things:

- to see in phpMyAdmin (or any other database tool) all the tables from a module grouped together. It will also distinguish them from the Core tables.

- in the code it will also make it easy to find the tables just by searching "mod_MODULENAME"

In the near future, we'll also consolidate names and characteristics of the typical fields in our modules, and provide them as guidelines.

When you look at our modules, the same field could be named differently in each module. Let's take "Group ID" - it could be: gid, g_id, group_id, gr_id, etc. And if you are trying to maintain a module from somebody else, we are wasting too much time trying to figure out what a particular field is actually for.

If you have improvements for this tutorial, please let us know.

And most importantly:

- If you can help us to streamline and standardize module development, we would very much appreciate it.

- If you like how a particular module does something and think that other modules should do the same, let us know.

- If you see something cool being done by other Open Source Projects that XOOPS could benefit from, please let us know too.

Please follow up in this thread

Xortify 4.01 (Cloud Client)

Tue, 05 Mar 2013 04:11:33 -2300

Xortify is a network security drone that uses Web 2.0 techniques to link between your XOOPS installs and other via a Server Cloud. This will prevent security intrusions to your xoops with accurate deceptive notation of the intruder and prevent any farmed attacks. It is an accessory and required Protector to be installed an running to be part of the hookup. Otherwise it will run without protector just make sure you deselect protector as a provider.

It will display a template if you are banned and is an accessory to protector or any other firewall technology. The site itself is driven from xortify.chronolabs.coop and mirrored at www.xortify.com .. Cloud computing is web 2.0/3.0 stuff it used a SOAP or JSON, XML or Serialisation to exchange on the API backend to work, this will eventually be included in xoops as a support class.

A cloud computing process is one which staggers multiple networks sometime and mainly unknown to the webmaster into a network or cloud of data. In this example it is IP and Netaddy names to control access lists.

This will prevent predators from exposing your network to lag and other attacks from link farming, often this means many xoops are attacked in occasions which is all the time caught by protector, this way if an attack is in process across a large spectrum of links, your site will down itself to your sourced attack even if it is discovered on a completely unaffiliated site that is link farmed to yours or on a XOOPS User list.

Xortify is a cloud solution to protectors Bad IPs, if someone attempts to hack your site and becomes a bad IP it will then send the IP to the Ban Cloud on Xortify.com and its paired cloud Xortify.chronolabs.coop. It will also poll the server to make sure it has the latest ban list so your website will be aware of malusers before they attack through farming IP from services like Google or bing.

Xortify is finally bug free, there was a lasting reminder of how it can be quiet frustrating developing software, especially cloud solutions with so many variables to hone to make sure the system is working, you should enjoy this version and any future releases for XOOPS 2.7, but as it stands I can't find anymore situations, warnings, notices or WSOD with this copy.

Download: https://code.google.com/p/chronolabs2/ ... .zip&can=2&q=#makechanges

Features
* Cloud Server List Propogation - Floating cloud
* Cache Maintenance Cleanup
* Better Ban List
* Better XOOPS 2.5 Module Class GUI
* Greater Ban Diagnostics
* CURL Resolution Timeout
* Fault Locking/Delay
* Performance Extras - fixed
* Cron Job State and Timing
* Pre PHP 5.2 Compatibility
* My IP Information Anti Ban Prevention
* Provider Plugins
* Admin Usage Log
* Protector Module Provider
* Project Honeypot Provider
* Stop Forum Spam Provider
* Spider Module Provide
* XML Polling Protocol
* Serialisation API Protocol
* JSON API Protocol
* SOAP API Protocol
* Anti Spamming with User Signupl
* Anti Harvesting
* Serialisation API Protocol

Installation

Download the lastest version from Chronolabs on Google code or off sourceforge. Unzip the archive you should have a folder called 'htdocs' in the unzipped location. Copy the contents of 'htdocs' folder to your CMS root path this is generally a folder called 'public_html' or 'www' on your FTP service of your website. Log into your CMS and goto the modules/applications installation section, this is generally in your system control area under modules. Click on the icon that represent installing the module. If all has behaved as need be then your module is installed. If your module requires a user licences, keys or a username then sign-up to the apprpriate sites and retreieve your keys or IDs (Links should be provided in the preferences) and paste the values into preferences. Now your right to go!

Upgrading

Download the lastest version from Chronolabs on Google code or off sourceforge. Unzip the archive you should have a folder called 'htdocs' in the unzipped location. Copy the contents of 'htdocs' folder to your CMS root path this is generally a folder called 'public_html' or 'www' on your FTP service of your website. Log into your CMS and goto the modules/applications installation section, this is generally in your system control area under modules. Click on the icon that represent upgrading the module. Your version number should no longer be in bold and would have changed!

Reporting a Bug

The google code section has an area for reporting bugs called issues. Any issue or bug you believe you are having that is not a result of your site services then please report it here. The URL for reporting bugs is as follows: code.google.com/p/chronolabs2/issues/entry

Please report the following:

Quote:

a) Version of CMS
b) Version of PHP
c) Version of MySQL
d) Services Software ie. Apache, Zeus etc.
e) Version of Software
f) Error Messages
g) Steps to reproduce
e) Contact details for the team to get in touch should they need!