Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Feedback to: Textpattern CMS 4.8.0 Released
It doesn’t work. That’s what is so weird.
If I do <txp:variable name=“previous_page” value=’<txp:permlink />’ />
Then immediately do <txp:variable name=“previous_page” /> it is correct.
But if I put <txp:variable name=“previous_page” /> on a different page, it’s empty.
But was I always doing it wrong? Should it be done in forms?
Offline
Re: Feedback to: Textpattern CMS 4.8.0 Released
amordecosmos wrote #321986:
But if I put
<txp:variable name="previous_page" />on a different page, it’s empty.
By different page I take it that you mean txp page (template). It would not work like this as variables should be in all pages that make use of them. If it was working before it was definitely a bug.
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: Feedback to: Textpattern CMS 4.8.0 Released
amordecosmos wrote #321986:
if I put <txp:variable name=“previous_page” /> on a different page, it’s empty.
If it worked this way before, it was definitely a bug. There’s no variable state remembered from page to page. You need to treat each request as a discrete event and set everything you might need on it at the start of the page flow.
Sorry for the inconvenience if it really did work this way before: honestly never noticed.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
Re: Feedback to: Textpattern CMS 4.8.0 Released
Cheers for all the hard work, chaps.
Just pre-flighting an upgrade, and noticed that css.php and .htaccess in sites/site1/public have not been updated to correspond to the changes in their top-level counterparts, and it looks to me as though they should.
Code is topiary
Offline
Re: Feedback to: Textpattern CMS 4.8.0 Released
jsoo wrote #321993:
Just pre-flighting an upgrade, and noticed that
css.phpand.htaccessinsites/site1/publichave not been updated to correspond to the changes in their top-level counterparts, and it looks to me as though they should.
Hi Jeff – I think this is now done in dev, should be released with 4.8.1.
Last edited by gaekwad (2020-03-02 14:06:01)
Offline
Re: Feedback to: Textpattern CMS 4.8.0 Released
Excellent, thank you.
Code is topiary
Offline
#22 2020-03-26 21:03:33
- wavesource
- Member
- From: Australia
- Registered: 2011-08-02
- Posts: 56
Re: Feedback to: Textpattern CMS 4.8.0 Released
It is a thing of beauty. Thank you.
Offline
Re: Feedback to: Textpattern CMS 4.8.0 Released
i am looking forward to trying it out, but i have decided to await the 4.8.1 release as it is to address some issues identified by others.
…. texted postive
Offline
#24 2020-04-01 10:27:42
- singaz
- Member
- Registered: 2017-03-12
- Posts: 150
Re: Feedback to: Textpattern CMS 4.8.0 Released
Textpattern 4.8.0
<txp:author link="1" this_section="0" />
<txp:category link="1" this_section="0" />
In which field to fix?
tag_author
or
author
And categories, which field to fix:
tag_category
or
category
or
category_tags ?
Sorry my horror English. I’m learning textpattern, I’m learning English
Offline
Re: Feedback to: Textpattern CMS 4.8.0 Released
singaz: author@ and category strings.
I would like to fix this asap so it uses English strings regardless. I tried in 4.8.0 but was (rightly) reeled in. I wonder if 4.8.1 is a suitable place to do so since we have more time to test? Hmmmm…
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
Re: Feedback to: Textpattern CMS 4.8.0 Released
Bloke wrote #322420:
I would like to fix this asap so it uses English strings regardless. I tried in 4.8.0 but was (rightly) reeled in. I wonder if 4.8.1 is a suitable place to do so since we have more time to test? Hmmmm…
you had posted a fairly decent suggestion in your most recent post on the relevant GitHub post. I thought I had posted an answer, but it seems that got lost into thin air. Maybe I forgot to press the submit button… Anyway, recap, your idea – and I think it is a fairly workable solution:
- for new installs, default to English independently of the front-end language of the site
- for existing installs, a pref is available to choose to use English or use the front-end language.
The second option would allow existing sites to keep their existing localised URL schemes. That is good. One site I help manage uses both Front-end and Back-end non-English language and the URL’s reflect that – part. for categories. Those are also referenced by other sites.
Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
phiw13 on Codeberg
Offline
#27 2020-04-02 08:20:36
- singaz
- Member
- Registered: 2017-03-12
- Posts: 150
Re: Feedback to: Textpattern CMS 4.8.0 Released
Sorry my horror English. I’m learning textpattern, I’m learning English
Offline
#28 2020-06-09 17:36:48
- singaz
- Member
- Registered: 2017-03-12
- Posts: 150
Re: Feedback to: Textpattern CMS 4.8.0 Released
Accidentally noticed.
I am using textpattern version: 4.8.1.
I use the code in the default form:
<txp:etc_query data='<txp:body />' separator="|\/|" replace='h2[1]/preceding::*[1]$=<txp:output_form form="soo_toc" />|\/|p[2]$=<txp:output_form form="promo" />|\/|p[6]$=<txp:output_form form="related" />' />
When the menu “Production status” established to “Debugging” i get a message:
When the “Production Status” menu is set to “Debugging”, when I open the “Write” article, I get a message:
Sorry my horror English. I’m learning textpattern, I’m learning English
Offline