Textpattern CMS support forum

You are not logged in. Register | Login | Help

#11 2018-11-12 21:37:03

detail
Member
From: geez, I seem to be in NZ
Registered: 2010-07-13
Posts: 130
Website

Re: Upgrade 4.5.7? > 4.7.1

Bloke wrote #315173:

Yes, 4.7 is a lot tighter. You can no longer use id in <txp:article /> calls because articles get their ID from the URL context. The fact you could specify an id in previous versions was sort of a bug. If you want to grab specific articles “out of context” you must now use <txp:article_custom />.

That explains it. Thanks Stef.

jakob is right, it should definitely be with the trailing /textpattern. The reason your site still “works” is because we have an auto-detect mechanism that checks that value in config.php and makes an educated guess what it should be, then rewrites it in the database if it think it’s wrong. That’s why you see the “corrected” value in Diagnostics.

Ditto. Will experiment at a low visiting time.

Hey, thanks for all the work you guys put in to a). do these updates, and b). explain things to uneducated dolts . . .

Now just have to convert to https. Not looking forward to that.

Offline

#12 2018-11-12 21:49:24

jakob
Moderator
From: Germany
Registered: 2005-01-20
Posts: 3,159
Website

Re: Upgrade 4.5.7? > 4.7.1

Now just have to convert to https. Not looking forward to that.

That’s not so bad. You asked us before here.

And if you need a hand with auto search-replacing in your DB, you can also ask one of us.


TXP Builders – finely-crafted code, design and txp

Offline

#13 2018-11-18 19:15:09

detail
Member
From: geez, I seem to be in NZ
Registered: 2010-07-13
Posts: 130
Website

Re: Upgrade 4.5.7? > 4.7.1

jakob wrote #315179:

That’s not so bad. You asked us before here.

And if you need a hand with auto search-replacing in your DB, you can also ask one of us.

Thanks Jakob. You guys are extremely helpful. For someone completely self-taught I would be lost otherwise.

I have changed three simple single webpage sites relatively easily.

It’s the 1000+ webpage site with a number of txp pages for different sections that I’m procrastinating about. (Avoiding lists of conditionals seemed easier at the time. 13 sections!!)

Offline

#14 2018-11-22 01:55:47

detail
Member
From: geez, I seem to be in NZ
Registered: 2010-07-13
Posts: 130
Website

Re: Upgrade 4.5.7? > 4.7.1

As it turned out there was another issue with this upgrade.

Clear that txp 4.7.1 is stricter about the code than earlier iterations because a few sections of a 13 section website weren’t displaying properly. No menu for a start.

Only 394 lines of code to check, and compare to a similar number that worked.

Eventually after much tugging of my hair, oh, that’s not right, I don’t have any, it turned out to be a stray <txp:else /> that earlier versions had ignored.

Finally staggered over the line and it is all displaying as intended once again.

4.7.1 still seems to be able to cope with the odd non-closing <p>.

But not <txp:else />.

Offline

#15 2018-11-22 14:14:28

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 8,458
Website

Re: Upgrade 4.5.7? > 4.7.1

detail wrote #315383:

4.7.1 still seems to be able to cope with the odd non-closing <p>. But not <txp:else />.

The parser doesn’t care much about regular HTML tags – they’re just filler as far as it’s concerned. But it will kick up a fuss over any mismatching or badly-formed Textpattern / plugin tags. And as you are finding, incorrect <txp:else /> tags are its speciality!


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

Board footer

Powered by FluxBB