error message about headers / blog posts w/o images

[Carl @ ATS]

P.S. In Serendipity's upgrade agent, it says:

"If after installation you get uncircumventable errors, you can make sure to set $serendipity['product'] = true; in your serendipity_config_local.inc.php file. This should lower error reporting to a way that will not interfere with incompatible problem. But this is no solution in the long run, you need to update your plugins."

This message seems to relate to 1.7-rc2, but the rc I've just uploaded and installed is 3, not 2. Is it still necessary/advisable to modify config_local.inc.php this way? (I've just done it, but it hasn't made any difference to the fatal error message.)

Carl

[Timbalu]

I would say: Check the permissions to be writable on serendipity_config_local.inc.php

But you said, you had an 1.6 (release?) version before, and uploaded an 1.7 release zip now. So you should not have a testing error mode! [Check your serendipity_config_local.inc.php, if it has a $serendipity['production'] = false; setting. Delete this line, if have.] Why did you upload the rc3 (RC mean Release Candidate) and where did you get that from? Serendipity 1.7 final was released a few weeks ago and the rc versions do not show up any more.

And please change your db password now, since it seems you just posted your credentials here ... (I edited this line to not show up any more in your previous post.)

[Carl @ ATS]

Thanks for your reply, Ian.

My config_local file doesn't contain "$serendipity['production'] = false;", so that's not the answer, I'm afraid.

I've just modified the config_local file to make it writable, which may (or may not) have solved the problem; I'll check that tomorrow once I've uploaded the final version of v1.7. I didn't realise that had appeared as I haven't subscribed to the blog yet - I've been too busy getting to grips with the basics in Serendipity and trying to resolve unexpected issues. I downloaded the rc3 version a little while ago, which explains the difference in versions. (In retrospect, it would have been better for me to check the development site again before attempting to upgrade my system.) Has a testing error appeared because I'm using an RC version? Is that what you're implying?

Incidentally, I did actually modify all the paths indicating the full address of my blog before I posted my two messages, substituting my personal data with "...". Did I miss anything? I'll change my data in any case.

Regards

Carl

[Timbalu]

I've just modified the config_local file to make it writable, which may (or may not) have solved the problem;

Has a testing error appeared because I'm using an RC version? Is that what you're implying?

substituting my personal data with "...". Did I miss anything? I'll change my data in any case.

Good.

Yes/no; you get the "testing" including the trace path; release errors are not that verbose.

As I said, the db data trace path #2 looked like non-anonymized db user/pass settings, that is why I changed it here and told you to set a new password, so you can be sure nobody (like google) catched that before.

Maybe you also have an error in your configuration path section. Please paste your setting and anonymize the first where it pronounces the userDir.

[Carl @ ATS]

Hello Ian,

Following your advice yesterday, I changed the permissions for the config_local file and the errors disappeared after that. So now the blog's up and working again (even though it's running on v1.7-rc3). Thanks.

I think it would be wise for the developers to include information like this in their update instructions - however obvious it may seem to them - as it's not there at the moment (as far as I can see). Things like this are unnecessary obstacles for people who just want to blog and update their software quickly and smoothly when a new release comes out.

Anyhow, you asked about my configuration path yesterday:

Maybe you also have an error in your configuration path section. Please paste your setting

Well, it's "/www/htdocs/.../blog/" and the index file is simply index.php (/.../ is a placeholder for my user directory). The relative path is "/blog/" and Autodetect used HTTP-Host is set to "yes" (which presumably means "true").

Regarding the auto-updater, the notes on the plug-in say this: "When the dashboard-plugin (once a day) detects an update, this plugin adds the option to manually download or start an automatic and secured upgrade of the blog directly with one click from within the admin area".
Well, I've now installed the dashboard plug-in and Serendipity auto-updater, but no update facility has appeared in the dashboard/back-end "front page" yet, so I can't update to the final version of 1.7 easily (i.e. automatically). The dashboard is second in my list of event plug-ins, Spartacus is first and the auto-updater is third, so that order seems OK, doesn't it? (I quote: "Set autodetect host name to yes, install the dashboard plugin, then the Serendipity Autoupdate plugin, point yourself to backend startpage" - http://board.s9y.org/viewtopic.php?f=2&t=19357). I also updated all the plug-ins before checking the front page. Any ideas?

Regards

Carl

[Timbalu]

Well, actually there is a general demand already... read http://www.s9y.org/11.html#A15
and for starting purposes http://www.s9y.org/36.html#A5

To get a new xml file on the fly you need to change xml and/or download mirror server options in the Spartacus plugin config (I am not sure this will actually solve the once by date update search, though).

In case not, it is not that long to wait for tomorrow.