MACTEP:
I will investigate this bug tomorrow.
Any other can reproduce this bug please contribute.
it seems a jQuery bug.

Quote:
It's there. In order to make it more consistent with other XOOPS classes, it is now in folder:
/class

Thanks Mamba, i saw and try the new class.

I am very confused, the core 2.5.5 migrate to moduleadmin GUI in Frameworks, now are all removed.

An upgrade to final 2.6 core, all modules would not work!!!
a simple upgrade as in the past is no possible, all modules for 2.5.5 are incompatible.

I expected the moduleadmin i frameworks dir, with deprecated message for a gradual migration.

I forgot.

In prevision to new core,i have fix all deprecated message in all modules, fixed command
Now in 2.5.5 i have 0 deprecated message, 0 errors in all modules. I thought in this mode upgrade to final 2.6 without many problems.

Quote:
Yes. IMO all these modules must work in 2.6.0 final with 0 errors and X deprecated messages.

I hope core team pay attention to that.
Also core team implement many features in admin theme in 2.6.0.
honestly my priority for features is like below:
1- server side programming features. all php and mysql related features that will improve the functionality of a website. (priority 9/10)
2- user side programing features. like html, css (like bootstrap) and js (like jQuery) improvements that can be useful for themes and templates. (priority 7/10)
3- user theme improvements. It means the implementation of (#2) features in user theme. Also everybody can implement them himself. (priority 5/10)
4- admin theme improvements. It means the implementation of (#2) features in admin theme to have a nice admin side. (priority 1/10)

It seems core team pay too much attention to #4 in 2.6.0 which has not any priority at this time.
the module admin class is introduced/implemented for this purpose in 2.5.5 and now the "extensions" name and menu is implemented in 2.6.0 alpha 1.

I as a webmaster need:
first: functionality/stability/security for my website
second: nice user theme for my users and visitors
and third: nice admin theme (for myself??? yeah it is cool for me too)

It seems core team pay too much attention to a nice admin theme because they are developers and most of coders/developers work in admin side themselves.

Quote:

I started a new thread to talk about modules/extensions with 2.6:
https://xoops.org/modules/newbb/viewtopic.php?topic_id=75465

But in short it PROBABLY would be simple to create a class or group of classes to mimic the old classes if necessary as long as they don't conflict with the new class but really the fix should be a simple syntax change as outlined in the thread above.

MACTEP:
The displaying issue in IE8 is definitely a bug.
somebody should send it to the bug tracker.
Im sure everybody can replicate it.
my knowledge in js and jQuery is ver very limited and i cannot solve these kinds of bugs.
a theme designer can easily find the root of this issue and solve it.

Quote:

Ищите ошибку в /media/bootstrap/css/xoops.bootstrap.css строка 39 (filter:)
и в /media/xoops/css/moduladmin.css строка 13 (filter:)

Look for an error in the /media/bootstrap/css/xoops.bootstrap.css line 39 (filter:)
and /media/xoops/css/moduladmin.css line 13 (filter:)

I make a script to check deprecated function and command php <5.3 in a module in xoops 2.5.5.
Now i want upgrade for the future final release 2.6.0.

There are a list of the all deprecated and removed file in 2.6.0?.

I started a document, based on a list provided by Zyspec, it's on Google Docs.

If you want to add things there, let me know and I'll give you access to edit.