51
irmtfan
Re: XOOPS 2.6.0 Alpha 1 Testing
  • 2012/9/5 4:29

  • irmtfan

  • Module Developer

  • Posts: 3419

  • Since: 2003/12/7


amazing,
Thank you Zyspec. it is very needed.
Its good to have a brief explanation of those API in column D.
So module developers will understand Xoops API better.

52
kris_fr
Re: XOOPS 2.6.0 Alpha 1 Testing
  • 2012/9/5 18:44

  • kris_fr

  • Theme Designer

  • Posts: 1009

  • Since: 2005/12/31



53
zyspec
Re: XOOPS 2.6.0 Alpha 1 Testing
  • 2012/9/5 18:55

  • zyspec

  • Module Developer

  • Posts: 1091

  • Since: 2004/9/21


Thanks kris_fr!

54
Roby73
Re: XOOPS 2.6.0 Alpha 1 Testing
  • 2012/9/5 22:33

  • Roby73

  • Friend of XOOPS

  • Posts: 262

  • Since: 2011/6/15


Tanks

55
tatane
Re: XOOPS 2.6.0 Alpha 1 Testing
  • 2012/9/7 17:29

  • tatane

  • Just can't stay away

  • Posts: 649

  • Since: 2008/5/6 1


Hello,
Today many CMS use libraries such as Gravatar avatar
Would it be possible to integrate this system in version 2.6 Xoops ?

56
irmtfan
Re: XOOPS 2.6.0 Alpha 1 Testing
  • 2012/9/8 5:43

  • irmtfan

  • Module Developer

  • Posts: 3419

  • Since: 2003/12/7


thanks kris_fr.
I hope you clould be involved more in helping core team to document a theme standards for xoops 2.6.0
It is very needed too.

Gravatar is good feature to add.
btw implement globalize features like this make some issues for some countries. please add these features as optional.
anyway please send it to the sf.net tracker.

57
culex
Re: XOOPS 2.6.0 Alpha 1 Testing
  • 2012/9/8 15:51

  • culex

  • Module Developer

  • Posts: 711

  • Since: 2004/9/23


Quote:


Mamba Quote: I can confirm that blocks are not draggable. Hmm, don't have these problems with PHP 5.3.15 and PHP 5.4.5 Can somebody else confirm the issues, and specify the platform they are using?


It's due to double including jquery.ui.

One inclusion from /media/jquery/plugins/ wich is UI version 1.70 AND another including from /media/plugins/ui/ wich is the new ui version 1.83...

Problem is the old overwrites the new in the header giving dom error "d is undefined" in the browser..

Solution is to locate
addScript($xoops->url('/media/jquery/plugins/jquery.ui.js'));


and replace with
addScript($xoops->url('/media/jquery/ui/jquery.ui.js'));


in all of the following files
Modules/Banners/index.php
Modules/Banners/banners.php
Modules/Banners/clients.php
Modules/protector/Admin/Advisory.php
Modules/System/Admin/blocksadmin/Main.php
Modules/System/Themes/Default/Default.php

I have posted in tracker also
drag n' drop issue
Programming is like sex:
One mistake and you have to support it for the rest of your life.

58
irmtfan
Re: XOOPS 2.6.0 Alpha 1 Testing
  • 2012/9/9 4:19

  • irmtfan

  • Module Developer

  • Posts: 3419

  • Since: 2003/12/7


very nice catch culex.
it is better to send this bug fix to the sf.net tracker.
Thank you.

Edit:
my fault!!!
i see you already sent it here:
https://sourceforge.net/tracker/index. ... roup_id=41586&atid=430840

Thank you again!

59
Mage
Re: XOOPS 2.6.0 Alpha 1 Testing
  • 2012/9/9 18:37

  • Mage

  • Core Developer

  • Posts: 200

  • Since: 2009/8/2 1


Thank you for your feedback, I fixed some bugs.

I do not participate much on this topic because my English is very bad but I read your remarks.

Next week I will put on the SVN a new module of contents.

60
irmtfan
Re: XOOPS 2.6.0 Alpha 1 Testing
  • 2012/9/10 7:07

  • irmtfan

  • Module Developer

  • Posts: 3419

  • Since: 2003/12/7


thank you Mage,
IMO your english is more than sufficient to participate in answering some important questions. Also IMO you can answer in french community forum and there are many french users can interpret your answers.

There are some questions about xoops 2.6.0 that need a core developer response.
eg:
Quote:

but core team dont explain other deprecations.
eg: I cannot understand the below deprecations necessity.
xoops_getModuleHandler to $xoops->getModuleHandler

it needs an explanation because some people like Mamba should put their precious time and change all these functions in all xoops modules to make them compatible with the new 2.6 core.
therefore core team should have a very good reason for that.
Also i may disagree with the below deprecations until i can see a good reason from core team.

for example this one:
xoops_load to XoopsLoad::load

and our widely used function:
formatTimestamp to XoopsLocal::formatTimestamp

I know it is quite easy to change the above methods in calling functions to calling Classes::Functions but i want to know what is wrong with a function like formatTimestamp that we have to change millions of them in the whole xoops modules?


Quote:

Next week I will put on the SVN a new module of contents

brilliant!
it is vitally important task with the highest priority for 2.6.0
once we have a bug free, stable content we can continue and port from all exist content modules

Login

Username:
Password:

Lost Password? Register now!

Who's Online

84 user(s) are online (54 user(s) are browsing Support Forums)


Members: 0


Guests: 84


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Dec 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits