Koozali.org: home of the SME Server

Upgrade Fail 4.1 to 4.1.2

Alexie

Upgrade Fail 4.1 to 4.1.2
« on: April 21, 2001, 08:28:16 PM »
Hi There..

What have you done, EM.???

I did a upgrade from 4.1 to 4.1.2, now my MyPhPortal does not work anymore.??

All my PHP files is show as text files.!!

And, Yep, i have Webmail on and it works 100%..

HELP.!!!

Dan Elkins

Re: Upgrade Fail 4.1 to 4.1.2
« Reply #1 on: April 21, 2001, 09:50:39 PM »
If you have MyPhPortal installed in an ibay you must enable Execution of dynamic content option in the ibay configuration panel.

Dan Elkins

Alexie

Re: Upgrade Fail 4.1 to 4.1.2
« Reply #2 on: April 21, 2001, 10:22:58 PM »
Hi ..

It's in my Home Web PHP do not work..??

Not, my Ibays..

Alexie

Re: Upgrade Fail 4.1 to 4.1.2
« Reply #3 on: April 22, 2001, 04:33:14 AM »
Hmmm....

Something is nor right with the version 4.1.2..

I try a New install of the system, still no PHP support in the Primary dir.
Works fine in Ibays..??

Franck PIERRE

Re: Upgrade Fail 4.1 to 4.1.2
« Reply #4 on: April 22, 2001, 07:19:48 AM »
I still use the 4.1.1, but you should verify if .php or .php? are parsed by your server.

You could try to create a sample page with .php, .php3 and .php4 extension. Then, look if any works.

Regards.
--
Franck
grand-pa@grand-pa.dyndns.org
http://www.grand-pa.dyndns.org

Alexie

Re: Upgrade Fail 4.1 to 4.1.2
« Reply #5 on: April 22, 2001, 07:30:47 AM »
Hi Franck..

I have try it, No luck..??

Im back at Version 4.1 now, it works..

Charlie Brady

Re: Upgrade Fail 4.1 to 4.1.2
« Reply #6 on: April 22, 2001, 10:03:08 AM »
Alexie wrote:

> Something is nor right with the version 4.1.2..

You should report all bugs or suspected bugs to bugs@e-smith.com.

> I try a New install of the system, still no PHP support in
> the Primary dir.

Yes, you are quite right. This could be considered a bug. Officially, PHP is only included so that webmail works, but it was not intentional to disable PHP for the primary directory. Expect on update soon.

> Works fine in Ibays..??

Correct. So you have a workaround while waiting for a fix. Or someone can work out a simple fix to one of the templates, I'm sure.

Regards

Charlie

Alexie

Re: Upgrade Fail 4.1 to 4.1.2
« Reply #7 on: April 22, 2001, 06:08:13 PM »
I have send a Bug report to them..Charlie..

I use MyPhPNuke 1.8 system in my Primary dir, so this bug is bad for me..:-))

Jeff

Re: Upgrade Fail 4.1 to 4.1.2
« Reply #8 on: May 08, 2001, 12:59:49 AM »
this is bad for me too! anyone come up with a fix yet ?

Alexie

Re: Upgrade Fail 4.1 to 4.1.2
« Reply #9 on: May 08, 2001, 04:35:08 AM »
Yeps.. i have NOT try it YET, but it is out..

Link: ftp://ftp.e-smith.com/pub/e-smith/current/updates/RPMS/noarch/e-smith-base-4.4.0-14.noarch.rpm

Problem: There is a missing line in an httpd.conf template fragment, resulting in PHP being disabled for the primary i-bay.

Jeff

Re: Upgrade Fail 4.1 to 4.1.2
« Reply #10 on: May 08, 2001, 07:51:19 PM »
I upgraded the package, what else do I need to do, php still doesnt' work in the Primary site.

Alexie

Re: Upgrade Fail 4.1 to 4.1.2
« Reply #11 on: May 08, 2001, 09:18:52 PM »
Send in a Bug report..!!!

I think i will wait for 4.1.3..

Mr Allen

Re: Upgrade Fail 4.1 to 4.1.2
« Reply #12 on: May 15, 2001, 10:55:00 PM »
Dear Jeff:

To get php working in the primary directory you first need to goto:

http://www.e-smith.org/bugs/index.php3?op=showBug&bugID=27

and download the e-smith-base-4.4.0-14.noarch.rpm

And then run the following commands:
rpm -Uvh e-smith-base-4.4.0-14.noarch.rpm
/sbin/e-smith/signal-event console-save

Sincerely,
Mr. Allen

P.S.  Jeff I think you did everything correct, just didn't know that it would take at console-save command to invoke the changes.

Charlie Brady

Re: Upgrade Fail 4.1 to 4.1.2
« Reply #13 on: May 15, 2001, 11:04:25 PM »
Mr Allen wrote:

> and download the e-smith-base-4.4.0-14.noarch.rpm
>
> And then run the following commands:
> rpm -Uvh e-smith-base-4.4.0-14.noarch.rpm
> /sbin/e-smith/signal-event console-save

Actually, until we make an e-smith-base-4.4.0-15, you should do:

/sbin/e-smith-signal-event post-upgrade
/sbin/e-smith-signal-event reboot

There is a permissions problem in the e-smith-base-4.4.0-14 RPM, and it is corrected by that sequence of commands. Sorry for the inconvenience.

Regards

Charlie

Dan

Re: Upgrade Fail 4.1 to 4.1.2
« Reply #14 on: May 16, 2001, 07:52:07 AM »
For us new guys to Linux I think Charlie actually wanted to say:

/sbin/e-smith/signal-event post-upgrade
/sbin/e-smith/signal-event reboot


---
Dan