[RESOLVED] Error msg: Could not get category information

Newbie Joined: Dec 18, 2005 Posts: 10

Hi, I just installed the HTML Newsletter 1.2 on my site - ver 7.5

There are no sql error messages, however, in admins when I attenpt to configure categories, I get the following: Could not get category information.

Any suggestions?

Thanks.

Site Admin Joined: Jul 18, 2005 Posts: 388

Where the tables successfully installed?

Newbie Joined: Dec 18, 2005 Posts: 10

I checked the database, and both tables are there. However, I did notice that the tables have different case:

CREATE TABLE `nuke_HNL_config` (
CREATE TABLE `nuke_hnl_modules` (

I don't know if this makes a difference.

Newbie Joined: Dec 18, 2005 Posts: 10

I think I see the problem: I installed only two tables (I did not run the install script because I did not want to damage anything).

Is there a raw sql install that I can run in myphpadmin?

Thanks

Site Admin Joined: Jul 18, 2005 Posts: 388

Code:

CREATE TABLE `nuke_HNL_config` (
`dlmodule` varchar(50) NOT NULL default '',
`blockmmlimit` tinyint(4) NOT NULL default '0',
`blocknllimit` tinyint(4) NOT NULL default '0',
`scroll` tinyint(4) NOT NULL default '0',
`scrollheight` smallint(6) NOT NULL default '0',
`scrollamount` smallint(6) NOT NULL default '0',
`scrolldelay` smallint(6) NOT NULL default '0',
`version` varchar(10) NOT NULL default ''
) TYPE=MyISAM;

#
# Dumping data for table `nuke_HNL_config`
#

INSERT INTO `nuke_HNL_config` VALUES ('downloads', 2, 2, 1, 180, 2, 25, 'beta 0.1');

#
# Table structure for table `nuke_hnl_modules`
#

CREATE TABLE `nuke_hnl_modules` (
`mid` INT(10) NOT NULL,
`supported_yn` TINYINT(1) NOT NULL,
`saved_latest` INT(3) NOT NULL,
PRIMARY KEY (`mid`)
);

Newbie Joined: Dec 18, 2005 Posts: 10

Thanks, I installed those tables successfully, but the:

CREATE TABLE `nuke_hnl_categories`

and

CREATE TABLE nukr_hnl_newsletters

Regards.

Newbie Joined: Dec 18, 2005 Posts: 10

Hi, looked into the hnlinst.php and extracted the following tables that are missing. Let me know if this looks right:

CREATE TABLE `nuke_hnl_categories` (
`cid` int(11) NOT NULL auto_increment,
`ctitle` varchar(50) NOT NULL default '',
`cdescription` text NOT NULL,
`cblocklimit` int(4) NOT NULL default '10',
PRIMARY KEY (`cid`)
);

INSERT INTO `nuke_hnl_categories` VALUES (1, '*Unassigned*', 'This is a catch-all category where newsletters can default to or if all other categories are removed. Do NOT remove this category! This category of newsletters are only shown to the Admins. ', 5)");
INSERT INTO `nuke_hnl_categories` VALUES (2, 'Archived Newsletters', 'This category is for newsletter subscribers.', 5)");
INSERT INTO `nuke_hnl_categories` VALUES (3, 'Archived Mass Mails', 'This category is used for mass mails.', 5)");;

CREATE TABLE `nuke_hnl_newsletters` (
`nid` int(11) NOT NULL auto_increment,
`cid` int(11) NOT NULL default '1',
`topic` varchar(100) NOT NULL default '',
`sender` varchar(20) NOT NULL default '',
`filename` varchar(32) NOT NULL default '',
`datesent` date default NULL,
`view` int(1) NOT NULL default '0',
`groups` text NOT NULL,
`hits` int(11) NOT NULL default '0',
PRIMARY KEY (`nid`),
KEY cid (`cid`);

INSERT INTO `nuke_hnl_newsletters` VALUES (1, 1, 'PREVIEW Newsletter File', 'Admin', 'tmp.php', '0000-00-00', 99, '', 0)");
INSERT INTO `nuke_hnl_newsletters` VALUES (2, 1, 'Tested Email Temporary File', 'Admin', 'testemail.php', '0000-00-00', 99, '', 0)");

CREATE TABLE `nuke_hnl_config` (
`hnlmodulenm` varchar(32) NOT NULL default 'HTML_Newsletter',
`dlmodule` varchar(50) NOT NULL default '',
`blocklimit` tinyint(4) NOT NULL default '0',
`scroll tinyint` (4) NOT NULL default '0',
`scrollheight` smallint(6) NOT NULL default '0',
`scrollamount` smallint(6) NOT NULL default '0',
`scrolldelay` smallint(6) NOT NULL default '0',
`version` varchar(10) NOT NULL default '',
`showhits` tinyint(1) NOT NULL default '0',
`showdates` tinyint(1) NOT NULL default '0',
`showsender` tinyint(1) NOT NULL default '0',
`showcategories` tinyint(1) NOT NULL default '0',
`nsngroups` tinyint(1) NOT NULL default '0',
`debugmode` tinyint(1) NOT NULL default '0',
`latest_news` tinyint(4) NOT NULL default '0',
`latest_downloads` tinyint(4) NOT NULL default '0',
`latest_links` tinyint(4) NOT NULL default '0',
`latest_forums` tinyint(4) NOT NULL default '0',
`latest_reviews` tinyint(4) NOT NULL default '0')");

INSERT INTO `nuke_hnl_config` VALUES ('HTML_Newsletter', 'downloads', 10, 1, 180, 2, 100, '1.2', 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0)");

/Thanks.

Site Admin Joined: Jul 18, 2005 Posts: 388

Oops, sorry!
Having re-checked that sql dump, I realise that is not the one in use. Have no idea were it came from but the one below is correct, I just grabbed it from my database to be certain.

Code:

-- Table structure for table `nuke_hnl_categories`
--

CREATE TABLE `nuke_hnl_categories` (
`cid` int(11) NOT NULL auto_increment,
`ctitle` varchar(50) NOT NULL default '',
`cdescription` text NOT NULL,
`cblocklimit` int(4) NOT NULL default '10',
PRIMARY KEY (`cid`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=4 ;

--
-- Dumping data for table `nuke_hnl_categories`
--

INSERT INTO `nuke_hnl_categories` (`cid`, `ctitle`, `cdescription`, `cblocklimit`) VALUES (1, '*Unassigned*', 'This is a catch-all category where newsletters can default to or if all other categories are removed. Do NOT remove this category! This category of newsletters are only shown to the Admins. ', 5);
INSERT INTO `nuke_hnl_categories` (`cid`, `ctitle`, `cdescription`, `cblocklimit`) VALUES (2, 'Archived Newsletters', 'This category is for newsletter subscribers.', 5);
INSERT INTO `nuke_hnl_categories` (`cid`, `ctitle`, `cdescription`, `cblocklimit`) VALUES (3, 'Archived Mass Mails', 'This category is used for mass mails.', 5);

-- --------------------------------------------------------

--
-- Table structure for table `nuke_hnl_config`
--

CREATE TABLE `nuke_hnl_config` (
`hnlmodulenm` varchar(32) NOT NULL default 'HTML_Newsletter',
`dlmodule` varchar(50) NOT NULL default '',
`blocklimit` tinyint(4) NOT NULL default '0',
`scroll` tinyint(4) NOT NULL default '0',
`scrollheight` smallint(6) NOT NULL default '0',
`scrollamount` smallint(6) NOT NULL default '0',
`scrolldelay` smallint(6) NOT NULL default '0',
`version` varchar(10) NOT NULL default '',
`showhits` tinyint(1) NOT NULL default '0',
`showdates` tinyint(1) NOT NULL default '0',
`showsender` tinyint(1) NOT NULL default '0',
`showcategories` tinyint(1) NOT NULL default '0',
`nsngroups` tinyint(1) NOT NULL default '0',
`debugmode` tinyint(1) NOT NULL default '0',
`latest_news` tinyint(4) NOT NULL default '0',
`latest_downloads` tinyint(4) NOT NULL default '0',
`latest_links` tinyint(4) NOT NULL default '0',
`latest_forums` tinyint(4) NOT NULL default '0',
`latest_reviews` tinyint(4) NOT NULL default '0'
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

--
-- Dumping data for table `nuke_hnl_config`
--

INSERT INTO `nuke_hnl_config` (`hnlmodulenm`, `dlmodule`, `blocklimit`, `scroll`, `scrollheight`, `scrollamount`, `scrolldelay`, `version`, `showhits`, `showdates`, `showsender`, `showcategories`, `nsngroups`, `debugmode`, `latest_news`, `latest_downloads`, `latest_links`, `latest_forums`, `latest_reviews`) VALUES ('HTML_Newsletter', 'downloads', 10, 1, 180, 2, 100, '1.2', 1, 1, 1, 1, 0, 0, 10, 10, 10, 20, 10);

-- --------------------------------------------------------

--
-- Table structure for table `nuke_hnl_newsletters`
--

CREATE TABLE `nuke_hnl_newsletters` (
`nid` int(11) NOT NULL auto_increment,
`cid` int(11) NOT NULL default '1',
`topic` varchar(100) NOT NULL default '',
`sender` varchar(20) NOT NULL default '',
`filename` varchar(32) NOT NULL default '',
`datesent` date default NULL,
`view` int(1) NOT NULL default '0',
`groups` text NOT NULL,
`hits` int(11) NOT NULL default '0',
PRIMARY KEY (`nid`),
KEY `cid` (`cid`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=3 ;

--
-- Dumping data for table `nuke_hnl_newsletters`
--

INSERT INTO `nuke_hnl_newsletters` (`nid`, `cid`, `topic`, `sender`, `filename`, `datesent`, `view`, `groups`, `hits`) VALUES (1, 1, 'PREVIEW Newsletter File', 'Admin', 'tmp.php', '0000-00-00', 99, '', 0);
INSERT INTO `nuke_hnl_newsletters` (`nid`, `cid`, `topic`, `sender`, `filename`, `datesent`, `view`, `groups`, `hits`) VALUES (2, 1, 'Tested Email Temporary File', 'Admin', 'testemail.php', '0000-00-00', 99, '', 0);

Newbie Joined: Dec 18, 2005 Posts: 10

IT's WORKING:-) Thanks!

Now I need to get the banner and the preview features working.

Is there a thread for these issues?

Regards.

Newbie Joined: Dec 18, 2005 Posts: 10

Hi, I have the banner working:-)

Site Admin/Owner Joined: Feb 12, 2005 Posts: 1360

mdwilson wrote:

IT's WORKING:-) Thanks!

Now I need to get the banner and the preview features working.

Is there a thread for these issues?

Regards.

Wow. I go away for a day and look what I come back to. Laughing

Guardian, many thanks for helping mdwilson out.

mdwilson, I don't understand why you wouldn't follow the instructions and use the installer. That is what it is used for. It will NOT mess up anything else within your nuke installation. I do not provide the raw SQL because I do not want to temp someone who is upgrading to use the raw SQL by mistake! If they had done that between 1.1 and 1.2 it would have ruined their HTML Newsletter installation.

What is not working with the banners and preview? See this thread for banners:

http://montegoscripts.com/ftopict-13.html

What exactly is happening with preview?

Thanks

Site Admin/Owner Joined: Feb 12, 2005 Posts: 1360

mdwilson wrote:

Hi, I have the banner working:-)

Sorry. You already caught it! Good job!

Newbie Joined: Dec 18, 2005 Posts: 10

HI.

The reason I did not run the installer is that I have the Nuke Hall multi-portal script installed on my site which is supporting numerous sub-domain nuke sites.

And I was unsure of how the installer would behave. Also I would want to be able to offer all of my portal (dorms) members the option to have the newsletter feature on their site.

To do this, I will have to install it manually for each dorm, which I have done on several occassions with other scripts.

Although it is working fine (except for the preview newsletter), I still have some unique things I need to work out such as the themes logos (each site has its own images directory and logo) before I can offer the newsletter feature to other dorms.

Still another item to resolve are the themes offered; currently all themes are in one location which means all dorms will have access to them all versus have their own newsletter theme directory.

But for the moment, I want to get it working properly on my main dorm 1st.

Regards.

Site Admin/Owner Joined: Feb 12, 2005 Posts: 1360

mdwilson wrote:

The reason I did not run the installer is that I have the Nuke Hall multi-portal script installed on my site which is supporting numerous sub-domain nuke sites.

And I was unsure of how the installer would behave. Also I would want to be able to offer all of my portal (dorms) members the option to have the newsletter feature on their site.

To do this, I will have to install it manually for each dorm, which I have done on several occassions with other scripts.

Hhhmmm... Never heard of such a "beast". I may need to rethink my distribution strategy. However, you would have had a serious issue with an upgrade from 1.1 to 1.2 because it also involved existing newsletter file upgrades and not just the database. I am trying to avoid that in the future.

Quote:

Although it is working fine (except for the preview newsletter),

You still haven't told me what isn't working exactly! I can't help you if you don't tell me what is it doing? Are you getting any error messages? Are you getting the pop-up browser window, but with no text?

I am sure you have already looked at this, but you need to enable pop-ups for your domain IF your computer has a pop-up blocker installed.

Quote:

But for the moment, I want to get it working properly on my main dorm 1st.

Since I have never heard of this "Nuke Hall" script I am not sure how it is all structured. Are you saying that you really have only ONE set of nuke script files and are running multiple databases? When you said sub-domains, that led me to believe that each nuke installation is really separate, under each sub-domain's file structure.

If all your dorms would be running off the same set of scripts you may be able to give each dorm their own template. Each template directory is self-contained and unique to the individual newsletter template. You would replace the logo.gif/jpg/png file with their logo. However, if you would be supporting a large number of these, the template list may get too large.

How is the database structured in this environment? Is it ONE mySQL database and each subdomain has its own nuke prefix? If so, how does the config.php work my subdomain? The installer uses the $prefix variable, so if that is set properly, it should install properly. However, ALL newsletter files would still be placed into the same directory.

Since this type of an environment was never thought of and certainly is non-standard, I had not even considered what would happen if two people created a newsletter within a second of each other. Still a remote chance, but one could trample the other.

If you want/need additional help, please be specific with what the issue is.

Regards,
montego

Site Admin Joined: Jul 18, 2005 Posts: 388

I seem to remember something about this system a while ago.
If I remember correctly, each nuke site has its own set of files but a lot of the DB data is 'shared' to allow each user to access every 'dorm' i.e user accounts and preferences are shared across the network of dorms.
I was of the opninion at the time, no disrespect to mdwilson, that this sort of system was vulnerable to XXS and it would seem possible, by the very nature that the various dorms need to communicated to one DB there is no way to effectively lock down referers.