i upgraded myalbum and everything didn't turn out well.

first of all.. i couldn't save the settings in "Pic up block" the images shows the original sizes..

second. Only thumb nail can be shown.., when clicked. the pictures couldn't be shown

example :http://www.catscity.com/modules/myalbum/photo.php?lid=2

help help help~

You don't allow module permissions to guests.
You should check permissions in system & myAlbum-P.

And again, myAlbum-P is not a new version of myalbum.

ouch..forgot..to allow the permission..
nvm..i reverse the version already..

Thanks anyway
luckily everything was restored to normal

As per my other posts on 2.50, I can't get 2.60 to work either, here are the php errors:

Warning [PHP]: unlink() failed (No such file or directory) in file modules/myalbum/include/functions.php line 91

Warning [PHP]: imagecreatetruecolor(): requires GD 2.0 or later in file modules/myalbum/include/functions.php line 117

All settings are correct, including CHMOD

I also still get the update photo table error.

Any help is much appreciated.

Quote:
Both are not errors.
Though I don't have time to explain meanings of the codes, it is absolutely normal behavior.

I think the object which should be doubted might be a setting of PHP.
Because these functions called with @, the warning should be eliminated.

Quote:
Probably, your structure of photos table is not same as myalbum 1.1.3.
I've never used myalbum without 1.1.3, I don't know whether some version of myalbum has another structures.

query "SHOW COLUMNS FROM *_myalbum_photos" to MySQL by some DB tools.

I did then do a fresh install (uninstall/reinstall) of myalbum-p and still the same problems on one site but not the other, as I said both are on the same server.

hmmm...
It sounds strange.

Tell me the differences with two.

like:

XOOPS_DB_PREFIX (xoops_ or not)
DB instance
directory for photos or thumbnails
...

Quote:

I had the same problem when I moved from 2.5 to 2.60 & 2.62.
After several hours fibbling around I think I know, if not the solution at least a workaround...
I think it's becourse GIJOE implemented support for templates.

************************
2003-1-30 v2.61 (small fixes)
- fixed typo in myalbum_imagemanager.html rxcoder -> xcoder fixed (thx Olorin)
- feature changed not to close imagemanager after [img] added (thx Olorin)
- sort by date desc added (thx Collo)
- pagenav bug fixed (thx Collo)

2003-1-28 v2.60 release
- imagemanager integrated with XOOPS core added
- optimization for table view
- Updated swedish (thx Leif Madsen)

2003-1-27 v2.60beta01
- almost of front ends have been rewritten to use template
- selectable from two views of viewcat.php (list & table)
- global group permission added (add,edit,delete,rateview,ratevote)
- notifications added (new photos in global and categories)
- some improvement for admin
- some fix

**************************************
Here is what I did:

The problem has to do with templates. So In System Admin / Template manager / go to the active template, click on myalbum [list]. Now you click remove on all template files. Exit and return to Template manager, do a create list.
That's it (at least for me...)!

As always, take a backup before or at least try it first on a clone templete...

After this action myalbum-P works as supposed to!

//Madsen

Quote:

Both are not the default tables one is justatable_ and the other anothertable_ as opposed to xoops_

A case in www.xoopscube.jp:

When an admin using Norton Internet Security installed myAblum-P, he got DB errors with INSERT.

After he had uninstalled and re-installed it, his myAlbum-P has been running rightly.

Though I don't know tom uses Norton or not,
Uninstall & reinstall the module is an efficient measure when you get DB error.