11
peterr
XPressMe 2.3.9 and putting it together
  • 2011/4/2 6:15

  • peterr

  • Just can't stay away

  • Posts: 518

  • Since: 2004/8/5 9


Hi,

I have been reading and following the documentation How To module Making and Install(en) | XPressME Integration Kit

Have done the following locally ..

1. Downloaded version 2.3.9 and Wordpress 3.1

2. Made up a folder called (say) 'wordpress' , that will be /modules/wordpress

3. Copied the paths and files as per steps 1, 2 and 3 of "Making XPressME module for XOOPS" , so that they all 'sit' under /modules/wordpress/ path

Now to a part that nearly makes sense but not quite.

The words under the 'Localaize' section (should be 'Localize or Localise' )

Quote:

If the language & wp-config.php file that you need exists in the extras/xpress_i18n folder
The file and the folder in extras/xpress_i18n/en(or other)/xpressme_modules_root are overwrited to the route of the module.


If I unzip the ZIP file and go to this path
XPressME_Integration_Kit_Ver2.3.9/extras/xpress_i18n/en

there is only the following

howto_make_xpressme.html
xpressme_modules_root
---language
---wp-config.php
---wp-content

Both language and wp-content paths are empty

I thought possibly I have downloaded the wrong ZIP file, but there seems to be only one - http://ja.xpressme.info/wp-content/pl ... nitor/download.php?id=105

I'm hoping I don't have to make a localised english set of files and folder, like that described at http://ja.xpressme.info/codex/english/howto-make-localize-files/

Peter



12
peterr
Re: WF-Links or any Links Module??
  • 2011/4/2 4:32

  • peterr

  • Just can't stay away

  • Posts: 518

  • Since: 2004/8/5 9


Quote:

Mamba wrote:
Maybe you can work with him as his Beta tester?


Yes, okay. I notice that XOOPS use mylinks, and I was going to d/load from Sourceforge , but I'm a little confused at to what version to use, as the file size on the SEO version is the largest ??

Anyway, all that aside, I would definitely prefer to be using the latest and greatest (and I see that 'McDonald' is geared more for the XOOPS Impression with the wf-links module, rather than XOOPS core), so I will leave the links side of things to this new version, and help test it for zyspec

Peter



13
peterr
Re: WF-Links or any Links Module??
  • 2011/4/2 1:13

  • peterr

  • Just can't stay away

  • Posts: 518

  • Since: 2004/8/5 9


Running version 1.08 by Catwolf.

Various bugs ..

1. Country does not display correctly, it is shown as Country: <{$wfllink.countryname}>

2. Pagerank is displayed as

PageRank™:
<{$smarty.const._MD_WDFL_PAGERANKALT}>
<{$wfllink.pagerank}>(/10)

Also, the other link modules, like mylinks and weblinks don't look like they are supported anymore, no updates for quite a while.

I don't like the public being able to view the submitter and publisher in wf-links, as the username can be seen, which is, for a site that only has 'admin/webmaster', a security risk.

Not really impressed with any of the link modules for XOOPS, there seems to be only 3, weblinks, mylinks and wf-links.

Peter



14
peterr
Re: Sourceforge 2.2 modules downloads - script problem ?
  • 2011/3/30 6:32

  • peterr

  • Just can't stay away

  • Posts: 518

  • Since: 2004/8/5 9


Firefox version is 3.6.16 on Ubuntu 64-bit 10.04 LTS

I may try it with Seamonkey or similar.

Thanks,

Peter



15
peterr
Sourceforge 2.2 modules downloads - script problem ?
  • 2011/3/30 6:20

  • peterr

  • Just can't stay away

  • Posts: 518

  • Since: 2004/8/5 9


Hi,

I didn't know where to post this ??

I am getting a message "unresponsive script" from Sourceforge, the firefox msg is "A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

Script: http://a.fsdn.com/con/js/min.js?1301419720:23"

It locks firefox, all sessions. It always gets "stuck" waiting for something from http://b.scorecardresearch.com

