This website can use cookies to improve the user experience

This website can use cookies to improve the user experience and to provide certain services and functions to users. Cookies contain small amounts of information (such as login information and user preferences) and will be stored on your device.

Enable All Cookies Privacy Policy

Errors after upgrade to 1.32


avatar
johngaltnh 0
From: -
Errors after upgrade to 1.32

After an upgrade from Storyteller Standard 1.21 to 1.32, I am having some errors. But first, I should tell you how I did the upgrade.

1. This site has to be backed up frequently, and because there are no handlers that allow the php to run as the ftp user instead of the webserver - I have to add a variety of "chmod" statements in various places in the source so that the ftp user has access to download the files for a backup. This is NOT a problem with Storyteller - it's a problem with the host. (I have no choice regarding the host.)

2. Also - almost all of the templates have been extensively modified. (Great system!)

So when I did the upgrade to 1.3.2, I took note of the files that had been modifed or added - added the appropriate chmod statements to those - and then only uploaded those new/changed files. (Plus the new "cnt" files in the templates dir and chmoded everything appropriately) (I uploaded all files listed in the 1.3 announcement, 1.31 announcement and 1.32 announcement.)

Then, I ran  http://www.myurl.com/cadmin/cupgrade.php

It did NOT report success - it simply said "Edit." Subsequent attempts to run that file report that it has already been run (Error: 1060 Duplicate column name 'story_sticky') - which leads me to believe it probably went okay.

I now have two problems with the site - one small and one big (probably because I didn't copy over something important. - Please tell me what!)

Small Problem: The admin interface still reports that I am running version 1.2.1. How do I get it to report the right version?

Big Problem: Whenever a template is changed, when the button is pressed to upload the change - it just gives me a screen that says the one word "Edit". Some experimenting tells me that the changes ARE actually being saved - but obviously there is some sort of error going on.

So ... what are my next steps? Hopefully I gave enough info!

Thank you for your help!
Brett

Notice

This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic


1 Re: Errors after upgrade to 1.32
avatar
OP 0
From: -
Errors after upgrade to 1.32

Thank you, Philipp!

I was unable to change the permissions on some of the template files (.bak) from my ftp account, but wrote a tiny php script that did the same thing. I stole it from your mod_templates.php file, named it fix.php and loaded it into the cadmin dir temporarily.

This is very basic, but might be helpful for anyone else who has host restrictions like I do:

<?php

include("../core.php");

$template_dir = GetDir("../templates");

for($i=0;$i<count($template_dir);$i++) {
$template_name = $template_dir[$i];
chmod("../templates/$template_name", 0777);
echo "Fixed permissions $template_name<br />";
}

?>

Thanks again for all your help - and I'm certain to be upgrading to 1.4 in the not-to-distant future. The 1.3.2 version does a great job with the PHP Accelerators.

Very truly,

Brett
1 Re: Errors after upgrade to 1.32
avatar
Administrator
1340
From: Vienna, Austria
Errors after upgrade to 1.32

Hello Brett-

Both errors are caused by permission problems in your /templates directory

Originally posted by johngaltnh
Small Problem: The admin interface still reports that I am running version 1.2.1. How do I get it to report the right version?


Run the following query in phpMyAdmin:
UPDATE esselbach_st_version SET version_version = '1.3.1', version_date = '1063899575'


Originally posted by johngaltnh
Big Problem: Whenever a template is changed, when the button is pressed to upload the change - it just gives me a screen that says the one word "Edit". Some experimenting tells me that the changes ARE actually being saved - but obviously there is some sort of error going on.


chmod the /templates directory to 777. Also, set the permissions of all files in /templates to 777

I highly recommended that you also upgrade to Storyteller 1.4. This release includes some enhancements in the template system which will hopefully fix all permission issues.

Notice

This topic is archived. New comments cannot be posted and votes cannot be cast.