I'm trying to upgrade the XOOPS wordpress module to WordPress 2.1. The module currently uses WP 2.05 which has security vunerabilities.

Followed all of the instructions in the modules readme.html for about upgrading. Backed everything up, deleted the old wp-related files, kept wp-config.php and the xoops-related files, and uploaded the new 2.1 files.

When I went to update the module in XOOPS module admin, I got this message:

Quote:

The XOOPS version of WP uses a different wp-config set up than WordPress' version. Databasename, host, username, etc are all drawn from XOOPS in the former. The latter requires you to fill the information in manually.

I took a chance and edited the required entries including the language set to "en."

Now I get:

Quote:

All of the latest extra files required are installed (Frameworks, the extra XOOPS22 files for users of XOOPS 2.2.4 and the necessary text editor folder).

The module appears in the module admin section.

The module does not appear in the Main Menu or in the Preferences section.

So, my questions are:

1. Is it possible to upgrade this module to the latest version of WordPress? It is according to the instructions given:

Quote:

2. Are the instructions complete? WP 2.1 has a drastically new architecture, but I experienced the same problems when I tried to update the XOOPS 2.04 and 2.05 versions to WP 2.07. But the instructions work the same even if you're upgrading a non-XOOPS version of WP.


XOOPS 2.2.4
Apache/1.3.33 (Unix)
PHP 4.4.4
MySQL 4.0.27

This is on a hosted server, so I have no control over the environment. The host is already planning upgrades, so there is no need for me to change to another host.

I can easily roll the 2.1 version back to XOOPS' 2.05 version, but I'd really like to have the latest version installed for a few reasons. The combination of WP and XOOPS makes a pretty formidable web site.

Any help would be appreciated.

gestroud

Anonymous users should be able to vote if the module's settings are correct. Which poll module are you using?

I've had all sorts of problems with VideoBB - never seems to work right.

You may want to take a look at this API. I just came across it. Trying to figure out how to integrate it directly into XOOPS without using iframes, but coding isn't my strong point.

I've heard that there may be a new version of the debaser module coming soon, but the developer is extremely busy with another project. It may be worth the wait.

gestroud

If you're running your site with the 2.0 version of XOOPS, you may want to look at

Jinzora or Zina. Both of them are supposed to be XOOPS compatible.

or....

If you're familiar with Shoutcast and the ShoutCast Server, you may want to set up the ShoutCast DSP and run your media from your home computer.

You'll need WinAmp and a couple of plugins. The second one is optional

1. Shoutcast DSP for winamp

2. Null Output Plugin (great for streaming music from your computer/server without having to listen to the output on your speakers.)

To get these working with your XOOPS site, take a look at

1. The Shoutcast Radio Module

or

2. The DJ Culex module

I have a stripped-down version of the first one installed on this site. Look for the Radio Station block in the right column.

gestroud

Here's a good one
http://www.avantnews.com/

You could try this modulehttps://xoops.org/modules/news/article.php?storyid=3272

or maybe this one

https://xoops.org/modules/news/article.php?storyid=2599 for XOOPS 2.0

https://xoops.org/modules/news/article.php?storyid=2595 for XOOPS 2.2

The is also a Userpage module for users to create their own pages.

You can do one of two things:

1. Go into your admin section and look for

Preferences-->System-->General Settings

Click General Settings

Look for "Update module template .html files from themes/your theme/templates directory?" and set it to yes.

Scroll down to the bottom of the page and Submit.

Be sure to go back and turn the option back to no after you've made your changes.

2. Go into Modules-->Administration

Update the system module.

Simplicity, like beauty, is in the eye of the beholder.

I mess up installing this module and editing mainfile.php 1 out of every 10 times I do it. I see a distinct possibility that the number is going to increase.

I pretty much understand the concept of creating a directory outside of public_html, but what happens when:

1. there are more than one sites involved on the server

2. the directory structure doesn't use public_html? For example, what if your FTP program shows the server structure is basically empty and the root is just /:

/
site1
site2
site3
etc...
log

also,

3. Should a separate directory be created with individual subdirectories for the respective /xoops_trust_paths for each site and the xoops_trust_path/modules/protector be uploaded there?

4. Should the existing modules from each site be moved to the new subdirectories to take advantage of the security feature?

Sorry for so many questions, I just don't want to mess this up any more than I usually do.

gestroud

I really don't think it's possible, katim, but I could be wrong.

You're talking about inserting javascript into a database-driven and -created table, which would most likely disrupt its structure.

There may be someone who could implement it for you, but it'll probably cost you some cash.