Get XOOPS XOOPSXOOPS FAQFAQ ForumsForums NewsNews ThemesThemes ModulesModules
New Posts New Topics All Posts All Forums Index General Modules Themes Development International XOOPS.org

Search

Donat-O-Meter

Make donations with PayPal!
Stats
Goal: $100.00
Due Date: May 31
Gross Amount: $65.00
Net Balance: $61.80
Left to go: $38.20

Donations
studioC  ($25)May-17
Anonymous ($15)May-16
Anonymous ($25)May-4

Learn XOOPS Core

Local Support

Advertisement

XOOPS Code hosted on SourceForge

Cumulus Tag Cloud

2 2.5 2.5.5 2.6 3.0 2013 Abuse alimento AntiHarvesting AntiMalUser AntiSpam API Beats billige black block Blocking Blocks blue Captcha cell Christmas chronolabs content Conversion demo Dictionary docek download Dresses editor Elastic evden eve facebook floor forms framework free herre Honeypot Human Hymn instant-zero IP jQuery kantor Karaoke lamps Load log logger mobile module modules Monster MyAlbum-p nakliyat newbb news online PageRank Permissions pink Plugin pollos portal Prevention profile project Protector publisher REST Rights rmcommon Room sale security Server site Smarty Spam SQL stem StopForumSpam Studio tag tags tdmcreate Theme themes Transaction userlog website Whitepaper Wishcraft XFriendica xoops Xortify ZendFramework

New Users

Registering user

# 136015

handrick12

Welcome to XOOPS!




Bottom   Previous Topic   Next Topic  Register To Post

(1) 2 »


#1 Posted on: 2005/11/1 18:00 xoops2.2.3 final - PM update, minor message ??
Hi,

Thanks for all the hard work put into getting 2.2 final up, great job. :)

I just uploaded 2.2.3 (final) files, then updated the 3 modules, system, PM and Extended profiles. All went okay, but then I _think_ I saw a msg right dowm the bottom , on the PM update.

So, did the PM update again, and here is the message:

Quote:

Module Private Messaging updated successfully.

Warning [PHP]: executescript(/home/username/public_html/modules/pm/include/update.php): failed to open stream: No such file or directory in file kernel/module.php line 1218
Warning [PHP]: executescript(): Failed opening '/home/username/public_html/modules/pm/include/update.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in file kernel/module.php line 1218
Warning [PHP]: executescript(/home/username/public_html/modules/pm/include/update.php): failed to open stream: No such file or directory in file kernel/module.php line 1218
Warning [PHP]: executescript(): Failed opening '/home/username/public_html/modules/pm/include/update.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in file kernel/module.php line 1218


Note, it did say that the module PM was updated sucessfully though, so I consider this msg a non-event maybe ??

I looked for the file update.php in the /modules/pm, not there, and it is not in rel 2.2.2 either. The searched through all the 2.2.2 release, and there was an update.php, in the /modules/system folder.

Could this just be an include path problem on this site ??

Peter

Top


NO to the Microsoft Office format as an ISO standard.
Sign the petition
peterr
Just can't stay away
Just can't stay away
Joined:
2004/8/5 4:17
From here
Group:
Registered Users
Posts: 518
(Show More) (Show Less)


#2 Posted on: 2005/11/1 19:38 Re: xoops2.2.3 final - PM update, minor message ??
Hmm, I think I saw this today or a couple of days ago. Try to copy the files again, overwriting the old ones. Not sure to what it can be on windows side. Sounds like permissions problem to me.

Does actuall file in that directory exist? And what about permissions?

Gediminas

Top

gediminasbyt
Joined:
2005/3/18 14:36
From Where Silicon is called a place
Group:
Registered Users
Posts: 471
(Show More) (Show Less)


#3 Posted on: 2005/11/1 21:19 Re: xoops2.2.3 final - PM update, minor message ??
Quote:

gediminasbyt wrote:
Try to copy the files again, overwriting the old ones.


The file size was exact (65048 bytes - /kernel/module.php), but I uploaded again, tried the PM update again, ... same message.

Quote:

gediminasbyt wrote:
Does actual file in that directory exist? And what about permissions ?


No, the file it is looking for is /modules/pm/include/update.php , and the line of code that is trying to include the file is line 1218 of /kernel/module.php

include_once XOOPS_ROOT_PATH.'/modules/'.$this->getVar('dirname').'/'.trim($script);


but when updating the other modules (system and extended profiles), there was no such message.

There is only one file called /update.php and it is in /modules/system/include path.

Basically the error msg is just a warning, PHP can't include the file, but why the msg doesn't appear for other modules, I don't know ?

Thanks,

Peter

Top


NO to the Microsoft Office format as an ISO standard.
Sign the petition
peterr
Just can't stay away
Just can't stay away
Joined:
2004/8/5 4:17
From here
Group:
Registered Users
Posts: 518
(Show More) (Show Less)


#4 Posted on: 2005/11/1 21:34 Re: xoops2.2.3 final - PM update, minor message ??
As I was updating from 2.2.2, I did not run xoopsupdate.php, as is advised here

