GetSimple Support Forum

My site's completely borked after upgrading from 1.7 to 2.0 to 3.0. It happened on the last iteration. I get a white screen with these errors:

Warning: include(template_functions.php) [function.include]: failed to open stream: No such file or directory in /home/@@@@@/public_html/getsimple/admin/inc/common.php on line 26

Warning: include(template_functions.php) [function.include]: failed to open stream: No such file or directory in /home/@@@@@/public_html/getsimple/admin/inc/common.php on line 26

Warning: include() [function.include]: Failed opening 'template_functions.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/@@@@@/public_html/getsimple/admin/inc/common.php on line 26

Fatal error: Call to undefined function get_root_path() in /home/@@@@@/public_html/getsimple/admin/inc/common.php on line 28

It seems like it's asking for a file (templates_function.php) that isn't in the distro. I guess I should revert back to 2.0 for the time being? Fortunately, this is my sandbox site, but I was getting ready to upgrade a client from 1.7 to 3.0.

Advice?

I've reverted back to 2.0 until I can solve that issue. And my client's upgrade is on hold until that time as well. If anyone has any ideas (I searched and didn't find this issue anywhere in the forums), I'm all ears.

did you try the upgrade steps defined here? http://get-simple.info/wiki/installation:upgrade

If all else fails - use Opt #2 at the bottom of the page. That should do it.

Nope, that didn't work either. I made sure to delete the /admin folder and upload the fresh one from the distro. I am still getting the same error messages here:
http://getsimple.mytestbed.com

I even tried different browsers and different computers (I have a laptop and a desktop here in my office).

Still no go.


It's very frustrating because I would LOVE to start using 3.0 and actively promoting it to my clients.

How about a fresh installation, and then moving old
/data/pages
/data/thumbs
/data/uploads
/theme/
...
and so on to fresh instance ?

If you have problems with inc/common.php line 26 & 28
they may be related with you base directory rule in htaccess file.

yojoe Wrote:How about  a fresh installation

agreed - if it can't find get_root_path(), then you didnt copy over all the new files from the zip file. The best way to be certain you get them all is to do a completely fresh install into a new folder - which is what Opt #1 suggests - so try that one.

I deleted EVERYTHING except the cgi-bin folder. Uploaded GS 3. from distro. Still getting error message.

http://getsimple.mytestbed.com

What's up with this?

pixelita Wrote:I deleted EVERYTHING except the cgi-bin folder. Uploaded GS 3. from distro. Still getting error message.

http://getsimple.mytestbed.com

Here's the error.log just generated by this fresh install. Bear in mind, 2.0 works just fine and dandy.

pixelita Wrote:

pixelita Wrote:I deleted EVERYTHING except the cgi-bin folder. Uploaded GS 3. from distro. Still getting error message.

http://getsimple.mytestbed.com

Here's the error.log just generated by this fresh install. Bear in mind, 2.0 works just fine and dandy.

{snipped}

I'm beginning to think it's a faulty distro. But I have re-downloaded it several times, stashed in different places. Always with the same result.

It was a faulty distro after all. I uploaded a new zip file to my server, unzipped it there, and moved it, and I got an installation panel. However, when I went to change my password, and hit SAVE, I now have this error:

Quote:CSRF detected!

pixelita Wrote:It was a faulty distro after all. I uploaded a new zip file to my server, unzipped it there, and moved it, and I got an installation panel. However, when I went to change my password, and hit SAVE, I now have this error:

Quote:CSRF detected!

This seems to have gone away on its own too. But good grief, it's been a PITA.

It may be too late, but I see a nice working GS instance.


ps. I always had to say it twice: make sure you uploaded all files through ftp.
As uploading whole archive and unpacking it on the server is the best and most reliable way.