Dev news

etc · 2019-11-12 11:28:22

The situation can be complicated even in single-site setups. Recall that we have themes that can be used simultaneously (one per section). Themes contain tags. Tags can be these of core, but also plugins ones.

Suppose now that Theme A requires a plugin version incompatible with this of Theme B. How do we manage it?

gaekwad · 2019-11-12 19:24:44

Bloke wrote #320016:

Think what would happen if all sites shared a single Txp installation and you upgrade or delete a plugin on Site A… it gets updated/removed in the central repo and Site B is affected.

I would hope (perhaps I’m being optimistic) that someone with enough scope to figure out multi-site has the smarts and visibility to factor that stuff in. I toyed with multi-site a while ago, couldn’t get it to work and I’ve never properly embraced it…I’m probably less likely to now, especially with the ease that a new Textpattern can be spun up and themed.

I know people who run multiple Txp versions and symlink clients to the latest version on a case-by-case basis once they’ve paid the upgrade fee and/or it’s been tested on their site.

That’s genius. Never would’ve thought of that, how clever!

etc · 2019-11-17 23:18:32

Have I mentioned we have a global evaluate attribute in 4.8? It’s more than just a shortcut for <txp:evaluate /> tag. Consider the following block, outputting a category list with articles count:

<txp:category_list children="1" wraptag="ul" break="li">
    <txp:evaluate test="article_custom">
        <txp:category title link /> (<txp:article_custom category pgonly pageby="1" escape="trim, integer" />)
    </txp:evaluate>
</txp:category_list>

Categories that have no articles will not be output (escape="trim, integer" makes 0 values fail the test). But break="li" will still apply, even to empty blocks, so we might get something like

<ul>
    <li>Animals (5)</li>
    <li></li>
    ...
</ul>

With evaluate attribute the problem is solved:

<txp:category_list children="1" evaluate="article_custom" wraptag="ul" break="li">
    <txp:category title link /> (<txp:article_custom category pgonly pageby="1" escape="trim, integer" />)
</txp:category_list>

will remove empty blocks from the output.

Should we make global trim attribute act this way too? Currently it trims list items, but does not remove the empty ones.

jakob · 2019-11-18 20:08:40

etc wrote #320105:

Have I mentioned we have a global evaluate attribute in 4.8?

Another excellent addition! And a great use case that will allow @bici to put cbs_category_list to rest (as mentioned here).

Should we make global trim attribute act this way too? Currently it trims list items, but does not remove the empty ones.

I reckon that’s a good idea but admittedly I can’t think of any situations off the top of my head where that might not be a good idea.

jakob · 2019-11-18 20:17:40

One more thing :-) I come up against where I wonder whether some trick might help is dealing with if_different and the first wrapping item.

Say you have something like:

<txp:if_first_article>
    <header>
        …
    </header>

    <section class="container">
        <div class="month hidden">
</txp:if_variable>
</txp:if_first_article>

<txp:if_different>
        </div>
        <div class="month">
            <txp:posted format="%B" wraptag="h3" class="month-title" />
</txp:if_different>

            <article>
                …
            </article>

<txp:if_last_article>
        </div>
    </section>
</txp:if_last_article>

to group articles into month containers and add the month name as a title.

If you use txp:if_first_article within txp:if_different it shows you the first and the second article as being different. So I often place the first opening div and the last closing div in the if_first/if_last but you end up with an empty div at the top (which I then hide with css). I know I can search and replace it out, but I can’t help thinking there’s a better way to avoid it.

I seem to remember that @els (?) had a complicated solution for this using a comment or variable or something, which I’ve forgotten how to do, but maybe you have something better in your arsenal of new attributes.

etc · 2019-11-18 22:05:30

Assuming the header is exterior to articles, this should work:

<txp:article label="My parsed header" labeltag="header"
    breakby="<txp:posted format='%B' />" break="div" breakclass="month"
    wraptag="section" class="container"
>
    <txp:if_different>
        <txp:posted format="%B" wraptag="h3" class="month-title" />
    </txp:if_different>
    <article>
        ...
    </article>
</txp:article>

Note that breakby value is double-quoted, otherwise it wouldn’t work as expected.

jakob · 2019-11-18 22:40:55

Ha, that is damn clever!

I realise I’ve not got my head round breakby yet (or breakform for that matter). You did actually write it in the docs and give an example as well.

The use of double quotes feels counter-intuitive given everything we’ve learnt about tags as attributes, but I guess the reason is that in this case the expression should be evaluated and not the result of the tag?

Thanks for the tip!

