1, When I create a content by pico, there is some filters option like this:
Quote:
10 HTML special character escape
20 Smiley
30 BBCode
40 Auto new line
0 php code
0 Page wraps (note: the file specified by virtual path is displayed instead of body
0 Smarty(XoopsTpl)
15 PEAR TextWiki
What meaning each line of front the number is?
2, How can I wrap a content into pico?
Regards,
walkman
Quote:
walkman wrotes:
1, When I create a content by pico, there is some filters option like this:
(snip)
What meaning each line of front the number is?
An order to be processed
Quote:
2, How can I wrap a content into pico?
Almost same as wraps module.
- Make a folder XOOPS_TRUST_PATH/wraps/(dirname)
- Put files into the folder
It is hard to explain pico's spec of wrapping in few sentences.
I'll add pico's manual which is translated by machine from my Japanese into English.
It is expected. Thank you very much.
Here is the automated manual
http://xoops.peak.ne.jp/md/repository/manuals/pico_manual_e.htmlI know it is hard to read and should be fixed...
Thank you, GIJOE. I'll try to read it.
In the "Wraps mode", "Virtual pass" should be "Virtual path"?
Sure.
Almost pass should be path.
(In Japanese, the two words have same spelling each other)
It looks quite bad translation ...
Quote:
Almost same as wraps module.
- Make a folder XOOPS_TRUST_PATH/wraps/(dirname)
- Put files into the folder
What should the virtual path look like?
wraps/maps/map.html
/wraps/maps/map.html
/wraps/maps/
/wraps/maps
wraps/maps
any of these?
You can select a file for wrapping by the drop down.
well dumbie me must have something messed up in setup......all I get under virtual path in the drop down is "---"
Below is the directory structure...
xoops
|
|
-modules
-xoops_trust_path
|
-wraps
|
-dir1
|
-file1.ext
-dir2
Which dirname do you install pico?
This is a sample of directory structures.
xoops
|
-modules
|
-pico
xoops_trust_path
|
-wraps
|
-pico
|
-dir1
|
-file1.ext
-dir2
And you'd better place xoops_trust_path outside of xoops.
Or, add .htaccess (deny from all) just under xoops_trust_path/