XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Community Support forums / 
  3. Q and A 
  4.  / Most modules do not work on xoops-2.0.15
Register
21
jensclas
Re: Most modules do not work on xoops-2.0.15

Keep an eye on the newsposts - active developers have been working on modules consistently since this release. I don't know all of the moudles by name and purpose but a search for a 'mail module' will bring up recent posts n the news section and help you find them. In the mean time there is work being done on a new module repository and we are all waiting patiently for this.

HTH
22
davidl2
Re: Most modules do not work on xoops-2.0.15

  • 2006/10/5 15:36

  • davidl2

  • XOOPS is my life!

  • Posts: 4843

  • Since: 2003/5/26


see here - most modules will work fine on 2.0.14 & 2.0.15

However, the above minor fix is required in some cases.

With this, I have had no problems (so far) with new modules I have been testing.
23
yongzhang
Re: Most modules do not work on xoops-2.0.15

  • 2006/10/5 19:19

  • yongzhang

  • Just popping in

  • Posts: 26

  • Since: 2005/2/12


Quote:

yongzhang wrote:
Could some one answer to my question? I really do not know how can other people manage to use xoops-2.0.15 with modules developed before 2.0.15 was released.

YZ


I do not think that other people who use suse 10.1 together with xoops-2.0.15 can make all the modules work. I really tested very hard for more than 20 modules. Few worked well.

Who can give advice about this problem? I posted this question many days ago but noe one could answer this question so I reposted it in new post.


Yongzhang
24
davidl2
Re: Most modules do not work on xoops-2.0.15

  • 2006/10/5 20:14

  • davidl2

  • XOOPS is my life!

  • Posts: 4843

  • Since: 2003/5/26


Please do not repost the same question multiple times.

A simple solution to "bump" a thread back to view is to post with the word "bump".

Creating extra threads makes more work for the moderators.
25
JCDunnart
Re: Most modules do not work on xoops-2.0.15

  • 2006/10/5 20:35

  • JCDunnart

  • Not too shy to talk

  • Posts: 114

  • Since: 2006/7/1 5


Instead of general accusations why not just say what the problem is? Every module I've tried works fine with XOOPS 2.0.15.

I see in your list in the first post you include liaise, which is one that works for me.

So give a few specifics of what the problem is, use the FAQ which was posted earlier as a guide to what information you can provide, then maybe someone can help you.
26
Peekay
Re: Most modules do not work on xoops-2.0.15

  • 2006/10/5 20:49

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


IMHO, I think it should be policy for Xoops.org to automatically declare ALL modules incompatible after a version change until each module developer has explicitly declared their modules to be compatible.

To support this, the modules in the repository should have a version attribute that is searchable.

If a module is no longer supported, users should still be able to download it, but it should be made clear that it may not work.

And beer should be cheaper worldwide.
A thread is for life. Not just for Christmas.
27
McNaz
Re: Most modules do not work on xoops-2.0.15

  • 2006/10/5 21:45

  • McNaz

  • Just can't stay away

  • Posts: 574

  • Since: 2003/4/21


Quote:
And beer should be cheaper worldwide.


I second that.
28
yongzhang
Re: Most modules do not work on xoops-2.0.15

  • 2006/10/6 19:13

  • yongzhang

  • Just popping in

  • Posts: 26

  • Since: 2005/2/12


I installed xoops-2.0.15 in Suse 10.1 with PHP5.

Xoops-2.0.13 can not be installed in Suse10.1 with PHP5 (see my earleir post). Therefore, the only choice for a normal user who has suse 10.1 to do is to install xoops-2.0.14 or .15. But most modules published before 2.0.14 or 15 being released would not work on 2.0.14 or 2.0.15.

You said that you do not have the problem. It is maybe true. But I do not think your PHP, MySQL etc are the latest version. 2.0.13 could not be installed in suse 10.1 with PH5 but 2.0.14 or .15 maybe can be installed in earleir version of suse (for example 9.1 0r 9.2), or in other linux OS with PHP 4.x or so. In this case, maybe all modules work well. I think your case maybe is this case.

Unfortunately, I just do not have older suse version than 10.1 with PHP5.


YZ
29
m0nty
Re: Most modules do not work on xoops-2.0.15

  • 2006/10/6 20:35

  • m0nty

  • XOOPS is my life!

  • Posts: 3337

  • Since: 2003/10/24


i have XOOPS 2.0.15 installed on suse 10.1 and also even had XOOPS 2.0.12, 2.0.13.2 installed on it aswell.

it makes no difference what the operating system is.. the only thing that matters is what mysql/php/apache/IIS etc you are using and how they are all configured..

the older XOOPS versions had problems with php5 & possibly MySQL 4.1x or MySQL 5.. but that doesn't mean you can't install them on suse 10.1, you can install them and they work fine but you need to use a version of php/mysql they are compatible with or make changes to the code instead..

operating system has nothing to do with it..

and i also have not had a problem with any modules not working on 2.0.15 (with the exception of having to replace the form.php file as suggested earlier)

of course there will be some modules that don't work, my cricketstats/soccerstats module for 1 will not work.. it hasn't worked properly since 2.0.10, but that's more to do with the module coding than XOOPS and i don't have time to recode the module, so it's left as is for now (there is a warning on the module article stating this tho :-p )
30
jalikid
Re: Most modules do not work on xoops-2.0.15

  • 2006/10/7 2:21

  • jalikid

  • Just popping in

  • Posts: 7

  • Since: 2006/9/27


Quote:

Peekay wrote:
IMHO, I think it should be policy for Xoops.org to automatically declare ALL modules incompatible after a version change until each module developer has explicitly declared their modules to be compatible.

To support this, the modules in the repository should have a version attribute that is searchable.

If a module is no longer supported, users should still be able to download it, but it should be made clear that it may not work.

And beer should be cheaper worldwide.

Yeah, I'm agree with this guy. I think each module should has info like:
-Module version
-Which XOOPS version is supported
-Which modules are related
-...
« 1 2 (3) 4 »

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

233 user(s) are online (140 user(s) are browsing Support Forums)

Members: 0

Guests: 233

more...

Donat-O-Meter

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

Latest GitHub Commits