主題: 請問這個問題要怎麼解決..lifetype1.1全新安裝
作者: 黑夜舞 於 十月 14, 2006, 05:21:45 下午
我是全新安裝... 昨天就一直有問題... 我今天又拆掉重新安裝.. 但是一直卡在這裡..
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
主題: Re: 請問這個問題要怎麼解決..lifetype1.1全新安裝
作者: CrazyLion 於 十月 14, 2006, 07:55:17 下午
類似這種問題嗎? 要不要看看底下的作法 看對你有無幫助 :D
http://forum.lifetype.org.tw/index.php?topic=2715.0
主題: Re: 請問這個問題要怎麼解決..lifetype1.1全新安裝
作者: 黑夜舞 於 十月 15, 2006, 07:21:57 上午
謝謝你.. 不過該連結裡是針對mysql5的.而我是用mysql4.. 他的錯誤訊息.也跟我的不太一樣... 我實在不知道怎麼辦..
因為目前主機上還有phpbb論壇在運作. 所以我不敢亂動一些有的沒的東西..
謝謝你...
繼續努力爬文...
主題: Re: 請問這個問題要怎麼解決..lifetype1.1全新安裝
作者: james 於 十月 15, 2006, 10:05:05 上午
不過該連結裡是針對mysql5的.而我是用mysql4..
Hi 黑夜舞: 這是你的安裝程式內容:●您安裝的程式:Apache 2.0.58 + PHP 4.4.2+MySQL 5.0.22 + phpmyadmin 2.8.2 是我眼花看錯嗎? 怎會前後不一致呢!? 你要不要先確認一下安裝的mysql的版本是多少呢!? James.
主題: Re: 請問這個問題要怎麼解決..lifetype1.1全新安裝
作者: 黑夜舞 於 十月 15, 2006, 10:39:56 上午
不好意思.. 我的是mysql5.. 最近才升級.腦袋一直卡在mysql4.抱歉抱歉...
該連結裡提供的方式.我實在看不懂說.. 而那個解決成功的方法.又扯到別的程式.. 實在令人一個頭兩個大耶...
另外..因為一直卡在這裡. 而如果重新安裝的話.都會出現叫我把wizard.php移除的資訊. 我就試著把他改掉.發現wizard.php改掉之後. 有出現blog的畫面.但仍舊無法使用...
我又把資料表全刪了.再重新安裝... 但又卡在同一個地方 / \
主題: Re: 請問這個問題要怎麼解決..lifetype1.1全新安裝
作者: CrazyLion 於 十月 15, 2006, 12:27:26 下午
你用appserv的話 可以在appserv的捷徑中找到MySQL Edit the my.ini Configuration File 這個 然後點下去後 找到 restrict mode 然後把這兩個字刪除,那一串設定可能是用 ,隔開,記得多刪一個,就好囉:D 刪完存檔,然後重開mysql 看看 這樣行不行 :P
不過先把這個檔案備份一下啦XD
主題: Re: 請問這個問題要怎麼解決..lifetype1.1全新安裝
作者: 黑夜舞 於 十月 15, 2006, 04:24:11 下午
咦...引用會出現一堆亂碼.. 我照樓上大大的方式打開了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
主題: Re: 請問這個問題要怎麼解決..lifetype1.1全新安裝
作者: CrazyLion 於 十月 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
主題: Re: 請問這個問題要怎麼解決..lifetype1.1全新安裝
作者: 黑夜舞 於 十月 15, 2006, 08:00:42 下午
謝謝~ 我安裝成功了.. 不過為什麼這邊改掉就ok了呢?
對其他已安裝的程式會有影響嗎?
主題: Re: 請問這個問題要怎麼解決..lifetype1.1全新安裝
作者: CrazyLion 於 十月 15, 2006, 08:14:00 下午
謝謝~ 我安裝成功了.. 不過為什麼這邊改掉就ok了呢?
對其他已安裝的程式會有影響嗎?
嚴格模式不吃null :D 應該是這樣 @@ 不會影響其他程式啦
|