Does it need xoops_excape? or doesn't?

• 回報者: minahito
• 負責人: minahito
• 類型: XOOPSCube2.1 Bugs
• 狀態: 關閉
• 元件: (無)
• 里程碑: (無)
• 優先權: 3
• 嚴重程度: 5 - 中
• 處理結果: 修正
• 檔案: 無

細節 回覆

Reported by Okuhiki,

/modules/legacy/admin/theme/admin_theme.html Line76

Reporter said that 'xoops_escape' may be need here for
$menu.link as the following:

<li><a
href="<{$menu.link|xoops_escape:link}>"><{$menu.title|xoops_escape:link}></a></li>

But, for the compatibility, we may not have to embed
'xoops_escape' here. We need to check whether xoops
2.0.x escapes menu links in the core side.

Ticket History (3/3 Histories)

2007-02-19 14:29 Updated by: minahito

• 負責人 Update from (無) to minahito
• 處理結果 Update from 無 to Accepted

評語 回覆

Logged In: YES
user_id=8353

> But, for the compatibility, we may not have to embed
> 'xoops_escape' here. We need to check whether xoops
> 2.0.x escapes menu links in the core side.

XOOPS 2.0.x handles these values as escaped values, so our
templates should not embed them with escape-modifier. But,
it does not follow XOOPS Cube's policy which developers
handle all values as unescaped values.

Umm...,

To solve these issues, I had to introduce new array key.

More Informations:
http://xoopscube.org/modules/pukiwiki/?XOOPSCubeLegacy%2FReference%2FValueMethodologyOverview

2007-02-19 14:32 Updated by: minahito

• 處理結果 Update from Accepted to 修正

評語 回覆

Logged In: YES
user_id=8353

It may be good spec that modules which are defined
'cube_style' have "escaped=false" automatically.

2007-02-19 15:58 Updated by: minahito

• Ticket Close date is changed to 2007-02-19 15:58
• 狀態 Update from 開啟 to 關閉