Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#11 2019-12-22 19:55:02
- etc
- Developer
- Registered: 2010-11-11
- Posts: 4,076
- Website
Re: Feedback to: Textpattern CMS 4.8.0-beta released
Thanks for testing, hope you will like it. Our recent activity has been quite intensive, so some bugs might still hide themselves. Please stress-test article preview and second pass PHP if you have time.
And thanks for all your support, you are great, old chaps!
Offline
#12 2019-12-22 21:48:45
- jakob
- Admin
- From: Germany
- Registered: 2005-01-20
- Posts: 4,035
- Website
Re: Feedback to: Textpattern CMS 4.8.0-beta released
Just want to reiterate how great this next update is.
My emergency upgrade of the ancient site mentioned in the other thread took me from txp 4.0.8 to txp 4.8.0-beta in one leap. The upgrade went well despite the huge distance (tho’ in visual terms the 8 and 0 have just switched places ;-) and about the only thing that didn’t seem to be quite as it should were some Admin preferences that were no longer on the right pane/order.
The site was from asy_wondertag / chh_if_data / sed_section_fields / lam_accordian / hak_image / upm_textile / mem_glinklist days (remember those!) and I have dropped from 40+ plugins to just 6 now – and one of those is for dev purposes, one for a dashboard and one I might be able to get around by enabling a php tag for txp:evaluate. Pretty good all in all.
So: thank you all again!
EDIT: I hadn’t updated the “master” branch of my fork, so it tells me there were 640 commits between 4.7.3 and 4.8.0-beta 1.
TXP Builders – finely-crafted code, design and txp
Offline
#13 2019-12-23 08:05:46
- Myusername
- Member
- Registered: 2019-12-12
- Posts: 96
Re: Feedback to: Textpattern CMS 4.8.0-beta released
All my XML pages (sitemaps, for example) are no longer working.
The <txp: header>
tag no longer functions as before. Was this expected?
Last edited by Myusername (2019-12-23 08:06:02)
Offline
#14 2019-12-23 08:35:33
- phiw13
- Plugin Author
- From: Japan
- Registered: 2004-02-27
- Posts: 2,233
- Website
Re: Feedback to: Textpattern CMS 4.8.0-beta released
Myusername wrote #320670:
All my XML pages (sitemaps, for example) are no longer working.
The
<txp: header>
tag no longer functions as before. Was this expected?
Indeed, there seems to be a problem with the header
. On localhost here, the sitemap is sent as text/html
.
Where is that emoji for a solar powered submarine when you need it ?
Offline
#15 2019-12-23 11:01:08
- etc
- Developer
- Registered: 2010-11-11
- Posts: 4,076
- Website
Offline
#16 2019-12-23 19:07:52
- Myusername
- Member
- Registered: 2019-12-12
- Posts: 96
Re: Feedback to: Textpattern CMS 4.8.0-beta released
etc wrote #320675:
Can not reproduce, sorry. The tag has been modified but works as before in my tests. Are you sure to have php enabled?
Yes, it’s all right here except the header
tag and the “Please force re-load the page or clear your caches” warning that I insisted on appearing.
I thought maybe I could have missed something by upgrading from 7.7.3 to 7.8.0-beta, so I did an installation from scratch, but still these things keep happening.
Offline
#17 2019-12-23 19:18:58
- etc
- Developer
- Registered: 2010-11-11
- Posts: 4,076
- Website
Re: Feedback to: Textpattern CMS 4.8.0-beta released
Could you try to reproduce the problem on beta demo site please? We’ve got about 2 hours until the next reset.
Offline
#18 2019-12-23 19:28:38
- Bloke
- Developer
- From: Leeds, UK
- Registered: 2006-01-29
- Posts: 9,993
- Website
Re: Feedback to: Textpattern CMS 4.8.0-beta released
Myusername wrote #320676:
Yes, it’s all right here except the
header
tag
Could you perhaps give us a little clue? Like how you’re trying to use the header: post a relevant bit of code so we can maybe try to replicate what you see. Thank you.
the “Please force re-load the page or clear your caches” warning
Not sure why this is appearing. After you refresh, clear your cache, use a private browsing session or whatever, the message should disappear.
What is the version number in your textpattern/textpattern.js
file, your textpattern/index.php
(both near the top) and the version
string in your txp_prefs table. They should all match.
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
#19 2019-12-24 00:09:55
- phiw13
- Plugin Author
- From: Japan
- Registered: 2004-02-27
- Posts: 2,233
- Website
Re: Feedback to: Textpattern CMS 4.8.0-beta released
So, those headers.
The txp:header
is not working, it seems to me, or at the very least, the <txp:header value="application/xml; charset=utf-8" />
is not.
Test one, local copy of an existing site, on TXP 4.7.3 the xml code displays as expected, but its twin brother (complete copy except for the TXP code) running on the same server with TXP 4.8-dev is displayed as text/html
.
Test two: my recently created TXP 4.8-dev playground/test site, pretty much the default install, with just a couple of articles added. As per the multiple forum threads on how to create an xml map with native code, I created a dedicated Section (sitemap
) and Page (sitemap-xml.tpl
), the dedicated section is set to use the sitemap-xml.tpl
page. That page is using – Copy paste! – the Colak code. (with minor adjustments to adapt to local set up)
Accessing txp-dev.local/sitemap gives me this unexpected display (Safari/Firefox – both browsers tell this is a text/html
file):
TXP 4.8-dev – MySQL 5.7.x and 8.0.x with Apache/2.4.41 (Unix) PHP/7.3.9
Last edited by phiw13 (2019-12-24 00:11:20)
Where is that emoji for a solar powered submarine when you need it ?
Offline
#20 2019-12-24 02:09:10
- Myusername
- Member
- Registered: 2019-12-12
- Posts: 96
Re: Feedback to: Textpattern CMS 4.8.0-beta released
phiw13 wrote #320679:
So, those headers.
The
txp:header
is not working, it seems to me, or at the very least, the<txp:header value="application/xml; charset=utf-8" />
is not.
By my tests an <txp:header>
tag is not working at all. Try using two forms: <txp:header value="application/xml;charset=utf-8"/>
and <txp:header value="application/json;charset=utf-8" />
. unsuccessfully.
Offline