Feedback for the Textpattern 4.4.0 release

Bloke · 2011-03-27 20:39:20

hcgtv wrote:

Wasn’t there work being done towards a new version of Textpattern.org?

Uhhh, yes. *embarrassed*. Needs some more resource thrown at it to get it to the top of the hill.

Bloke · 2011-03-27 21:49:09

zero / gomedia / all

Upgrade instructions tweaked slightly. Is that better? Any further improvements that can be made?

gomedia · 2011-03-27 22:16:04

Bloke wrote:

Upgrade instructions tweaked slightly. Is that better? Any further improvements that can be made?

I’d shift the “You must make a copy of your config.php file as a minimum” to before “Duplicate the Existing Txp File Tree” – so it’s more in your face. However even this might be giving the user a false sense of security.

To be honest I still think the old style procedure is so much safer:

take a backup
copy files css.php, index.php etc … across
copy folders rpc, sites etc … across
copy contents of textpattern folder across

Then you can add in the bits about .htaccess etc.

… copy the new files from there to the original location on your server, overwriting the old installation files.

… is very vague. I’m still worried that a user will copy the vanilla images or files folder across & destroy their website. I’ve learnt the hard way in the past that copying the whole folder is not the same as copying the contents of a folder – which is why alarm bells started ringing with me when I read the new procedure.

A one click automatic upgrade process would be fabulous of course – TXP 5 maybe?

els · 2011-03-27 22:20:10

I always follow these steps, minus the MLP specific steps (#7 and #10).

Last edited by els (2011-03-27 22:21:05)

maverick · 2011-03-27 22:24:24

fwiw

The import tab is showing the following error:
Notice: Undefined offset: 1 in /path to textpattern/textpattern/lib/txplib_misc.php(653) : eval()’d code on line 94

Last edited by maverick (2011-03-27 22:24:41)

Bloke · 2011-03-27 22:29:34

RE: upgrade instructions; point taken. I’m sure someone can improve on them further.

Bloke · 2011-03-27 22:33:02

maverick wrote:

Notice: Undefined offset: 1 in /path to textpattern/textpattern/lib/txplib_misc.php(653) : eval()’d code on line 94

That error’s not showing on my install. A plugin problem, perhaps? (line 653 is where plugin code is eval’d).

If you track it down, please let us know. Or if it’s not a plugin, throw us a bit more info about your setup so we can try and replicate.

EDIT: and if it’s one of my plugins I apologise in advance :-)

Last edited by Bloke (2011-03-27 22:34:08)

gomedia · 2011-03-27 22:51:13

Bloke wrote:

RE: upgrade instructions; point taken. I’m sure someone can improve on them further.

Thanks Stef. And as Ruud mentioned before you could lose this bit:

Then copy your existing config.php from the /textpattern/ folder in the folder you created in step 2 to the corresponding folder on your server.

merz1 · 2011-03-27 22:57:10

Bloke wrote:

Upgrade instructions tweaked slightly. Is that better? Any further improvements that can be made?

To me the upgrade instructions look good. But may I mention that a short block for CLI users could help. Using the terminal is much faster and safer than the FTP transmission. Something like:

(Logout from Textpattern admin)
cd <website root>
cp -r * txp-bak // I assume you have the user rights to read&write the hidden .-files like .htacccess
mysqldump // sorry I don’t know the exact command as I use DB Backup as a 1st step, check “man mysqldump”
wget http://path/to/download/textpattern-nnn.zip
unzip textpattern-nnn.zip
cd textpattern-nnn
cp -r * ../<website root> // Only files with the same name will be overwritten
(Proceed with step 4)

In my case everything is fine that way.

maverick · 2011-03-27 23:04:41

Bloke wrote:

EDIT: and if it’s one of my plugins I apologise in advance :-)

LOL — how did you guess? — no apology necessary.

It’s smd_prognostics.

Both v0.16 and v0.17 yield the same error.

I’ll post in the appropriate thread.

Thanks
Mike

Last edited by maverick (2011-03-27 23:10:21)

michaelkpate · 2011-03-27 23:40:41

gomedia wrote:

I’d shift the “You must make a copy of your config.php file as a minimum” to before “Duplicate the Existing Txp File Tree” – so it’s more in your face. However even this might be giving the user a false sense of security.

I probably shouldn’t admit this, and don’t recommend it, but being an old-school user, I still follow the original instructions.

Dean wrote:

To move from one version of Txp to the next, simply replace everything in your /textpattern/ directory EXCEPT config.php

zero · 2011-03-28 07:32:10

My mistake regarding config.php was not because of upgrade instructions but because of my unfamiliarity with ftp software. With Filezilla I could copy the Textpattern folder from my computer to server and it would leave any renamed files alone, such as configold.php. With Coda I have to use Merge to do this.

Although the new detailed instructions are necessary, I still basically use Dean’s original instructions too :-)

merz1 · 2011-03-28 07:40:27

Dean wrote:

To move from one version of Txp to the next, simply replace everything in your /textpattern/ directory EXCEPT config.php

Well, this simple and elegant sentence is basically how I understand & practice the TXP upgrade process till today (see above).
And reality is that esp. this self confident sentence encouraged me a lot to always make the upgrade ASAP and not to postpone it until ‘later’.

Maybe this simply replace order should be engraved as a golden motto above all the complicated upgrade write up. Thanks Michael for the reminder :)

mrdale · 2011-03-28 14:48:02

i haven’t upgraded/installed with anything other than svn in years. Always works.

johnstephens · 2011-03-28 14:53:23

I always upgrade from the command line:

wget http://textpattern.com/file_download/XX/textpattern-4.X.X.tar.gz
tar -zxvf textpattern-4.X.X.tar.gz
cp -r textpattern-4.X.X/* ~/my/document/root

Since I generally have custom .htaccess directives, I manually copy .htaccess changes. The cp -r command only overwrites files that are present in the distribution, so it never touches my conflig file, images, files, or custom admin themes.

Textpattern CMS

Textpattern CMS support forum

#31 2011-03-27 20:39:20

Re: Feedback for the Textpattern 4.4.0 release

#32 2011-03-27 21:49:09

Re: Feedback for the Textpattern 4.4.0 release

#33 2011-03-27 22:16:04

Re: Feedback for the Textpattern 4.4.0 release

#34 2011-03-27 22:20:10

Re: Feedback for the Textpattern 4.4.0 release

#35 2011-03-27 22:24:24

Re: Feedback for the Textpattern 4.4.0 release

#36 2011-03-27 22:29:34

Re: Feedback for the Textpattern 4.4.0 release

#37 2011-03-27 22:33:02

Re: Feedback for the Textpattern 4.4.0 release

#38 2011-03-27 22:51:13

Re: Feedback for the Textpattern 4.4.0 release

#39 2011-03-27 22:57:10

Re: Feedback for the Textpattern 4.4.0 release

#40 2011-03-27 23:04:41

Re: Feedback for the Textpattern 4.4.0 release

#41 2011-03-27 23:40:41

Re: Feedback for the Textpattern 4.4.0 release

#42 2011-03-28 07:32:10

Re: Feedback for the Textpattern 4.4.0 release

#43 2011-03-28 07:40:27

Re: Feedback for the Textpattern 4.4.0 release

#44 2011-03-28 14:48:02

Re: Feedback for the Textpattern 4.4.0 release

#45 2011-03-28 14:53:23

Re: Feedback for the Textpattern 4.4.0 release

Board footer