Greetings!

edit: Using Zina version zina-2.0b13-XOOPS-2.3.tar.gz

because 2.0b15 does not have a Xoops install.

I'm thinking I may need to chat with the Zina dev, but I thought I would post here too. I'm using Xoops 2.4.4, and would like to play MP3 files on the server. I have three issues with Zina.

1. Won't play MP3s on server (mpg123 issue)
2. mootools.js conflict?
3. No icons - just textlabels - is this right?

With regard to each, in detail:
1. to play MP3s on the server it appears that I need mpg123 or some other MP3 player installed by the site administrator. Is there an MP3 player available for integration in Xoops? I can probably talk admins into installing, but would rather handle myself.

2. The output from the zina help command says that all items shown in RED must be fixed, and this one failed/is in red:

"Jquery status: If this test fails, it is most likely a conflict with mootools.js or a module/component/plugin that uses mootools. Try disabling that module on Zina pages and/or check your browsers JavaScript debugger for an error message."

The modules I have installed are:
System
Private Messaging
User Profile
Protector
Weblog
Zina

I have no idea which one (if any) use mootools, and I also cannot find any place in the "Zina pages" to "disable that module". The error message appears in both browsers I use: Opera 10.51 and IE8...but where would I go to look at JS debug output?

3. No icons - only text labels - and in IE8, red X missing image symbols. I can't find a css file to integrate with xoops.css (and don't know if that would fix the problem).

Here is my system overview output:
XOOPS Version XOOPS 2.4.4
PHP Version 5.2.6
mySQL Version 4.1.22
Server API apache2handler
OS Linux
safe_mode Off
register_globals Off
magic_quotes_gpc Off
allow_url_fopen Off
fsockopen On
post_max_size 128M
max_input_time 60
output_buffering 4096
max_execution_time 30
memory_limit 128M
file_uploads On
upload_max_filesize 128M

Thanks for any help you can provide!

James

I'm about to post a help request on a related issue, and know the answer to this one.

Zina version 2.0b15 and 2.0b14 do not have a Xoops flavor.

Use Zina 2.0b13 - it installs, at least.

The temporary folder for sessions was missing for that domain. It was added by tech support for my server admin and it now works.

Thanks for the tip!

OK, that didn't work. Here's what happened.

I presume the session test is the one you mean - but I did the cookie test too - cookies are fine.

I copied/pasted the code for the two session tests exactly. I presume the referenced missing backslashes have been repaired...I didn't find any errors. The lines that wrap below are fine in the code.

Uploaded files to server. Filenames checked and rechecked.

setsession.php generated an error. Opera says the page is missing, IE8 gives a 500 error. Here is the exact code in the file:



and for tstsession.php


The tstsession.php returns:
Quote:

OK. So, I googled "PHP sessions not working" and I get tons of hits - some exact. I think we are on to something.

I tried another test I found online:

test2.php


Running this does not generate an error, it does go to next.php. And next.php:


This however does not echo a variable on the screen - I get a blank screen.

Thanks for your help! What next? I am cc'ing my site support on this message.

Greetings.

Trying to install 2.4.4 from scratch, following instruction manual carefully. I have 2.3.2 (apparently 2.3.2b) installed, but backed up and offline, and I have 2.4.4 attempting to install.

Currently:
XOOPS Version - XOOPS 2.3.2 (b)
PHP Version - 5.2.6
MySQL Version - 4.1.22
Server API Version - apache2handler
OS Version - Linux

MySQL is working fine with this and several other databases. I have username and password.

Referencing these two threads:

https://xoops.org/modules/newbb/viewtopic.php?topic_id=70061&forum=13&post_id=319794#forumpost319794

https://xoops.org/modules/newbb/viewtopic.php?post_id=300519#forumpost300519

I believe I am suffering something similar. I am not actually getting an error. Rather, I am cycling back to page_dbconnection.php from page_dbsettings.php. The install will not move forward. In other words, the username and pw are correct, it goes to dbsettings, gets some sort of generic error, and cycles back to dbconnection.

I've tried adding " mysql_close($link);" to the error handling routine in dbconnection, but it didn't seem to do anything. I am uncertain how to add "only the extended error reporting" in dbsettings.

I would appreciate any help.

Aha.

Found this in the distro rel notes.

...the 2.3.2b release we have security fixes improved with help from DSRG.

color me solved.

But you really should make the ... oh nevermind.

I thought I was clear - I read the release notes, and understand what it says. Perfectly. I know I need to "Get the right update package from the sourceforge file repository".

Once again:
I have XOOPS 2.3.2
Not 2.3.2a
Not 2.3.2b

I would really like to have 2.3.2a (or b) because then I could patch.

For some reason unknown to me, version 2.3.2 is the single only isolated version of XOOPS that is NOT listed on sourceforge. I am presuming here that the "x" in 2.3.x needs to be exactly the same.

There is :
XOOPS 2.4.3
XOOPS 2.4.2
XOOPS 2.4.1
XOOPS 2.4.0
XOOPS 2.3.3b
XOOPS 2.3.3
XOOPS 2.3.2b
XOOPS 2.3.2a

<<< hellooooo --- no 2.3.2 --->>>

XOOPS 2.3.1
XOOPS 2.3.0

So, I would really like to upgrade. Should I just try the 2.3.2a upgrade, even though it's not exactly the same as my 2.3.2 install? I guess to be crystal clear, since there is not a 2.3.2 patch, what is the "right update package"?

And really, why is it that 2.3.2 just isn't there? It's like a conspiracy. Or something.

And thanks for the info on the alpha.

Greetings XOOPS people!

I have the following:
XOOPS Version - XOOPS 2.3.2
PHP Version - 5.2.6
MySQL Version - 4.1.22
Server API Version - apache2handler
OS Version - Linux

I want to go to 2.4.4 (at least)

Question: When reviewing instructions to upgrade, I see:
"1. Get the right update package from the sourceforge file repository"

And at sourceforge, the available update packages do NOT include one for 2.3.2.

There's one from 2.3.3b...but not 2.3.2.

So, OK, I'm thinking I can patch from 2.3.2 to 2.3.3b...but there is NOT ANY patch from 2.3.2 to anything. You can patch from 2.3.2a, or 2.3.2b...but AFAIK, I don't have 2.3.2a or b.

I have 2.3.2.

So...what do I do with that? Why am I so different? Must I always be the problem child?

Q2: Is the second alpha stable enough to roll with?

Thanks!
James
:)