| Re: Warning [Xoops]: Smarty error: unable to read resource: "db:system_block_login.html" |
| by ghia on 2009/4/29 9:57:11 Seems it has to do with older versions of MySQL not correctly handling the used UTF-8 character set. I try to find an upgrading solution for it. |
| Warning [Xoops]: Smarty error: unable to read resource: "db:system_block_login.html" |
| by ghia on 2009/4/28 22:09:17 I get some warnings like these after I installed a XOOPS 2.2.6 on an older PHP 4.3.9 and MySQL 4.1.20 box. Result is that the content of the site and blocks are empty. The theme is showed and admin parts which don't use Smarty are working. I traced the cause of this error to the query for the template, which doesn't find the records. le="color: #000000"><?php SELECT * FROM xoops_tplfile WHERE (tpl_tplset = 'default' AND tpl_file = 'system_block_user.html') ORDER BY tpl_refid In phpMyAdmin are no result records returned and no syntax errors are flagged. When only one part is used of the where clause as in le="color: #000000"><?php SELECT * FROM xoops_tplfile WHERE (tpl_tplset = 'default' ) ORDER BY tpl_refid le="color: #000000"><?php SELECT * FROM xoops_tplfile WHERE (tpl_file = 'system_block_user.html') ORDER BY tpl_refid There are 2 and 39 records in the results, with the targeted record in both sets. Strange is that without the order clause the record is found: le="color: #000000"><?php SELECT * FROM xoops_tplfile WHERE (tpl_tplset = 'default' AND tpl_file = 'system_block_user.html') Someone has a clue for this phenomena? |
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|