Joined: May 19, 2004 Posts: 363 Location: Ogden, UT
Posted:
Mon Jan 31, 2005 12:54 pm
Ok I've set up a site using Raven's 7.3 disto, chat's patches, NSN Supporters (univ), MS-Analysis v2.1, Nuke Treasury 1.1, NSN Workboard (univ) and NukeSentinel(tm) 2.1.3.
I set up the disto first, and configured everything, including the blocks. Then added each of the above add ons.
Now I can't add blocks or delete information from the MS-Analysis database through Nuke. I can change block information, just can't add anymore or delete any.
This is SO weird, I've never had a nuke site do this! This is also the first site I've upgraded NukeSentinel ... everythiing else is/was on 2.1.1. Could this be it? Should I delete all the add ons and see if that fixes the problem? This will be a lot work, but since the database doesn't change I won't loose any information.
I tried to upload all the core files again (and chat's patches), but that didn't fix it. So I'm thinking it's a incompatable script somewhere, or something not installed correctly (I'm thinking this is really the problem). Could it be a php thing or server security thing? Raven's not hosting this site, it's donated server space from someone else. I know because of this not all functions of NukeSentinel are working right. No error are thrown out, except the header error I haven't fixed yet {blush}.
The site is
Only registered users can see links on this board! Get registered or login to the forums!
Compare a structure dump of the nuke_blocks table to the admin/modules/blocks.php
in the function BlocksAdd at the very end you will see an insert like this make sure the number of values matches the number of fields in the structure dump.
$db->sql_query("insert into ".$prefix."_blocks values (NULL, '$bkey', '$title', '$content', '$url', '$bposition', '$weight', '$active', '$refresh', '$btime', '$blanguage', '$blockfile', '$view', '$expire', '$action', '$subscription')");
Chances are its something related to sommaire or some other addon like that.
Joined: May 19, 2004 Posts: 363 Location: Ogden, UT
Posted:
Mon Jan 31, 2005 1:41 pm
Ok they should be the same. I re did the sql in the database for the blocks and that fixed the problem. I wonder where I get the bad info from .... hmmm.
Oh well that part works
I'll go to the creator of MS-Analysis to see what's up with that one
This is what I have in each. My site was hacked two days ago due to outdated software. I deleted everything and loaded RavenNuke. I then selectively filled some of my tables with data from my old site but didnt change the structure of anything. But I too cannot add blocks no matter what I do. Here is what I have.
Really, it's any block that is there - take your pick. I was going to post the code for two or three but I found that it is ANY block. The Sentinel blocks, User-Info, all of them. I add them and it throws me right back to the admin menu with no block added. Thanks in advance. I'm so sick of trying to keep up with updates and changes that I have slowly been changing each and every one of my sites over to RavenNuke. All told, it will be about 22 sites...
Mike
if(!defined('NUKE_FILE') && !defined('BLOCK_FILE')) { die("You can't access this file directly..."); }
global $db, $prefix, $ab_config;
$total_ips = $db->sql_numrows($db->sql_query("SELECT * FROM `".$prefix."_nsnst_blocked_ips`"));
if(!$total_ips) { $total_ips = 0; }
$content = "<center><img src=\"images/nukesentinel/Sentinel_Medium.png\" alt=\"You have been warned!\" title=\"You have been warned!\"><br />We have caught ".intval($total_ips)." shameful hackers.</center>";
$content .= "<hr><center><a href=\"http://www.nukescripts.net\" target=\"_blank\" title=\"NukeSentinel™ Available at Nuke Scripts Network\">"._AB_NUKESENTINEL." ".$ab_config['version_number']."</a></center>\n";
?>
And here's Survey;
<?php
/************************************************************************/
/* PHP-NUKE: Web Portal System */
/* =========================== */
/* */
/* Copyright (c) 2002 by Francisco Burzi */
/* http://phpnuke.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. */
/************************************************************************/
/* Additional security & Abstraction layer conversion */
/* 2003 chatserv */
/* http://www.nukefixes.com -- http://www.nukeresources.com */
/************************************************************************/
if ( !defined('BLOCK_FILE') ) {
Header("Location: ../index.php");
die();
}
Anybody have any ideas??? When I get home in a bit I'm gonna start from scratch again and recreate the domain and sql to see if something went wacko along the way. Just really excited to get a more secure of nuke on all of my sites and would love to have this weekend to do it. How I missed this site in the past, I have no clue. You guys are a Godsend. Thanks in advance. You guys get too many complaints and not enough thanks on these sites... (Not brown-nosing - been using nuke since the 4.whatever days)
Joined: Aug 29, 2004 Posts: 7487 Location: Arizona
Posted:
Mon Feb 06, 2006 10:13 pm
ohiodarter, this may not be as easy as it sounds or it could be... all depends on how you went about upgrading from 7.3 to 7.6. RavenNuke76 is mostly 7.6 core nuke with version 2.02 having added NSN Groups as well. If you did not upgrade your 7.3 data model to a 7.6 3.1 patched phpBB 2.0.19 data model before you started copying over... (now, that does not solve your specific problem - maybe - but wanted to mention it in case that brought a very large "Ahh Hahhhh" to your mind.
Ok, now for what might be the problem. Assuming you had already properly done the above, RavenNuke76 2.02 also comes with NSN Groups. The script files expect that Step 2 of the installation procedure (to install NSN Groups) was completed successfully. If you had skipped that step in your install, that could be your problem.
However, if you did not skip that step, then the other problem may be with the data you imported into the nuke_modules, nuke_blocks and nuke_messages tables. All of these tables had a new field inserted in the middle of them called "groups". You may not have caught that as I prabably would have made the same mistake too if I hadn't already had NSN Groups installed on my 7.5 site before I upgraded. You may need to look at your INSERT statements for these tables and possibly add an additional column (can just be '' in the values clause) so everything inserts properly.
Finally somebody shedding some light on this. I may be able to figure this out based on what you just said. I did the install verbatum and did not skip anything. Started with a fresh site. Empty database and uploaded all files. I think where I ran into problems was with the importing of data, as you have outlined. Unfortunately for me, I have erased everything and went back to the original distros. I feel much more secure in using what this site releases so I am going back to the drawing board and working with what you gave me. Using what I get from the distro packs leaves me feeling a little naked - no offense to those guys. I'll let you know how I make out. Thanks.
Mike
Well, I thought I had this figured out. Found an error to be in the nuke_blocks structure. As was pointed out, there was an additional field added in Ravens distro. Subscriptions. I added the field and then went through each entry and added ,0 to it. That way the structure had the correct number of fields and the entried all had the same number. Apparently I am still missing something as I cannot add blocks still... I am going to list all three examples. First I will list how it looked in my 7.0 install. Then I will list what Raven has in the distro. Lastly I will list what I changed my original sql to to match Ravens structure. I am hoping that maybe I just did something stupid and somebody will catch it for me. Thanks to anybody who can help out.
ORIGINAL SQL;
Code:
--
-- Table structure for table `nuke_blocks`
--
DROP TABLE IF EXISTS nuke_blocks;
CREATE TABLE nuke_blocks (
bid int(10) NOT NULL auto_increment,
bkey varchar(15) NOT NULL default '',
title varchar(60) NOT NULL default '',
content text NOT NULL,
url varchar(200) NOT NULL default '',
bposition char(1) NOT NULL default '',
weight int(10) NOT NULL default '1',
active int(1) NOT NULL default '1',
refresh int(10) NOT NULL default '0',
time varchar(14) NOT NULL default '0',
blanguage varchar(30) NOT NULL default '',
blockfile varchar(255) NOT NULL default '',
view int(1) NOT NULL default '0',
expire varchar(14) NOT NULL default '0',
action char(1) NOT NULL default '',
PRIMARY KEY (bid),
KEY bid (bid),
KEY title (title)
) TYPE=MyISAM;
DROP TABLE IF EXISTS nuke_blocks;
CREATE TABLE nuke_blocks (
bid int(10) NOT NULL auto_increment,
bkey varchar(15) NOT NULL default '',
title varchar(60) NOT NULL default '',
content text NOT NULL,
url varchar(200) NOT NULL default '',
bposition char(1) NOT NULL default '',
weight int(10) NOT NULL default '1',
active int(1) NOT NULL default '1',
refresh int(10) NOT NULL default '0',
time varchar(14) NOT NULL default '0',
blanguage varchar(30) NOT NULL default '',
blockfile varchar(255) NOT NULL default '',
view int(1) NOT NULL default '0',
expire varchar(14) NOT NULL default '0',
action char(1) NOT NULL default '',
subscription int(1) NOT NULL default '0',
PRIMARY KEY (bid),
KEY bid (bid),
KEY title (title)
) TYPE=MyISAM;
--
-- Dumping data for table `nuke_blocks`
--
INSERT INTO nuke_blocks VALUES (NULL,'','Modules','','','l',2,1,0,'','','block-Modules.php',0,'0','',0);
INSERT INTO nuke_blocks VALUES (NULL,'admin','Administration','<strong><big>�</big></strong> <a href=\"admin.php\">Administration</a><br>\r\n<strong><big>�</big></strong> <a href=\"admin.php?op=adminStory\">NEW Story</a><br>\r\n<strong><big>�</big></strong> <a href=\"admin.php?op=create\">Change Survey</a><br>\r\n<strong><big>�</big></strong> <a href=\"admin.php?op=content\">Content</a><br>\r\n<strong><big>�</big></strong> <a href=\"admin.php?op=logout\">Logout</a>','','l',3,1,0,'985591188','','',2,'0','',0);
INSERT INTO nuke_blocks VALUES (NULL,'','Search','','','l',4,0,3600,'','','block-Search.php',0,'0','',0);
INSERT INTO nuke_blocks VALUES (NULL,'','Languages','','','l',5,0,3600,'','','block-Languages.php',0,'0','',0);
Joined: Aug 27, 2002 Posts: 15235 Location: Kansas
Posted:
Tue Feb 07, 2006 10:15 am
The correct way to do an upgrade to my distro and use your current database is to first run Chatserv's database upgrade scripts to bring your database up to nuke v7.6. Then, use that as your core nuke database. Next, run installSQL.php and skip the core nuke install and just run the NSN Groups and NukeSentinel(tm).
The correct way to do an upgrade to my distro and use your current database is to first run Chatserv's database upgrade scripts to bring your database up to nuke v7.6. Then, use that as your core nuke database. Next, run installSQL.php and skip the core nuke install and just run the NSN Groups and NukeSentinel(tm).
You are my God. I'll try that and report back. I had no clue there was a database upgrade script. Thank you so much. I'll report back.
Mike
BTW, is that file on here? Not seeing it on the other two sites that I always see Chatserv on. Thanks again.
Please forgive me cauz I'm really stupid. Yea, really I am... Let me make sure I am doing things right here.
1. Leave old database intact
2. Load your distro files, overwriting my old files.
3. Use Chatservs Upgrade files from his patched 7.6 distro to go from 7.0 to 7.6 on my old database
4. Run your install and skip the core install portion.
I am under the assumption that I do NOT copy over the changed files from Chatservs distro, only the Upgrade Folder. Your release incorporates his fixes so I am only getting his release to have the upgrade files. This will make the database compatible with your release.
First I did exactly as I outlined above - didnt work. Then I deleted the site completely and started with a fresh sql database and redid the installation from scratch, not skipping anything. Same thing - I give up... Site has been down for four days and dropped from 7th to 11th in the top listings. I'll continue using these distros on all new sites that I do, but none of my existing sites. Too hard to retrieve any old data and have the site working properly. Thanks for the help. I wish it would have worked. This, my largest site, will be my "naked" site...
Well, to be quite honest, I think that if I had a reasonably clean database and not so many framents of this and that installed, it probably would have been fine on my site as well. I have been using Nuke since like 4.5 and never did a clean install - always upgrading. Leaving this behind and that behind. So, as I said, I'm using it on all new sites and my naked site is gonna be reworked and probably started from scratch. Using your releases on it. Got a lot to save and such so I don't lose too much. As I mentioned above, thanks for all that you do. You guys are great.
Joined: Aug 27, 2002 Posts: 15235 Location: Kansas
Posted:
Tue Feb 14, 2006 9:23 am
ohiodarter, this is the exact procedure that I have been doing and just did again last night to someone's site.
- Installed RavenNuke76(tm) v2.02.00 as a brand new install - all tables
- Made a backup copy of the current database, in this case v7.3
- Ran Chat's upgrades from 7.3-7.4, 7.4-7.5, 7.5-7.6 on current database to bring database up to v2.0.19
- Exported only CORE table DATA that I wanted to transfer over from upgraded 7.3 database to my new RavenNuke76(tm) database. You may have others too.
---- authors
---- users
---- bb*
---- stories
---- stories_cat
---- comments
---- message
---- modules
---- blocks
If any of these won't export in then you need to figure out why. 99% of the time it's because of a column that's either missing or extraneous. At this point you should now have your new bas RavenNuke76(tm) v2.02.00 site with your original table data. Now it's just a matter of adding back in your third party modules.
Joined: Aug 29, 2004 Posts: 7487 Location: Arizona
Posted:
Tue Feb 14, 2006 10:10 pm
The only that I would add is to watch out for message, modules and blocks as a new field called *groups* was inserted in the middle of these to accomodate NSN Groups. But, it may be fairly easy to insert an extra empty value within your INSERT statements depending on the number of rows you have...