The url is http://sourceforge.net/projects/xoops ... dule%20Repository/XOOPS2/

Peter



16
peterr
Re: Protector - error messages
  • 2011/3/30 6:05

  • peterr

  • Just can't stay away

  • Posts: 518

  • Since: 2004/8/5 9


Hi Mamba,

I'd be hesitant to do those 4 steps, as XOOPS is running just fine. I only have the core XOOPS installed, plus installed Protector from the core. Have added/installed xreaggregator which is running okay (except a 404 there, minor).

I can actually 'do' everything okay in XOOPS, no problems, just that the server logs are filling up with 404's from Protector. :)

I did the install as XOOPS wanted it, that is, when any path had the wrong perms, I corrected it until it was okay, then proceeded.

I just logged in via SFTP and the permissions on /home/username/secretpathname/ directory are 755 , so that is okay.

I'm thinking that either ..

(i) Protector is doing this in other sites, and people don't take any notice of 404's

OR

(ii) Protector can handle ..

/home/username/public_html
/home/username/renamed_xoops_data
/home/username/renamed_xoops_lib

BUT (maybe) not ..

/home/username/public_html
/home/username/secretpathname/
/home/username/secretpathname/renamed_xoops_data
/home/username/secretpathname/renamed_xoops_lib

Although the path names are resolved just fine in mainfile.php

Thanks,

Peter



17
peterr
Protector - error messages
  • 2011/3/30 5:38

  • peterr

  • Just can't stay away

  • Posts: 518

  • Since: 2004/8/5 9


Running a freshly installed XOOPS 2.5.0 , and have installed Protector from the system / modules part of XOOPS.

Continuing to get these error messages ..

404 - /public_html/modules/protector/css
referer: http://example.com/modules/protector/admin/index.php?page=advisory

404 - /public_html/XOOPS_TRUST_PATH
referer: http://example.com/modules/protector/admin/index.php?page=advisory

As Protector comes "with" XOOPS 2.5.0 , I am reporting this as an XOOPS core bug. Some info ..

I have this structure ..

/home/username/
/home/username/public_html
/home/username/secretpathname/
/home/username/secretpathname/renamed_xoops_data
/home/username/secretpathname/renamed_xoops_lib

Here is the mainfile.php ...

// XOOPS Physical Paths

    // Physical path to the XOOPS documents (served) directory WITHOUT trailing slash

    
define('XOOPS_ROOT_PATH''/home/username/public_html');

    
// For forward compatibility

    // Physical path to the XOOPS library directory WITHOUT trailing slash

    
define('XOOPS_PATH''/home/username/secretpathname/renamed_xoops_lib');

    
// Physical path to the XOOPS datafiles (writable) directory WITHOUT trailing slash

    
define('XOOPS_VAR_PATH''/home/username/secretpathname/renamed_xoops_data');

    
// Alias of XOOPS_PATH, for compatibility, temporary solution

    
define("XOOPS_TRUST_PATH"XOOPS_PATH);

    
// URL Association for SSL and Protocol Compatibility

    
$http 'http://';

    if (!empty(
$_SERVER['HTTPS'])) {

        
$http = ($_SERVER['HTTPS']=='on') ? 'https://' 'http://';

    }

    
define('XOOPS_PROT'$http);

    
// XOOPS Virtual Path (URL)

    // Virtual path to your main XOOPS directory WITHOUT trailing slash

    // Example: define('XOOPS_URL', 'http://example.com');

    
define('XOOPS_URL''http://example.com');


When I look at admin | protector , it seems the paths are looking okay. For example, where you define IP's to ban, it has the full pathname correctly.

The 'security advisor' TAB in protector has a link up the top which says "Check php files inside TRUST_PATH are private (it must be 404,403 or 500 error" , and that link is resolved incorrectly. It has resolved to http://example.com/secretpathname/ren ... rotector/public_check.php , which is wrong, it should be /home/username/secretpathname/renamed_xoops_lib/modules/protector/public_check.php

Thanks,

Peter



