å…ˆå‘ä½ èªªè²æŠ±æ­‰ï¼Œç„¡æ³•å‹å–„çš„å›žæ‡‰ä½ çš„å•é¡Œã€‚
å¦‚æžœå› ç‚ºæˆ‘çš„å›žæ‡‰ç…§æˆä½ çš„ä»»ä½•ä¸èˆ’æœï¼Œå†æ¬¡å‘ä½ èªªè²æŠ±æ­‰ã€‚

我想我必需先做些簡單的說明：
從接觸plog到現在已經快3年了，我從來沒有覺得我對plog有多熟悉。

James.

不好意思...(我引用還是會亂碼 = =|||)

我真的很感謝大大們的分享...
無意冒犯..
文件裡的功能影音說明真的蠻不錯..
不過我剛進來的時候真的不知該從哪裡找起..
而通常最容易想到的地方.就是討論區找起..
因為討論區通常會有很多差不多的使用者問題..
沒安裝成功之前.說真的沒人會去看那個什麼功能如何使用的說明
(而且點了那個連結之後.竟然還連到英文的網頁.傻眼...這不是中文支援站嗎 @@".或許當時網頁有問題吧..)
全新安裝一個程式.卡在同一個地方2天.也找不到相關的問題答案..
或許也讓我急躁了吧..
才讓我冒出.這對新手真的不太友善的感覺...
因為教學文件裡...(嗯..那個文件的標題.或許改成"教學文件"會比較好...)
並沒有提到會有這樣的問題...及可以怎麼解決的辦法..

LifeType 這真的是不錯的blog程式...(我也是看到其他大大的blog才經由連結過來的..)
不然我也不會傻傻的花了4天在安裝和摸索使用介面上...

整合論壇的問題.我暫時放下了...
造成困擾,很抱歉....

祝有愉快的一天...
謝謝~

ps.我會努力摸索LifeType,期望自己哪天也能貢獻一點小小的心力...謝謝~

試了好久.還是有問題 /  \
在論壇上新增會員可以成功使用blog.
在blog註冊也可以使用論壇.(不過會員的註冊時間會變成1970年x月x日 @@")
但在 summary.php會無法正常顯示畫面

Fatal error: Call to a member function on a non-object in D:\php-web\AppServ\www\blog\class\dao\userdata\baseuserdataprovider.class.php on line 109

而且論壇上的舊成員.無法直接使用blog.
沒整合前的管理員身份在整合後也進不了後台...
看來整合果然不是一件簡單的事情..

決定先放過自己幾天.
不然這幾天腦袋裡都是blog..blog..會瘋掉 = =|||
先乖乖玩單純的blog好了 >"<

革命仍未成功,同志仍需努力 >"<
謝謝~

抱歉~我無意冒犯....

在我發問之前.都是有搜尋過文章..
也看過所有能看的東西...
(在註冊會員前我也己經爬了2.3天的文章了..)
我英文不好..但我很努力用翻譯網頁來了解那些英文寫了什麼東東...

我已經搜尋了兩天了...
除了找到那個plog1.02整合phpbb2.0.18的失效連結以外...
沒發現其他能用的..用google搜尋出來的.也是人家沒得到解答的問題.
要不就是又連結失效的...

一個安裝的問題,花了我兩天的時間...
裝好了.自己去摸索那些功能.又花了2天...
明明一個早己被問過很多遍的問題..
我翻來翻去.爬來爬去.卻沒有一個解答...
有的也只是...
"已經有相關的問題了,請愛用搜尋...."

天知道搜尋有用的話.我幹嘛還來發問浪費版面....浪費大家的時間....

我知道問問題.人家不一定要回答我...
在沒有人幫我解答之前,我自己也很努力找答案..

(在我安裝一開始的時候出問題,我blog程式和資料庫反覆刪了n次,
兩天我什麼都沒做.搜尋了各大網頁,有看到大大的連結,我就點過去看,
反覆的刪除.安裝.刪除.安裝,就為了找那一個問題點..
終於有大大給了我解答.我得以更進一步的使用這個程式.
在摸索功能的過程中.我因為一個設定不對.也反覆安裝了好幾次.終於摸出一些使用心得)

有幫我的大大我都抱著很感恩的心...

但是否能在友善一點~
在新人苦惱時.能指點一條明路....
給個連結也好....
對英文苦手的人..真的是一個路標..
會來中文支援站的人.多少是對英文有點不行的,
不然直接往英文站找資料不就好了嗎...

或許您對LifeType己經很熟了..
但請別忘了還有人只是一個小小的新手...
我無意冒犯各位辛苦的大大們..
我只是一個剛接觸這個大家庭的小朋友..
抱著卑微的心.在這裡虛心求教....
也期望自己有一天能將所學回饋給大家..
謝謝~


關於phpbb的整合.還請好心的大大們指點一條明路..
謝謝~

奇怪.我要引用都一堆亂碼 = =

不好意思.我想請問你.
你是在哪找到整合phpbb的資料的..
我搜尋了半天.唯一找到和plog整合phpbb相關的大陸連結.也失效..
感覺上LifeType的支援不太完整, 好像很多都變成非公開資訊..
只有熟的人才知道.對剛入門的新手真的不太友善 >"<
挫折感十足  冏rz

謝謝~
我安裝成功了..
不過為什麼這邊改掉就ok了呢?

對其他已安裝的程式會有影響嗎?

咦...引用會出現一堆亂碼..

我照樓上大大的方式打開了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

不好意思..
我的是mysql5..
最近才升級.腦袋一直卡在mysql4.抱歉抱歉...

該連結裡提供的方式.我實在看不懂說..
而那個解決成功的方法.又扯到別的程式..
實在令人一個頭兩個大耶...

另外..因為一直卡在這裡.
而如果重新安裝的話.都會出現叫我把wizard.php移除的資訊.
我就試著把他改掉.發現wizard.php改掉之後.
有出現blog的畫面.但仍舊無法使用...

我又把資料表全刪了.再重新安裝...
但又卡在同一個地方 /  \

謝謝你..
不過該連結裡是針對mysql5的.而我是用mysql4..
他的錯誤訊息.也跟我的不太一樣...
我實在不知道怎麼辦..

因為目前主機上還有phpbb論壇在運作.
所以我不敢亂動一些有的沒的東西..

謝謝你...

繼續努力爬文...

我是全新安裝...
昨天就一直有問題...
我今天又拆掉重新安裝..
但是一直卡在這裡..

Fatal error: Call to a member function on a non-object in D:\php-web\AppServ\www\blog\class\dao\articles.class.php on line 669
請問是哪裡有問題嗎...我第一次使用這個blog程式.
請幫幫忙..

架站環境
●架設主機作業系統：Windows Xp Pro
●快速架站程式：Appserv2.4.6
●您安裝的程式：Apache 2.0.58 + PHP 4.4.2+MySQL 5.0.22 + phpmyadmin 2.8.2