IRCMaxwell, I'm getting a MYSQL syntax error after installing (successfully) page cache 1.08 on my shared webhosting server (www.russbo.com/index.php). Site works fine, it appears to be caching pages as per the component cached pages section, but I'm getting this error on the bottom of every page:

Powered By Page_Cache by Ircmaxell
Generated in 9.17652893066 Seconds
Cannot Open The Cache FileYou have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'ON DUPLICATE KEY UPDATE uhit = uhit + 1, utime = utime + 9.1765 SQL=INSERT INTO jos_page_cache_stats (url,chit,uhit,utime,ctime,dhit,dtime) VALUES ('/Doc/doc.htm',0,1,0,9.17652893066406,0,0) ON DUPLICATE KEY UPDATE uhit = uhit + 1, utime = utime + 9.17652893066406

Server info:

PHP built On: FreeBSD host379.ipowerweb.com 4.11-STABLE FreeBSD 4.11-STABLE #0: Wed Apr i386
Database Version: 4.0.27
PHP Version: 4.4.1
Web Server: Apache
WebServer to PHP interface: apache
Joomla! Version: Joomla! 1.0.12 Stable [ Sunfire ] 25 December 2006 01:00 UTC


I get this error regardless of using "database" or "file" method.

File method does not seem to store pages, despite having 777 chmod file /home/xxxxx/public_html/pagecache/ file in configuration.

Second question: which method will diminish the MYSQL data hits? I've been hitting 50000 MYSQL data requests with this new JOOMLA site, and it's shutting down the MYSQL server from time to time. Better to use the "file" method???

Thanks!
rich

Either will reduce the database hits... Are you sure that the directory for cache path is correct? Does it have a trailing slash? That database error comes from using an old version of MySQL... For Some reason, pageCache is not detecting the old version... It should.

IRCMaxell Thanks for the quick and informative reply!

My MYSQL client API version is 4.1.11
My cache folder is /home/myusername/public_html/cachefoldername/

cachefolder privileges are set at 755.

Not sure what I've done wrong.

When using the database aspect, it certainly does speed up the pages. When using the file system, it slows it down (guess I don't have it set up correctly)

Appreciate the help!

Also, when trying to use "debug" in JOOMLA, I get this error when attempting to go to the index.php page:
'REQUEST URI: /index.php
URL FOUND: index.php
MATCH IN DATABASE

I have tried turning off PageCache, along with turning off JOOMLA's SEO caching, (and returning the .htaccess file to original); still do not get debug information on the front end. I see the debug information in the admin area however. I see from other posts that PageCache should be disabled before attempting debugging. I'm having no luck seeing how many queries my front page is generating. Any ideas?

Still getting that MYSQL error on the bottom of every page. I'm baffled.

Thanks!

What components are you using? The newest version of PageCache (due out in a few weeks) should take care of a few of the problems (or at least make it easier to fix)... The turning PageCache off before debuging will soon be a thing of the past...

Banners
Community Builder
Frontpage SlideShow
Jambook
Joomap
joomlaXplorer
Mass Mail
News Feeds
Polls
Redirect
swMenuPro
swMmenuMaker
Syndicate
Web Links

Thought the PageCache or SH404SEF might be the reason, turned them off, still getting this MATCH IN DATABASE error, LOL, really not sure what's triggering it. But turning off PageCache did remove that bottom of the page error.

Will wait patiently for new version of PageCache.

I see that these SEO components can really cause some issues (MYSQL database queries, etc). Got any recommendations? My site has been online for twelve years, there are a lot of google links to it, and I hate to lose all of that when I transfer the site to JOOMLA, which I'm just about ready to do.

Thanks! See you do the volunteer thing. I taught Upstate New York's very first EMT P program (many many) years ago; was one of NY's first EMT-P paramedics, when that first started. Oh, we're looking back before you were born....

Well, I personally like OpenSEF... That database error looks to be from SH404SEF, because there's no core query that checks the page name...

Thanks IRC. Appreciate it. Looking forward to the new version. Anything to cut down on MYSQL hits. (BTW, any idea on that JOOMLA forum discussion about increasing database users and admin failure??) What you wrote seems to be working, except for allowing admin access...