18
peterr
Re: Various modules - 404's
  • 2011/3/29 6:47

  • peterr

  • Just can't stay away

  • Posts: 518

  • Since: 2004/8/5 9


I have this structure ..

/home/username/
/home/username/public_html
/home/username/secretpathname/
/home/username/secretpathname/renamed_xoops_data
/home/username/secretpathname/renamed_xoops_lib

Quote:

Mamba wrote:

Maybe there is a mistake in your mainfile.php?


Here is the mainfile.php , with obvious security changes ..

// XOOPS Physical Paths

    // Physical path to the XOOPS documents (served) directory WITHOUT trailing slash

    
define('XOOPS_ROOT_PATH''/home/username/public_html');


    
// For forward compatibility

    // Physical path to the XOOPS library directory WITHOUT trailing slash

    
define('XOOPS_PATH''/home/username/secretpathname/renamed_xoops_lib');

    
// Physical path to the XOOPS datafiles (writable) directory WITHOUT trailing slash

    
define('XOOPS_VAR_PATH''/home/username/secretpathname/renamed_xoops_data');

    
// Alias of XOOPS_PATH, for compatibility, temporary solution

    
define("XOOPS_TRUST_PATH"XOOPS_PATH);


    
// URL Association for SSL and Protocol Compatibility

    
$http 'http://';

    if (!empty(
$_SERVER['HTTPS'])) {

        
$http = ($_SERVER['HTTPS']=='on') ? 'https://' 'http://';

    }

    
define('XOOPS_PROT'$http);


    
// XOOPS Virtual Path (URL)

    // Virtual path to your main XOOPS directory WITHOUT trailing slash

    // Example: define('XOOPS_URL', 'http://example.com');

    
define('XOOPS_URL''http://example.com');


Quote:

Mamba wrote:
Did you just upgrade your Website to 2.5.0?


I removed everything, and did a fresh install of 2.5.0; had to wipe as couldn't login to XOOPS for ages.

Quote:

Mamba wrote:
Maybe you need to clear the Cache?


Under System | Prefs | General Settings , there are 3 cache settings down the bottom, and they are all 'no cache'.

Quote:

Mamba wrote:
And check if the Protector files are in the right places?


When I look at admin | protector , it seems the paths are looking okay. For example, where you define IP's to ban, it has the full pathname correctly.

The 'security advisor' TAB in protector has a link up the top which says "Check php files inside TRUST_PATH are private (it must be 404,403 or 500 error" , and that link is resolved incorrectly. It has resolved to http://example.com/secretpathname/ren ... rotector/public_check.php , which is wrong, it should be /home/username/secretpathname/renamed_xoops_lib/modules/protector/public_check.php

Thanks,

Peter



19
peterr
Various modules - 404's
  • 2011/3/29 3:02

  • peterr

  • Just can't stay away

  • Posts: 518

  • Since: 2004/8/5 9


Using XOOPS 2.5.0

Module - xreaggregator

404 - /public_html/modules/xreaggregator/images/bg.gif
Many referers

Module - Protector

404 - /public_html/modules/protector/css
referer: http://example.com/modules/protector/admin/index.php?page=advisory

404 - /public_html/XOOPS_TRUST_PATH
referer: http://example.com/modules/protector/admin/index.php?page=advisory

In the last one, Protector is looking in the wrong place, as the XOOPS_TRUST_PATH is outside of the web root, not inside.

Peter



20
peterr
Re: Module advice needed please
  • 2011/3/29 1:37

  • peterr

  • Just can't stay away

  • Posts: 518

  • Since: 2004/8/5 9


What about the module 'X-Re-aggregator' instead of XHLD ? I tried the demo, seems what I need, and XHLD and D3pipes are messy to install.

I see there are .htaccess mods for 'X-Re-aggregator' ; hopefully I don't need those, they are just SEO purposes I think, which doesn't interest me.

Peter




TopTop
« 1 (2) 3 4 5 ... 49 »



Login

Who's Online

78 user(s) are online (47 user(s) are browsing Support Forums)


Members: 0


Guests: 78


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Jul 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits