[d]
[color=ff0000]
if (!$config) { // If there is a config error, we use xoops
$xoops_auth_method = 'xoops';
} else {
$xoops_auth_method = $config[0]->getVar('conf_value');
}
[/color][/d]
if (!$config) { // If there is a config error, we use xoops
$xoops_auth_method = 'xoops';
} else {
$xoops_auth_method = $config[0]->getConfValueForOutput();
if(!is_readable( XOOPS_ROOT_PATH.'/class/auth/auth_' . $xoops_auth_method . '.php')){
$xoops_auth_method = 'xoops';
}
}
| Bookmark this article at these sites |
|---|
|
Broken links to the packages. Great idea though! One other question: will the modules that have been 'slightly modified' be easy to update from when those module developers make a new version?
Quote:Quote:
Broken links to the packages. Great idea though! One other question: will the modules that have been 'slightly modified' be easy to update from when those module developers make a new version?
What packages are broken?? They are hosted on sf.net and may not be fully uploaded everywhere - but just try another mirror.
Fixed bug in system/admin/modulesadmin/modulesadmin.php where block templates could remain in the database after module uninstall (Mithrandir
After I've installed XOOPS 2.2.2 to 2.2.3 Patch, when I try to log in, I'm taken to a blank page
(http://mysite/users/user.php) from where I can do nothing
![Open in new window](javascript:CaricaFoto("http://www.xoops.org/modules/core/images/icon/downloads.gif");){kind=icon}
![Open in new window](javascript:CaricaFoto("http://www.xoops.org/modules/core/images/targz.gif");)
Poster: DCrussader Posted: 2005/8/26 14:18:39
Do not upgrade is a exatcly what I wanna say:
What the hell fixes this release ?
...
And maybe a lot of other sux are done to this release, gzip compression again is a problem, yeah ?
Now can u provide downgrader to 2.2.2 please ?
Hard working people who get no appreciation from certain people!
If theres an problem, report it and let it get dealt with!
People are working for FREE, you are using there stuff for FREE. This is not the way to communicate to the Xoops development people.
require_once XOOPS_ROOT_PATH.'/class/auth/auth.php';
if (!$config) { // If there is a config error, we use xoops
$xoops_auth_method = 'xoops';
} else {
$xoops_auth_method = $config[0]->getVar('conf_value');
[b] if(!is_readable(XOOPS_ROOT_PATH.'/class/auth/auth_' . $xoops_auth_method . '.php')){
$xoops_auth_method = 'xoops';
}
[/b]
}
Fatal error: [] operator not supported for strings in /MY_WWW_DIR/class/module.textsanitizer.php on line 168
require_once XOOPS_ROOT_PATH.'/class/auth/auth.php';
if (!$config) { // If there is a config error, we use xoops
$xoops_auth_method = 'xoops';
} else {
$xoops_auth_method = $config[0]->getVar('conf_value');
}
require_once XOOPS_ROOT_PATH.'/class/auth/auth.php';
if (!$config) { // If there is a config error, we use xoops
$xoops_auth_method = 'xoops';
} else {
$xoops_auth_method = $config[0]->getVar('conf_value');
if(!is_readable(XOOPS_ROOT_PATH.'/class/auth/auth_' . $xoops_auth_method . '.php')){
$xoops_auth_method = 'xoops';
}
}
2.2.3 is however working flawlessly on my test site.
WF-Downloads 2.05a (Slightly modified for XOOPS 2.2)
WF-Links 1.03 (Slightly modified for XOOPS 2.2)
XF-Guestbook 2.22 (Slightly modified for XOOPS 2.2)
SmartFAQ 1.04 (Slightly modified for XOOPS 2.2)
SmartSection 1.0 (Slightly modified for XOOPS 2.2)
SmartClient 1.02 (Slightly modified for XOOPS 2.2)
SmartPartner 1.02 (Slightly modified for XOOPS 2.2)
here is the link to 2.2.3 to 2.2.2 downgrader
Was it an upgrade form 2.2.2 or a fresh install?
. maybe you should get this version on CVS and give it a good testing yourselves, and then lets get this version back on track as it should be instead of wasting all the time on complaining and saying this should be done and that's not working.
As moderator of the Dutch xoops community supportsite I totally agree with Marco and Frankblanc.
It is undoable to give proper support at this stage. There are to many problems with the 2.2.x version release(s) themselves and next the modules compatibilitie(s).
Please turn the clock back and give it RC release.
If people ask (and they do) I recommend them to stay at 2.0.13.x. at this moment.
Sorry tot say and by all means no offence to the hard work of devs.
Grtz., Shine
Who can download CVS?
why is yours the only one working. What magical insight do you have? Anxious to solve the problems.
Possibly, because I use a custom loggin built into my theme, not the login block? Anyway I have logged in and out most all day, no blank pages, no errors, only one admin page for a module giving me formatting problems, but still works.
There are a few things you need to get started
* A SourceForge account
* An account here, in the XOOPS development site
* Authorization to use CVS
* A CVS client
but instead the developers never got the required feedback about bugs, neither were they discovered or reported either. some were, some weren't.
Do u remeber PD-Downloads 1.2 dissusion, why to submit bug reports when no one take it seriously ?
A zip file is not CVS.
So is there CVS access or not?
I just updated from 2.2.2 -> 2.2.3 and got a blank page after upgrade.
Here's what to do:
1: Add 'auth' patch mentioned above.
2: Use 'class/module.textsanitizer.php' from 2.2.2 (2.2.3 fails in line 168 acording to PHP Debug mode!)
sorry, i thougt...
1
SELECT DISTINCT i.instanceid, b.*, i.* FROM myprefix_block_instance i, myprefix_newblocks b, myprefix_block_module_link m WHERE m.block_id=i.instanceid AND i.instanceid IN (1,2,3,4,71,5,7,8,9,10,11,12,44,60,61,139,68,70,72,73,74,75,76,77,80,81,83,84,135,150,149,110,138,109,136,116,117,118,120,141,152,153,154) AND i.visible=1 AND i.bid=b.bid AND b.isactive=1 AND m.module_id=0 AND m.pageid IN (0, 1) ORDER BY i.weight,i.instanceid
( 0.005817)
Notice [PHP]: Only variables should be assigned by reference in file d:\www\kernel\object.php line 819
Warning [PHP]: session_start(): Cannot send session cache limiter - headers already sent (output started at d:\www\language\lithuanian\global.php:1) in file d:\www\include\common.php line 206
Notice [PHP]: Only variables should be assigned by reference in file d:\www\kernel\profile.php line 93
Notice [PHP]: Only variables should be assigned by reference in file d:\www\kernel\user.php line 610
Notice [PHP]: Only variables should be assigned by reference in file d:\www\include\common.php line 209
Notice [PHP]: Only variables should be assigned by reference in file d:\www\include\common.php line 223
Notice [PHP]: Only variables should be assigned by reference in file d:\www\kernel\object.php line 819
Notice [PHP]: Only variables should be assigned by reference in file d:\www\kernel\object.php line 819
Warning [PHP]: Cannot modify header information - headers already sent by (output started at d:\www\language\lithuanian\global.php:1) in file d:\www\user.php line 60
When I don't find any bugs, I find it is time for a release.
but it was not enough.
We need beta/RC/Release testers, yes. We sure do. Everyone says so and everyone agrees. Let me see someone actually DO something about it. Contact me, so we can get you organised and know where to send the releases for testing.
if (!empty($xoopsModuleConfig['minpass']) && [b][color=FF0000]strlen[/color][/b]($_POST['pass']) <$xoopsModuleConfig['minpass']) {
My 2.2.3 test site is working ok so far ...
You don't need to fall down on your knees thanking your deity of choice for XOOPS 2.2.3, but I must admit that I feel like crying right now.
That may not be very manly, but the feedback I get for the work I do is really awful.
I have called out for help on numerous occasions. Anyone remember the time (quite recently) where I asked for help to give the Links section a facelift? I have received ONE reply - and he doesn't respond to my messages about how I foresee the process.
We need beta/RC/Release testers, yes. We sure do. Everyone says so and everyone agrees. Let me see someone actually DO something about it. Contact me, so we can get you organised and know where to send the releases for testing.
We need documenters to look at the changes in XOOPS 2.2 and how they affect modules so module developers know how to make their modules work with XOOPS 2.2
Let me see someone actually DO something about it. Contact me, so we can get you organised and get a dialogue going on how modules should be updated.
We need module testers to test which modules have critters with XOOPS 2.2
Let me see someone actually DO something about it. Contact me, so we can get you organised and get a dialogue going on how modules should be tested.
I'll go off and sob somewhere quiet for the weekend.
Will be back Monday.
I think Mith is talking about future releases..
... Prior to upgrade xoopsgallery would work. Now it does not. Now where the album name was I get nl2br instead. See post above it also has nl2br referenced in it.
...but does anyone know what happened with Xoopsgallery module...
A team of people... perhaps only 12 or so... who have experience with Xoops - but are able to think from an ordinary users point of view - and able to give consise error reports - could achieve more than having hundreds of people giving the same answers and asking the same questions.
Polite Opening,
I'm experiencing a bug after [installing | upgrading to] <xoops version> and would like to report a bug.
Bug Description:
----------------
Provide as much information regarding the bug as possible. Include any appropriate information such as, what you did prior to noticing the bug, what are the affects of the bug, does the bug affect all users, is the bug viewable in all browsers, etc.
Steps for reproduce the bug:
----------------------------
In clear, concise, numbered steps, walk the Devs through the proces of reproducting the error, if possible.
Example:
1. Add "Site Info" to the list of used blocks
2. Edit block and enable to show admins
3. Configure other settings as you want
4. Check block on frontend page and detect missing part of information
Debug Output:
-------------
Put your PHP, MySQL, and Smarty Debug output here. Seperate with headings. If you are getting a White Screen of Death (WSOD), paste whatever php output is on the screen.
Example:
PHP Debug Output:
<output goes here>
MySQL Debug Output:
<output goes here>
Additional information:
-----------------------
The bug in question can be viewed at <link> (provide indicators of where to look on the page). Admin rights granted to responsible person on request (optional, but may be helpful).
Posible solution:
-----------------
If possible, provide a detailed description of how to fix the problem. As above, write in clear, conscise, numbered steps that the Devs can easily follow.
Server Information:
------------------
<Operating System>
<Web Server/version>
<PHP Version>
<MySQL Version>
Polite Closing,
Your Name
your@email.com
http://yourwebsite.com/
When we report about core issues, themes and modules play nothing
<div id='buttontop'>
<table style="width: 100%; padding: 0; " cellspacing="0">
<tr>
<td style="width: 70%; font-size: 10px; text-align: left; color: #2F5376; padding: 0 6px; line-height: 18px;">
<a href="../index.php"><{$smarty.const._AD_NAV_MODHOME}></a>
</td>
<td style="width: 30%; font-size: 10px; text-align: right; color: #2F5376; padding: 0 6px; line-height: 18px;">
<b><{$modulemenu.name}> <{$smarty.const._AD_NAV_MODADMIN}></b> <{$modulemenu.breadcrumb}>
</td>
</tr>
</table>
</div>
[color=FF0000] <br style="clear:both;" />[/color]
<div id='buttonbar'>
<ul>
<{foreach item=link from=$modulemenu.links key=id}>
<{if $id == $modulemenu.current}>
<li class='current'>
<{else}>
<li>
<{/if}>
<a href='<{$link.link}>'><span><{$link.title}></span></a>
</li>
<{/foreach}>
</ul>
</div>
<br style="clear:both;" />
and the "packages feature"...Our programming philosophy is inspired from Extreme Programming; our interface philosophy benefits from the Usability theory developed by Jakob Nielsen.
Working with us means:
* you keep control on the evolution of the software you ordered;
* you can follow the evolution of the programme step by step;
* you can change your mind in the middle of development process;
* you can see interface before programme is written;
* you get just enough of what you asked for;
* your interface remains simple;
* you are confronted to other people's views on the same problems,
which will help you take the better decision;
* good teaching remains the objective and it is never alienated to any
technical autonomous ambition.
"Sorry, your password must be at least 3 characters long."
modules/profile/register.php
line #75
if (!empty($xoopsModuleConfig['minpass']) && strlen($_POST['pass']) <$xoopsModuleConfig['minpass']) {