Peter

Top


NO to the Microsoft Office format as an ISO standard.
Sign the petition
peterr
Just can't stay away
Just can't stay away
Joined:
2004/8/5 4:17
From here
Group:
Registered Users
Posts: 518
(Show More) (Show Less)


#5 Posted on: 2005/11/2 8:53 Re: xoops2.2.3 final - PM update, minor message ??
Peter,

sometimes reading instructions is helpfull

Glad you fixed it. You could have done the same thing by updating the system module in ModuleAdmin->Update system.

Gediminas

Top

gediminasbyt
Joined:
2005/3/18 14:36
From Where Silicon is called a place
Group:
Registered Users
Posts: 471
(Show More) (Show Less)


#6 Posted on: 2005/11/2 20:24 Re: xoops2.2.3 final - PM update, minor message ??
Quote:

gediminasbyt wrote:
Glad you fixed it. You could have done the same thing by updating the system module in ModuleAdmin->Update system.


No, I haven't fixed it, as my previous post stated, the error messages still appear, when I try to update the PM module.

PHP debug is on, which is good, otherwise I wouldn't have seen the warning.

I actually did update the system module also.

Peter

Top


NO to the Microsoft Office format as an ISO standard.
Sign the petition
peterr
Just can't stay away
Just can't stay away
Joined:
2004/8/5 4:17
From here
Group:
Registered Users
Posts: 518
(Show More) (Show Less)


#7 Posted on: 2005/11/2 20:55 Re: xoops2.2.3 final - PM update, minor message ??
Not sure, but have you set a correct XOOPS path in mainfile.php?

You mention that you run the latest version but then say it's a 2.2.2 the latest one is 2.2.3.

If it's a fresh install I would recommend to try once more. Wipe out database before you reinstall and get a fresh downloaded copy. Get a zip not tar because widoze can screw up extraction from tarball.

By the way did you get full install or just update? Because sounds like you have fresh install and then you mention you do an update. For fresh install there is no need to to use an update.php.

Gediminas

Top

gediminasbyt
Joined:
2005/3/18 14:36
From Where Silicon is called a place
Group:
Registered Users
Posts: 471
(Show More) (Show Less)


#8 Posted on: 2005/11/2 21:05 Re: xoops2.2.3 final - PM update, minor message ??
Quote:

gediminasbyt wrote:
Not sure, but have you set a correct XOOPS path in mainfile.php?


This was the XOOPS 2.2.3 final, so mainfile.php did not (need to) change.

Quote:

gediminasbyt wrote:
You mention that you run the latest version but then say it's a 2.2.2 the latest one is 2.2.3.


Quote:

peterr wrote:
As I was updating from 2.2.2



Quote:

gediminasbyt wrote:
If it's a fresh install I would recommend to ....


It is an update, the 2.2.3 final is only an update, not a fresh install.

Peter

Top


NO to the Microsoft Office format as an ISO standard.
Sign the petition
peterr
Just can't stay away
Just can't stay away
Joined:
2004/8/5 4:17
From here
Group:
Registered Users
Posts: 518
(Show More) (Show Less)


#9 Posted on: 2005/11/2 21:27 Re: xoops2.2.3 final - PM update, minor message ??
I can confirm the message you get when updating the PM module. It's because an update file has been declared by the module which doesn't actually exist.

Could you please post a bug report about it? Just use the 'Report core bug' link on the left. It's not really a bug, but the trackers are how the developers keep track of things like this (funnily enough )

Rowd

Top

rowdie
Just can't stay away
Just can't stay away
Joined:
2004/7/21 13:21
Group:
Registered Users
Posts: 836
(Show More) (Show Less)


#10 Posted on: 2005/11/2 21:43 Re: xoops2.2.3 final - PM update, minor message ??
Hi,

Quote:

rowdie wrote:
I can confirm the message you get when updating the PM module. It's because an update file has been declared by the module which doesn't actually exist.


Yes, the PM module tries to include it, can't find it, so gives the message. Updating the system module gives no such msg, because there is a modules/system/include/update.php

The extended profles update does not give the message, even though there is no /modules/profile/include/update.php ; the reasom may be that within the extended profile update, PHP error logging levels are modified, not to display warnings ??

Anyway, I'm glad to see someone understands me, and has the same problem, it's no big deal, as you say though. :D

Quote:

rowdie wrote:
Could you please post a bug report about it? Just use the 'Report core bug' link on the left. It's not really a bug, but the trackers are how the developers keep track of things like this (funnily enough )


Yes I report it, and yes, it's not really a bug. I had to find out if it was site secific first, .... so thanks for confirming.

Peter

Top


NO to the Microsoft Office format as an ISO standard.
Sign the petition
peterr
Just can't stay away
Just can't stay away
Joined:
2004/8/5 4:17
From here
Group:
Registered Users
Posts: 518
(Show More) (Show Less)




(1) 2 »



You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You can vote in polls.
You cannot attach files to posts.
You cannot post without approval.
You cannot use topic type.
You cannot use HTML syntax.
You cannot use signature.

[Advanced Search]