Support Forums - All Posts - XOOPS Web Application System

5721

@fixed::- xoops_getBaseDomain() -- Suggested Ammendment by Geek Write!! you know you do scribe code!

2015/6/9 6:07
wishcraft
Module Developer
Posts: 3711
Since: 2007/5/18

You know what i think would be best is make a folder in xoops_data/apis for .txt lists for whois lookups etc, for those apis then you can simply to find a working one in the route do the following:-

 $stratas = file(XOOPS_VAR_PATH . DIRECTORY_SEPARATOR . 'apis' .  . DIRECTORY_SEPARATOR . 'strata.txt'); 
shuffle($stratas) 
 
// Then foreach($stratas as $strata) -- so you don't opped any main one for load balancing 
 
//then in the foreach loop you:-- 
 
if(!empty($G_TLD))  
    continue; 
 
//and it will drop out and continue; this is a multileveled command!

Richard: is it peers.example.com for an API that lists API peers... If you want to look up the lists as well

If you want to quickly make a peers apis for the http://sourceforge.net/projects/chronolabsapis -- just make it so it does a 3/5 point check of data integrity that leavers as a 'trust' level..

Cause then we can have the API announce themselves and self audit with a cron that multiple peers.xoops.org ie. peers.labs.coop that go around spot checking the simulcasting.

Just leave the fonts one, today I bought a new intel 64bit computer and will be picking it up and putting releases.ubuntu.com on in a few days and fonts.labs.coop -- will be changing dramatically to version 2.0..

5722

@fixed::- xoops_getBaseDomain() -- required for multitiered cookies!

2015/6/9 5:54
wishcraft
Module Developer
Posts: 3711
Since: 2007/5/18

 /** 
     * Function to get the base domain name from a URL. 
     * credit for this function should goto Phosphorus and Lime, it is released under LGPL. 
     * 
     * @param string $url the URL to be stripped. 
     * @return string 
     * @fixed 
     */ 
    function xoops_getBaseDomain($url, $debug = 0) 
    { 
        xoops_load("XoopsCache"); 
        $base_domain = ''; 
        $url = strtolower($url); 
         
        if ($G_TLD = XoopsCache::read('dms_realms_list')) 
        { 
            $G_TLD = array_keys(unserialize(file_get_contents("http://strata.labs.coop/v1/strata/serial.api"))); 
            if (empty($G_TLD)) 
                $G_TLD = array_keys(unserialize(file_get_contents("https://strata.ringwould.com.au/v1/strata/serial.api"))); 
                if (empty($G_TLD)) 
                    $G_TLD = array_keys(unserialize(file_get_contents("http://strata.ringwould.com.au/v1/strata/serial.api"))); 
            XoopsCache::write('dms_realms_list', $G_TLD, 3600*24*mt(3.75,11)); 
        } 
        if ($C_TLD = XoopsCache::read('fallout_realms_list')) 
        { 
                $C_TLD = array_keys(unserialize(file_get_contents("http://strata.labs.coop/v1/fallout/serial.api"))); 
                if (empty($C_TLD)) 
                    $C_TLD = array_keys(unserialize(file_get_contents("https://strata.ringwould.com.au/v1/fallout/serial.api"))); 
                    if (empty($C_TLD)) 
                        $C_TLD = array_keys(unserialize(file_get_contents("http://strata.ringwould.com.au/v1/fallout/serial.api"))); 
                XoopsCache::read('fallout_realms_list', $C_TLD, 3600*24*mt(3.75,11)); 
        } 
     
        // get domain 
        if (!$full_domain = signed_getUrlDomain($url)) { 
            return $base_domain; 
        } 
     
        // break up domain, reverse 
        $DOMAIN = explode('.', $full_domain); 
        $DOMAIN = array_reverse($DOMAIN); 
        // first check for ip address 
        if (count($DOMAIN) == 4 && is_numeric($DOMAIN[0]) && is_numeric($DOMAIN[3])) { 
            return $full_domain; 
        } 
        // if only 2 domain parts, that must be our domain 
        if (count($DOMAIN) <= 2) { 
            return $full_domain; 
        } 
     
        /* 
         finally, with 3+ domain parts: obviously D0 is tld now, 
        if D0 = ctld and D1 = gtld, we might have something like com.uk so, 
        if D0 = ctld && D1 = gtld && D2 != 'www', domain = D2.D1.D0 else if D0 = ctld && D1 = gtld && D2 == 'www', 
        domain = D1.D0 else domain = D1.D0 - these rules are simplified below. 
        */ 
        if (in_array($DOMAIN[0], $C_TLD) && in_array($DOMAIN[1], $G_TLD) && $DOMAIN[2] != 'www') { 
            $full_domain = $DOMAIN[2] . '.' . $DOMAIN[1] . '.' . $DOMAIN[0]; 
        } else { 
            $full_domain = $DOMAIN[1] . '.' . $DOMAIN[0]; 
        } 
        // did we succeed? 
        return $full_domain; 
    }

