Support Forums - All Posts - XOOPS Web Application System

11

Re: Yee-ha! upgrade to 2.0.6 WENT smoothly!

2004/4/27 12:51
treefrog
Just popping in
Posts: 20
Since: 2004/4/17

I wish I knew.

If these are things that should've been done the first time anyway, I didn't know about it... but the succesful upgrade time, I did do the following (different) things first (I don't know if it affected it):

I turned off (deactivated) the third-party modules... and uninstalled WFChannel, WFFaq, Soapbox, and Tiny Content (they were just on the test site, so I didn't lose anything.) I reverted to the default theme, and I replaced the "uploader.php" in root/class/ that WFChannel had earlier replaced with a fresh copy. Then I did the upgrade.

What anything had to do with anything, I don't know.

On the real site, the only third party module I have up and running is a counter, and I deactivated (but didn't uninstall) it, and also reverted the theme to default (just for kicks.) I didn't want to take any chances... That upgrade went without a hitch.

So, if you think any of that helped (rather than me being a dork the first go-round and the XOOPS forum channeling psychic help), let me know, and I'll be sure to keep that in mind for the next upgrade another day down the road.

If at first you don't succeeed, try try again.
Then post to the XOOPS forum and try try again.

12

Yee-ha! upgrade to 2.0.6 WENT smoothly!

2004/4/27 4:09
treefrog
Just popping in
Posts: 20
Since: 2004/4/17

Sorry to distract you all.

My real site is upgraded, and I acknowledge that I must be a flake.

So sorry... I guess there's a bit of a learning curve.

Keep up the good work!

(and I see that the 2.0.6 registers in the module administration footer... just not the home page... but at least now I know that!)

13

Re: upgrade to 2.0.6 didn't go smoothly

2004/4/27 3:27
treefrog
Just popping in
Posts: 20
Since: 2004/4/17

Okay, so apparently my goal in life is to mess up my Xoops.. frustrate myself that I can't figure it out... post to this forum, and then go back and figure out how to fix it myself anyhow.

Gee posting here really works, I guess.

So my reinstallation of the back up test site root from earlier today got me back to where I was before I tried to upgrade.

Then, I went with a third party ftp to upload the the changed files (much faster too, I might add... I don't know what I was thinking earlier)...

and, voila! I seem to have a functional site. Although, I'm not sure where to look to make sure the version is actually upgraded to 2.0.6 I would've thought the footer would change. There's no indicator that there's anything different, except that I am free of gobbledygook again.

Thank you XOOPS forum for fixing my site by osmosis.

Let's hope the upgrade of the real site goes just as smoothly...

14

upgrade to 2.0.6 didn't go smoothly

2004/4/27 1:12
treefrog
Just popping in
Posts: 20
Since: 2004/4/17

I'm glad I tried it on a test site first.

I uploaded and overwrote all the changed files as per the intsructions via CPanelX. I did this to my "test site" (another installation of XOOPS on my server)...

I updated all the modules, including at least three times for "system"... and I still have problems. I reverted to the default theme (just in case), which didn't change anything. I also re-uploaded the files in the root folder and the files in the system module again, which still didn't help.

I turned on PHP debug, but I had gobbledygook before that anyhow.

This is what is at the top of my browser in the Module Admin page:

Quote:

common.php1.1?4"'À1?4"'ÀmBIN‚?Ì1errorhandler.php?1?4"#B1?4"#BmBIN‚?…œ functions.phpZª»êÖV»êÖVmBIN‚?£‚databasefactory.php»Äéê»ÄéêmBIN‚?:1mysqldatabase.php(k»õR»õRmBIN‚?êídatabase.php5»ã1»ã1mBIN‚?t‰criteria.php&F»â°»â°mBIN‚?oÏ config.php(t1?47|1?47|mBIN‚?p!version.php11?4Ii21?4Ii2mBIN‚?¿— member.php4R1?46ú|1?46ú|mBIN‚?ÔÊuser.phpVÚ1?4'ü1?4'ümBIN‚?ƒsession.php1?4äB1?4äBmBIN‚?ÉF constants.php ê1?4¯º1?4¯ºmBIN‚?¥main.phpn©˜1?4IÉ21?4IÉ2mBIN‚?¥ªxoopsblock.phpI¯1?4 ´`1?4 ´`mBIN‚?åVmodulesadmin.php”71?4IÉ41?4IÉ4mBIN‚??

and then on the bottom is this:
Quote:

Warning [PHP]: session_start(): Cannot send session cookie - headers already sent by (output started at /home/root/public_html/testsite/include/common.php:2) in file include/common.php line 159
Warning [PHP]: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/root/public_html/testsite/include/common.php:2) in file include/common.php line 159
Notice [PHP]: Undefined index: anonrefer in file modules/wfchannel/xoops_version.php line 82

Can anyone tell me what I did wrong and how I can fix it, so that when I go to upgrade the real site I'm slightly more successful?

By the way, even though wfchannel is in that message, it's "disabled" right now. And there are no additional modules on the real site, just the default ones.

Thanks so much, really.

15

Re: How do I stop guests from viewing registered user profiles?

2004/4/24 21:02
treefrog
Just popping in
Posts: 20
Since: 2004/4/17

I answered my own question. Sorry.

I had forgotten to close the if clause. that's all. Now I can do it any way I please.

That's what happens when you're learning!

16

Re: How do I stop guests from viewing registered user profiles?

2004/4/24 20:56
treefrog
Just popping in
Posts: 20
Since: 2004/4/17

I tried both:

$xoopsUser or redirect_header('index.php', 3, _NOPERM);

and the if clause version above. Both only render a completely blank page for me when I test it out as a guest user...

am I missing something?

Is it possible to add a:

<{if $xoops_isuser}>

somewhere in the template instead? If so, where would be the best place?

Could I actually just plug it in the certain boxes in the table for just the info I'd like covered? (i.e., the email address)

I'm sorry to sound like a ditz... I'm still trying to understand PHP...

17

Re: modules looking in root instead of module/*.php

2004/4/21 13:49
treefrog
Just popping in
Posts: 20
Since: 2004/4/17

Just in case anyone's following up on this, I was unable to solve my problems, so I went the extreme route of starting off with a fresh installation of Xoops, and it worked. (Since fresh insallation of the modules didn't). So, I still don't know what happened. Fortunately, my site wasn't "live" yet... so I only crushed my own work, instead of others'...

Things seem to be happy right now. I hope they stay that way...

overall, I'm extraordinarily happy with my Xoops!

18

Re: modules looking in root instead of module/*.php

2004/4/17 20:56
treefrog
Just popping in
Posts: 20
Since: 2004/4/17

Okay, so I got frustrated enough attemping to tamper with the files that I uninstalled and removed newbb from the modules folder.

I then installed newbb Pro, and even uploaded a fresh "regular" newbb module from a clean download of Xoops.

I still have the same problem. Is there a master template file somewhere that sets the root folder for newbb's executed scripts? Why do all the other links work okay? And, if I manually type into the address bar the missing directories, I can pull up the post file. (http:/siteroot/modules/newbb/newtopic.php?forum=1etc.......

But, I can't actually post, because the submit button also lops off the subdirectories.

Any ideas about where this is taking place that I could fix it?

I'm grateful for any help...

19

Re: modules looking in root instead of module/*.php

2004/4/17 19:28
treefrog
Just popping in
Posts: 20
Since: 2004/4/17

I did that, and the debug header disppears on the error page, so I have no information. I even did MySQL debugger, and the error page just comes up by itself...

If I copy the link location, I can see that it is requesting

http://siteroot/newtopic.php --->(plus a session ID)

All the other links I have tried so far are using

http://siteroot/modules/newbb/*.php

I can't find the file that is pointing out the URL.

the template file for newbb_viewforum.html
says:

<td align="right"><{$forum_post_or_register}></td>

where is that process happening?

20

modules looking in root instead of module/*.php

2004/4/17 18:17
treefrog
Just popping in
Posts: 20
Since: 2004/4/17

I'm still somewhat of a newbie, so bear with me.

My forums module appears to be looking in the site root folder for newtopic.php when you click on "new topic" as opposed to siteroot/modules/newbb/... so right now I cannot add any new topics (I get a 404 error). I'm not sure where to fix that... the config.php shows this:

// You shouldn't have to change any of these
$bbUrl['root'] = XOOPS_URL."/modules/newbb/";
$bbUrl['admin'] = $bbUrl['root']."admin";
$bbUrl['images'] = $bbUrl['root']."images";
$bbUrl['smilies'] = $bbUrl['images']."smiles";

Am I just looking in the wrong spot?

Pleeeeeaaaasssee help me!

BTW, the "archives" section of the news module also has this problem... clicking on April 2004 (there are no others) also gives a 404 error because it is also looking in the siteroot.

I have tried uninstall/install and update module, to no avail... and I can't find any other applicable info in this forum...

Thanks so much!

Stats
Goal:	$100.00
Due Date:	Apr 30
Gross Amount:	$0.00
Net Balance:	$0.00
Left to go:	$100.00

Forum Index

Re: Yee-ha! upgrade to 2.0.6 WENT smoothly!

Yee-ha! upgrade to 2.0.6 WENT smoothly!

Re: upgrade to 2.0.6 didn't go smoothly

upgrade to 2.0.6 didn't go smoothly

Re: How do I stop guests from viewing registered user profiles?

Re: How do I stop guests from viewing registered user profiles?

Re: modules looking in root instead of module/*.php

Re: modules looking in root instead of module/*.php

Re: modules looking in root instead of module/*.php

modules looking in root instead of module/*.php

Login

Search

Recent Posts

Re: Rebuilding and Updating a 20 years old Xoops Website from 2.0.18? to 2.5.11

Rebuilding and Updating a 20 years old Xoops Website from 2.0.18? to 2.5.11

Re: NewBB v 5.1.0 b 6

Re: NewBB v 5.1.0 b 6

NewBB v 5.1.0 b 6

Re: XOOPS 2.5.11 search user is not working

Re: oledrion

Re: oledrion

Re: oledrion

Re: oledrion

Who's Online

Donat-O-Meter

Latest GitHub Commits

{{ record.sha.slice(0, 7) }} - {{ record.commit.message | truncate }}