post-nuke-users — Users List. Questions and support

[Post-nuke-users] Download Module Issue

[Robert S. <ro...@co...>]

Hi

If I add an url to the download section of the site, the link is not added
to the download list, however the text says Membership Forms ()

There are 2 Downloads and 1 Categories in the database.

Clicking on the membership forms section just takes me back to the main
download page. I have checked the permissions of the modules, and they are
all correct.

The url to access the site is http://www.cobraclub.com/index.php root takes
you to the main site, I am just trialing Postnuke to find out if it does
what I want.


Best Regards

Robert

[Post-nuke-users] Error message in right column blocks

[McCoy, A. <am...@go...>]

Can anyone help me figure out where the MySQL error messages are coming
from in the right column of my site? The URL is
http://64.224.99.12/index.php. All other database connections for the
site seem to be working fine. I just can't figure out why the blocks in
the right column (under the ads) won't show up.

Any help with this would be greatly appreciated.

Thanks!

Alan McCoy
am...@go...

Re[2]: SV: [Post-nuke-users] Problem with upgrading php

[jotajota <jot...@jo...>]

More on the passwords issue here:

http://www.postnuke.com/modules.php?op=modload&name=News&file=article&sid=1440
http://www.postnuke.com/modules.php?op=modload&name=News&file=article&sid=1440
http://www.postnuke.com/modules.php?op=modload&name=News&file=article&sid=1440

In case it is wrapped:

http://makeashorterlink.com/?I13752B4

jotajota


> I am not in the mood to upgrade to 0.7 now for I would have to rewrite
> many modules made to work with 0.64 and so the theme and all of
> that... and we already are some two or three weeks behind schedule :/

> My host has made something that I would not blame them for: upgrading
> the software (is something far unusual), what I blame them for (and
> ahve written them about) is for not adverting it in advance... but
> nobody's perfect :)

> I am afraid they will be switching to safe_mode one of these days...

> jotajota

>> I'm not positively sure about it, but an upgrade to 0.7 will fix your
>> problem.

>> But then U say U have too many costum modules.
>> Which modules does your site posses?

>> And if i was U i would call my host and say that they better fix the
>> problem.
>> As they are responsible for the change.

>> -----Oprindelig meddelelse-----
>> Fra: jotajota [mailto:jot...@jo...]
>> Sendt: 14. januar 2002 12:17
>> Til: pos...@li...
>> Emne: [Post-nuke-users] Problem with upgrading php


>> Hola

>> My host has just upgraded php to version 4.1.1 and suddenly my two pn
>> sites have stopped working :/. Pn versions are 0.6.2 (yes, I know,
>> I'll upgrade when I have some time) and 0.6.4 (this one should be
>> working soon with this version: upgrading to 0.7.x is not an option at
>> this time - many custom modules)

>> The problem appears when new users try to access the site, the
>> password that the site gives to them doesn't work. The same happens
>> with old users that try to change their passwords. I have taken a look
>> at the nuke_users and this is what I've found in the password field:

>> Old user: 6LVu/xe07tCRw
>> New user: $1$C3PWQigb$njBSgrygCxpDe0fb6VE3l0

>> Seems clear to me that there has been some kind of change in the
>> default behaviour of the function used to crypt the password. However
>> this default does not apply to the function that takes the user input
>> and compares it to the database. I should change one of them, but I
>> don't know where they are or what to change them to.

>> Does anyone have a clue?





>> ----
>>  jotajota                          mailto:jot...@jo...


>> _______________________________________________
>> Post-nuke-users mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/post-nuke-users










-- 
 jotajota                            mailto:jot...@jo...

Re: SV: [Post-nuke-users] Problem with upgrading php

[jotajota <jot...@jo...>]

I am not in the mood to upgrade to 0.7 now for I would have to rewrite
many modules made to work with 0.64 and so the theme and all of
that... and we already are some two or three weeks behind schedule :/

My host has made something that I would not blame them for: upgrading
the software (is something far unusual), what I blame them for (and
ahve written them about) is for not adverting it in advance... but
nobody's perfect :)

I am afraid they will be switching to safe_mode one of these days...

jotajota

> I'm not positively sure about it, but an upgrade to 0.7 will fix your
> problem.

