Fixing Pligg after a Server Move

Pligg Content Management System

Recently, Dreamhost has moved all of my sites hosted through them to a new server.  There were a few reasons for the switch, but mostly they were in the process of upgrading their machines to more powerful and energy efficient ones and this means a migration off the old servers.

Well, the transition didn’t completely go off without a hitch.  Actually, Pligg gave me a few difficulties and it was even tough to find a solution online so hopefully this post will show up for anyone else who encounters a similar issue.
Here are some of the error codes (modified to remove personally identifying information, hopefully):

Warning: require_once (/plugins/function.checkActionsTpl.php) [function.require-once]: failed to open stream: No such file or directory in /templates_c/c_334b448556830a276d8bcc20f7022192.php on line 1
Fatal error: require_once() [function.require]: Failed opening required ‘/home/plugins/function.checkActionsTpl.php’ (include_path=’.’) in /templates_c/c_334b448556830a276d8bcc20f7022192.php on line 1

Other plugins might trigger a similar error message:

  • function.checkForCss.php
  • function.checkForJs.php
  • function.eipItem.php
  • function.embedvideos.php
  • function.html_options.php
  • modifier.escape.php
  • modifier.repeat_count.php
  • modifier.sanitize.php
  • shared.escape_chars.php

See, what happens is that after the move, script file paths don’t need to include the server name (/home/.server/account/domain/) becomes (/home/account/domain/)

The guys at Dreamhost seem to have acknowledged this and I noticed quite a few files had been recently modified.  When they did the switch, they might have popped in a search query for the extraneous location variable, so for the most part there was no real impact on the operation of the moved websites.

Then again, Pligg was being difficult, so here’s the simple solution that escaped me for an hour or two last night and drove me nutty:

Delete all of the files in your Template_C directory.

Don’t delete the actual directory – or if you do, be sure to create a new one with the same name.  Basically, its just a cache of template files and even if your file paths are updated, this can linger for a while until its reset.

Really though, I felt kind of silly after spending close to two hours digging in to all of the configuration and settings files, when all that had to be done was delete the temporary template cache.  Hopefully, if anyone else runs into this or a similar issue (whether at Dreamhost or not) then this post will give them some ideas of how to proceed!

Be the first to comment

Leave a Reply

Your email address will not be published.