PEAK XOOPS - Re: Templates problem in 2.0.14/15 from xoops.org 
Re: Templates problem in 2.0.14/15 from xoops.org
- As this forum is only for commentation, you cannot open a new topic
- Guests cannot post into this forum
| Target | News |
| Subject | 本家版2.0.14/15のハマリ点 |
| Summary | 本家版2.0.14では、テンプレートの扱いが大きく変わった、ということだけは知っていたのですが、wrapsが動かない、という症状を改善するためにあちこち追ってみて、どこなのかがようやくわかりました。いわゆる肝は１箇所だけです。下のソースコードを読むのが一番手っ取... |
Previous post
-
Next post
|
Parent
-
Children.1
|
Posted on 2006/12/27 9:19
borpin
Posts: 1
Posts: 1
I think I solved the problem for 2.0.15 for me anyway!. It is difficult to explain. I am calling my folder testwrap so I will use that. The system was looking for a template file templates/testwrap_index.html in the normal /modules/testwrap/ directory instead of the trusted path directory. I copied the file /trusted_path/modules/templates/index.html to a new folder /modules/testwrap/templates/testwrap_index.html and that seemed to do the trick.
I looked at the oninstall and onupdate files and they seem to be the problem, but as I do not understand the templates I can't fix it!
I looked at the oninstall and onupdate files and they seem to be the problem, but as I do not understand the templates I can't fix it!
Votes:3
Average:10.00
GIJOE
Posts: 4110
Posts: 4110
Quote:In the way, you have to copy and rename the templates manually for every modules.
At least, I cannot do such a bother way. lol
I say again, this is an incompatibility just with core 2.0.14/15/16 from xoops.org
Core team of xoops.org should fix it.
Just insert a few lines
I copied the file /trusted_path/modules/templates/index.html to a new folder /modules/testwrap/templates/testwrap_index.html and that seemed to do the trick.
At least, I cannot do such a bother way. lol
I say again, this is an incompatibility just with core 2.0.14/15/16 from xoops.org
Core team of xoops.org should fix it.
Just insert a few lines
Votes:3
Average:10.00
Bandit-x
From: UsA - MiChIgAn
Posts: 17
From: UsA - MiChIgAn
Posts: 17
Quote:
but they are not . since the template files are supposed to be in the . templates directory.
Found It On SF.Net.
http://sourceforge.net/tracker/index.php?func=detail&aid=1549165&group_id=41586&atid=...
GIJOE wrotes:
I say again, this is an incompatibility just with core 2.0.14/15/16 from xoops.org
Core team of xoops.org should fix it.
Just insert a few lines
but they are not . since the template files are supposed to be in the . templates directory.
Found It On SF.Net.
http://sourceforge.net/tracker/index.php?func=detail&aid=1549165&group_id=41586&atid=...
Votes:4
Average:5.00
GIJOE
Posts: 4110
Posts: 4110
Quote:Are you a member of core team of xoops.org?
Thus, I have to say you misunderstood the original spec of template system.
XOOPS uses DB template instead of FILE template for modules or blocks.
(Just theme uses FILE template system)
This is the real 2.0.x spec.
Only 2.0.14/15/16 from xoops.org break the compatibility.
Of course, 2.0.16 from xoopscube.org follow the compatilibity
If you break the compatilibity, you should number them 2.1.x or 2.2.x etc.
And do you know template robber?
XOOPS_ROOT_PATH/modules/(dirname)/template
is almost PUBLIC and anyone can access the template.
(Though my modules are protected by .htaccess)
Base templates for DB templates should be out of DocumentRoot.
This is just one of the reason I use XOOPS_TRUST_PATH
Bandit-x wrotes:
but they are not . since the template files are supposed to be in the . templates directory.
Thus, I have to say you misunderstood the original spec of template system.
XOOPS uses DB template instead of FILE template for modules or blocks.
(Just theme uses FILE template system)
This is the real 2.0.x spec.
Only 2.0.14/15/16 from xoops.org break the compatibility.
Of course, 2.0.16 from xoopscube.org follow the compatilibity
If you break the compatilibity, you should number them 2.1.x or 2.2.x etc.
And do you know template robber?
XOOPS_ROOT_PATH/modules/(dirname)/template
is almost PUBLIC and anyone can access the template.
(Though my modules are protected by .htaccess)
Base templates for DB templates should be out of DocumentRoot.
This is just one of the reason I use XOOPS_TRUST_PATH
Votes:3
Average:6.67
Bandit-x
From: UsA - MiChIgAn
Posts: 17
From: UsA - MiChIgAn
Posts: 17
im just the messenger.
Votes:2
Average:10.00
Previous post
-
Next post
|
Parent
-
No child
|
Posted on 2006/12/29 6:35
GIJOE
Posts: 4110
Posts: 4110
hi Bandit-x
Quote:OK
Thus, I'm stacking another message
2.0.14's incompatibility means the resource 'db:' interprets 'file:'.
This is a contradiction for the resource type of Smarty.
But I never deny your "modification" just by logical consistencies.
I just mean merging your modification and the compatibility.
I believe you can aware my patch never denies the 2.0.14's modification but it goes together the new feature in XOOPS >= 2.0.14 and compatibility with XOOPS <= 2.0.13.2
Quote:
im just the messenger.
Thus, I'm stacking another message
2.0.14's incompatibility means the resource 'db:' interprets 'file:'.
This is a contradiction for the resource type of Smarty.
But I never deny your "modification" just by logical consistencies.
I just mean merging your modification and the compatibility.
I believe you can aware my patch never denies the 2.0.14's modification but it goes together the new feature in XOOPS >= 2.0.14 and compatibility with XOOPS <= 2.0.13.2
Votes:3
Average:6.67
Login