PEAK XOOPS - xoops 2.0.17 and GIJOE's works 
xoops 2.0.17 and GIJOE's works
- You cannot open a new topic into this forum
- Guests cannot post into this forum
avtx30
Posts: 36
Posts: 36
XOOPS 2.0.17 has just been released thanks to The XOOPS core development team lead by phppp!
Quote:
I hope that GIJOE will continue to support XOOPS.ORG and soonly release patch/hacks/compatible (D3) modules for 2.0.17. Your works save our life! Thank you verymuch.
Well, I've just upgraded my site from xoops 2.0.16 to 2.0.17 smoothly. Unfortunately the lastest version of module D3forum seems to be not worked with 2.0.17. It gives blank page. Please help!
- xoops 2.0.17
- File class/smarty/xoops_plugins/resource.db.php is edited according to this link
- d3forum ver.0.75 alpha
- php 4.3.9
- mysql 4.1.20
- altsys 0.55
- protector 3.13 works perfectly
- Turn-on debug mode but NO errors are printed out.
Quote:
This is mainly a maintenance release containing a lot of bugfixes, as well as some functionality enhancements. Read the full changelog for details.
I hope that GIJOE will continue to support XOOPS.ORG and soonly release patch/hacks/compatible (D3) modules for 2.0.17. Your works save our life! Thank you verymuch.
Well, I've just upgraded my site from xoops 2.0.16 to 2.0.17 smoothly. Unfortunately the lastest version of module D3forum seems to be not worked with 2.0.17. It gives blank page. Please help!
- xoops 2.0.17
- File class/smarty/xoops_plugins/resource.db.php is edited according to this link
- d3forum ver.0.75 alpha
- php 4.3.9
- mysql 4.1.20
- altsys 0.55
- protector 3.13 works perfectly
- Turn-on debug mode but NO errors are printed out.
Votes:23
Average:5.22
GIJOE
Posts: 4110
Posts: 4110
hi avtx30.
I've updated my local xoops for test.
(I don't use core from xoops.org for public sites at all)
And I'm disappointed 2.0.17 and the new core team headed phppp.
Sadly, they neglects or ignorants the concept of "compatibility".
Perhaps, I will stop supporting core from xoops.org in not so far future.
Anyway, you can use D3 modules with 2.0.17 just by applying this patch.
http://xoops.peak.ne.jp/md/mydownloads/singlefile.php?lid=110
Don't forget clearing the template cache after overwriting the file.
I've updated my local xoops for test.
(I don't use core from xoops.org for public sites at all)
And I'm disappointed 2.0.17 and the new core team headed phppp.
Sadly, they neglects or ignorants the concept of "compatibility".
Perhaps, I will stop supporting core from xoops.org in not so far future.
Anyway, you can use D3 modules with 2.0.17 just by applying this patch.
http://xoops.peak.ne.jp/md/mydownloads/singlefile.php?lid=110
Don't forget clearing the template cache after overwriting the file.
Votes:29
Average:3.79
Nicko
Posts: 3
Posts: 3
Will you update AutoLogin Hack to work with 2.0.17 Xoops version please?
Thanks for the answer ^^
Thanks for the answer ^^
Votes:21
Average:4.29
Nicko
Posts: 3
Posts: 3
Sorry, I didn't saw the hacks was already in the download section >_< Thanks for it ^^
Just one question please, what's the bug in 2.0.17 version as there is a "bug fix for XOOPS 2.0.17" in the download section.
Thanks ^^
Just one question please, what's the bug in 2.0.17 version as there is a "bug fix for XOOPS 2.0.17" in the download section.
Thanks ^^
Votes:21
Average:5.71
GIJOE
Posts: 4110
Posts: 4110
Votes:17
Average:5.29
Nicko
Posts: 3
Posts: 3
OK, thanks for the info 
Votes:13
Average:5.38
avtx30
Posts: 36
Posts: 36
Thanks GIJOE!
My d3forum @ xoops 2.0.17 worked after applying the resource.db.php patch.
It's a big pain that you will stop supporting xoops.org >= 2.0.17. You meant I should switch to xoopscube in order to use D3 compatible stuffs?
Thanks again.
My d3forum @ xoops 2.0.17 worked after applying the resource.db.php patch.
It's a big pain that you will stop supporting xoops.org >= 2.0.17. You meant I should switch to xoopscube in order to use D3 compatible stuffs?
Thanks again.
Votes:19
Average:4.74
PepeMty
From: Monterrey, M
Posts: 17
From: Monterrey, M
Posts: 17
Hello GIJOE!
I rely heavily on your modules, Protector, Pico and Altsys, under xoops.org core.
So you understand my worries that you stop supporting xoops core.
Should I go to xoopscube instead?
Warm regards from sunny M
I rely heavily on your modules, Protector, Pico and Altsys, under xoops.org core.
So you understand my worries that you stop supporting xoops core.
Should I go to xoopscube instead?
Warm regards from sunny M
Votes:1
Average:0.00
renewehle
From: Deutschland - ドイツ
Posts: 34
From: Deutschland - ドイツ
Posts: 34
お帰りなさい、
ショックを受けました。
どうしてそれをしているの？
佐藤 レネー
ショックを受けました。
どうしてそれをしているの？
佐藤 レネー
Votes:0
Average:0.00
voltan
From: iran-tehran
Posts: 70
From: iran-tehran
Posts: 70
i test pico , protector , d3forum to 2.0.17 (2.0.16 up to 2.0.17 and resource.db.php bug fixed for 2.0.17) and i dont have problem !!!
but if you stop supporting core from xoops.org we to lost xoops power
but if you stop supporting core from xoops.org we to lost xoops power
Votes:0
Average:0.00
marcan
Posts: 13
Posts: 13
GIJOE said :
"And I'm disappointed 2.0.17 and the new core team headed phppp.
Sadly, they neglects or ignorants the concept of "compatibility".
Perhaps, I will stop supporting core from xoops.org in not so far future.
Anyway, you can use D3 modules with 2.0.17 just by applying this patch.
http://xoops.peak.ne.jp/md/mydownloads/singlefile.php?lid=110"
Hi guys,
Since a few releases, XOOPS has included a resource.db.php file to overcome the issue you are talking about. And XOOPS 2.0.17 is no different. The package contains an extra folder where this file is located. Documentation about this file is located in the release notes of the package :
Quote:
avtx30, did you tried this before ?
Best regards,
"And I'm disappointed 2.0.17 and the new core team headed phppp.
Sadly, they neglects or ignorants the concept of "compatibility".
Perhaps, I will stop supporting core from xoops.org in not so far future.
Anyway, you can use D3 modules with 2.0.17 just by applying this patch.
http://xoops.peak.ne.jp/md/mydownloads/singlefile.php?lid=110"
Hi guys,
Since a few releases, XOOPS has included a resource.db.php file to overcome the issue you are talking about. And XOOPS 2.0.17 is no different. The package contains an extra folder where this file is located. Documentation about this file is located in the release notes of the package :
Quote:
Unsupported templates access
-----------------------------------
It has come to our knowledge that some modules contain a hacked version of the XOOPS module installation routine and access the templates/blocks database tables directly, bypassing the regular templates declaration mechanisms. Because of this, some recent changes in the templates handling system made those modules unable to access their template data.
If you use one of these modules, you may fix this problem by replacing the resource.db.php file located in the class/smarty/xoops_plugins/ folder by the one provided in the package extras folder. Please note however that such bypassing of standard interfaces through the inclusion of hacked core parts is not supported and that those modules won't work with future versions.
avtx30, did you tried this before ?
Best regards,
Votes:1
Average:0.00
gigamaster
From: Geneva, Switzerland
Posts: 94
From: Geneva, Switzerland
Posts: 94
Hi All,
Do you really need one to tell you what to do?
When i was kid, i learn to not let others tell me what to fear and what to feel. Instead, learn from others and discover my own way to live.
But if you need so...
XOOPS Cube Legacy is a clean code made by professional and skilled people that emulates Xoops2 better than Xoops itself.
2.0.17 is just a bug fix after 3 years of messy development (by people trying to capitalize an open source project - personal opinion!).
Legacy and D3 modules are the future of Xoops2 !
Such configuration assure a new code, compatibility, security, scalability, and the simplicity that made the success of this project with neophyte
My advise: test it and get your own opinion!
Have Fun !
P.S. If you want to test the quality of a module code - just run it with Legacy!
Do you really need one to tell you what to do?
When i was kid, i learn to not let others tell me what to fear and what to feel. Instead, learn from others and discover my own way to live.
But if you need so...
XOOPS Cube Legacy is a clean code made by professional and skilled people that emulates Xoops2 better than Xoops itself.
2.0.17 is just a bug fix after 3 years of messy development (by people trying to capitalize an open source project - personal opinion!).
Legacy and D3 modules are the future of Xoops2 !
Such configuration assure a new code, compatibility, security, scalability, and the simplicity that made the success of this project with neophyte
My advise: test it and get your own opinion!
Have Fun !
P.S. If you want to test the quality of a module code - just run it with Legacy!
Votes:2
Average:10.00
GIJOE
Posts: 4110
Posts: 4110
hi marcan.
Quote:no differences?
I doubt my eyes.
marcan, don't you know how to use "diff"?
Quote:
What a stupid article!
Do you know the meaning of 'db'?
If you want to use file template, use 'file' instead.
"standard interfaces"?
Who defines the "standard" of X2?
D3 modules accesses templates by standard way of XOOPS 2.0.x
Don't forgery "standard" of X2!
And editing XOOPS_ROOT_PATH/modules/*/templates/*.html is insecure.
Because these files are under DocumentRoot.
I know there are many templates robbers.
Also, you should know:
Though I don't agree with such template system of 2.0.14/15/16/17,
my patch never denies your changes.
Just adding the last branch. (read it!)
How many times I write it ...sigh
...OK...
I have to declare "I don't support xoops.org anymore", now.
I cannot go with crowd.
I go with minahito.
He is the real hero.
Quote:
marcan wrotes:
Since a few releases, XOOPS has included a resource.db.php file to overcome the issue you are talking about. And XOOPS 2.0.17 is no different. The package contains an extra folder where this file is located. Documentation about this file is located in the release notes of the package :
I doubt my eyes.
marcan, don't you know how to use "diff"?
Quote:
Unsupported templates access
-----------------------------------
It has come to our knowledge that some modules contain a hacked version of the XOOPS module installation routine and access the templates/blocks database tables directly, bypassing the regular templates declaration mechanisms. Because of this, some recent changes in the templates handling system made those modules unable to access their template data.
If you use one of these modules, you may fix this problem by replacing the resource.db.php file located in the class/smarty/xoops_plugins/ folder by the one provided in the package extras folder. Please note however that such bypassing of standard interfaces through the inclusion of hacked core parts is not supported and that those modules won't work with future versions.
What a stupid article!
Do you know the meaning of 'db'?
If you want to use file template, use 'file' instead.
"standard interfaces"?
Who defines the "standard" of X2?
D3 modules accesses templates by standard way of XOOPS 2.0.x
Don't forgery "standard" of X2!
And editing XOOPS_ROOT_PATH/modules/*/templates/*.html is insecure.
Because these files are under DocumentRoot.
I know there are many templates robbers.
Also, you should know:
Though I don't agree with such template system of 2.0.14/15/16/17,
my patch never denies your changes.
Just adding the last branch. (read it!)
How many times I write it ...sigh
...OK...
I have to declare "I don't support xoops.org anymore", now.
I cannot go with crowd.
I go with minahito.
He is the real hero.
Votes:6
Average:6.67
avtx30
Posts: 36
Posts: 36
I'm totally confused!
Hi marcan,
thank you for your great Smart* modules.
I had read the release_notes before asking GIJOE about the D3 compatibility. The release_notes just made me feel anxious about the future of xoops {core, modules}, so I did not use the resource.db in the extras.
Hi gigamaster,
Please teach me Cube at another thread!
Hi GIJOE,
We xoops users do not know much about the standard or the specs of xoops. We just need the compatibility of modules. My sites are xoops cored since 2.0.13 without info about the branches of xoops (e.g. xoopscube). I want to but CANNOT swith to cube. The hacks, the modules, the db,... I have to go with xoops, the same to the crowd. I need D3 modules too. How to get through?
Yes, I'm totally confused.
Hi marcan,
thank you for your great Smart* modules.
I had read the release_notes before asking GIJOE about the D3 compatibility. The release_notes just made me feel anxious about the future of xoops {core, modules}, so I did not use the resource.db in the extras.
Hi gigamaster,
Please teach me Cube at another thread!
Hi GIJOE,
We xoops users do not know much about the standard or the specs of xoops. We just need the compatibility of modules. My sites are xoops cored since 2.0.13 without info about the branches of xoops (e.g. xoopscube). I want to but CANNOT swith to cube. The hacks, the modules, the db,... I have to go with xoops, the same to the crowd. I need D3 modules too. How to get through?
Yes, I'm totally confused.
Votes:1
Average:10.00
marcan
Posts: 13
Posts: 13
Please come down... I just want to find a solution that will accommodate as many people as possible. Before yesterday I was not aware of all this. But when a user reported an incompatibility with you modules I looked around and found the quote I gave you in the release notes. Thought that this was fixing the problem and perhaps that the user who reported this did not know about this.
Remember, we are a new team in the core development since Skalpa left. And we are doing the very best we can.
So allow me to further inquiry your patch and see it can replace the one in our core. I really was on the impression that the file on the extra folder was addressing this issue.
I will discuss with DJ to see how we could best accomodate everyone.
Cordially,
Remember, we are a new team in the core development since Skalpa left. And we are doing the very best we can.
So allow me to further inquiry your patch and see it can replace the one in our core. I really was on the impression that the file on the extra folder was addressing this issue.
I will discuss with DJ to see how we could best accomodate everyone.
Cordially,
Votes:1
Average:0.00
marcan
Posts: 13
Posts: 13
Oh and a last thing, I just saw this : http://xoops.peak.ne.jp/md/news/index.php?page=article&storyid=354
I did not see this before. Now I do
Remember, we are a new team. We have very little past information.
But we'll get there
Best regards,
I did not see this before
. Now I do Remember, we are a new team. We have very little past information.
But we'll get there
Best regards,
Votes:1
Average:0.00
marcan
Posts: 13
Posts: 13
Here is a post I made about this issue on SourecForge.
http://sourceforge.net/forum/forum.php?thread_id=1813655&forum_id=347994
Bets regards,
http://sourceforge.net/forum/forum.php?thread_id=1813655&forum_id=347994
Bets regards,
Votes:1
Average:0.00
GIJOE
Posts: 4110
Posts: 4110
marcan.
I thank to your kindness.
I thank to your kindness.
Votes:0
Average:0.00
suico
Posts: 7
Posts: 7
Hey GIJOE, who is minahito?
Come on, I have your modules on all my sites and thanks to you I feel more secure. Xoops core developers also love your work, they always mention the importance of having your protector module installed for security reasons. Everyone admire your work, so why unsuport the xoops.org version because of this. I hope you were with your head hot and misunderstood the messages from the admins there, or maybe they were a little lazy to go further understanding your patch. Both ways there is no need for a sepration here. This is open source developement, we must all help each other.
Though, I will respect your decision whatever it will be and hope a lot that you chosse to stay and core developers choose to withdrwal the changes they made that are making some incompatibility with your modules or fix it in a way that both agree. Everyone will win from this.
Come on, I have your modules on all my sites and thanks to you I feel more secure. Xoops core developers also love your work, they always mention the importance of having your protector module installed for security reasons. Everyone admire your work, so why unsuport the xoops.org version because of this. I hope you were with your head hot and misunderstood the messages from the admins there, or maybe they were a little lazy to go further understanding your patch. Both ways there is no need for a sepration here. This is open source developement, we must all help each other.
Though, I will respect your decision whatever it will be and hope a lot that you chosse to stay and core developers choose to withdrwal the changes they made that are making some incompatibility with your modules or fix it in a way that both agree. Everyone will win from this.
Votes:0
Average:0.00
GIJOE
Posts: 4110
Posts: 4110
suico, who are you?
Quote:
I wrote "The real hero".
The developper of XoopsCube core and Legacy 2.1 system.
If you are programmer, read his code once.
All xoopsers in Japan must know his name and his high skill.
Quote:
suico wrotes:
Hey GIJOE, who is minahito?
I wrote "The real hero".
The developper of XoopsCube core and Legacy 2.1 system.
If you are programmer, read his code once.
All xoopsers in Japan must know his name and his high skill.
Votes:0
Average:0.00
GIJOE
Posts: 4110
Posts: 4110
Quote:Why do you think?
Have your head been washed by xoops.org?
It's quite easy to migrate a site into xoopscube.
Just overwrite it.
Though I'm a neutral module developper, I can say XoopsCube Legacy 2.1's code is far better than 2.0/2.2 from xoops.org.
avtx30 wrotes:
Hi GIJOE,
I want to but CANNOT swith to cube.
Have your head been washed by xoops.org?
It's quite easy to migrate a site into xoopscube.
Just overwrite it.
Though I'm a neutral module developper, I can say XoopsCube Legacy 2.1's code is far better than 2.0/2.2 from xoops.org.
Votes:3
Average:6.67
gigamaster
From: Geneva, Switzerland
Posts: 94
From: Geneva, Switzerland
Posts: 94
Quote:
For a xoops user since 2003 with 210 Comments/Posts at xoops.org,
such question is absurd and disrespectful.
[portuguese]
[i]Para um usu
suico wrotes:
Hey GIJOE, who is minahito?
For a xoops user since 2003 with 210 Comments/Posts at xoops.org,
such question is absurd and disrespectful.
[portuguese]
[i]Para um usu
Votes:1
Average:0.00
suico
Posts: 7
Posts: 7
My respected colleague Gigamaster,
Well I didn't mean to be disrespectful, and I am sure that Minahito whoever he is won't feel disrespected by not be known from a simple xoops user like me. I know for many users of xoops knowing every programmer that works with it is a matter of respect or disrespect, but don't feel offended by me, it is really not important for me.
But still, I am one member of this comunity here and xoops.org too. And for this reason , yes I know some names or nicknames like GIJOE but still I don't know Minahito(sorry pal really never heard about you before GIJOE mentionned you).
Not knowing who is Minahito (And at this moment I only know that he's probably a great japanese programmer since GIJOE said that) I hope is not a barrier that will forbidden me to come here more often, as I like a lot the job people do here.
My best Regards,
[portugues]
Desculpa se ofendi algu
Well I didn't mean to be disrespectful, and I am sure that Minahito whoever he is won't feel disrespected by not be known from a simple xoops user like me. I know for many users of xoops knowing every programmer that works with it is a matter of respect or disrespect, but don't feel offended by me, it is really not important for me.
But still, I am one member of this comunity here and xoops.org too. And for this reason , yes I know some names or nicknames like GIJOE but still I don't know Minahito(sorry pal really never heard about you before GIJOE mentionned you).
Not knowing who is Minahito (And at this moment I only know that he's probably a great japanese programmer since GIJOE said that) I hope is not a barrier that will forbidden me to come here more often, as I like a lot the job people do here.
My best Regards,
[portugues]
Desculpa se ofendi algu
Votes:3
Average:3.33
gigamaster
From: Geneva, Switzerland
Posts: 94
From: Geneva, Switzerland
Posts: 94
Honestly I would like to believe you...
But i prefer to think by myself in my quest of knowledge.
And i already know that on the left column of Gijoe site's
there is a block XC developers rings for long now...
Since we are learning from skilled persons alike Mr. Minahito
and Mr. Gijoe among others, recognize sincerely our mistakes
and ignorance is maybe a sign of some respect and intelligence.
Have a nice day!
[portuguese]
Honestamente eu gostaria de acreditar...
Mas eu prefiro pensar por
mim mesmo na busca da verdade e conhecimento.
E sei que na coluna esquerda
do site de Gijoe h
But i prefer to think by myself in my quest of knowledge.
And i already know that on the left column of Gijoe site's
there is a block XC developers rings for long now...
Since we are learning from skilled persons alike Mr. Minahito
and Mr. Gijoe among others, recognize sincerely our mistakes
and ignorance is maybe a sign of some respect and intelligence.
Have a nice day!
[portuguese]
Honestamente eu gostaria de acreditar...
Mas eu prefiro pensar por
mim mesmo na busca da verdade e conhecimento.
E sei que na coluna esquerda
do site de Gijoe h
Votes:3
Average:3.33
Login