This is the working copy of which polls several places on the API to have the complete list of Realms, Domains, TLDs and gTLDs as well as what normally goes on the end the fallout!!

5723

TDMCreate 1.91 testing with Codeception

2015/6/8 7:49
timgno
Module Developer
Posts: 1504
Since: 2007/6/21

@goffy hi -> (Thanks for tests)

Some things I had already tested myself and the other fixed I'm doing now to those who have shown anyway thanks for the help is always important hand.
I'm not sending other release because I want to complete the first part of the template style bootstrap and do further testing.

There is one thing I want to know!

"The code and the classes of this new module are good enough, or have some limit?"

Why do I sometimes encounter difficulties to create another code, but unfortunately the time to rewrite is limited.

Meanwhile, I found a bug that seems to belong also to the core.
I mentioned that by clicking on the link Go to Module in admin and the main menu there is a carriage return, was due to the index.html file of the home module.

Deleting it all only works for some modules for others while deleting the links do not work equally at home module

@To Others Users

This is an importat module to create others modules in xoops.

5724

Re: SourceForge hijacks inactive popular software accounts and adds bundleware

2015/6/6 23:30
Mamba
Moderator
Posts: 11373
Since: 2004/4/23

1) It looks like somebody made some very bad decisions at SourceForge

2) SourceForge was good to us for almost 15 years now, and as everybody else, they should get a chance to fix these issues.

3) Our active new development is happening right now on GitHub, so this doesn't effect us much, anyway.

4) However, we'll be monitoring the situation to see if there are other steps required.

Please note: all our themes listed on XOOPS have been recently uploaded to GitHub, so you can fork and improve them there

:

a) old archive, for XOOPS < 2.01.14 (753 themes) - probably won't work with current XOOPS version, but might be used as inspiration, if you find interesting ideas there

b) for XOOPS 2.0.14+ (1/2 columns) (197 themes) - most of them should be compatible with current XOOPS

c) for XOOPS 2.0.14+ (3 columns) (674 themes) - most of them should be compatible with current XOOPS

d) Current themes (especially based on xBootstrap), but this will need to be updated, as many recent themes are missing there.

Any volunteers to help us with updating the Current themes?

Support XOOPS => DONATE
Use 2.5.10 | Docs | Modules | Bugs

5725

Re: SourceForge hijacks inactive popular software accounts and adds bundleware

2015/6/6 17:10
JulioNC
Quite a regular
Posts: 239
Since: 2004/10/8

Tmux has left SourceForge

https://news.ycombinator.com/item?id=9657271

5726

Re: Upgrading Xoops 2.5.6 > 2.5.7.1

2015/6/6 12:20
Cesagonchu
Moderator
Posts: 892
Since: 2010/2/1 2

Most recent guide is here:
https://xoops.org/modules/news/article.php?storyid=6658

Quote:

Upgrading from 2.5.6 to 2.5.7 Final:

