PEAK XOOPS - Still learning 
Still learning
- As this forum is only for commentation, you cannot open a new topic
- Guests cannot post into this forum
| Target | News |
| Subject | Templates problem in 2.0.14/15 from xoops.org |
| Summary | In 2.0.14 from xoops.org, the system of templates are modified.You have to see just a function.- Using tplset other than default ... DB template. (== XOOPS 2.0.13)- Using default tplset ... FILE template. (no longer DB template!)-- Try to read /themes/... |
gigamaster
From: Geneva, Switzerland
Posts: 94
From: Geneva, Switzerland
Posts: 94
Oops,
However if they didn't discover anything, they still learning by putting another name on same thing. The emergence of these issues are just the symptoms of what has become so stopped by uncreation that it tries to disguise recycling into progress. At least it contributes to self-improvement and learning development.
It remembers me now that someone already wrote something similar somewhere.
Well, thanks a lot to make it clear!
However if they didn't discover anything, they still learning by putting another name on same thing. The emergence of these issues are just the symptoms of what has become so stopped by uncreation that it tries to disguise recycling into progress. At least it contributes to self-improvement and learning development.
It remembers me now that someone already wrote something similar somewhere.
Well, thanks a lot to make it clear!
Votes:6
Average:8.33
GIJOE
Posts: 4110
Posts: 4110
hi gigamaster.
Your comment is hard to understand for me
Anyway, thank you for the comment.
Your comment is hard to understand for me
Anyway, thank you for the comment.
Votes:2
Average:10.00
Shine
From: Netherlands
Posts: 35
From: Netherlands
Posts: 35
FYI:
Today a new realease of xoops which makes it compatible again.
See: http://www.xoops.org/modules/news/article.php?storyid=3939
Release of XOOPS 2.0.17.1 RC
Quote:
We also took the opportunity of this release to update the resource.db.php located under the extras folder of the package. This file is fixing a problem that may occur with modules not having their templates under module/dirname/templates/. Please carefully read extras/readme.txt for all information.
They've listen to you finally GIJoe
Today a new realease of xoops which makes it compatible again.
See: http://www.xoops.org/modules/news/article.php?storyid=3939
Release of XOOPS 2.0.17.1 RC
Quote:
We also took the opportunity of this release to update the resource.db.php located under the extras folder of the package. This file is fixing a problem that may occur with modules not having their templates under module/dirname/templates/. Please carefully read extras/readme.txt for all information.
They've listen to you finally GIJoe
Votes:22
Average:10.00
GIJOE
Posts: 4110
Posts: 4110
hi Shine.
I've checked the archive.
Certainly I can find "fixed resource.db.php" in extras folder.
But, this is quite NON-SENSE.
Almost Users of the core from xoops.org still ask me how to run my works.
And the poor core team don't understand what I mean at all, sadly.
My patch is just adding a fall-back...
Perhaps, they cannot read PHP code at all
Then I'll target only XoopsCube.
Good-bye! xoops.org.
I've checked the archive.
Certainly I can find "fixed resource.db.php" in extras folder.
But, this is quite NON-SENSE.
Almost Users of the core from xoops.org still ask me how to run my works.
And the poor core team don't understand what I mean at all, sadly.
My patch is just adding a fall-back...
Perhaps, they cannot read PHP code at all
Then I'll target only XoopsCube.
Good-bye! xoops.org.
Votes:2
Average:10.00
GIJOE
Posts: 4110
Posts: 4110
Incidentally...
I did stand neutral zone far from both projects Xoops and XoopsCube.
I am/was making my modules/hacks can work with both XOOPS and XOOPS Cube as possible.
My proud D3 modules works perfectly with XOOPS 2.0.13.2/XOOPS 2.0.16a-JP/XOOPS Cube Legacy 2.1.x
But you -xoops.org- kill the basic compatibility of XOOPS one-sidedly and suddenly in 2.0.14
However the version counts 2.0.17.1RC now, you still ignore my modest proposal "just add fall-backing code for compatibility". (sigh)
That's the reason why I have to stop supporting the core from xoops.org.
Dear "core team" of xoops.org:
read once minahito's entry
http://sunday-lab.blogspot.com/2007/09/core-team-was-dead-2.html
I did stand neutral zone far from both projects Xoops and XoopsCube.
I am/was making my modules/hacks can work with both XOOPS and XOOPS Cube as possible.
My proud D3 modules works perfectly with XOOPS 2.0.13.2/XOOPS 2.0.16a-JP/XOOPS Cube Legacy 2.1.x
But you -xoops.org- kill the basic compatibility of XOOPS one-sidedly and suddenly in 2.0.14
However the version counts 2.0.17.1RC now, you still ignore my modest proposal "just add fall-backing code for compatibility". (sigh)
That's the reason why I have to stop supporting the core from xoops.org.
Dear "core team" of xoops.org:
read once minahito's entry
http://sunday-lab.blogspot.com/2007/09/core-team-was-dead-2.html
Votes:2
Average:10.00
Previous post
-
Next post
|
Parent
-
No child
|
Posted on 2007/9/23 8:41
gigamaster
From: Geneva, Switzerland
Posts: 94
From: Geneva, Switzerland
Posts: 94
Still Learning !
Votes:3
Average:10.00
Login