Textpattern CMS

#1 2006-10-18 13:04:04

kimiko

Member

Registered: 2005-12-01

Posts: 35

Website

Kickstart Textpattern upgrade

Hi,

how do I kickstart the Textpattern upgrade from 4.0.3 to 4.0.4 ? I replaced the files according to the installation notes (left config.php intact) and opened the TextPattern admin page, but the upgrade function didn’t start.

How do I kickstart the Upgrade function? I see an Update directory and the _update.php file, but it’s set so you can’t open it directly.

4.0.4 is now uploaded on my client’s website, but I hope to have the upgrade resolved before they start logging back on. (CSS file need to be upgraded for the admin changes — it looks horrible without it)

Thanks in advance

#2 2006-10-18 13:06:19

kimiko

Member

Registered: 2005-12-01

Posts: 35

Website

Re: Kickstart Textpattern upgrade

Oh, Diagnostics is okay, no problems whatsoever.

The upgrade routine might have been skipped since I was already logged in.

#3 2006-10-18 13:21:15

ruud

Developer Emeritus

From: a galaxy far far away

Registered: 2006-06-04

Posts: 5,068

Website

Re: Kickstart Textpattern upgrade

I doubt the upgrade PHP files do anything with the CSS file.
Assuming the CSS file was updated on the server, hit CTRL-F5 in your browser so the new CSS file is loaded instead of using one from the browser cache.

#4 2006-10-18 14:09:14

Neko

Member

Registered: 2004-03-18

Posts: 458

Re: Kickstart Textpattern upgrade

The upgrade seems transparent this time. As ruud said, you might want to force the refresh of the CSS (they’re cached) with CTRL+refresh/reload.

#5 2006-10-18 17:59:34

wet

Developer Emeritus

From: Schoerfling, Austria

Registered: 2005-06-06

Posts: 3,330

Website Mastodon

Re: Kickstart Textpattern upgrade

You can verify if the database upgrade ran upon upgrade by checking for a preference with the name ‘version’. You will need a MySQL client like phpMyAdmin or rss_admin_db_manager in order to execute this SQL query (apply table prefix when necessary):

select * from txp_version where name='version'

The result is either ’4.0.4’, otherwise the database upgrade was supressed by whatever reason. Another option is to check for the presence of the “Prevent widowed words in article titles?” preference (admin > preferences > advanced > publish), which was introduced with the upgrade to 4.0.4.

Last edited by wet (2006-10-18 18:06:40)