PEAK XOOPS - Re: Install ALTSYS on XOOPS 2.3.x in englishin japanese

Top > XOOPS Modules >OtherMods >Install ALTSYS

Re: Install ALTSYS on XOOPS 2.3.x

List posts in the topic

none Re: Install ALTSYS on XOOPS 2.3.x

msg# 1.3.1
depth:
2
Previous post - Next post | Parent - Children.1 | Posted on 2008/12/19 5:50 | Last modified
GIJOE  ÀèǤ·³Áâ   Posts: 4110
hi info.

Quote:

I've set it up on my XOOPS 2.3.x install and generally AltSys runs fine (as always). However, I'm getting one small error related to the adminmenu.php file found in the cache folder (now xoops_data/caches/xoops_cache with 2.3.x). Here's what happens....

AltSys inserts some information into the adminmenu.php file and uses it for its own purposes. However, because XOOPS changed their methodology for the admin menu, XOOPS no longer uses or needs the adminmenu.php file, and when any module is updated, the file is deleted by XOOPS. This causes both Protector 3.22 and especially AltSys to throw up an error for some of their functions.

So, you have to somehow keep from deleting this file when a module is updated. Currently, what I'm doing is just touching the file to create it file and then AltSys does it's thing just fine (inserts its code). I've tried changing permissions on it so it can't be removed or overwritten, but that doesn't seem to work. Note: when using the default Control Panel GUI, a file called xoops_adminmenu_XoopsGuiDefault.php is created in the xoops_cache folder (but not when using ThAdmin). The problem exists except when Control Panel GUI is set to 'legacy'.
OK.
It might be caused by the branch of the core types.

Try this hack.
include/adminmenu_functions.php

//
// insert/replace items of mymenu into adminmenu
//
function altsys_adminmenu_insert_mymenu( &$module )
{
	global $altsysModuleConfig ;

	if( empty( $altsysModuleConfig['adminmenu_insert_mymenu'] ) ) return ;

	if( altsys_get_core_type() < ALTSYS_CORE_TYPE_ORE ) {
	if( altsys_get_core_type() == ALTSYS_CORE_TYPE_X20 ) {
		altsys_adminmenu_insert_mymenu_x20( $module ) ;
	}
}


Quote:
Otherwise, AltSys works very well (still wish we could manage bottom blocks, but don't use these too often, so not a major issue for me).

FWIW, I'm using AltSys 0.61a on XOOPS 2.3.2b, currently. I haven't tested the error against the other versions of 2.3.x, but I expect that it's the same issue there as well.
Why don't you try Altsys-0.70?
It supports bottom blocks.
At least, I've comfirmed it works fine with ImpressCMS.

leco reported it works properly with XOOPS2.3.


And you'd better know I'm supporting "ALL XOOPS"

- XOOPS 2.0 (original)
- XOOPS 2.0-JP by XOOPS Cube Project
- XOOPS Cube Legacy 2.1
- ImpressCMS
- Oreteki XOOPS
- XOOPS 2.0.x by Skalpa
- XOOPS 2.3.x by phppp

XOOPS 2.3.x is just a kind of various core types for me
Votes:56 Average:5.54

Posts tree

  Advanced search

Login
Username or e-mail:

Password:

Remember Me

Lost Password?

Register now!