> But then U say U have too many costum modules.
> Which modules does your site posses?

> And if i was U i would call my host and say that they better fix the
> problem.
> As they are responsible for the change.

> -----Oprindelig meddelelse-----
> Fra: jotajota [mailto:jot...@jo...]
> Sendt: 14. januar 2002 12:17
> Til: pos...@li...
> Emne: [Post-nuke-users] Problem with upgrading php


> Hola

> My host has just upgraded php to version 4.1.1 and suddenly my two pn
> sites have stopped working :/. Pn versions are 0.6.2 (yes, I know,
> I'll upgrade when I have some time) and 0.6.4 (this one should be
> working soon with this version: upgrading to 0.7.x is not an option at
> this time - many custom modules)

> The problem appears when new users try to access the site, the
> password that the site gives to them doesn't work. The same happens
> with old users that try to change their passwords. I have taken a look
> at the nuke_users and this is what I've found in the password field:

> Old user: 6LVu/xe07tCRw
> New user: $1$C3PWQigb$njBSgrygCxpDe0fb6VE3l0

> Seems clear to me that there has been some kind of change in the
> default behaviour of the function used to crypt the password. However
> this default does not apply to the function that takes the user input
> and compares it to the database. I should change one of them, but I
> don't know where they are or what to change them to.

> Does anyone have a clue?





> ----
>  jotajota                          mailto:jot...@jo...


> _______________________________________________
> Post-nuke-users mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/post-nuke-users






-- 
 jotajota                            mailto:jot...@jo...

[Post-nuke-users] Problem with upgrading php

[jotajota <jot...@jo...>]

Hola

My host has just upgraded php to version 4.1.1 and suddenly my two pn
sites have stopped working :/. Pn versions are 0.6.2 (yes, I know,
I'll upgrade when I have some time) and 0.6.4 (this one should be
working soon with this version: upgrading to 0.7.x is not an option at
this time - many custom modules)

The problem appears when new users try to access the site, the
password that the site gives to them doesn't work. The same happens
with old users that try to change their passwords. I have taken a look
at the nuke_users and this is what I've found in the password field:

Old user: 6LVu/xe07tCRw
New user: $1$C3PWQigb$njBSgrygCxpDe0fb6VE3l0

Seems clear to me that there has been some kind of change in the
default behaviour of the function used to crypt the password. However
this default does not apply to the function that takes the user input
and compares it to the database. I should change one of them, but I
don't know where they are or what to change them to.

Does anyone have a clue?





----
 jotajota                          mailto:jot...@jo...

Re: [Post-nuke-users] FW: Cannot Add Header Information

[John C. <ad...@di...>]

Your config.php probably has a carriage return after the closing php tag.


----- Original Message -----
From: "Robert Stanley" <ro...@co...>
To: <pos...@li...>
Sent: Sunday, January 13, 2002 9:00 PM
Subject: [Post-nuke-users] FW: Cannot Add Header Information


> Sorry
>
> The error message is.
>
> Warning: Cannot add header information - headers already sent by (output
> started at /home/www/cobraclub/html/config.php:412) in
> /home/www/cobraclub/html/modules/NS-User/tools.php on line 34
> Logging you in, hang tight!
>
> but does not log me in.
>
> I am running the following.
>
> Apache/1.3.20 (Unix) PHP/4.0.6
>
> I have installed OK, and checked the database and that has the username
and
> password in, but I cannot login to access any admin functions.
>
> Best Regards
>
> Robert
>
> -----Original Message-----
> From: Robert Stanley [mailto:ro...@co...]
> Sent: 14 January 2002 01:56
> To: pos...@li...
> Subject: Cannot Add Header Information
>
>
> Hi
>
> I need a bit of help with the following error message.
>
>
> _______________________________________________
> Post-nuke-users mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/post-nuke-users
>
>

[Post-nuke-users] FW: Cannot Add Header Information

[Robert S. <ro...@co...>]

Sorry

The error message is.

Warning: Cannot add header information - headers already sent by (output
started at /home/www/cobraclub/html/config.php:412) in
/home/www/cobraclub/html/modules/NS-User/tools.php on line 34
Logging you in, hang tight!

but does not log me in.

I am running the following.

Apache/1.3.20 (Unix) PHP/4.0.6

