6
Thanks Voltan. I said that without take a look at the file and i was wrong.
that is very bad hardcode in XOOPS Core in 2.5.5 and 2.6 versions.
Also 2 weeks ago i found another hardcode in that pagenav class.
$ret = '<form action="" name="pagenavform">';
// some codes ....
$ret .= '</form>';
No need a form without any action. core team should remove that form because it will cause problems when you have another form.
As i said above the final solution is removing those hardcodes.
But for this time we can use smarty replace function in templates like this.
<{$pagenav|replace:'form':'div'|replace:'id="xo-pagenav"':''}>
Quote:
Is there a hack for pagenav not to display ALL pages for a module ABC unless you are an admin member?
what do you exactly want to do?
1- show the pagenav only for admins?
2- show other pages than page=1 only for admins?
I think you mean (2).
for that purpose you should control the $_GET['start'] value in the URL. eg like this:
$start = isset($_GET['start']) ? $_GET['start'] : 0;
if (!$isadmin) $start=0;
then you are sure that regular user cannot use start value other than 0.
easyb9:
W3C validation is a
guide. as you said some issues and errors are not important. but some of them are important.
for example this id="xo-pagenav" issue is very important because for example the css code will just affect the first pagenav (in the top) in viewtopic.php in newbb.
