xoops-development — For those who are interested in XOOPS development

[Xoops-development] Documentation links broken...

[Ankit P. <ank...@ya...>]

Hi,

If i am posting this at a wrong place then please
direct me in proper direction...

I have been using XOOPS for my own web development. I
am great lover of it. I am also interested in
promoting xoops among people. I have given link of
xoops to my friends. They tried to learn through FAQ
section of Xoops.org but the documentation links are
broken. I also tried to check out and i found that the
links which points to docs.xoops.com are broken.

Can any of you please repair this section, as this
will reduce the interest for a new comer....



Thanks a lot!
Ankit Patel

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Xoops-development] support request

[Open S. S. <ope...@gm...>]

Dear Developers,

First we would like to tell you that this is not spam, but a one time
request for your support.

We are two master students from the Erasmus University Rotterdam
(http://www.eur.nl) in the Netherlands, and we are doing research on
the subject of Open Source developer motivation.

To gather data for this research we are conducting an online survey.
We hope that you are willing to help us out by participating. Our
survey can be accessed by clicking on the following link:

http://smeijer.homelinux.org:8080/survey/index.php

Completing the survey will only take about 10 minutes, is completely
anonymous, and will really help us out a lot.

Of course we are more than willing to share our findings with you. If
you are interested in the outcomes of our research, let us know at
ope...@gm... and we will send you the final results.

Sincerely yours,

Cornelis & Douwe
Students Erasmus University Rotterdam

[Xoops-development] XOOPS for Debian

[<vr...@gm...>]

Hi

I have finish packing xoops for Debian.

You can download it from:
http://www.vmxt.com/debian/

I will appreciate your feedback.

Also, I have a question: You (developers) support xoops installed in apache=
2 ?
Just to know if I can a dependency in the package. I mean, the package
will depend on apache or apache2.

Thanks in advance.


--=20
"Libertad es a=FAn la idea m=E1s radical de todas."
---Nathaniel Branden

[Xoops-development] hello - hope to help

[Ted Stresen-R. <ted...@ma...>]

Hi,

My name is Ted Stresen-Reuter. I am a web developer from Chicago 
currently living in Las Palmas de Gran Canaria (Canary Islands). I have 
a couple years of experience developing web sites using the fusebox 
application framework (http://www.fusebox.org) and have recently 
starting using XOOPS.

I'd like to help the XOOPS community improve XOOPS as much as possible 
as I expect to use it as the foundation of all future projects. I am 
particularly interested in helping make XOOPS multilingual. I've 
installed/configured the multilingual hack, but obviously, using such a 
hack on a production web site has its drawbacks (difficulty upgrading 
to newer versions of XOOPS, for example). Please count on me to help in 
this particular area if not in others.

Sincerely,

Ted Stresen-Reuter
http://www.tedmasterweb.com/
(xoops version of web site is in development... thus, this email ;-)

[Xoops-development] xoops and Gentoo

[Renat L. <rl...@ge...>]

xoops devs,

Just a quick note that xoops is now available through Gentoo Portage, so Ge=
ntoo users can now install it by simply typing emerge xoops. Please conside=
r mentioning this in the appropriate section of your website.

Best,
--=20
Renat Lumpau
Gentoo developer
GPG key id #C6A838DA on http://pgp.mit.edu
Key fingerprint =3D 04AF B5EE 17CB 1000 DDA5  D3FC 1338 ADC2 C6A8 38DA

Re: [Xoops-development] development?

[Glen S. <grs...@co...>]

Jannik Nielsen wrote:

> Hi there.
>
> Is this the official Xoops development mailinglist?
>
> Is anyone actually using it? According to SF there hasn't been a mail 
> sent to it for 3 months.
>
> We need a good way to communicate developer to developer. There will 
> always be someone that has a lot of experience in the different fields 
> of Xoops and therefore quickly can answer questions. Aparently this 
> isn't where people talk?
>
> I have joined an irc channel called xoops in the freenode network 
> (irc.freenode.net) if anyone wants to they can join me and have chats 
> about xoops.
>
> I have been developing xoops modules professionaly for about a year 
> now, and has just signed a contract for another year in a new team. I 
> have created some modules which I will try to complete and upload to 
> xoops.org soon.
>
> I hope people decide to join the irc channel.

 From what I've seen, the devs communicate mostly via instant messenger 
and dev.xoops.org.  I'll join you in IRC :)

-- 
Glen Starrett

[Xoops-development] development?

[Jannik N. <bi...@cy...>]

Hi there.

Is this the official Xoops development mailinglist?

Is anyone actually using it? According to SF there hasn't been a mail 
sent to it for 3 months.

We need a good way to communicate developer to developer. There will 
always be someone that has a lot of experience in the different fields 
of Xoops and therefore quickly can answer questions. Aparently this 
isn't where people talk?

I have joined an irc channel called xoops in the freenode network 
(irc.freenode.net) if anyone wants to they can join me and have chats 
about xoops.

I have been developing xoops modules professionaly for about a year 
now, and has just signed a contract for another year in a new team. I 
have created some modules which I will try to complete and upload to 
xoops.org soon.

I hope people decide to join the irc channel.

Cheers

Jannik Nielsen (bitkid)

[Xoops-development] FASD project: Online survey launched

[<ben...@id...>]

Dear Open Source developer

I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate.
You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it.

With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development.


With many thanks for your participation,
Benno Luthiger


PS:
The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/.
We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list.

_______________________________________________________________________

Benno Luthiger
Swiss Federal Institute of Technology Zurich
8092 Zurich

Mail: benno.luthiger(at)id.ethz.ch
_______________________________________________________________________

Re: [Xoops-development] Bug fix

[<wol...@ma...>]

To Onokazu or some one who can fix code,

When we post new post. Click "image" to add picture. The POP Up window will
Show Up your Website logo.
and use error picture size. The Website logo will not show currect image
size, To solve this Bug. Please
follow this instruction

1. use UltraEdit open file in :
/modules/system/templates/system_imagemanager.html line 48
/modules/system/templates/system_imagemanager2.html line 29

(Two line should be the same code)
<img src="<{$xoops_url}>/images/logo.gif" width="150" height="80" alt="" />

2. Del width="150" height="80" code
3. Go to system module and renew it

Finish. If you don't use default template theme. please do step 4


4. Go to system module and see system_imagemanager.html → copy this code to
your custom template right place. Same as system_imagemanager2.html

----- Original Message ----- 
From: "Geoff Gibbs" <geo...@bt...>
To: <xoo...@li...>
Sent: Saturday, May 01, 2004 8:08 PM
Subject: [Xoops-development] Bug fix


> Hi,
>
> I'm new to this list and have a fix for bug 920480 "xoops_substr adds
three dots (...)".
>
> Where or should I send the patch to?
>
> --
> Geoff Gibbs
> http://www.world-of-geoff.co.uk
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market... Oracle 10g.
> Take an Oracle 10g class now, and we'll give you the exam FREE.
> http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
> _______________________________________________
> Xoops-development mailing list
> Xoo...@li...
> https://lists.sourceforge.net/lists/listinfo/xoops-development
>

[Xoops-development] Bug fix

[Geoff G. <geo...@bt...>]

Hi,

I'm new to this list and have a fix for bug 920480 "xoops_substr adds three dots (...)".

Where or should I send the patch to?

--
Geoff Gibbs
http://www.world-of-geoff.co.uk 

[Xoops-development] does xoops support sub-catagory in Faq management?

[Scott X. - A. <sco...@an...>]

Hi, I am newbie, need some help regarding xoops.
 I have installed xoops,works well.but,does xoops support sub-catagory in
Faq management?I want this feature,but not sure if can configure.e.g. under
hardware faq catagory,I 'd like to put " mail server", " notebook " down
there,also hope some questins can go to the same anser page: e.g when user-a
goes to catagaory "smtp" ,check a question "how to configure smtp on my
notebook",it shows a answer " abc---abc", when user-b goest to catagary "
notebook",click the question "how to configure my notebook to user OE with
SMTP and pop3?" ,it will go to the same URL or page" abc---abc".Is it
possible?Thanks!!

Thanks & best regards,
Scott , Xiao Qian

[Xoops-development] question

[Dima <ad...@al...>]

Hello!

I need special module for me! I can pay. Who can help me?
Thank you.

-- 
Отправлено M2, революционной почтовой программой Opera: 
http://www.opera.com/

[Xoops-development] XOOPS 2.0.5.1 Released!

[K. O. <web...@my...>]

XOOPS Team is pleased to announce the release of XOOPS 2.0.5.1. It includes
some important security related bug fixes therefore it is
[color=ff0000]highly recommended[/color] that all users upgrade to this
version. All files are available for download
[url=http://www.xoops.org/general/download.php]here[/url].

Changes
===============================
- Added $option parameter to xoops_gethandler function (skalpa)
- Security fix in banners.php (onokazu)
- Security fix in modules/newss/include/forumform.inc.php (onokazu)
- Security fix in include/common.php (onokazu)
- Temporarily disabled XoopsErrorHandler class (onokazu)
- Security fix in include/functions.php (onokazu)
- Removed XoopsHandlerRegistry class (onokazu)
- Added fix for preventing users entering infinite loop when recovering a
lost password (onokazu)

For users currently running 2.0.5, extract xoops-2.0.5-to-2.0.5.1.patch.zip
or xoops-2.0.5-to-2.0.5.1.patch.tar.gz and just overwrite the old files with
the new ones.

Re: [Xoops-development] The admin menu.

[Marco <blu...@em...>]

hi Michael,

I have downloaded the file that you have modified and tested in local.
The result was good and also the feeling by using that positive.
If you accept a suggestion, I would prefer that the all the menus
that were open, remain open also after you have clicked a link.
Don't you thinks is a good idea?

kind regards,
Marco Ragogna

ps. Sorry for my english


>Hi everyone.
>
>I have some progress in providing an alternative administration menu. I 
>made a
>post to the xoops.org forum about it. I would like some feedback about this
>change, if it could become eligeable for inclusion in xoops???
>
>[begin quote]
>Okay, now I have cleaned it up somewhat and even made a small change.
>
>Menus now show/hide when you click on them, and they remember state across
>pages.
>
>The Url is still the same http://www.fyn.dk/xoops2/cp_functions.php.tar.gz
>
>You have to replace include/cp_functions.php with the new file and delete 
>your
>cache/adminmenu.php file.
>
>WARNING DO NOT APPLY THIS TO A LIVE SITE. YOU HAVE BEEN WARNED
>[end quote]
>
>Kind regards
>Michael Wulff Nielsen
>
>--
>I have a red sign on my door. It says "If this sign is blue, you're going too
>fast."
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: SF.net Giveback Program.
>Does SourceForge.net help you be more productive?  Does it
>help you create better code?   SHARE THE LOVE, and help us help
>YOU!  Click Here: http://sourceforge.net/donate/
>_______________________________________________
>Xoops-development mailing list
>Xoo...@li...
>https://lists.sourceforge.net/lists/listinfo/xoops-development



--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f

Sponsor:
Sconti fino al 20% per i magnifici bouquet di Artefiori! Clicca qui!
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=750&d=6-11

Re: [Xoops-development] The admin menu.

[Skalpa K. <ps...@ps...>]

Hi Michael,

> I have some progress in providing an alternative administration menu. I
made a
> post to the xoops.org forum about it. I would like some feedback about
this
> change, if it could become eligeable for inclusion in xoops???
>
Actually, I've already done something about admin theming ;-) (hehehe)
As you may have seen on xoops.org, we're preparing the next "big" version of
Xoops.
And in that one, you'll be able to create as many cp_functions.php files as
you want,
put them all in the appropriate folder, and the admin will be able to choose
the one
he wants to use.
It's more or less like making what you've done official (except that like
this, you can add
other themes to the admin without replacing the default file: it gives admin
a way to go back
to the default theme if something gets messed with a custom one).
So even if we don't include your file, you'll just have to change a few
things and will then be
able to distribute it without calling that a "hack"...

Also, I'm sorry I didn't send this to CVS already, but as there will many
changes in the next
release, we're discussing about creating a new cvs branch so we don't mess
with the v2 files...
And waiting for that, a few things recently done haven't been committed.

Anyway, I'll have a look at it and send you comments...
Thanks for that.

Skalpa.>

[Xoops-development] The admin menu.

[Michael W. N. <na...@kl...>]

Hi everyone.

I have some progress in providing an alternative administration menu. I made a 
post to the xoops.org forum about it. I would like some feedback about this 
change, if it could become eligeable for inclusion in xoops???

[begin quote]
Okay, now I have cleaned it up somewhat and even made a small change.

Menus now show/hide when you click on them, and they remember state across 
pages.

The Url is still the same http://www.fyn.dk/xoops2/cp_functions.php.tar.gz

You have to replace include/cp_functions.php with the new file and delete your 
cache/adminmenu.php file.

WARNING DO NOT APPLY THIS TO A LIVE SITE. YOU HAVE BEEN WARNED
[end quote]

Kind regards
Michael Wulff Nielsen

-- 
I have a red sign on my door. It says "If this sign is blue, you're going too 
fast."

[Xoops-development] Re: [ Xoops-Support ML] XOOPS 2.0.5 RC Released!

[K. O. <web...@my...>]

Hi all,

Sorry for the last. That should have been titled 'XOOPS2.0.5 Relesed!' ;-)

-Kazu

----- Original Message -----
From: "K. Ono" <web...@my...>
To: "xoops-support" <xoo...@co...>
Sent: Wednesday, October 08, 2003 10:34 PM
Subject: [ Xoops-Support ML] XOOPS 2.0.5 RC Released!


>
> XOOPS Team is pleased to announce the release of XOOPS 2.0.5. XOOPS 2.0.5
is
> a bug-fix release fixing a few critical issues in XOOPS 2.0.4, as well as
> some other minor bug fixes and changes.
>
> Changes
> ========
> - Fixed template files not being updated even when the 'allow update from
> themes directory' option was enabled in preferences
> - Fixed RSS channel title being cutoff at special characters
> - Minor bug fix in pagenav.php
> - Fixed blocks disappearing from the block admin page on certain occasion
> - Additional fixes to work with register_globals off
> - Fixed problem with XoopsCode Img button not working on certain occasion
> - Added missing SQL query in kernel/avatar.php
> - Fixed problem with the newbb module where users could post without a
> thread title on certain occasion
> - Fixed problem in banner admin page where banner edit form not being
> displayed on certain occasion
> - Fixed group selection option in the blocks admin page not being selected
> on certain occasion
> - Fixed poll option textbox forms not displaying the correct values
> - Fixed show all link in user profile page not working in 2.0.5RC
> - Additional phrases in language/english/global.php(_NOTITLE),
> language/english/search.php(_SR_IGNOREDWORDS),
> install/language/english/install.php(_INSTALL_L128, _INSTALL_L200)
> - Added check in install/index.php to read $HTTP_ACCEPT_LANGUAGE on
initial
> load
>
> Lang file changes
> ========
> - /language/english/global.php
> - /language/english/search.php
> - /install/language/english/install.php
>
> Requirements
> ========
> PHP 4.1.0 or later (on IIS, 4.3.1 or later)
> MySQL 3.23.xx or later
>
> Install
> ========
> [url=http://www.xoops.org/general/download.php#xoops2]Download the full
> package[/url], unpack it and upload all files included. Point your browser
> to /install/index.php to start the installer.  Please read
docs/INSTALL.html
> for details on installation and/or read the Install and Upgrade sections
of
> the Wiki ( http://wiki.xoops.org ).
>
> Upgrade
> ========
> [b]Upgrade from XOOPS 2.0.4/2.0.5RC[/b]
> 1. From [url=http://www.xoops.org/general/download.php]the download
> page[/url], download [b]XOOPS 2.0.4 ≫≫ 2.0.5 Patch[/b] and upload all
> files included (files will be overwritten).
>
> [b]Upgrade from XOOPS 2.0.3[/b]
> 1. From [url=http://www.xoops.org/general/download.php]the download
> page[/url], download [b]XOOPS 2.0.3 ≫≫ 2.0.4 Patch[/b] and upload all
> files included (files will be overwritten).
> 2. Now that you have upgraded to 2.0.4, follow the upgrade instruction
above
> for XOOPS 2.0.4.
>
> [b]Upgrade from XOOPS 2.0.2[/b]
> 1. From [url=http://www.xoops.org/general/download.php]the download
> page[/url], download [b]XOOPS 2.0.2 ≫≫ 2.0.3 Patch[/b] and upload all
> files included (files will be overwritten).
> 2. Now that you have upgraded to 2.0.3, follow the upgrade instruction
above
> for XOOPS 2.0.3.
>
> [b]Upgrade from XOOPS 2.0.1[/b]
> 1. From [url=http://www.xoops.org/general/download.php]the download
> page[/url], download [b]XOOPS 2.0.1 ≫≫ 2.0.2 Patch[/b] and upload all
> files included (files will be overwritten).
> 2. Now that you have upgraded to 2.0.2, follow the upgrade instruction
above
> for XOOPS 2.0.2.
>
> [b]Upgrade from XOOPS 2.0.0[/b]
> 1. From [url=http://www.xoops.org/general/download.php]the download
> page[/url], download [b]XOOPS 2.0.0 ≫≫ 2.0.1 Patch[/b] and upload all
> files included (files will be overwritten).
> 2. Point your browser to
http://path_to_xoops/upgrade/xoops2_0_to_2_0_1.php
> and follow the instruction displayed.
> 3. Now that you have upgraded to 2.0.1, follow the upgrade instruction
above
> for XOOPS 2.0.1.
>
> [b]Upgrade from XOOPS 2.0 RC3[/b]
> 1. From [url=http://www.xoops.org/general/download.php]the download
> page[/url], download [b]XOOPS 2.0 RC3 ≫≫ 2.0.0 Patch[/b] and upload all
> files included (files will be overwritten).
> 2. You have now upgraded to 2.0.0. Follow the upgrade instruction above
for
> XOOPS 2.0.0.
>
> [b]Upgrade from XOOPS 2.0 RC2[/b]
> 1. Read
[url=http://www.xoops.org/modules/news/article.php?storyid=700]this
> article[/url] and upgrade to XOOPS 2.0 RC3 first. Then follow the upgrade
> instruction above for XOOPS 2.0 RC3.
>
> [b]Upgrade from XOOPS 1.3.x[/b]
> 1. [url=http://www.xoops.org/general/download.php#xoops2]Download the full
> package[/url], unpack it and upload all files included (some files will be
> overwritten).
> 2. Point your browser to /install/index.php to start the installer. The
> installer will automatically detect your 1.3.x and upgrade to 2.0.4.
Please
> read docs/INSTALL.html for details on installation and/or read the Install
> and Upgrade sections of the Wiki (wiki.xoops.org).
>
> Language
> ========
> Language files can be (or will be) downloaded
>
[url=http://sourceforge.net/project/showfiles.php?group_id=41586]here[/url].
>
> Xoops-Support Mailing List [ http://www.xoops.org ]
> [Sponsored by:]
>
____________________________________________________________________________
_
> The newest lyrics on the Net!
>
>        http://lyrics.astraweb.com
>
> Click NOW!
>

[Xoops-development] XOOPS 2.0.5 RC Released!

[K. O. <web...@my...>]

XOOPS Team is pleased to announce the release of XOOPS 2.0.5. XOOPS 2.0.5 is
a bug-fix release fixing a few critical issues in XOOPS 2.0.4, as well as
some other minor bug fixes and changes.

Changes
========
- Fixed template files not being updated even when the 'allow update from
themes directory' option was enabled in preferences
- Fixed RSS channel title being cutoff at special characters
- Minor bug fix in pagenav.php
- Fixed blocks disappearing from the block admin page on certain occasion
- Additional fixes to work with register_globals off
- Fixed problem with XoopsCode Img button not working on certain occasion
- Added missing SQL query in kernel/avatar.php
- Fixed problem with the newbb module where users could post without a
thread title on certain occasion
- Fixed problem in banner admin page where banner edit form not being
displayed on certain occasion
- Fixed group selection option in the blocks admin page not being selected
on certain occasion
- Fixed poll option textbox forms not displaying the correct values
- Fixed show all link in user profile page not working in 2.0.5RC
- Additional phrases in language/english/global.php(_NOTITLE),
language/english/search.php(_SR_IGNOREDWORDS),
install/language/english/install.php(_INSTALL_L128, _INSTALL_L200)
- Added check in install/index.php to read $HTTP_ACCEPT_LANGUAGE on initial
load

Lang file changes
========
- /language/english/global.php
- /language/english/search.php
- /install/language/english/install.php

Requirements
========
PHP 4.1.0 or later (on IIS, 4.3.1 or later)
MySQL 3.23.xx or later

Install
========
[url=http://www.xoops.org/general/download.php#xoops2]Download the full
package[/url], unpack it and upload all files included. Point your browser
to /install/index.php to start the installer.  Please read docs/INSTALL.html
for details on installation and/or read the Install and Upgrade sections of
the Wiki ( http://wiki.xoops.org ).

Upgrade
========
[b]Upgrade from XOOPS 2.0.4/2.0.5RC[/b]
1. From [url=http://www.xoops.org/general/download.php]the download
page[/url], download [b]XOOPS 2.0.4 ≫≫ 2.0.5 Patch[/b] and upload all
files included (files will be overwritten).

[b]Upgrade from XOOPS 2.0.3[/b]
1. From [url=http://www.xoops.org/general/download.php]the download
page[/url], download [b]XOOPS 2.0.3 ≫≫ 2.0.4 Patch[/b] and upload all
files included (files will be overwritten).
2. Now that you have upgraded to 2.0.4, follow the upgrade instruction above
for XOOPS 2.0.4.

[b]Upgrade from XOOPS 2.0.2[/b]
1. From [url=http://www.xoops.org/general/download.php]the download
page[/url], download [b]XOOPS 2.0.2 ≫≫ 2.0.3 Patch[/b] and upload all
files included (files will be overwritten).
2. Now that you have upgraded to 2.0.3, follow the upgrade instruction above
for XOOPS 2.0.3.

[b]Upgrade from XOOPS 2.0.1[/b]
1. From [url=http://www.xoops.org/general/download.php]the download
page[/url], download [b]XOOPS 2.0.1 ≫≫ 2.0.2 Patch[/b] and upload all
files included (files will be overwritten).
2. Now that you have upgraded to 2.0.2, follow the upgrade instruction above
for XOOPS 2.0.2.

[b]Upgrade from XOOPS 2.0.0[/b]
1. From [url=http://www.xoops.org/general/download.php]the download
page[/url], download [b]XOOPS 2.0.0 ≫≫ 2.0.1 Patch[/b] and upload all
files included (files will be overwritten).
2. Point your browser to http://path_to_xoops/upgrade/xoops2_0_to_2_0_1.php
and follow the instruction displayed.
3. Now that you have upgraded to 2.0.1, follow the upgrade instruction above
for XOOPS 2.0.1.

[b]Upgrade from XOOPS 2.0 RC3[/b]
1. From [url=http://www.xoops.org/general/download.php]the download
page[/url], download [b]XOOPS 2.0 RC3 ≫≫ 2.0.0 Patch[/b] and upload all
files included (files will be overwritten).
2. You have now upgraded to 2.0.0. Follow the upgrade instruction above for
XOOPS 2.0.0.

[b]Upgrade from XOOPS 2.0 RC2[/b]
1. Read [url=http://www.xoops.org/modules/news/article.php?storyid=700]this
article[/url] and upgrade to XOOPS 2.0 RC3 first. Then follow the upgrade
instruction above for XOOPS 2.0 RC3.

[b]Upgrade from XOOPS 1.3.x[/b]
1. [url=http://www.xoops.org/general/download.php#xoops2]Download the full
package[/url], unpack it and upload all files included (some files will be
overwritten).
2. Point your browser to /install/index.php to start the installer. The
installer will automatically detect your 1.3.x and upgrade to 2.0.4. Please
read docs/INSTALL.html for details on installation and/or read the Install
and Upgrade sections of the Wiki (wiki.xoops.org).

Language
========
Language files can be (or will be) downloaded
[url=http://sourceforge.net/project/showfiles.php?group_id=41586]here[/url].

[Xoops-development] XOOPS 2.0.5RC Released!

[K. O. <web...@my...>]

XOOPS 2.0.5 RC has been released for testing. Please test this release as
much as possible, so that any remaining issues can be uncovered and resolved
before the final 2.0.5 release.

Both zip and tar.gz packages are available on our
[url=http://www.xoops.org/general/download.php]download page[/url].

XOOPS Core Team


CHANGES
=======
- Fixed email checking bug mentioned in
[url=http://www.xoops.org/modules/newbb/viewtopic.php?topic_id=12288&forum=2
]this thread[/url] (mvandam)
- Fixed a number of bugs in blocks admin page (onokazu)
- More usability fix in blocks admin page (onokazu)
- Fixed forum topic links to correctly use the # feature in url (onokazu)
- Fixed password checking bug mentioned in
[url=http://www.xoops.org/modules/newbb/viewtopic.php?viewmode=thread&order=
ASC&topic_id=12301&forum=21]this thread[/url]
- Fixed database connection error when creating database during install
(onokazu)
- Fixed mb_output_handler causing problems in
backend.php/image.php/downloader (onokazu)
- Fixed search feature to use GET requests for prev/next/showall links
(onokazu)
- Register_globals related fix in /include/comment_post.php (contrib by
gstarrett)
- Added $xoopsUserIsAdmin global variable (onokazu)
- Added xoops_getLinkedUnameById function to /include/functions.php
(Catzwolf)
- Fixed invalid Smarty tags in
system/templates/system_siteclosed.html
system/templates/system_redirect.html
system/templates/system_imagemanager2.html

[Xoops-development] 2.0.4, XoopsErrorHandler and Smarty

[tuff <tu...@br...>]

Hi all,

I noticed that the new XoopsErrorHandler class of x-2.0.4 generates a 
number of "Undefined index" error, while most the undefined variables 
are generated by Smarty. For example if a page has no right blocks to 
display, the follow line will be shown if php-debug is turned on:
Notice [PHP]: Undefined index:  xoops_rblocks in file 
class/smarty/Smarty.class.php line 626

Or if a specific variable is not assigned, a msg appears just like this:
Notice [PHP]: Undefined index:  foo in file 
templates_c/sometheme^templates^somefile.html line 69

Since this kind of "error" may not be fixed without a heavy rewrite of 
Smarty, is it possible to strip them out by the XoopsErrorHandler class?


Cheers,
tuff
http://www.brandycoke.com/

[Xoops-development] Help me out

[<an...@mu...>]

Hi Xoops fellas,
=20
I am planning to translate XOOPS into Lao language but a colleague of =
mine asks me to look into PhPNuke also. Can someone please give me some =
suggestions why should go about of picking one not the other or I should =
I do both.=20
If I choose XOOPS, are there any tools to help me in translation? What =
is the url link or pointer to doc? Thanks in advance.
=20
laonux
=20

Re: [Xoops-development] sobig and other viruses/worms

[Steve P. <st...@pu...>]

Hi Mike,

I'm increasingly annoyed at Mr. Gates' software sending out virus emails in 
my name. I do not use his software, yet it still causes me pain.

Here's a good virus cure: Reinstall your computer with Linux - it's really 
quite good you know.

Steve Purkiss
http://www.purkiss.com
doing IT with free software

On Sat, 23 Aug 2003 13:23:08 -0700 (PDT), R. Michael van Dam 
<mv...@ca...> wrote:

>
> Can I request that everyone who reads this list please clean their system
> of viruses.  For those that are not aware, mail worms propagate by 
> sending
> themselves to people listed in an infected persons addressbook (e.g. from
> outlook express)... many of the latest viruses list in the "From" field
> another random name from that addressbook.
>
> Recently I have been receiving a huge number of messages 'returned mail'
> because my email has been listed in the 'From' field.  In the last day, I
> have seen that some of these messages are addressed to individual people
> on this list.  Thus I suspect that someone who reads this list and runs
> outlook express has an infected system.  BTW, I use 'pine' on linux for
> all my email.
>
> Has anyone else in this list been experiencing similar problems?
>
> Thanks,
> Mike
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: VM Ware
> With VMware you can run multiple operating systems on a single machine.
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
> at the same time. Free trial click 
> here:http://www.vmware.com/wl/offer/358/0
> _______________________________________________
> Xoops-development mailing list
> Xoo...@li...
> https://lists.sourceforge.net/lists/listinfo/xoops-development
>
>
>



 

[Xoops-development] Xoops developers in Perth, Australia?

[Ian H. H. <ia...@co...>]

Hello:

First of all, I believe that this is not off-topic but if I'm wrong, my
apologies! I tried searching through the archives but the sourceforge
server is down for maintenance.

I am really interested in proposing the use of Xoops for our
Intranet/Internet site. I would feel far more confident however if I was
able to secure the services of a company to develop and maintain the
system reliably, as well as provide custom modules if required. Can
anyone suggest a *local* Xoops developer to implement and maintain a
website using Xoops? What about one in Australia?

Regards,

-=3D-=3D-=3D-=3D-=3D
Ian Hogben
IS Manager
Town of Cottesloe
PH: 9285 5014
FX: 9285 5061

Re: [Xoops-development] addressing "blank page" problem

[K. O. <web...@my...>]

Looks nice. I will start modifying the core codes to use the trigger_error
function.

- Kazu

----- Original Message -----
From: "R. Michael van Dam" <mv...@ca...>
To: <xoo...@li...>
Sent: Tuesday, July 29, 2003 8:22 AM
Subject: Re: [Xoops-development] addressing "blank page" problem


>
> I've commit to CVS a preliminary version of a new error handler for
> review in class/errorhandler.php.  Changes were also made in
> include/common.php to 'activate' it.
>
> By default, I have turned on error reporting at the beginning, which later
> gets turned off once the DB is connected and the config value
> (debug_mode) can be read.
>
> It cannot trap PHP 'fatal' or 'parse' errors, so 'trigger_error' should be
> added throughout the code where problems can be detected early.  e.g. I
> have modified common.php so if the database is not connected, an error is
> triggered.  (If the code were to continue instead, it would trigger a
> 'fatal' error, "call to a member of a non-object" which cannot be
> trapped.)  When an error cannot be trapped, it leads to the blank page
> problem (if server has display_errors Off).
>
> Currently an error triggered with type 'E_USER_ERROR' will add its message
> then exit immediately.  This should be used for unrecoverable problems
> (such as not able to connect to DB).  'E_USER_WARNING' and 'E_USER_NOTICE'
> can be used to print helpful diagnostics due to unexpected but not fatal
> conditions.
>
> e.g.
>
>   trigger_error("Encountered major error and cannot continue generating
> page", E_USER_ERROR");
>
>   trigger_error("Encountered a less major problem which we can ignore
> but here is a diagnostic message", E_USER_WARNING);
>
>
> Anyways, please let me know if you like it.  I can remove it / correct it
> if anyone finds any problems with it.
>
> Regards,
>
> Mike
>

Re: [Xoops-development] addressing "blank page" problem

[R. M. v. D. <mv...@ca...>]

I've commit to CVS a preliminary version of a new error handler for
review in class/errorhandler.php.  Changes were also made in
include/common.php to 'activate' it.

By default, I have turned on error reporting at the beginning, which later
gets turned off once the DB is connected and the config value
(debug_mode) can be read.

It cannot trap PHP 'fatal' or 'parse' errors, so 'trigger_error' should be
added throughout the code where problems can be detected early.  e.g. I
have modified common.php so if the database is not connected, an error is
triggered.  (If the code were to continue instead, it would trigger a
'fatal' error, "call to a member of a non-object" which cannot be
trapped.)  When an error cannot be trapped, it leads to the blank page
problem (if server has display_errors Off).

Currently an error triggered with type 'E_USER_ERROR' will add its message
then exit immediately.  This should be used for unrecoverable problems
(such as not able to connect to DB).  'E_USER_WARNING' and 'E_USER_NOTICE'
can be used to print helpful diagnostics due to unexpected but not fatal
conditions.

e.g.

  trigger_error("Encountered major error and cannot continue generating
page", E_USER_ERROR");

  trigger_error("Encountered a less major problem which we can ignore
but here is a diagnostic message", E_USER_WARNING);


Anyways, please let me know if you like it.  I can remove it / correct it
if anyone finds any problems with it.

Regards,

Mike


On Fri, 11 Jul 2003, K. Ono wrote:

> I guess we'd better stick with using the trigger_error function directly
> otherwise we would need to pass the file name and line numbers explicitly
> like
> notice($msg, __FILE__, __LINE__); if we need to know where the error
> occurred exactly and that doesn't seem to make things any easier for the
> developers..
>
> - Kazu
>
>
> ----- Original Message -----
> From: "K. Ono" <web...@my...>
> To: <xoo...@li...>
> Sent: Thursday, July 10, 2003 4:21 PM
> Subject: Re: [Xoops-development] addressing "blank page" problem
>
>
> > > Or maybe this:  Leave the error handler always ON.  If debug mode is on,
> > > show all errors and warnings (native PHP messages AND explicitly
> > > 'triggered' messages).  If debug mode is off, show only 'triggered'
> > > messages.  If we use trigger_error very sparingly (or E_USER_ERROR for
> > > errors-to-be-displayed) then the end user will only see a message if
> > > something goes very wrong (e.g. can't connect to database), which may be
> > > useful to alert the site administrator.  (In a custom error handler you
> > > can strip out any path info so this is not a security risk.)
> >
> > I like this idea.. Maybe we can wrap the trigger_error() function with a
> > custom function/class so that we
> >  can always call the custom trigger error function/method within the codes
> > which does
> > not always call the native trigger_error function. This way, the coders
> > wouldn't need to
> > think about whether to use the native trigger_error() function in certain
> > areas of their
> > codes but just always use the custom one wherever something wrong might
> > happen.
> >
> > For example,
> >
> >
> > class ErrorHandler
> > {
> >
> >  function ErrorHandler()
> >  {
> >   set_error_handler(array(&$this, 'trigger'));
> >  }
> >
> >  function trigger($errno, $errstr, $errfile, $errline)
> >  {
> >   switch ($errno) {
> >     case E_USER_ERROR:
> >       // do something here
> >       break;
> >     case E_USER_WARNING:
> >       // do something here
> >       break;
> >     case E_USER_NOTICE:
> >       // do something here
> >       break;
> >     default:
> >       // do something here
> >       break;
> >   }
> >
> >  }
> >
> > // A class that triggers all errors
> > class ShowAllErrorHandler extends ErrorHandler
> > {
> >
> >  function notice($msg)
> >  {
> >   trigger_error(E_USER_NOTICE, $msg);
> >  }
> >
> >  function warning($msg)
> >  {
> >   trigger_error(E_USER_WARNING, $msg);
> >  }
> >
> >  function fatal($msg)
> >  {
> >   trigger_error(E_USER_ERROR, $msg);
> >  }
> > }
> >
> > // A class that triggers only fatal-level errors
> > class FatalErrorHandler extends ErrorHandler
> > {
> >  function notice($msg)
> >  {
> >   // do nothing
> >  }
> >
> >  function warning($msg)
> >  {
> >   // do nothing
> >  }
> >
> >  function fatal($msg)
> >  {
> >   trigger_error(E_USER_ERROR, $msg);
> >  }
> > }
> >
> >
> > And at startup, we can use a factory method/class to create one of the
> error
> > handler classes
> > depending on a config setting or the user level (admin, anonymous, etc).
> >
> > $debug_level = $xoopsUser->isAdmin() ? XOOPS_DEBUG_SHOWALL :
> > $config['debug_level'];
> > $error_handler =& ErrorHandler::getInstance($debug_level);
> > ...
> > $error_handler->notice('A notice error');
> > ...
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Parasoft
> Error proof Web apps, automate testing & more.
> Download & eval WebKing and get a free book.
> www.parasoft.com/bulletproofapps1
> _______________________________________________
> Xoops-development mailing list
> Xoo...@li...
> https://lists.sourceforge.net/lists/listinfo/xoops-development
>
>