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. 2.4.x Support 
  4.  / First comments on 2.4
Register
1
kaotik
First comments on 2.4

  • 2009/8/10 14:33

  • kaotik

  • Just can't stay away

  • Posts: 861

  • Since: 2004/2/19


New oxygen theme for admin looks great. I really like the use of jquery with tooltip plugin.
A couple of minor issues:
- Some tooltips have misspelled words "whit blocks". I can provide a full list later on as I find them.
- In List groups, the column width group ID is bigger then any other (click on groups from control panel).
I'm using firefox 3.5.2
2
frankblack
Re: First comments on 2.4

  • 2009/8/10 15:08

  • frankblack

  • Just can't stay away

  • Posts: 830

  • Since: 2005/6/13


I still notice extra spaces / linefeeds in several files (smarty nearly all) after the closing ?>.

This COULD lead to problems (sometimes eventually)...

class/soap/soapfactory.php line instead of:
le="color: #000000"><?php if (file_exists($GLOBALS['xoops']->path('class/soap/'.strtolower(XOOPS_SOAP_LIB).'/'.strtolower(XOOPS_SOAP_LIB).'.php'))

must be:
le="color: #000000"><?php if (file_exists($GLOBALS['xoops']->path('class/soap/'.strtolower(XOOPS_SOAP_LIB).'/'.strtolower(XOOPS_SOAP_LIB).'.php')))


class/auth/auth_ads.php line 93 instead of:
le="color: #000000"><?php else {

must be:
le="color: #000000"><?php } else {


class/auth/auth_ldap.php line 146 instead of:
le="color: #000000"><?php else {

must be:
le="color: #000000"><?php } else {


edit: added to bug tracker
3
Anonymous
Re: First comments on 2.4

  • 2009/8/10 17:43

  • Anonymous

  • Posts: 0

  • Since:


install/img/xoops_2.3.3.png file not linked to any page or css file.

plz delete it and remove this line from checksum.md5 file:

install/img/xoops_2.3.3.png:8ad0cec440ef48b45f92fb04b2e69ad2

4
xsell
Re: First comments on 2.4

  • 2009/8/10 19:32

  • xsell

  • Quite a regular

  • Posts: 245

  • Since: 2008/9/2 1


are we going to Have Pure Php in this Version .. wht i mean By Pure is that we dont have to go beg Our Hosting Companies to enable , ini_set.. or the Disabled Function for Security Reasons ..
5
trabis
Re: First comments on 2.4

  • 2009/8/10 19:49

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


Please do not update a live site with 2.4 beta
I found some serious problems related with the ERM implementation and the hashing processing overhead.
Thanks.
6
Mamba
Re: First comments on 2.4

  • 2009/8/10 19:53

  • Mamba

  • Moderator

  • Posts: 11521

  • Since: 2004/4/23


Quote:
Please do not update a live site with 2.4 beta

As we've said in the 2.4 announcement:

Please remember:This release is ONLY for testing! Do NOT use it on productions sites. And if you're installing it over previous test installation, make a BACKUP first!
Please also note that some hacks done for previous XOOPS versions might not work with this release: testing before installing is always a good choice
7
ghia
Re: First comments on 2.4

  • 2009/8/10 22:59

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1


/userinfo.php does not contain a closing php tag.
le="color: #000000"><?php } include XOOPS_ROOT_PATH . '/footer.php';
Many files have their include for mainfile replaced from
le="color: #000000"><?php include 'mainfile.php';
to
le="color: #000000"><?php include dirname(__FILE__) . DIRECTORY_SEPARATOR . 'mainfile.php';
What is the point for having this? To me it seems not a progress for readability nor for efficiency and it makes XOOPS dependent to external vars, which aren't set always right. Also the standard gpl header Quote:
https://xoops.org/> // // ------------------------------------------------------------------------ // // This program is free software; you can redistribute it and/or modify // // it under the terms of the GNU General Public License as published by // // the Free Software Foundation; either version 2 of the License, or // // (at your option) any later version. // // // // You may not change or alter any portion of this comment or credits // // of supporting developers from this source code or any supporting // // source code which is considered copyrighted (c) material of the // // original comment or credit authors. // // // // This program is distributed in the hope that it will be useful, // // but WITHOUT ANY WARRANTY; without even the implied warranty of // // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the // // GNU General Public License for more details. // // // // You should have received a copy of the GNU General Public License // // along with this program; if not, write to the Free Software // // Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA // // ------------------------------------------------------------------------ //
is been replaced by Quote:
http://www.fsf.org/copyleft/gpl.html * * @copyright The XOOPS Project http://sourceforge.net/projects/xoops/ * @license http://www.fsf.org/copyleft/gpl.html GNU General Public License (GPL) * @package core * @since 2.0.0 * @author Kazumi Ono * @version $Id: userinfo.php 3151 2009-04-18 13:25:43Z catzwolf $ */
Seems not entirly according to the guidelines for me. Did not yet test with 2.4, but in 2.3.3 there is an error when automatic converting hostnames to links. You mention eg http://www.myhost.com and without url tags it becomes a link anyway. When you mention the site at the end of a sentence as in Have a look at http://www.mysite.com. then the full stop (point) is taken also in the link, which makes the link unreachable. Probably a bad regexp.
8
trabis
Re: First comments on 2.4

  • 2009/8/10 23:59

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


Hi Ghia,
Closing missing tags are optional. I think they should be removed in every file. This would avoid undesirable output if someone accidentally types an empty space(new line, etc) after the closing tag. Bur for consistency, we should put the closing tag there :)

I usually use this
include dirname(__FILE__) . '/mainfile.php';

I'm not aware of the need of normalizing the directory separator but, I think is important not to use relative paths.
An example:
when you include cp functions file from yourmod/admin/subfolder you get a mainfile.php not found. This happens because mainfile is included with '../../../' making it relative to yourmod/admin folder. If we used dirname(__FILE__) we could be pretty sure that the file would be found.
Maybe catz can explain it better.

I have no idea on why the gpl header was changed.
Maybe catz can explain.

"There is an error when automatic converting hostnames to links"
I did not fix this, maybe catz did.



9
trabis
Re: First comments on 2.4

  • 2009/8/11 0:06

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


Quote:

frankblack wrote:
I still notice extra spaces / linefeeds in several files (smarty nearly all) after the closing ?>.


I have updated 4 or 5 files in smarty. Some times is your php editor that does that. Are you using eclipse? Can you point me one of that files so I can check here?
10
Anonymous
Re: First comments on 2.4

  • 2009/8/11 0:52

  • Anonymous

  • Posts: 0

  • Since:


xoopseditor is too big size .. is it required or optional ? please keep it away of XOOPS package so the user can choose what he/she like.
(1) 2 3 4 5 »

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Donat-O-Meter

Stats
Goal: $15.00
Due Date: Jul 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $15.00
Make donations with PayPal!

Latest GitHub Commits