etc · 2019-11-18 23:03:13

jakob wrote #320122:

The use of double quotes feels counter-intuitive given everything we’ve learnt about tags as attributes, but I guess the reason is that in this case the expression should be evaluated and not the result of the tag?

Yes, exactly. You can avoid it by creating a monthbreak form instead

<txp:posted format="%B" />

and then calling

<txp:article label="My parsed header" labeltag="header"
    breakby="monthbreak" break="div" breakclass="month"
    wraptag="section" class="container"
>
    <txp:if_different>
        <txp:posted format="%B" wraptag="h3" class="month-title" />
    </txp:if_different>
    <article>
        ...
    </article>
</txp:article>

Or additionally create a month form

<div class="month">
    <txp:posted format="%B" wraptag="h3" class="month-title" />
    <+>
</div>

and call

<txp:article label="My parsed header" labeltag="header"
    breakby="monthbreak" breakform="month"
    wraptag="section" class="container"
>
    <article>
        ...
    </article>
</txp:article>

jakob · 2019-11-18 23:34:52

Well, I’m glad I asked that. It worked perfectly!

My situation was a bit more complex than I quoted above, especially the header, but it made it possible for me to remove most of the logic aspects out of the listform altogether, which has made things neater.

I think the expression in breakby is tolerable – easier to follow later than creating another form – but the breakform with the <+> placeholder has made it possible to keep the listform clean and re-usable for different situations: now the year view includes the breakform to wrap by month and the month view simply shows the regular listform without the wrapper.

etc · 2019-11-19 08:22:32

jakob wrote #320124:

I think the expression in breakby is tolerable – easier to follow later than creating another form – but the breakform with the <+> placeholder has made it possible to keep the listform clean and re-usable for different situations: now the year view includes the breakform to wrap by month and the month view simply shows the regular listform without the wrapper.

Glad it works for you. It will be even more flexible in 4.8 since breakform can be made breakby-agnostic:

<div class="month">
    <txp:yield item="breakby" wraptag="h3" class="month-title" />
    <+>
</div>

Note that item functionality is delegated to <txp:yield /> now, so <txp:item /> tag is available for future use.

etc · 2019-11-27 20:04:25

Global yield attribute for short-tags users: instead of

<txp:tag a='<txp:yield name="a" />' b='<txp:yield name="b" default="B" />' />

you can type just

<txp:tag yield="a,b" b="B" />

inside forms.

gaekwad · 2019-11-28 16:15:22

Since there’s a lot of traction in this thread, I’ll leave this here:

Textpattern 4.8.0 release – preflight

Extra brains and eyeballs appreciated on this issue, what else needs doing as part of the release process?

gaekwad · 2019-11-29 08:43:22

Bloke sifted through the dev changes since 4.7.3 and updated HISTORY.txt last night – it’s impressive!

github.com/textpattern/textpattern/blob/dev/HISTORY.txt

etc · 2019-12-06 15:55:21

Article preview gets its own movable/resizeable modal panel, paving a way to live preview:

phiw13 · 2019-12-07 02:50:50

etc wrote #320386:

Article preview gets its own movable/resizeable modal panel, paving a way to live preview:

That is interesting. Those mini-tabs at the top of the page will finally disappear, maybe to be replaced with a plain link, similar to the Pages & Forms tabs?

But live preview ? Hmm, something for users with large screens and wide browser windows. Can’t imagine that being useable on my MBA. But interesting nonetheless.

Textpattern CMS

Textpattern CMS support forum

#46 2019-11-12 11:28:22

Re: Dev news

#47 2019-11-12 19:24:44

Re: Dev news

Bloke wrote #320016:

#48 2019-11-17 23:18:32

Re: Dev news

#49 2019-11-18 20:08:40

Re: Dev news

etc wrote #320105:

#50 2019-11-18 20:17:40

Re: Dev news

#51 2019-11-18 22:05:30

Re: Dev news

#52 2019-11-18 22:40:55

Re: Dev news

#53 2019-11-18 23:03:13

Re: Dev news

jakob wrote #320122:

#54 2019-11-18 23:34:52

Re: Dev news

#55 2019-11-19 08:22:32

Re: Dev news

jakob wrote #320124:

#56 2019-11-27 20:04:25

Re: Dev news

#57 2019-11-28 16:15:22

Re: Dev news

#58 2019-11-29 08:43:22

Re: Dev news

#59 2019-12-06 15:55:21

Re: Dev news

#60 2019-12-07 02:50:50

Re: Dev news

etc wrote #320386:

Board footer