feed problem

[rj]

I am usually more adept in many of these things than I am in this case as I do not understand what the version process actually does...
So with that said. My last version was. 1.3.1, my current version is 1.4-beta.

I should rename my carl_contest directory.
I should rename my two lang files.
I should type over the 1.4beta with 1.3.1 in the loc_inc.php file.
Upload it to the server root.
Call it in the browser. Cross my fingers, my toes and hide under the desk and hope for the best!
Then replace my tweaked files in the best way...

[Don Chambers]

I am usually more adept in many of these things than I am in this case as I do not understand what the version process actually does...
So with that said. My last version was. 1.3.1, my current version is 1.4-beta.

I should rename my carl_contest directory.
I should rename my two lang files.
I should type over the 1.4beta with 1.3.1 in the loc_inc.php file.
Upload it to the server root.
Call it in the browser. Cross my fingers, my toes and hide under the desk and hope for the best!
Then replace my tweaked files in the best way...

Changing the installed version to read 1.3.1, instead of 1.4 beta will essentially trick serendipity (well, its not really a trick) into thinking the upgrade has NEVER been run, so it should execute all steps required, including the database upgrade which seems to have not happened last time.

I think the better way to handle the template would have been to create a new folder, copy your files to that new folder, activate that COPY as your actual working template. You will never have to stop and think about losing your custom modifications to a template. If you do this, I recommend modifying the COPY's info.txt and change the name of the template slightly so it is obvious to you that it is your copy, and not the original carl_contest (Serendipity 3.0).

[rj]

Lets see if I can wrap this up.

1) I backup my DB!

2) I rename my template folder.

3) I rename my checksums.inc.php file.

4) I rename both my lang files.

5) I edit the config_local_inc.php file from beta1.4 to 1.3.1.

6) I load the config file in the browser and GO.

The issue I am unclear on... I must delete the orginal named directory and files or it will still tell me it sees edited files and will not proceed... Right?

[Don Chambers]

RJ - this is what I would do....

1) Create new folder for your template.... let's call it /templates/rackjite/
2) Copy all files from /templates/carl_contest/ to this folder.
3) Edit the file /templates/rackjite/info.txt
4) Change the first line of that file from "Name: Serendipity v3.0" to "Name: RJ's modified Serendipity v3.0" (no quotes for either).
5) Go to "manage styles" and scroll through the list of available templates until you find "RJ's modified Serendipity v3.0 and select this as your template. From this point forward, you will be using this copy of the template, and not using the files in carl_contest. Since this copy is not included in the verification code, you will not receive errors.
6) You may have already overwritten your language files the last time you uploaded 1.4.1. Either verify this, or make a COPY of the files and save them somewhere.
7) Back up your DB
8 ) Back up all files via ftp
9) Upload 1.4 (or 1.4.1) in its entirety again just to make sure all files are uploaded.
10) Open/edit config_local_inc.php file from beta1.4 to 1.3.1.
11) After all files are uploaded, hit your WEBSITE ADDRESS to trigger the upgrade.

After the upgrade is complete, the only open issue will be your language files... they may have already been overwritten when you first uploaded 1.4beta, or perhaps you have a saved copy of them, or know exactly what had been modified. You can use your backup versions or memory to make the same modifications to the newly uploaded language files. I would not use your old ones as replacements simply because i do not know for sure if they changed or not.

[rj]

Boy thanks a bunch don!
I printed this out and studied it! It is coming clear... Until I get to step 9)
What I have on my hard drive is 1.3.1 not 1.4beta, I must have lost it when I got the new computer or something...

SO I go to Serendipity and download 1.4.1 zip. Or maybe 1.5beta?
I unzip it to my HD.
Upload the files to the server. which will overwrite my lang files and solve that issue?
Do the config change to 1.3.1.
Do the upgrade.

What will I end up with? 1.4.1 or 1.3.1?

[Don Chambers]

My understanding from this thread is that you upgraded from 1.3.1 to 1.4-beta1, but the upgrade may have missed something in the DB update... I suggest you download 1.4.1 full release and upload that version. Before hitting your site, you will want to edit config.inc.php and set the version back to 1.3.1. When the site is visited, the upgrade will be triggered. You could go all the way to 1.5 beta if you want, but I rarely use the beta versions in live sites.

Understand that the first visit to your site will trigger the upgrade... I personally use a a special .htaccess file to block all traffic to my sites when I am upgrading except for my IP address....

[rj]

Hey, I chickened out on all that at the time!
But now I am getting more complaints about no RSS. What has changed is I now have 1.5.1 in a folder on my drive, and have a template folder of my own with my own tweaked stuff in it.
I guess I need your .htacess code to shut it down for a while?
And maybe to go over it once again. Is the TODO list the same?
I think I forgot how to being the process...
I just backed up my DB...

[Don Chambers]

I guess I need your .htacess code to shut it down for a while?

It is not flawless, but will keep everyone except you out. May disrupt css in the backend while active, but s9y will remain functional. It is documented on Judebert's blog.

[rj]

Ok, I decided to wait until the new full version came out to do this scary thing!

To remind you from September:
Serentipity is running fine ACCEPT for RSS which I am getting more and more user requests to fix.
I am running 1.4.1 beta.
I upgraded from 1.3.1 full.

So now I am ready to do this but lost track of things.

I have downloaded 1.5.1 full upgrade.
I made a newly named template folder back in Sept of my tweaks that works just fine.
I have all my tweaked files on my home computer just in case, including plugins and info text tweaks.
I have judeberts .htaccess file that shuts it down.
I just made a DB backup and I don't plan on doing anything to the blog until Monday.

So... Now what exactly!

Should I upload all the 1.5.1 files to my server root replacing the ones there now?
I assume so because that will then overwrite the corrupted files that put a halt on all this.
Then I upload the .htaccess stop file.
Then I load the config file from my browser and replace the 1.4.1 with 1.3.1.
Assuming things go well...
Then how do I apply 1.5.1?

Thanx I know we been over this and am sorry...

RJ

[garvinhicking]

Hi!

Upload judeberts .htaccess, upload 1.5.1, edit your serendipity_config_local.inc.php to enter the 1.3.1 version string, go to your s9y blog admin, confirm update, replace .htaccess with your old .htaccess.

[rj]

It all went very well!!

Except when I click a RSS category I get this:

XML Parsing Error: syntax error
Location: http://rackjite.com/feeds/categories/38-Politics.rss
Line Number 1, Column 1:Query failed: <pre>SELECT
^
There is no /feeds folder

I have to admit that RSS has not worked for so long that I forgot just about everything there is to know about it!

[garvinhicking]

Hi!

This error comes from the event_categorytemplates plugin. Are you using its recent version? Check spartacus.s9y.org for the latest revision...

Regards,
Garvin

[rj]

I added the syndication sidebar and get the same error for all feeds

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

I can see rss.php in the root...

I forgot everything I once knew about feeds...

I bet I may be forgetting something very basic!

Its at the bottom of my sidebar at present... http://rackjite.com

[Don Chambers]

RJ - did you disable the plugin Garvin mentioned?

[rj]

I upgraded it as I was told. But I did not shut it off.
But now that I have moved it over to inactive, things seem to work!
So this simple thing was IT all along, 2 years of no RSS!