1. Get the right update package from the sourceforge file repository
2. Overwrite files in XOOPS directory on your server with the content of /htdocs
* make sure that you copy the content of /xoops_lib to whatever directory you keep it on the server now (it should be your current XOOPS_TRUST_PATH directory), then delete the /xoops_lib directory. There can NOT be two directories with the content of /xoops_lib
3. Go to http://www.yoursite.com/upgrade and run the Upgrade from there. Once done, delete the folder /upgrade
4. If not done as part of the Upgrade above, run Update af the the "System" module from the modules administration interface. Other modules, especially "Profile", "PM", and "Protector" are recommended to update as well

Upgrading from previous versions older than 2.5.6 (Full Update):

0. Verify the system requirements, in particular the version of PHP. Backup your XOOPS database and site directory. (There are several ways to do these actions, which are discussed elsewhere.) Turning your site off is optional.
Change the permissions on mainfile.php and /include/license.php to be writable, for example:
File Normal For upgrade
mainfile.php 400 700
/include/license.php 444 777
Get the XOOPS 2.5.7 package from the SourceForge file repository.
1. In the upgrade package folder, move the "upgrade" folder inside the "htdocs" folder, if it's not already there. Remove the install folder from the "htdocs" folder, if it's there. Remove the mainfile.php file from the "htdocs" folder, if it's there.
If you've moved the xoops_data and xoops_lib folders outside your site's root directory, move these folders out of the "htdocs" folder in the upgrade package folder.
2. Delete the /modules/system directory on your current XOOPS site (to get rid of any old unnecessary files).
3. Overwrite the files in the XOOPS directory on your current XOOPS site with the content of "htdocs" folder of the upgrade package. (There are several ways to do this action, which are discussed elsewhere.)
As noted above, if relocated, overwrite the files in your current xoops_data and xoops_lib with the content of those in the upgrade package.
4. If you have Protector previously installed, open the "mainfile.php" file , and remove the Pre-check and Post-check lines (if they exist):
include XOOPS_TRUST_PATH.'/modules/protector/include/precheck.inc.php' ;
include XOOPS_TRUST_PATH.'/modules/protector/include/postcheck.inc.php' ;
5. At your site's address (URL), login as administrator. Access /upgrade/ with a browser, and follow the instructions (and any for updating your XOOPS database). After all updates have been applied (green checkmarks), note the link in the Updater to update the "system" module, and do so.
6. Delete the "upgrade" folder from your site's "htdocs" directory.
7. Update (reload) other modules, especially "Profile", "PM", and "Protector," if necessary.
8. Change permissions on the files noted above back to their normal state.
9. Turn your site back on, if you turned it off earlier.

Debug information display level
-----------------------------------

Since XOOPS 2.3.1 debug information display level is enabled to show debug information to different level of users: to all users, to members or to admins only.
The configuration can be set in /xoops_data/configs/xoopsconfig.php
As a default, the display level is set for 2 (Admin only).

Files integrity check
-----------------------------------

The full XOOPS package is released with a script able to check if all the system files have been correctly uploaded to the server. To use it, follow these instructions:

1. Upload the checksum.php and checksum.md5 files located in the XOOPS package root to your XOOPS server folder (putting them next to mainfile.php).
2. Execute checksum.php with your browser
3. If necessary, re-upload the missing or corrupted system files
4. Remove checksum.php and checksum.md5 from your server

Modules
-----------------------------------

This release contains only the "system-related modules". You are invited to browse the XOOPS modules repository to if you need additional functionality. Note: as a new repository is being built, the current repository is not up-to-date, PLEASE VISIT INDIVIDUAL DEVELOPERS' WEBSITES TO MAKE SURE YOU ARE USING LATEST VERSION OF MODULES.

2.5.7.1 is Xoops 2.5.7 with security patch.

5727

SourceForge hijacks inactive popular software accounts and adds bundleware

2015/6/5 18:22
xoobaru
Just can't stay away
Posts: 494
Since: 2010/12/2

The related article.

5728

Re: Alumni version 3.1 ALPHA for Xoops 2.6.0 ALPHA from GitHub

2015/6/5 13:55
xoobaru
Just can't stay away
Posts: 494
Since: 2010/12/2

If you want to appreciate how big it really is, take a look here.

5729

Re: Alumni version 3.1 ALPHA for Xoops 2.6.0 ALPHA from GitHub

