Serendipity Forums

Hi there,

I've just tried to upgrade my serendipity Blog (it's nessecary, I'm runing on 1.0.3).

Now as I was following the explanation in the faq (http://www.s9y.org/11.html#A19), I had first made a dump and a directory backup, that extracted the new serendipity.zip, loaded it up to my server, hit "Overwrite all" and than uploaded the old "serendipity_config_local.inc.php" again.

That far I came. Next step in the tutorial is: "Then go to your Serendipity Admin Panel, and you will see the Serendipity upgrader."

Well, no.
I can loginto the admincp, there have been serval changes in the blog layout, so the new version must be working. But there is no upgrader.

Where did i go wrong?

greets and thanks
Rod

Hi!

If you have a site that is heavily visited, you might want to put it down for maintenance while you upgrade with a simple .htaccess:
(Put that on the top of the file if you already have one. Also make sure you insert a proper file path to a .htpasswd file and create yourself a valid user/password - you can google for ".htpasswd creator" if you don't know one)

This ensures that nobody can execute your upgrade.

Then you edit your serendipity_config_local.inc.php file and reset the versionInstalled variable to 1.0.3 - if you did that, then going to your admin panel should present you the admin upgrader screen.

Also make sure you did NOT upload the old serendipity_config.inc.php file! It is VITAL that you use the serendipity_config.inc.php from the fresh release. Only serendipity_config_local.inc.php is not contained in the fresh release file and thus remains from your old install.

Regards,
Garvin

okay, it sees to have worked, even tho its been a bit weired.

You were right, I had accidently forgot to upload the serendipity_config.inc.
As I had it upload and wanted to log off the admincp, the upgrader appeared emideately.

All tests were finished with green, so i choosed to press continue.

Than a couple of red colored database writing errors occured but i had a green checkmark that said: Upgrade successfull.

Can that be trouble?

I've tried already, I can make new entries, can use plugins .. no trouble.

But those database writing errors are weired alright.

Hi!

Did you maybe note down the red errors?

It might only be due to some indexes in which cases nothing would be bad.

Regards,
Garvin

no I missed to record the errors. should know that better after all those years ...

but it seems like there is no problem so far. if there is one appearing, i'll ask here .

thanks for help dude.

Okay, I found a problem


I've tried to install new themes and get an writing error.

Trying to open URL xml.gif?rev=1.9999...
Fetched 1030 bytes from the URL above. Saving file as /home/www/accountnumber/html/rodlog//templates/mimbo/img/xml.gif...
Cannot write to file /home/www/accountnumber/html/rodlog//templates/mimbo/img.


about every line in the install routine ends with an writing error.

Chmod problem or database access?

Hi!

chmod problem; you need to use FTP to make /templates (and /plugins) writable.

Regards,
Garvin

HAve chmodded
/templates
/plugins and
/templates_c

to 777


Still,
Fetched 2328 bytes from the URL above. Saving file as /home/www/web152/html/rodlog//templates/freshy/commentform.tpl...
Cannot write to file /home/www/accountnumber/html/rodlog//templates/freshy.
Trying to open URL comments.tpl?rev=1.9999...

Could it be a problem, that there is a double slash (//) between my blog directory and the template folder?

Example: Cannot write to file /home/www/accountnumber/html/rodlog//templates/mimbo/img.

I get the impression, the plugins don't find the folder. .....

Okay, Problem still appearing. Would be thankful if somebody had an idea what to do.

I've been searching the code myself for serval url definitions, but couldn't find the right point.


and by the way, i like the in-code documentation:

// We don't care who tells us what to do
// Some stuff...

is "/templates/freshy" writeable?

Hi!

The "//" should not be a problem; have you checked if your "templates" directory already has a "fresh" subdirectory? If yes, is it writable?

S9y should only report write failures if the directory is not writable...

Regards,
Garvin

no, there is no subdirectory called "fresh" inside the template folder.

Should I manually create one?

[edit]
Okay, just did that, no change.

Have also checced the chmod for the Template folder, its 777. means write, reade and execute.

Hi!

Where do you check your current chmod mask? If s9y complains about not being able to write, there must be a permission mismatch somehow.

Regards,
Garvin