I have installed OK, and checked the database and that has the username and
password in, but I cannot login to access any admin functions.

Best Regards

Robert

-----Original Message-----
From: Robert Stanley [mailto:ro...@co...]
Sent: 14 January 2002 01:56
To: pos...@li...
Subject: Cannot Add Header Information


Hi

I need a bit of help with the following error message.

[Post-nuke-users] Cannot Add Header Information

[Robert S. <ro...@co...>]

Hi

I need a bit of help with the following error message.

[Post-nuke-users] Document on Structured Text?

[Devanesan <sd...@ba...>]

Hi,

  Where can I find a document for the structured text used in postnuke?. It 
will be helpful for the non-technical staffs.

Cheers
Devanesan.

Re: [Post-nuke-users] Sucess->Problem upgrading from old php-nuke

[John C. <ad...@di...>]

Feel free to copy me.  Nice catch on that!  I'll upload it to SourceForge
with the other upgrade scripts that are there.

jc
----- Original Message -----
From: <jg...@fl...>
To: <pos...@li...>
Sent: Wednesday, January 09, 2002 5:10 PM
Subject: [Post-nuke-users] Sucess->Problem upgrading from old php-nuke


> I have edited and combined the following php-nuke upgrade scripts:
> upgrade1-25.php
> upgrade25-35.php
> upgrade35-4.php
> upgrade42_43.php
> upgrade43-44.php
> upgrade44-50.php
>
> I skipped upgrade2-25.php because it appears to be a duplicate of
> upgrade1-25.php.  After adding some comments and debug type stuff I
> found I recieved this error:
>
> Alteration of stories table failed! #3
> 1064: You have an error in your SQL syntax near 'fulltext bodytext text'
> at line 1
>
> The #3 was added by me to differentiate a little quicker where the
> script was failing.  This code is located in the upgrade25-35.php file.
>  Here is the code block:
>
> $result = mysql_query(
>     "ALTER TABLE stories
>     CHANGE fulltext bodytext text");
> if (!$result) {
>     echo "Alteration of stories table failed! #3<br>"
>     .mysql_errno(). ": ".mysql_error(). "<br>";
>     return;
> }
>
> I've formatted it a little to (hopefully) make it more readable.  I
> surfed over to:
> http://www.mysql.com/doc/A/L/ALTER_TABLE.html
>
> According to them, the syntax for CHANGE is:
> CHANGE [COLUMN] old_col_name create_definition [FIRST | AFTER column_name]
>
> I wasn't sure what to do so I commented out that particular block hoping
> the post-nuke conversion scripts would handle it (after I thought about
> it, it made sense they didn't, this is php-nuke v2.5-v3.5).  After
> commenting it out I ran the upgrade scripts without error and then ran
> the post-nuke upgrade/conversion scripts.  Everything ran smoothly.
>  When I pressed finish it took me to the sites index page and I got this
> error after the "Welcome to PostNuke" article:
> DB Error: getArticles: 1054: Unknown column 'nuke_stories.bodytext' in
> 'field list'
>
> After a little investigation I noticed that my php-nuke-pre4.4 database
> table nuke.stories had a column called resttext.  After comparing this
> with the post-nuke.sql script for a new install I discovered that there
> was a column in the $prefix_stories table called bodytext.  It appears
> there was a typo in the upgrade scripts for php-nuke 2.5-3.5.  The
> CHANGE statement should read:
>
> CHANGE resttext bodytext text
>
> After I implemented this in my upgrade script I have finally succedded
> in converting the php-nuke-pre4.4 database to a post-nuke .72.  Yeah
> baby!!!!!!
>
> Now I'm off to seperate the sludge which appears to have crept into a
> few of the other areas.
>
> I have the custom script with comments available and would like to send
> it to someone at postnuke but don't know who.
>
> Thanks for all the quick responses and tips.
>
> Jesse
>
>
>
>
>
> _______________________________________________
> Post-nuke-users mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/post-nuke-users
>
>

[Post-nuke-users] Sucess->Problem upgrading from old php-nuke

[<jg...@fl...>]

I have edited and combined the following php-nuke upgrade scripts:
upgrade1-25.php
upgrade25-35.php
upgrade35-4.php
upgrade42_43.php
upgrade43-44.php
upgrade44-50.php

I skipped upgrade2-25.php because it appears to be a duplicate of 
upgrade1-25.php.  After adding some comments and debug type stuff I 
found I recieved this error:
 
Alteration of stories table failed! #3
1064: You have an error in your SQL syntax near 'fulltext bodytext text' 
at line 1

The #3 was added by me to differentiate a little quicker where the 
script was failing.  This code is located in the upgrade25-35.php file. 
 Here is the code block:

$result = mysql_query(
    "ALTER TABLE stories
    CHANGE fulltext bodytext text");
if (!$result) {
    echo "Alteration of stories table failed! #3<br>"
    .mysql_errno(). ": ".mysql_error(). "<br>";
    return;
}

I've formatted it a little to (hopefully) make it more readable.  I 
surfed over to:
http://www.mysql.com/doc/A/L/ALTER_TABLE.html

According to them, the syntax for CHANGE is:
CHANGE [COLUMN] old_col_name create_definition [FIRST | AFTER column_name]

I wasn't sure what to do so I commented out that particular block hoping 
the post-nuke conversion scripts would handle it (after I thought about 
it, it made sense they didn't, this is php-nuke v2.5-v3.5).  After 
commenting it out I ran the upgrade scripts without error and then ran 
the post-nuke upgrade/conversion scripts.  Everything ran smoothly. 
 When I pressed finish it took me to the sites index page and I got this 
error after the "Welcome to PostNuke" article:
DB Error: getArticles: 1054: Unknown column 'nuke_stories.bodytext' in 
'field list'

After a little investigation I noticed that my php-nuke-pre4.4 database 
table nuke.stories had a column called resttext.  After comparing this 
with the post-nuke.sql script for a new install I discovered that there 
was a column in the $prefix_stories table called bodytext.  It appears 
there was a typo in the upgrade scripts for php-nuke 2.5-3.5.  The 
CHANGE statement should read:

CHANGE resttext bodytext text

After I implemented this in my upgrade script I have finally succedded 
in converting the php-nuke-pre4.4 database to a post-nuke .72.  Yeah 
baby!!!!!!

Now I'm off to seperate the sludge which appears to have crept into a 
few of the other areas.

I have the custom script with comments available and would like to send 
it to someone at postnuke but don't know who.  

Thanks for all the quick responses and tips.

Jesse

Re: [Post-nuke-users] version of php-nuke a site is running

[<jg...@fl...>]

Andy Burnham - Sun Uk - VSP - Systems Engineer wrote:

>>>Does anyone know how to find out which version of
>>>php-nuke a site is running? (Sorry about the OT question)
>>>
>The stats page will tell you, if it has one:
>eg: http://www.megalithic.co.uk/stats.php
>
>Good luck, upgrading can be a tricky process, I'm stuck with Nuke 5.0 as I made 
>too many database hacks.
>Cheers,
>Andy
>
Thanks Andy.  Turns out they didn't like the default stats and installed 
something else to handle it :(.  I wouldn't have known that without your 
tip.  Another thing to deal with ;)

Jesse

Re: [Post-nuke-users] Problems with prefix sharing in PNtables

[John C. <ad...@di...>]

Just edit the pntables.php to reflect the tables that you want to share.
One table from one of the sites will become the primary, and the other will
not be used.


----- Original Message -----
From: "Tom Ahasverussen" <to...@pe...>
To: <pos...@li...>
Sent: Tuesday, January 08, 2002 2:25 PM
Subject: [Post-nuke-users] Problems with prefix sharing in PNtables


> What kind of Prefix settings do i have to change if i want 2 portals in
the
> same data base with these following prefixes:
>
> Prefix1: nuke
> Prefix2: site2
>
> to share it's userdatabase.
> I have tried before to change it manually but i don't know the correct
> syntax.
> Because Postnuke makes it default to be a value.
> What i want is to hardcode it in site2.
>
> Best Regards
> Tom Ahasverussen
>
>
>
> _______________________________________________
> Post-nuke-users mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/post-nuke-users
>
>

[Post-nuke-users] Problems with prefix sharing in PNtables

[Tom A. <to...@pe...>]

What kind of Prefix settings do i have to change if i want 2 portals in the
same data base with these following prefixes:

Prefix1: nuke
Prefix2: site2

to share it's userdatabase.
I have tried before to change it manually but i don't know the correct
syntax.
Because Postnuke makes it default to be a value.
What i want is to hardcode it in site2.

Best Regards
Tom Ahasverussen

[Post-nuke-users] How do i fix the Download sektion issue in Rogue 702?

[Tom A. <to...@pe...>]

Does anyone know?

[Post-nuke-users] version of php-nuke a site is running

[Andy B. - S. Uk - V. - S. E. <And...@Su...>]

> > Does anyone know how to find out which version of
> > php-nuke a site is running? (Sorry about the OT question)
> 
The stats page will tell you, if it has one:
eg: http://www.megalithic.co.uk/stats.php

Good luck, upgrading can be a tricky process, I'm stuck with Nuke 5.0 as I made 
too many database hacks.
Cheers,
Andy

[Post-nuke-users] UTCache v2.0.4

[TooGooB <to...@be...>]

UTCache 2.0.4
http://prowebdesignservices.com

I created the program to install the maps in your cache folder
 (can also un-install, and or delete cache files or maps)
=20
 Added check for temp files in the root folder.

 Added a feature that scans installed maps for any "custom"
 files that are referenced in it like, sounds, music, textures, system =
files, etc...
 (..might be useful, I dont know)

 requirments:
 16 megs ram
 p-100 + CPU
 Unreal Tournament v4.3.6+
 Win95B/98/Me/XP
 =20
 This program is freeware, if shared as shipped.

  "...for our fallen, you are not forgotten."
  =BB=AB from the WinWareZ staff =BB=AB

 ..any questions or ideas,
 We...@pr...

Re: [Post-nuke-users] Re: Problem upgrading from old php-nuke

[<jg...@fl...>]

jim barchuk wrote:

>[snip]
>
>>Now The page is loading but I get this error right after the Welcome to
>>Postnuke block:
>>
>>DB Error: getArticles: 1146: Table 'nuke.osc_news_stories_cat' doesn't exist
>>
>
>Never seen exactly that one before either but that table name sure doesn't
>look right. Prefix should be 'nuke_' not 'nuke.'. (I already tossed your
>previous message but I'm pretty sure that it said 'nuke'.) Are other table
>names similar or is that the only one like that? Or is your prefix
>'nuke.osc'?
>
Actually nuke is the database name, osc_news is the prefix.  It seems 
the upgrade scripts tack on the table names as _table_name.  So I'm 
assuming that the name of the table being inserted is _stories_cat.  I 
tried doing this without prefixes as well which is why I'm assuming that.

>
>[snip]
>
>OK, if it's still broke... :) ...
>
>Aside from checking cookies another thing I do when repetitively trying to
>upgrade is to drop and recreate the new database via mysqladmin. I don't
>trust -anything- old lying around even vaguely related when trying to
>create something new.
>
I've been using mysql directly.  I used this:
 mysqldump -u root -p > old_php_nuke_db.sql

to get the original dump.  No on another machine I have been testing it. 
 I basically drop the database after each attempt, re-create it in 
mysql, then do a:
mysql -u root -p < old_php_nuke_db.sql

So I always start with the original database.  Each time I've been 
applying the patches (from php-nuke) and then use the post-nuke 
installer.  It's tedious, but I'm making headway slowly.  I can't 
imagine doing it without all these scripts ;)

>
>
>>Does anyone know how to find out which version of
>>php-nuke a site is running? (Sorry about the OT question)
>>
>
>No, but realated to that maybe it'd be a better idea to upgrade the php-
>version of the site to something more current? I'm testing only 5.? (I
>forget exactly which.)
>
I had originally thought of this but thought it would be easier to just 
upgrade from 4.4 since the post-nuke installer is just so darn nice ;) 
 The real problem here is I'm not starting from a known state--I don't 
know what version of php-nuke this is :(

>
>>Does anyone know what this table's (stories_cat) ancestry is (was it
>>always in php-nuke/post-nuke or was it added to post-nuke based on a
>>previous table)?  Maybe I can create an sql statement to convert the old
>>table to the new table.
>>
>
>It exists in php- 5.?. The PN conversion scripts are in ~/install. If you
>find anything interesting/broken please post it to sourceforge postnuke
>bugs.
>
>Have a :) day!
>
>jb
>
That's good to know!  I'll check the php-nuke "upgrade" scripts and see 
if there is something there.  If the table exists there (in php-nuke 
5.x) I should be able to upgrade to that and then convert over and get 
it working.

Thanks again for all your prompt reponses. I guess it shouldn't be 
surprising but it is :)

