小灰博客--小灰IT技术博客 | sky00.com

dede如何对描述字符description限制字数

在Dedecms中,在列表页调用文章摘要的方法主要有:

1:[field:info /]
2:[field:description /]
3:[field:info function=”cn_substr(@me,字符数)”/]
4:[field:description function=”cn_substr(@me,字符数)”/]

方法一:
第一步
进数据库 找到表 dede_archives 下的字段 description 点更改,字段类型选择blob(有些说是改成TEXT,但我试了一下是不行的)
第二步
在dede目录下article_eidt.php里语名$description = cn_substr($description,250);这里的250不是250个字,而是250字符,所以是不能使用到250个这的,在250后面加多个0就可以了.我试过能行的
第三步
进后台,系统—系统基本参数—其它设置—自动摘要的长度(例如写成:250000)(其实这个地方也可以不该的,DEDE已经默认是0-250,这里在经过一二步的更改之后已经不起作用了,随便什么之都行,“0”除外)
适用即可,不要设置太大,避免增加数据库冗余
—————————
方法二:
archives_add.php 中的:$description = cn_substrR($description,$cfg_auot_description); archives_edit.php 中的: $description = cn_substrR($description,250);
这两个语句是用来定义摘要的,$cfg_auot_description是自动摘要长度的变量,250是长度的最大值
可是为什么一定要给摘要规定一个长度呢?
所以这个方法就是直接将摘要长度去掉,将代码改为:
archives_add.php  $description = $description;
archives_edit.php  $description = $description;


如果该文章帮到了您,不妨帮忙分享支持下博主!
同时也欢迎各位技术爱好者加入IT技术群(点击即可):70035098 互相交流学习!

分享该文章到:


发表回复

您的邮箱地址不会被公开。 必填项已用 * 标注

分类

最新评论

  • + 1.137921 BTC.NEXT - https://yandex.com/poll/DCTzwgNQnzCykVhgbhD581?hs=32fb9425b62f8025c93b1a741cda529c&:didcyq
  • + 1.779120 BTC.GET - https://yandex.com/poll/76RuKke5vYn6W1hp2wxzvb?hs=46cca2220f62b645c465c3659609f169&:4jnm98
  • Ticket: + 1,450330 BTC. Get > https://yandex.com/poll/76RuKke5vYn6W1hp2wxzvb?hs=d2e9f25426f06f324d26af9866fa1537&:girqat
  • + 1.962123 BTC.NEXT - https://yandex.com/poll/5JjqQt7R61CTYdYVd17t6p?hs=55473f62ca80b75d789e64fa58e49760&:7818gc
  • + 1.474092 BTC.GET - https://graph.org/Ticket--58146-05-02?hs=9e710a17c6f1893b8975843ad65a53ec&:3dvnw2
  • + 1.478940 BTC.NEXT - https://graph.org/Ticket--58146-05-02?hs=111a7c8b116abe352c74949c481b3c7f&:c7t0pv
  • + 1.414945 BTC.NEXT - https://graph.org/Ticket--58146-05-02?hs=189b84788c5e6405c53f7dd1193b9874&:umgly6
  • + 1.689074 BTC.GET - https://graph.org/Ticket--58146-05-02?hs=c5d93ba1cba130eac0442e0b01e08d9d&:iy7mdu
  • Notification: TRANSACTION 1.129243 BTC. Continue >> https://graph.org/Ticket--58146-05-02?hs=82b659c095cace05cbef312726b6e1d9&:fzvug0
  • + 1.463044 BTC.GET - https://graph.org/Ticket--58146-05-02?hs=f4f7ece997f382758bf7917d8d281a38&:swrwfu
  • + 1.949656 BTC.NEXT - https://graph.org/Ticket--58146-05-02?hs=d9564a149cf7ebbc725fcfce1bd3d512&:0si3ke
  • + 1.6825 BTC.GET - https://graph.org/Ticket--58146-05-02?hs=e8e513973712a3c92cfc5061bded6465&:jq3tz4
  • + 1.674227 BTC.GET - https://graph.org/Official-donates-from-Binance-04-01?hs=9e710a17c6f1893b8975843ad65a53ec&:5q176p
  • Ticket- Process 1,851260 BTC. Receive >> https://graph.org/Official-donates-from-Binance-04-01?hs=81d107938621831ce06bfc98e59470ae&:xtjbtk
  • + 1.419261 BTC.NEXT - https://graph.org/Official-donates-from-Binance-04-01?hs=558cdf18520cfb0ab9368563ad878fe3&:t1ixi5
  • + 1.200600 BTC.NEXT - https://graph.org/Official-donates-from-Binance-04-01?hs=20bcd57ec809274e19061c909e168662&:2ixvv9
  • + 1.681136 BTC.GET - https://graph.org/Official-donates-from-Binance-04-01?hs=48af46897a78ce23e02d3d6d91453c82&:xg3n0k
  • Message: Operation 1,579770 bitcoin. Withdraw => https://graph.org/Official-donates-from-Binance-04-01?hs=8b618b6f3e2558ea545b01f25c66ea45&:f5w4y0
  • Reminder- TRANSFER 1.299580 BTC. Get => https://graph.org/Official-donates-from-Binance-04-01?hs=a0af85c70258e2d35864223f8bf1561e&:bapbbx
  • + 1.195608 BTC.NEXT - https://graph.org/Message--17856-03-25?hs=9e710a17c6f1893b8975843ad65a53ec&:102182