have two phpnuke 7.6 portals(with sentinel 2.4.1), with different phpbb problems..
1, the phpbb admin page doesn't appear, just a 0byte white page..
i have god access, so dunno what to do Sad any idea where to look?
phpnuke guys said the problem is in mainfile.php, but dunno where..
2, phpbb admin page says: Access Denied..
i have god access, anything, but i got this error msg..
any idea about this?
i did, but didn't find any solution, just others also posted the same problem..
raven said in one of those topic that the guy missed something to edit while installing sentinel and that might be the problem..
i think i found my problem in mainfile.php
i upgraded to 3.1chatserv(downloaded from this portal), admin now works well (ofkoz, without sentinel!), but can't install sentinel
need to edit core files, done great!, except mainfile.php, where i can't find related lines
Code:
if (defined('FORUM_ADMIN')) {
@require_once("../../../config.php");
@require_once("../../../db/db.php");
@require_once("../../../includes/sql_layer.php");
if (file_exists("../../../includes/custom_files/custom_mainfile.php")) { @include_once("../../../includes/custom_files/custom_mainfile.php"); }
@require_once("../../../includes/ipban.php");
if (defined('NUKE_HEADER') && file_exists("../../../includes/custom_files/custom_head.php")) { @include_once("../../../includes/custom_files/custom_head.php"); }
if (defined('NUKE_HEADER') && file_exists("../../../includes/custom_files/custom_header.php")) { @include_once("../../../includes/custom_files/custom_header.php"); }
} elseif (defined('INSIDE_MOD')) {
@require_once("../../config.php");
@require_once("../../db/db.php");
@require_once("../../includes/sql_layer.php");
if (file_exists("../../includes/custom_files/custom_mainfile.php")) { @include_once("../../includes/custom_files/custom_mainfile.php"); }
@require_once("../../includes/ipban.php");
if (defined('NUKE_HEADER') && file_exists("../../includes/custom_files/custom_head.php")) { @include_once("../../includes/custom_files/custom_head.php"); }
if (defined('NUKE_HEADER') && file_exists("../../includes/custom_files/custom_header.php")) { @include_once("../../includes/custom_files/custom_header.php"); }
} else {
@require_once("config.php");
@require_once("db/db.php");
@require_once("includes/sql_layer.php");
if (file_exists("includes/custom_files/custom_mainfile.php")) { @include_once("includes/custom_files/custom_mainfile.php"); }
@require_once("includes/ipban.php");
if (defined('NUKE_HEADER') && file_exists("includes/custom_files/custom_head.php")) { @include_once("includes/custom_files/custom_head.php"); }
if (defined('NUKE_HEADER') && file_exists("includes/custom_files/custom_header.php")) { @include_once("includes/custom_files/custom_header.php"); }
}
please help in that, thx!
second problem is after the 3.1chatserv patch install coppermine page is blank
what do i have to find and replace to get it work?
Sorry I didn't mentioned this before, but we recommend that you not use version 7.7 - 7.9 for production sites as these version have security issues that even NukeSentinel cannot correct.
As for your mainfile, it might not look exactly like that, but you should be able to find something like
Code:
require_once("../../../config.php");
and the changes should apply there.
I haven't tried to run coppermine with the 3.1 patch. I have a test site where I can try that, but probably not until this weekend.
// define the INCLUDE PATH
if(defined('FORUM_ADMIN')) {
define('INCLUDE_PATH', '../../../');
} elseif(defined('INSIDE_MOD')) {
define('INCLUDE_PATH', '../../');
} else {
define('INCLUDE_PATH', './');
}
// Include the required files
@require_once(INCLUDE_PATH."config.php");
@require_once(INCLUDE_PATH."db/db.php");
@require_once(INCLUDE_PATH."includes/sql_layer.php");
@require_once(INCLUDE_PATH."includes/ipban.php");
if (file_exists(INCLUDE_PATH."includes/custom_files/custom_mainfile.php")) {
@include_once(INCLUDE_PATH."includes/custom_files/custom_mainfile.php");
}
#
#-----[ CHANGE TO ]------------------------------------------
#
// define the INCLUDE PATH
if(defined('FORUM_ADMIN')) {
define('INCLUDE_PATH', '../../../');
} elseif(defined('INSIDE_MOD')) {
define('INCLUDE_PATH', '../../');
} else {
define('INCLUDE_PATH', './');
}
// Include the required files
@require_once(INCLUDE_PATH."config.php");
@require_once(INCLUDE_PATH."db/db.php");
@require_once(INCLUDE_PATH."includes/sql_layer.php");
//@require_once(INCLUDE_PATH."includes/ipban.php");
@include_once(INCLUDE_PATH."includes/nukesentinel.php");
if (file_exists(INCLUDE_PATH."includes/custom_files/custom_mainfile.php")) {
@include_once(INCLUDE_PATH."includes/custom_files/custom_mainfile.php");
}
This type of change significantly impacts the installation instructions for many add on modules. I think it would have been better served to have this as a new patch version.
Also, I noticed that the includes/custom_files/custom_head.php and includes/custom_files/custom_header.php were removed in this patch. I've never seen these used, but if you happened to use this, watch out.
Last edited by kguske on Wed Sep 28, 2005 10:35 pm; edited 1 time in total
Maybe some planned changes were erroneously included in the latest 3.1 download - I noted that some other changes were added that are unrelated to security or bugs and have comments like "Beta". Definitely improvements, but maybe for 3.2...
now i modified mainfile.php, and found the error...
Quote:
#-----[ FIND ]------------------------------------------
#
$queryString = strtolower($_SERVER['QUERY_STRING']);
if (stripos_clone($queryString,'%20union%20') OR stripos_clone($queryString,'/*') OR stripos_clone($queryString,'*/union/*') OR stripos_clone($queryString,'c2nyaxb0')) {
header("Location: index.php");
die();
}
#
#-----[ CHANGE TO ]------------------------------------------
#
if(!file_exists('includes/nukesentinel.php')) {
if(isset($_SERVER['QUERY_STRING']) && (!stripos_clone($_SERVER['QUERY_STRING'], "ad_click") || !stripos_clone($_SERVER['QUERY_STRING'], "url"))) {
$queryString = $_SERVER['QUERY_STRING'];
if (stripos_clone($queryString,'%20union%20') OR stripos_clone($queryString,'/*') OR stripos_clone($queryString,'*/union/*') OR stripos_clone($queryString,'c2nyaxb0') OR stripos_clone($queryString,'+union+') OR stripos_clone($queryString,'http://') OR (stripos_clone($queryString,'cmd=') AND !stripos_clone($queryString,'&cmd')) OR (stripos_clone($queryString,'exec') AND !stripos_clone($queryString,'execu')) OR stripos_clone($queryString,'concat')) {
die('Illegal Operation');
}
}
}
in function function online() {
the last line is guilty, when i added this line got a blank page, without it, it's perfect...
my only remaining matter is the coppermine, pls test it and gimme solution, looking forward so excited
ps: also tried cpg 1.3.0, but it's so buggy, couldn't delete pics, blank page on new pics, etc, etc...soo, wanna stay with cpg 1.2.2b
i saw some info in chatserv 3.1 readme.txt, but didn't find anything related in /modules/coppermine/index.php
Quote:
2- Additional changes for third party add-ons:^
if ($mainfile == 1) {
should be changed to:
if (defined('NUKE_FILE')) {
if ($module == 1) {
should be changed to:
if (defined('MODULE_FILE')) {
if ($footer == 1) {
should be changed to:
if (defined('NUKE_FOOTER')) {
if ($header == 1) {
should be changed to:
if (defined('NUKE_HEADER')) {
Joined: Mar 06, 2004 Posts: 1156 Location: Sanbornton, NH USA
Posted:
Thu Sep 29, 2005 4:17 pm
This is kind of the problem with insignificant versioning of Patched and a long held complaint. Today's "Patched x.x" may not be the same as yesterday's "Patched x.x".
Instead of making these changes to existing versions, those changes should be incorporated into a new version number.
It's bad enough keeping up with revisions, but when changes happen in an existing revision version, it is nearly impossible for webmasters to keep up with where they are, nevermind developers.
I would humbly suggest that there be a freeze on changes to current revisions and new changes be available in either annotated form (for the next revision) or in CVS (for the next revision) or both.
This situation (of this post) is an excellent example of the problem in that module developers need to revise documentation (and yes, the actual coding of modules), but have no way of describing it nor a reliable method for making those changes with any kind of a predictable versioning strategy of their own. In other words, if I am a module developer, I can't say "compatible with Patched 3.1" because in truth, my block and/or module code may not be.
For example, you can't say, "In Patched 3.1 Change this to this" because while the user may have patched 3.1, what is described is not necessarily what will be seen in any particular user's code, depending on the date that they actually downloaded that revision. For that reason, the current methodology adds confusion where none need exist and simply complicates everyone's lives.
Finally, my biggest concern is that this major code modification marks a substantial change in the goals of Patched as it potentially creates a default, inherited incompatibility with an indeterminate number of modules, blocks and other add-on solutions with baseline PHP-Nuke. The problem being that not everyone is using the "Patched" code for modules and/or blocks due to custom mods employed by those users. To create an incompatibility defies the intensions of Patched which is to provide stabilization.
As this problem extends to other critical modules including Groups, YA and even affects NukeSentinel and other security solutions with no prior notice given to the community of users or developers, nor documented instructions on the changes that must be applied to any scripts that this change impacts (the aforementioned blocks and modules) and while I like the modification and appreciate what it does, I would humbly suggest that the patched team consider reverting to the previous methodology to eliminate this serious problem with Patched 3.1 that will affect all modules and blocks and actually incorporate those changes into Patched 3.2. Thus also, to annotate the changes that will be necessary to incorporate this major change into any module, block or core code.
Joined: Oct 30, 2002 Posts: 1043 Location: RedNeck Land (known as Kentucky)
Posted:
Thu Sep 29, 2005 9:40 pm
Okay, I went thru my backup cd's and found the following on Patched 3.1 versions:
Only registered users can see links on this board! Get registered or login to the forums!
(<-directory closed)
The dates are the dates that I downloaded copies to compare to the prior copy so they would not match anything in ChatServs CVS records, or I don't think they would.
BTW, this is just the 3.1 section of my backups of patched
This is the most frustrating thing I ever did. All these patches, changes, versions..etc. I only wanted to install sentinal on 7.6 like I did a year or so ago. You know when it worked with no issues? Now its filled with errors, denied access and blank pages. Ok, lets install 7.9 patched 3.1 and sentinal, should work right? hell no. Then looking for fixes come to find its junk. Ok, install 7.6 patched 3.1 and then install sentinal. Work? hell no. The mainfile is so completely different in the instruction. Then look for fixes and everything is different. Blank pages, access denied, no forums. What's the point of all this wasted time? Then you make us use patched so all the great modules and add-ons dont function right? Hell, im going back to the 7.6 from codezwiz. Sentinal and Patched Series can kiss my ...........
I would humbly suggest that there be a freeze on changes to current revisions and new changes be available in either annotated form (for the next revision) or in CVS (for the next revision) or both.
I agree. I think better documentation is needed, so I set up my own CVS just to do that. My own project tries to streamline patches into one core set. Even does some function checking, so files remain essentially backwards-compatible. I'll annotate all the changes to the Patched files, and any change that I find. Unfortunately chatserv has yet to use it, but I'd love to see it used.
Only registered users can see links on this board! Get registered or login to the forums!
Part of the problem is that we do want to eliminate global variables. Such changes are needed for security. But perhaps we should retain the old variables for compatibility, at least until a major 4.0 Patched version comes out. Eventually, these changes should make it into phpNuke itself. (It isn't like FB has done a great job of maintaining compability either hehe)
Joined: Aug 30, 2005 Posts: 243 Location: Flying to close to the sun
Posted:
Thu Nov 10, 2005 12:16 am
64bitguy wrote:
It's bad enough keeping up with revisions, but when changes happen in an existing revision version, it is nearly impossible for webmasters to keep up with where they are, nevermind developers.
I would humbly suggest that there be a freeze on changes to current revisions and new changes be available in either annotated form (for the next revision) or in CVS (for the next revision) or both.
just my two cents.
Steph
HERE HERE 64bitguy, i totally agree
at this point im about to just give up on NS because of all the confusion related to core file edits. and then to find out that the files i have from my version of 3.1 are not the same as other 3.1 revised versions.
64bitguy if you need any extra cash i would be interested in hiring you for some work on my site. just drop me an email at ethugsru@ethugsrus(DOT)net.
Yeah, i had the same problem when i tried installing sentinel, Im using protector but im not sure if its safe... theres alot of exploits on mine, if i were to install sentinel would that fix it?
Joined: Aug 27, 2002 Posts: 16987 Location: Kansas
Posted:
Sun Nov 13, 2005 1:46 pm
You need to upgrade to the latest patch level. Then make sure all of your addons are up to date. Then, get rid of Protector and install NukeSentinel(tm). It is much more secure and thorough.
I was supposed to install sentinel on phpnuke 7.6 patched 3.2b. Im having problems with editing mainfile.php then I looked for solutions here and got headache from all this. What is the right thing to do with patched 3.2b? Sentinel is talking about patched v. 3.1 Im really confused.
Just wanted to add that tooly's post with the link to
Only registered users can see links on this board! Get registered or login to the forums!
also fixed my problems.
I had white screen of death on the forum admin page. I have recently downloaded nuke 7.6 (from nuke.org) and then downloaded patch 3.2 (i thought I had downloaded from nukescripts but obviously not) and installed - however most of the things put in this post were not added to the patch I had. This is probably a problem with different patch versions as mentioned in another post.
All files except for the initial change to the mainfile.php had to be edited.
View next topic View previous topic
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
![[Valid RSS]](http://www.ravenphpscripts.com/images/valid-rss.png "Validate my RSS feed"){kind=small}
:: 
::