Jesse

Re: [Post-nuke-users] Re: Problem upgrading from old php-nuke

[jim b. <jb...@jb...>]

Hi Jesse!

> Thanks for the quick response Mike.  That fixed my first problem.

Cool. Glad that worked, because those other errors were *totally*
unfamiliar to me. :)

> Now The page is loading but I get this error right after the Welcome to
> Postnuke block:
>
> DB Error: getArticles: 1146: Table 'nuke.osc_news_stories_cat' doesn't exist

Never seen exactly that one before either but that table name sure doesn't
look right. Prefix should be 'nuke_' not 'nuke.'. (I already tossed your
previous message but I'm pretty sure that it said 'nuke'.) Are other table
names similar or is that the only one like that? Or is your prefix
'nuke.osc'?

If yes to prefix nuke.osc just for fun I'd try again without the '.' in
there. Can't recall if it's a legal table name char but it definitely
requires extra coding/consideration when used in a column name. Whether
it's legal or not it's always easier to stick to known legal chars such as
hyphen and underscore.

OK, if it's still broke... :) ...

Aside from checking cookies another thing I do when repetitively trying to
upgrade is to drop and recreate the new database via mysqladmin. I don't
trust -anything- old lying around even vaguely related when trying to
create something new.

> Does anyone know how to find out which version of
> php-nuke a site is running? (Sorry about the OT question)

No, but realated to that maybe it'd be a better idea to upgrade the php-
version of the site to something more current? I'm testing only 5.? (I
forget exactly which.)

