列出文章
|
頁: [1] 2 3 4
|
1
|
開發 / 核心補強精華區 / Re: 請問如何在 summary.php實做最新迴響?
|
於: 十一月 17, 2006, 08:49:11 下午
|
帮帮我啊!我照这个做了(我现在的版本是1.1.2),并在summarydefaultaction.class.php中加入了:$this->_view->setValue("recentComments",$recentComments); 另外几句,照你原来的,找不到了。现在这样子,在index.template中却不能显示出最新评论,麻烦看看是怎么回事?哪位大哥帮帮我? 谢谢了。
1.1.2我還沒試耶 我晚點幫你測看看 :P
|
|
|
2
|
開發 / 核心補強精華區 / Re: 請問如何在 summary.php實做最新迴響?
|
於: 十月 15, 2006, 08:16:57 下午
|
for 1.1的版本: 把 class/summary/dao/summarystats.class.php裡的 function getRecentComments( $maxComments = 20) 裡面的所有程式碼換成 換成 include_once( PLOG_CLASS_PATH.'class/dao/articlecomments.class.php' ); include_once( PLOG_CLASS_PATH.'class/dao/usercomment.class.php' ); include_once( PLOG_CLASS_PATH."class/dao/articles.class.php" ); $articleComments = new ArticleComments(); $articles = new Articles(); $prefix = $this->getPrefix(); $query = "SELECT * FROM {$prefix}articles_comments WHERE status = 0 ORDER BY date DESC LIMIT 0,".$maxComments; $result = $this->Execute($query); if(!$result) return false; $recentComments = Array(); while( $row = $result->FetchRow()){ $comment = $articleComments->getComment($row['id']); $comment->setArticle($articles->getArticle[$row['article_id']]); array_push($recentComments,$comment); } $result->Close(); return $recentComments;
這次簡潔多了阿!!! 1.1真不賴 :D
|
|
|
4
|
支援 / 安裝與設定 / Re: 請問這個問題要怎麼解決..lifetype1.1全新安裝
|
於: 十月 15, 2006, 05:58:32 下午
|
咦...引用會出現一堆亂碼.. 我照樓上大大的方式打開了my.ini. 但眼睛太大.找不到大大說的地方.. # MySQL Server Instance Configuration File # ---------------------------------------------------------------------- # Generated by the MySQL Server Instance Configuration Wizard # # # Installation Instructions # ---------------------------------------------------------------------- # # On Linux you can copy this file to /etc/my.cnf to set global options, # mysql-data-dir/my.cnf to set server-specific options # (@localstatedir@ for this installation) or to # ~/.my.cnf to set user-specific options. # # On Windows you should keep this file in the installation directory # of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To # make sure the server reads the config file use the startup option # "--defaults-file". # # To run run the server from the command line, execute this in a # command line shell, e.g. # mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini" # # To install the server as a Windows service manually, execute this in a # command line shell, e.g. # mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini" # # And then execute this in a command line shell to start the server, e.g. # net start MySQLXY # # # Guildlines for editing this file # ---------------------------------------------------------------------- # # In this file, you can use all long options that the program supports. # If you want to know the options a program supports, start the program # with the "--help" option. # # More detailed information about the individual options can also be # found in the manual. # # # CLIENT SECTION # ---------------------------------------------------------------------- # # The following options will be read by MySQL client applications. # Note that only client applications shipped by MySQL are guaranteed # to read this section. If you want your own MySQL client program to # honor these values, you need to specify it as an option during the # MySQL client library initialization. # [client]
port=3306
[mysql]
default-character-set=latin1
# SERVER SECTION # ---------------------------------------------------------------------- # # The following options will be read by the MySQL Server. Make sure that # you have installed the server correctly (see above) so it reads this # file. # [mysqld]
# The TCP/IP Port the MySQL Server will listen on port=3306
#Path to installation directory. All paths are usually resolved relative to this. basedir="D:/php-web/AppServ/MySQL"
#Path to the database root datadir="D:/php-web/AppServ/MySQL/data/"
# The default character set that will be used when a new schema or table is # created and no character set is defined default-character-set=latin1
# The default storage engine that will be used when create new tables when #default-storage-engine=INNODB
# Set the SQL mode to strict sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
# The maximum amount of concurrent sessions the MySQL server will # allow. One of these connections will be reserved for a user with # SUPER privileges to allow the administrator to login even if the # connection limit has been reached. max_connections=16384
# Query cache is used to cache SELECT results and later return them # without actual executing the same query once again. Having the query # cache enabled may result in significant speed improvements, if your # have a lot of identical queries and rarely changing tables. See the # "Qcache_lowmem_prunes" status variable to check if the current value # is high enough for your load. # Note: In case your tables change very often or if your queries are # textually different every time, the query cache may result in a # slowdown instead of a performance improvement. query_cache_size=0
# The number of open tables for all threads. Increasing this value # increases the number of file descriptors that mysqld requires. # Therefore you have to make sure to set the amount of open files # allowed to at least 4096 in the variable "open-files-limit" in # section [mysqld_safe] table_cache=256
# Maximum size for internal (in-memory) temporary tables. If a table # grows larger than this value, it is automatically converted to disk # based table This limitation is for a single table. There can be many # of them. tmp_table_size=9M
# How many threads we should keep in a cache for reuse. When a client # disconnects, the client's threads are put in the cache if there aren't # more than thread_cache_size threads from before. This greatly reduces # the amount of thread creations needed if you have a lot of new # connections. (Normally this doesn't give a notable performance # improvement if you have a good thread implementation.) thread_cache_size=8
#*** MyISAM Specific options
# The maximum size of the temporary file MySQL is allowed to use while # recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE. # If the file-size would be bigger than this, the index will be created # through the key cache (which is slower). myisam_max_sort_file_size=100G
# If the temporary file used for fast index creation would be bigger # than using the key cache by the amount specified here, then prefer the # key cache method. This is mainly used to force long character keys in # large tables to use the slower key cache method to create the index. myisam_max_extra_sort_file_size=100G
# If the temporary file used for fast index creation would be bigger # than using the key cache by the amount specified here, then prefer the # key cache method. This is mainly used to force long character keys in # large tables to use the slower key cache method to create the index. myisam_sort_buffer_size=17M
# Size of the Key Buffer, used to cache index blocks for MyISAM tables. # Do not set it larger than 30% of your available memory, as some memory # is also required by the OS to cache rows. Even if you're not using # MyISAM tables, you should still set it to 8-64M as it will also be # used for internal temporary disk tables. key_buffer_size=10M
# Size of the buffer used for doing full table scans of MyISAM tables. # Allocated per thread, if a full scan is needed. read_buffer_size=64K read_rnd_buffer_size=256K
# This buffer is allocated when MySQL needs to rebuild the index in # REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE # into an empty table. It is allocated per thread so be careful with # large settings. sort_buffer_size=256K
log-slow-queries=mysql-slow.log log-error=mysql.err
#*** INNODB Specific options ***
# Use this option if you have a MySQL server with InnoDB support enabled # but you do not plan to use it. This will save memory and disk space # and speed up some things. skip-innodb
# Additional memory pool that is used by InnoDB to store metadata # information. If InnoDB requires more memory for this purpose it will # start to allocate it from the OS. As this is fast enough on most # recent operating systems, you normally do not need to change this # value. SHOW INNODB STATUS will display the current amount used. innodb_additional_mem_pool_size=2M
# If set to 1, InnoDB will flush (fsync) the transaction logs to the # disk at each commit, which offers full ACID behavior. If you are # willing to compromise this safety, and you are running small # transactions, you may set this to 0 or 2 to reduce disk I/O to the # logs. Value 0 means that the log is only written to the log file and # the log file flushed to disk approximately once per second. Value 2 # means the log is written to the log file at each commit, but the log # file is only flushed to disk approximately once per second. innodb_flush_log_at_trx_commit=1
# The size of the buffer InnoDB uses for buffering log data. As soon as # it is full, InnoDB will have to flush it to disk. As it is flushed # once per second anyway, it does not make sense to have it very large # (even with long transactions). innodb_log_buffer_size=1M
# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and # row data. The bigger you set this the less disk I/O is needed to # access data in tables. On a dedicated database server you may set this # parameter up to 80% of the machine physical memory size. Do not set it # too large, though, because competition of the physical memory may # cause paging in the operating system. Note that on 32bit systems you # might be limited to 2-3.5G of user level memory per process, so do not # set it too high. innodb_buffer_pool_size=17M
# Size of each log file in a log group. You should set the combined size # of log files to about 25%-100% of your buffer pool size to avoid # unneeded buffer pool flush activity on log file overwrite. However, # note that a larger logfile size will increase the time needed for the # recovery process. innodb_log_file_size=10M
# Number of threads allowed inside the InnoDB kernel. The optimal value # depends highly on the application, hardware as well as the OS # scheduler properties. A too high value may lead to thread thrashing. innodb_thread_concurrency=8 對不起>"<是我的問題, 請把 87行那邊的 # Set the SQL mode to strict sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION" 改成 # Set the SQL mode to strict sql-mode=NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION 然後mysql重開 且lifetype重裝 看看:P 都是我的錯!! 希望對你有幫助阿T_T
|
|
|
5
|
支援 / 安裝與設定 / Re: 請問這個問題要怎麼解決..lifetype1.1全新安裝
|
於: 十月 15, 2006, 12:27:26 下午
|
你用appserv的話 可以在appserv的捷徑中找到MySQL Edit the my.ini Configuration File 這個 然後點下去後 找到 restrict mode 然後把這兩個字刪除,那一串設定可能是用 ,隔開,記得多刪一個,就好囉:D 刪完存檔,然後重開mysql 看看 這樣行不行 :P
不過先把這個檔案備份一下啦XD
|
|
|
10
|
支援 / 安裝與設定 / 請問一下使用自訂網址,部落格網址前一定要有/blog嗎?
|
於: 十月 13, 2006, 11:24:53 下午
|
請問一下,今天從1.06升級到1.1 可是發現使用自訂網址每個部落格的網址都會變成 xxxx.edu.tw/lifetype/blog/{blogname},我在設定的地方把/blog拿掉,可是就會找不到了。 請問原本可以使用xxxx.edu.tw/lifetype/{blogname} 這種格式,現在是不是不行了呢? 謝謝 。
|
|
|
12
|
開發 / 核心補強 / 垃圾迴響者沒有ip
|
於: 九月 01, 2006, 10:32:27 下午
|
最近我們實驗室被垃圾迴響弄得很煩@@...(1.06版) 我從後台看有些迴響的ip是空的 如附圖。 不知道ip是空的 是不是就代表這個迴響者有問題? 如果是的話,可能要先動手修一下了 :P
不知道1.1.是否已經過濾掉了呢:P
|
|
|
14
|
建議 / 發表與交流 / Re: 帶我爸到現在最熱門的部落格
|
於: 八月 26, 2006, 07:34:26 下午
|
那我請問一下像是蕃薯藤使用lifetype改的網誌那些,也沒公開原始碼 這樣可以嗎?@@ 搞不懂GPL阿 :P
实际上这样做是违反GPL协议的,但这个嘛。。这个。。。这样说吧,大家大概都知道这个 世界上有部分人就是喜欢做违反游戏规则的事情。而且由于软体的特殊性质,要毁灭证据 也是很容易,所以大概只能靠自律了。 感謝解答 原來如此 。 不過我看mark的網誌 似乎沒有很不高興阿?
|
|
|
|
|
|