2015/6/5 6:36
Mamba
Moderator
Posts: 11373
Since: 2004/4/23

John, few points about GitHub and XOOPS using it:

Quote:

I will keep my modules on my server, I did not want to have to open a github account, but it seems You have to, to install Xoops Now. Which I think is very wrong.

you don't have to have account on GitHub to download XOOPS or any of the modules from there.
For example, you can go right now to our XOOPS link:
https://github.com/XOOPS/XoopsCore
and click on the "Download Zip" and download it.

Quote:

Since when did the meaning of the word fork change? To me fork will ALWAYS mean taking the software and creating your own thing out of it. Like ICMS is a fork of Xoops. Who ever changed the meaning of that word was wrong to do so.

There are forks and there are forks!

a) "split forks" that just go separate ways never to merge

b) "version control forks" that are done to add a feature or fix a bug, and once tested, they are submitted to be merged back into the "trunk". This helps to keep the "trunk" clean and working, while allowing many people to collaborate on the development without stepping on each other toes. It is a tremendous help in team development and that's why we've seen such an explosion in people using Git in general, and GitHub in particular.

I can only encourage you to open an account and start using it by creating a repository for Alumni, to which we all can then contribute. Once you start using it, you'll wonder how you could ever live without it!

For example, in case of Alumni, this the original code from you on GitHub. This is the fork on GitHub I did. There I can make changes and I can submit them to you for merging via a "Pull Request".

If you click on the "10 commits" on top, GitHub will show you the changes that I've made.

Then you can see the individual changes, and you can click on them, and you can see exactly what has changed, for example here.

And if this was a part of a "Pull request", you could just review these changes and accept them, and you're done. As the "owner" of the repository, you'll be able to decide what will be accepted and what will be rejected. So there is no risk in getting "polluted" with code of questionable quality.

Let's face it - for collaborative development as XOOPS is, there is nothing better at the moment.

Of course, for people who like to develop by themselves, this won't be of interest.

As a side benefit, there are TONS of tools that are linked to GitHub that make development so much easier, and improve quality as well as team work.

For example, for quality, I can run the code through a static code analyzer and see the results and if they make sense, make the changes to the code. You can see result for Alumni here:

SenisoLabsInsight

CodeClimate

Codacy

Scrutinizer

All of these tools take the code from GitHub.

I can only encourage you to give it a try, and I promise you - once you do, you'll never look back!

Support XOOPS => DONATE
Use 2.5.10 | Docs | Modules | Bugs

5730

Re: TDMCreate 1.91 alpha 1 for Testing

2015/6/4 17:50
goffy
Just can't stay away
Posts: 535
Since: 2010/12/27

yes, http://wettklettern.eu and http://mtbrace.eu have been created with this tool

Stats
Goal:	$100.00
Due Date:	Jul 31
Gross Amount:	$0.00
Net Balance:	$0.00
Left to go:	$100.00

Forum Index

@fixed::- xoops_getBaseDomain() -- Suggested Ammendment by Geek Write!! you know you do scribe code!

@fixed::- xoops_getBaseDomain() -- required for multitiered cookies!

TDMCreate 1.91 testing with Codeception

Re: SourceForge hijacks inactive popular software accounts and adds bundleware

Re: SourceForge hijacks inactive popular software accounts and adds bundleware

Re: Upgrading Xoops 2.5.6 > 2.5.7.1

SourceForge hijacks inactive popular software accounts and adds bundleware

Re: Alumni version 3.1 ALPHA for Xoops 2.6.0 ALPHA from GitHub

Re: Alumni version 3.1 ALPHA for Xoops 2.6.0 ALPHA from GitHub

Re: TDMCreate 1.91 alpha 1 for Testing

Login

Search

Recent Posts

PHP 8.4.0 Alpha 1 released

Overview of the Composer packages in Admin

Re: xoops_getBaseDomain

xoops_getBaseDomain

Re: Test 3

Test 3

Re: Test2

Re: Test2

Re: Test2

Test2

Who's Online

Donat-O-Meter

Latest GitHub Commits

{{ record.sha.slice(0, 7) }} - {{ record.commit.message | truncate }}