> Does anyone know what this table's (stories_cat) ancestry is (was it
> always in php-nuke/post-nuke or was it added to post-nuke based on a
> previous table)?  Maybe I can create an sql statement to convert the old
> table to the new table.

It exists in php- 5.?. The PN conversion scripts are in ~/install. If you
find anything interesting/broken please post it to sourceforge postnuke
bugs.

Have a :) day!

jb

-- 
jim barchuk
jb...@jb...

Re: [Post-nuke-users] Re: Problem upgrading from old php-nuke

[<jg...@fl...>]

Michael Walter Mistak wrote:

> I'm not sure if anyone has answered this problem but you may need to 
> go into your cookies directory on the machine you are trying to view 
> the page on, shut down and restart the browser, and attempt to view 
> the page again.
>
> you may be trying to view the page using a cookie from phpnuke 4.4 or 
> even 3.5.
> -------
> Mike

Thanks for the quick response Mike.  That fixed my first problem.  

Now The page is loading but I get this error right after the Welcome to 
Postnuke block:

DB Error: getArticles: 1146: Table 'nuke.osc_news_stories_cat' doesn't exist

It appears I didn't upgrade/convert the database properly.  I have the 
mysql dump of the original so it's no problem to keep retrying till I 
get it right.  Does anyone know how to find out which version of 
php-nuke a site is running? (Sorry about the OT question)

