feed problem

[rj]

I lost track of doing feeds sometimes back and now a few people are asking for it and what I have up gives the error message
XML Parsing Error: syntax error
Location: http://rackjite.com/feeds/index.rss2
Line Number 1, Column 1:Query failed: <pre>SELECT

I do not see any feeds folder anywhere, including the dl of serendipity...
Been so long since I dealt with this I pretty much forgot how do any of it... I do have a feedburner account if I recall...

Thanx

RJ

[yellowled]

I lost track of doing feeds sometimes back

Okay, first of all: You shouldn't have to "do" feeds, s9y (or an external service like Feedburner) should do that automagically for you. That's actually why we use this piece of software

XML Parsing Error: syntax error
Location: http://rackjite.com/feeds/index.rss2
Line Number 1, Column 1:Query failed: <pre>SELECT

This usually means a syntax error in one of the entries. This can be kind of hard to track down. Basically, it can be anything from "bad" HTML markup in one of the syndicated entries to invalid code emitted by video players or stuff like that ...

I do not see any feeds folder anywhere, including the dl of serendipity...

That's because the feeds are generated dynamically, much like almost anything else in s9y. There is no actual physical representation of the feed. You also don't have to edit your feed manually, but you should make sure that your entries contain valid XHTML.

YL

[garvinhicking]

Hi!

This error means you have at some time updated Serendipity, but did not execute the upgrade as pointed out on the s9y FAQ. You skipped the database updates, and now your database does not hold the columns that Serendipity requires for operation.

You need to look at the FAQ and see what to do to re-execute an update, which involes setting bac k your version number to the old version, going to your admin panel, and re-executing the database updates.

Then the column "hide_rss" will be added to your database, and the feeds will be able to work again.

Regards
Garvin

[rj]

Sounds dangerous!

Just read the faq. It seems I can edit the config_local-inc.php file okay... But... this is what it says for version
$serendipity['versionInstalled'] = '1.4-beta1';

What version should I use you think? And by just upgrading to a newer version will this issue resolve itself?

I checked my profile and cannot figure why I am not being notified in email

Thanx

[garvinhicking]

Hi!

You should enter the version that you installed previously before the last update you executed... maybe 1.3.1?

Upgrading to a newer version will not help because the fields you are missing come from an older s9y version, and it would still not be there when you upgrade any further.

Regards,
Garvin

[rj]

The Serendipity folder on MY hd says 4.1beta.
I am sure you are correct that my last version was 3.1.1

I just am not clear what specifically I need to do. Do I need to download the old 3.1.1 which is no longer around and put it somewhere? Could you spell this out a little more for me? Step by step for dummies?

I have also been experiencing long SAVE ARTICLE times. 30 seconds and sometimes failure for Serendipity to say FINISHED when it is finihsed...
Even if I remove the ping and sitemap plugins and with no trakbacks it is slow. So I suspect something wrong with accessing the DB.

Thanx

RJ

[garvinhicking]

Hi!

Please look up the version numbers properly.

Do you mean 1.1.3 or 1.3.1?

Serendipity has never been higher than 1.5

You do not need to download an old s9y version, you only need to edit the serendipity_config_local.inc.php file and set the versionInstalled number to that version string you had earlier. And this time you need to enter the right one, 3.1.1 would be fatal.

If you previously when everything was running had 1.1.3 installed, enter 1.1.3, if you had 1.3.1, enter 1.3.1. If you don't know at all, first enter 1.3.1 and then enter the admin panel to upgrade; if that does not fix the error, enter 1.1.3 and execute the admin again.

Regards,
Garvin

[rj]

This is what I get when I replace the 1.4-beta1 with 1.3.1 in the local.php file:

Verify Installation Integrity
lang/serendipity_lang_en.inc.php corrupt or modified: failed verification
lang/UTF-8/serendipity_lang_en.inc.php corrupt or modified: failed verification
templates/carl_contest/index.tpl corrupt or modified: failed verification
templates/carl_contest/entries.tpl corrupt or modified: failed verification
templates/carl_contest/style.css corrupt or modified: failed verification
Permissions
/home/content/r/a/c/rackjite2/html/webkick/ Writable
/home/content/r/a/c/rackjite2/html/webkick/templates_c Writable
/home/content/r/a/c/rackjite2/html/webkick/uploads/ Writable
------
I have made changes to all those files which I want to keep. I do not think I could find exactly where I changed them though.
I think I may have an idea of what to do but would like to hear it from you.
On my HD I have un modified serendipity 1.4-beta1 directory...

Thanx
RJ

[onli]

Make a fork of the carl_contest-template and save the changes that way. Then overwrite the old files.
sincerely

[rj]

Thanx

You mean rename carlcontest directory? And then when its done go put those changed files back?
Do i do the same with the lang directory?

I dont really understand what happens when the software sees the version change. So forgive me my stupid questions!

Thanx again!

RJ

[Don Chambers]

I believe onli is suggesting that you

1) make a new subfolder, such as /templates/carl_contest_rj/
2) copy the contents of carl_contest into that new folder.
3) upgrade serendipity.
4) overwrite /templates/carl_contest with your saved version.

I do not think it is a good idea to do that with core language files though... there could be new language constants defined in an upgrade, and you would miss those new constants if there were any... unless we have some other way of overriding language constants that I do not know about....

[onli]

Don Chamber got it right

But if you made servere modifivations I wouldn't overwrite the new files, but instead use the fork as the new template. That way, that problem wouldn't reoccur.

[rj]

Getting there!

So what do I do about the lang files?

Thanx...

[garvinhicking]

Hi!

To perform the upgrade nevertheless, you should see a button there, don't you? Also you could temporarily remove the "checksums.inc.php" file so that those checks are not performed to 'execute' the upgrade.

HTH,
Garvin

[Don Chambers]

So what do I do about the lang files?

That's a bit more difficult... while you COULD also store your revised language files somewhere, then copy them back after an upgrade, you run the risk of losing any new language constants that might have been added/revised in the new version. I think it is best to store you revised version, then manually modify the new one with your prior modifications.

Or maybe Garvin knows of a better way to handle it... like using a file of a specific name, if it exists, for overriding default language constants...