32
Quote:
It's a problem specific to PHP 5.0.x. As the change they did broke some applications, the PHP team decided to fix this in 5.1, but didn't in 5.0
.
The fix is easy each time, but fixing one line doesn't mean you won't see the same problem reappear in another one (however: the way to fix it is the same each time). So I think you'd better report this to the devs so they can provide a real fix.
In the meantime, here's the idea:
you have to put the result of 'getVar' in a temporary variable each time, changing those line to this:
But again, there may be others (opening userinfo.php made me see the same syntax was used for 'user_signature' a few lines below ), so you'll have to do this each time
So a more definite solution would be appreciated.
I use php 5.0.5. by the way. It's a hosted domain, so I can't change anything about that.
It's a problem specific to PHP 5.0.x. As the change they did broke some applications, the PHP team decided to fix this in 5.1, but didn't in 5.0
.The fix is easy each time, but fixing one line doesn't mean you won't see the same problem reappear in another one (however: the way to fix it is the same each time). So I think you'd better report this to the devs so they can provide a real fix.
In the meantime, here's the idea:
// userinfo.php (115)
$xoopsTpl->assign('user_extrainfo', $myts->makeTareaData4Show([color=FF6666]$thisUser->getVar('bio', 'N')[/color],0,1,1));
// xoopsblock.php (152)
return str_replace('{X_SITEURL}', XOOPS_URL.'/', $myts->displayTarea([color=FF6666]$this->getVar('content', 'N')[/color], 1, 1));
you have to put the result of 'getVar' in a temporary variable each time, changing those line to this:
// userinfo.php (115)
$tmp = $thisUser->getVar('bio', 'N');
$xoopsTpl->assign('user_extrainfo', $myts->makeTareaData4Show($tmp,0,1,1));
// xoopsblock.php (152)
$tmp = $this->getVar('content', 'N');
return str_replace('{X_SITEURL}', XOOPS_URL.'/', $myts->displayTarea($tmp, 1, 1));
But again, there may be others (opening userinfo.php made me see the same syntax was used for 'user_signature' a few lines below ), so you'll have to do this each time
33
Quote:
Your database cannot be found. More precisely: the connection to the MySQL server doesnt work.
First possible cause: a problem with XOOPS_DB_HOST/USER/PASS.
Second possible cause: your MySQL server is too loaded and reaches the number of accepted connections
Warning: mysql_select_db(): supplied argument is not a valid MySQL-Link resource in /home/httpd/vhosts/xoops.net.br/httpdocs/modules/protector/include/precheck.inc.php on line 26
Your database cannot be found. More precisely: the connection to the MySQL server doesnt work.
First possible cause: a problem with XOOPS_DB_HOST/USER/PASS.
Second possible cause: your MySQL server is too loaded and reaches the number of accepted connections
34
Quote:
If you get this message, then the upgrade isn't complete (the "tammairanslip" message has been changed to "script removed" in 2.0.14):
- Delete all the ".php" files in templates_c to force the regeneration of your templates
- If that doesn't fix your problems, then use the files integrity checker released with 2.0.14 to verify that all the system files were correctly uploaded/updated
When I do that it sends me to a page that says..."the page cannot be displayed"..the url at the top is..
(tammairanslip)openWithSelfMain( 'http://bandofbrother.net/pmlite.php?send2=1&to_userid=5',%20'pmlite', %20450,%20380);
If you get this message, then the upgrade isn't complete (the "tammairanslip" message has been changed to "script removed" in 2.0.14):
- Delete all the ".php" files in templates_c to force the regeneration of your templates
- If that doesn't fix your problems, then use the files integrity checker released with 2.0.14 to verify that all the system files were correctly uploaded/updated
35
A 2.0.14 change requires support of the "xoops_module_header" feature in your theme (if you use an old theme that doesn't suppport this, one of the consequences may be what you're describing)...
- Open the file themes/yourtheme/theme.html
- Check that this file inserts the xoops_module_header content in the output page head. If not, add the following read line between <head> and </head>:
Once you've done this, delete all the files inside the template_c folder (except index.html), to ensure your change is seen by XOOPS.
- Open the file themes/yourtheme/theme.html
- Check that this file inserts the xoops_module_header content in the output page head. If not, add the following read line between <head> and </head>:
<head>
....
....
[color=FF3333]<{$xoops_module_header}>[/color]
</head>
Once you've done this, delete all the files inside the template_c folder (except index.html), to ensure your change is seen by XOOPS.
36
Quote:
Don't know... that's weird. That's what I did too, with no problem.
I just tried to redo an install quickly, dloading the tgz again, untarring and all, and everything goes fine (well, xoops_md5.php tells me 3 files are invalid but I saw in another thread it's due to a packaging error in the tgz and can be ignored).
So I don't know... I think you should try the upg again (get a new package, and do the copy again). Maybe you could try to check your new files perms too (owner and chmoding).
There are way too many "content invalid" files to list here. What did I do wrong?
Don't know... that's weird. That's what I did too, with no problem.
I just tried to redo an install quickly, dloading the tgz again, untarring and all, and everything goes fine (well, xoops_md5.php tells me 3 files are invalid but I saw in another thread it's due to a packaging error in the tgz and can be ignored).
So I don't know... I think you should try the upg again (get a new package, and do the copy again). Maybe you could try to check your new files perms too (owner and chmoding).
37
Quote:
I think it is not enough as error reporting is disabled in other places too. The only safe way to enable debug mode when you don't have access to the admin interface is by changing the config value manually in the DB (as indicated in the "troubleshooting blank page" FAQ if I remember).
Also, complete blank pages can often be the consequence of PHP parse errors. Did you check that you uploaded your files correctly using the file integrity checking script ?
I have gone into recovery.php and set debugging to 1 and still not getting any additional errors that are showing what is the problem. As backup insurance I edited common.php to for error reporting to E_ALL, and still not getting any errors either on screen on in my phperror.log.
I think it is not enough as error reporting is disabled in other places too. The only safe way to enable debug mode when you don't have access to the admin interface is by changing the config value manually in the DB (as indicated in the "troubleshooting blank page" FAQ if I remember).
Also, complete blank pages can often be the consequence of PHP parse errors. Did you check that you uploaded your files correctly using the file integrity checking script ?
38
Wow ! 
Why do simple when we can do complicated ?
1st step, insert this in footer.php (if you just need this feature in one of your theme templates), or better: in class/template.php (to make it available in every template).
footer.php version
class/template.php version
Now you can test if the user is a member of a specific group using something like this in your templates:
Quote:
To use the group name instead of its ID/number isn't recommended: the groupd Id will always stay the same, while you may want to change its display name in the future, whitout having to change all your templates.
Why do simple when we can do complicated ?
1st step, insert this in footer.php (if you just need this feature in one of your theme templates), or better: in class/template.php (to make it available in every template).
footer.php version
define("XOOPS_FOOTER_INCLUDED",1);
[color=FF6666] if ( @$xoopsUser && is_object($xoopsUser) ) {
$xoopsTpl->assign( 'xoops_usergroups', $xoopsUser->getGroups() );
}[/color]
class/template.php version
$this->Smarty();
[color=FF6666] global $xoopsUser;
if ( @$xoopsUser && is_object($xoopsUser) ) {
$this->assign( 'xoops_usergroups', $xoopsUser->getGroups() );
}[/color]
Now you can test if the user is a member of a specific group using something like this in your templates:
Quote:
<{if 1|in_array:$xoops_usergroups}>User is a member of group 1<{/if}>
<{if 2|in_array:$xoops_usergroups}>User is a member of group 2<{/if}>
To use the group name instead of its ID/number isn't recommended: the groupd Id will always stay the same, while you may want to change its display name in the future, whitout having to change all your templates.
39
I think the warning is just here because of the notices: it seems the installer tries to send a custom header, but as some notices have been printed, it fails to do so.
So, I think you shouldn't worry about it.
So, I think you shouldn't worry about it.
40
AFAIK, yes... But there are newer versions of most of these modules available, so I wouldn't recommend you to:
- There's an updated XOOPSPolls module
- There's formulaire to replace the old contact module
- The old newbb module has become CBB.
And so on...
- There's an updated XOOPSPolls module
- There's formulaire to replace the old contact module
- The old newbb module has become CBB.
And so on...
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|