Does anyone know what this table's (stories_cat) ancestry is (was it 
always in php-nuke/post-nuke or was it added to post-nuke based on a 
previous table)?  Maybe I can create an sql statement to convert the old 
table to the new table.

TIA,
Jesse

[Post-nuke-users] Re: Problem upgrading from old php-nuke

[Michael W. M. <mwm...@of...>]

I'm not sure if anyone has answered this problem but you may need to go into 
your cookies directory on the machine you are trying to view the page on, 
shut down and restart the browser, and attempt to view the page again.

you may be trying to view the page using a cookie from phpnuke 4.4 or even 
3.5. 

 -------
Mike 


jg...@fl... writes: 

> I've recently inherited a really old site which runs php-nuke 3.5.  At 
> least I think it's 3.5.  I applied the upgrade scripts from php-nuke to 
> get it up to 4.4.  This took a little hacking because they had syntax 
> errors but I believe I got it to work.  I then did the post-nuke install 
> and used the upgrade option for php-nuke 4.4. 
> 
> Here's the ouput from my upgrade: 
> 
> Table faqaategories is already as it should be.
> No need to rename itTable faqcategories is already as it should be.
> No need to rename itConverting old-style button blocks...Done converting 
> old-style button blocks 
> 
>    * Updating table: autonews... Skipped!
>    * Updating table: blocks... Skipped!
>    * Updating table: ephem... Skipped!
>    * Updating table: faqcategories... Skipped!
>    * Updating table: message... Skipped!
>    * Updating table: poll_desc... Skipped!
>    * Updating table: queue... Skipped!
>    * Updating table: reviews... Skipped!
>    * Updating table: reviews_add... Skipped!
>    * Updating table: seccont... Skipped!
>    * Updating table: stories... Skipped! 
> 
> Stories Authors Updated 
> 
> 
>  Migrated Admins to User Table 
> 
> *
> Write error* unable to update your "config.php" file
> You will have to modify this file yourself using a text editor.
> Here are the changes required:
> $pnconfig['dbtype'] = 'mysql';
> $pnconfig['dbhost'] = 'localhost';
> $pnconfig['dbuname'] = 'my_user';
> $pnconfig['dbpass'] = 'xxxxxxxxxx'
> $pnconfig['dbname'] = 'nuke';
> $pnconfig['prefix'] = 'my_prefix';
> Finished -- Your upgrade to the latest version of PostNuke is finished.
> Remember to change your config.php settings before using for the first 
> time. 
> 
> The above error I was believe due to file ownership issues.  I hand edited 
> the files with the appropiate information.  When I went to my site I 
> recieved the following errors: 
> 
>  
> 
> *Warning*: Invalid argument supplied for foreach() in 
> */var/www/Rogue_Seven_Oh_Two/html/includes/security.php* on line * 359* 
> 
> *Warning*: Invalid argument supplied for foreach() in 
> */var/www/Rogue_Seven_Oh_Two/html/includes/security.php* on line *359* 
> 
> *Warning*: Cannot add header information - headers already sent by (output 
> started at /var/www/Rogue_Seven_Oh_Two/html/includes/security.php:359) in 
> */var/www/Rogue_Seven_Oh_Two/html/mainfile2.php* on line *164
> **
> This error is a result of the above I believe:
> Fatal error*: Call to a member function on a non-object in 
> */var/www/Rogue_Seven_Oh_Two/html/mainfile2.php* on line *264* 
> 
>  
> 
> Line 359 of security.php puts me in this function: 
> 
> function getLevel($perms, $testrealm, $testcomponent, $testinstance)
> {
>    $level = ACCESS_INVALID; 
> 
>  // If we get a test component or instance purely consisting of ':' signs
>    // then it counts as blank
>    $testcomponent = preg_replace('/^:*$/', '', $testcomponent);
>    $testinstance = preg_replace('/^:*$/', '', $testinstance); 
> 
>    foreach ($perms as $perm) { // <-- Line 359 
> 
> 
> I'm posting this to see if this has happened to anyone else or if anyone 
> knows of a quick fix.  I'm still trying to track down the source of the 
> error.  BTW, great work on postnuke, especially the theme management! 
> 
> TIA,
> Jesse
> * 
> 
> * 
> 
>  
> 
>  
> 
> 
> _______________________________________________
> Post-nuke-users mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/post-nuke-users
 


Michael W. Mistak
mwm...@of...
AIM Screenname: mwmistak
cell: 734-673-6194
================================================================
President, Western Wayne County Young Democrats
 ----------------------------------------------------------------
Communications Director, Michigan Young Democrats
* http://www.mi-youngdems.org
 ----------------------------------------------------------------
Webmaster, The MDP Youth Caucus/College Democrats of Michigan
* http://www.youthcaucus.org
* http://www.mi-collegedems.com (Coming Soon)
 ----------------------------------------------------------------
Webmaster, The Justice Caucus
* http://www.justicecaucus.org
 ----------------------------------------------------------------
Webmaster, The Wayne County 11th District Democratic Committee
* http://www.wayne11dems.org
 ----------------------------------------------------------------
Webmaster, The 13th Congressional District Democratic Org.
* http://www.13thdistrictdems.org
================================================================ 

Re: [Post-nuke-users] Problem upgrading from old php-nuke

[<jg...@fl...>]

Sorry about that, I'm having mail problems as well :(.

Jesse

[Post-nuke-users] Problem upgrading from old php-nuke

[<jg...@fl...>]

I've recently inherited a really old site which runs php-nuke 3.5.  At 
least I think it's 3.5.  I applied the upgrade scripts from php-nuke to 
get it up to 4.4.  This took a little hacking because they had syntax 
errors but I believe I got it to work.  I then did the post-nuke install 
and used the upgrade option for php-nuke 4.4.

Here's the ouput from my upgrade:

Table faqaategories is already as it should be.
No need to rename itTable faqcategories is already as it should be.
No need to rename itConverting old-style button blocks...Done converting 
old-style button blocks

    * Updating table: autonews... Skipped!
    * Updating table: blocks... Skipped!
    * Updating table: ephem... Skipped!
    * Updating table: faqcategories... Skipped!
    * Updating table: message... Skipped!
    * Updating table: poll_desc... Skipped!
    * Updating table: queue... Skipped!
    * Updating table: reviews... Skipped!
    * Updating table: reviews_add... Skipped!
    * Updating table: seccont... Skipped!
    * Updating table: stories... Skipped!

Stories Authors Updated


  Migrated Admins to User Table

*
Write error* unable to update your "config.php" file
You will have to modify this file yourself using a text editor.
Here are the changes required:
$pnconfig['dbtype'] = 'mysql';
$pnconfig['dbhost'] = 'localhost';
$pnconfig['dbuname'] = 'my_user';
$pnconfig['dbpass'] = 'xxxxxxxxxx'
$pnconfig['dbname'] = 'nuke';
$pnconfig['prefix'] = 'my_prefix';
Finished -- Your upgrade to the latest version of PostNuke is finished.
Remember to change your config.php settings before using for the first time.

The above error I was believe due to file ownership issues.  I hand 
edited the files with the appropiate information.  When I went to my 
site I recieved the following errors:



*Warning*: Invalid argument supplied for foreach() in 
*/var/www/Rogue_Seven_Oh_Two/html/includes/security.php* on line * 359*

*Warning*: Invalid argument supplied for foreach() in 
*/var/www/Rogue_Seven_Oh_Two/html/includes/security.php* on line *359*

*Warning*: Cannot add header information - headers already sent by 
(output started at 
/var/www/Rogue_Seven_Oh_Two/html/includes/security.php:359) in 
*/var/www/Rogue_Seven_Oh_Two/html/mainfile2.php* on line *164
**
This error is a result of the above I believe:
Fatal error*: Call to a member function on a non-object in 
*/var/www/Rogue_Seven_Oh_Two/html/mainfile2.php* on line *264*



Line 359 of security.php puts me in this function:

function getLevel($perms, $testrealm, $testcomponent, $testinstance)
{
    $level = ACCESS_INVALID;

    // If we get a test component or instance purely consisting of ':' signs
    // then it counts as blank
    $testcomponent = preg_replace('/^:*$/', '', $testcomponent);
    $testinstance = preg_replace('/^:*$/', '', $testinstance);

    foreach ($perms as $perm) { // <-- Line 359


I'm posting this to see if this has happened to anyone else or if anyone 
knows of a quick fix.  I'm still trying to track down the source of the 
error.  BTW, great work on postnuke, especially the theme management!

TIA,
Jesse
*

*

Re: [Post-nuke-users] Prefix

[J. C. <ad...@di...>]

It depends on what you are trying to share amognst the sites as to what =
tables you need to edit in pntables. =20

If you aren't sharing any of the tables then it isn't necessary to edit =
the pntables at all.

jc
  ----- Original Message -----=20
  From: Tom Ahasverussen=20
  To: pos...@li...=20
  Sent: Thursday, January 03, 2002 6:41 AM
  Subject: [Post-nuke-users] Prefix


  Hey alle postnukers.
  Does anyody know how many tables you will have to edit in pntables.php =
to get prefix b to work with prefix a.
  =20
  Thanks in Advance
  Tom

[Post-nuke-users] Prefix

[Tom A. <to...@pe...>]

Hey alle postnukers.
Does anyody know how many tables you will have to edit in pntables.php =
to get prefix b to work with prefix a.

Thanks in Advance
Tom