XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk


« 1 ... 5 6 7 (8) 9 10 11 ... 212 »


71
Dave_L
Re: Migrating definitively to Php 5

  • 2007/7/14 17:57

  • Dave_L

  • XOOPS is my life!

  • Posts: 2277

  • Since: 2003/11/7


Quote:

jdseymour wrote:
Well I think this is really not an issue anymore. PHP.net just announced the "End of Life" for PHP 4 see here:

http://www.php.net/


I think that was posted earlier in this thread.

That doesn't mean that PHP 4 will suddenly vanish on Dec 31; people will continue to use it, even if it's no longer supported. But the fact the the PHP organization is dropping support for PHP 4 at the end of this year will encourage people to switch to PHP 5.
Topic | Forum


72
Dave_L
Re: Migrating definitively to Php 5

  • 2007/7/14 15:27

  • Dave_L

  • XOOPS is my life!

  • Posts: 2277

  • Since: 2003/11/7


I've posted the "Go PHP 5" proposal in the core developers' forum at sf.net to get opinions.
Topic | Forum


73
Dave_L
Re: dev.xoops.org seems to be down

  • 2007/7/10 16:48

  • Dave_L

  • XOOPS is my life!

  • Posts: 2277

  • Since: 2003/11/7


Do you mean Dave_L?

As far as I know, all the current posts on www.xoops.org and dev.xoops.org will be preserved for public reference. They may be moved to a different subdomain, or archived, but they won't be thrown away.
Topic | Forum


74
Dave_L
Re: dev.xoops.org IS NOT down

  • 2007/7/10 15:12

  • Dave_L

  • XOOPS is my life!

  • Posts: 2277

  • Since: 2003/11/7


xoopsinfo.com is a community support site, operated by its owners/administrators independently of the project.

xoops.org, or at least a subdomain, will have forums. I don't know exactly what role these forums will take.

A few of the council members are tasked with drafting the plan for the reorganized *.xoops.org sites. That's still underway, and I don't have the details yet.

Most of the teams have submitted their reports. These reports are being reviewed. When that's complete, the teams will be announced.
Topic | Forum


75
Dave_L
Re: dev.xoops.org seems to be down

  • 2007/7/10 11:03

  • Dave_L

  • XOOPS is my life!

  • Posts: 2277

  • Since: 2003/11/7


This thread has diverged from its original topic, so I'm not sure what you're asking.

What do you want the council to respond to? I'll try to provide an answer.
Topic | Forum


76
Dave_L
Re: Moving to Php5 definitively

  • 2007/7/10 8:55

  • Dave_L

  • XOOPS is my life!

  • Posts: 2277

  • Since: 2003/11/7


There are two issues here.

1) Should XOOPS be compatible with (the latest stable release of) PHP 5?

2) Should XOOPS be compatible with PHP 4?

The answer to #1 is definitely "yes". And as far as I know, the XOOPS core is fully compatible with PHP 5, although not all modules are.

The answer to #2 is "yes", for now. At some point in the future this will need to change, so that we can take advantage of features in PHP 5 that are not in PHP 4. The big question is when to abandon PHP 4 compatibility; I don't know the answer to that.

(I'm only expressing my opinion here; this is not an official viewpoint of the project council or core development team.)
Topic | Forum


77
Dave_L
Re: Evolution can run backwards

  • 2007/7/4 13:06

  • Dave_L

  • XOOPS is my life!

  • Posts: 2277

  • Since: 2003/11/7


The core development team has been discussing what to do about the 2.0/2.2/2.3 branches.

The roadmap hasn't been finalized yet, but I think the plan will be to merge the features from 2.2.x into 2.0.x or 2.3.x.

A way will be provided to "upgrade" from 2.2.x to the new version. (Since I use 2.2.x on a production site, that's important to me.)
Topic | Forum


78
Dave_L
Re: Migrating to PHP5

  • 2007/7/1 21:42

  • Dave_L

  • XOOPS is my life!

  • Posts: 2277

  • Since: 2003/11/7


You may have already seen this: Migrating from PHP 4 to PHP 5 / Backward Incompatible Changes

One item I didn't see on that page is that only a simple variable should be used as the parameter for "return", if the function result is to be used as a reference.

Example:

// Incorrect
function &foo()
{
...
return ($x + $y);
}

// Correct
function &foo()
{
...
$rtn = $x + $y;
return $rtn;
}


Actually, I'm not sure if this is a PHP 5 - specific issue, or if it was introduced in a late release of PHP 4.
Topic | Forum


79
Dave_L
Re: Xoops Core Discussion and Roadmap

  • 2007/6/29 16:40

  • Dave_L

  • XOOPS is my life!

  • Posts: 2277

  • Since: 2003/11/7


BlueStocking and kc0maz: That sounds good to me.

Quote:
Would the developers like to have the coordinators have accounts set-up on SF.net?


Creating accounts is probably a good idea, so when you post in an sf.net tracker or forum, your user name will be displayed, rather than "anonymous". If you prefer not to do that, it's ok, but a note should be included in posts stating who posted it, so that the person working on the bug knows who to contact if more information is needed.
Topic | Forum


80
Dave_L
Re: Xoops Core Discussion and Roadmap

  • 2007/6/29 15:41

  • Dave_L

  • XOOPS is my life!

  • Posts: 2277

  • Since: 2003/11/7


A couple of comments from a core developer:

1. Before reporting a core bug, it's helpful if the reporter could first attempt to determine whether it's really a core bug, or whether it's a bug in a module, theme, server configuration, etc.

If the reporter isn't sure, a discussion thread might be started in a support forum to enlist others to help with that determination. Or maybe kc0maz's team can assist with that. If necessary, the core developers can be called upon to help.

If it turns out to be a problem outside of the core, then it would be better to report it in the appropriate place, such as the module's support forum, theme's support forum, general support forum, and so on.

2. When I'm working on a core bug, my first step is to try to reproduce it (unless it's something I can obviously relate to a mistake in the code). If I have to track down a third-party module or theme, or use a server configuration that I don't already have set up, such as XOOPS 2.0.1 / MySQL 4.5 / PHP 5.9-beta / IIS / Windows Vista), reproducing the bug will be a challenge. It's much easier if I can reproduce the bug in the current version of XOOPS, without needing any special module or theme.
Topic | Forum



TopTop
« 1 ... 5 6 7 (8) 9 10 11 ... 212 »



[Advanced Search]

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

199 user(s) are online (134 user(s) are browsing Support Forums)

Members: 0

Guests: 199

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