etc

And I don't remember why we don't internally store them as `$thisarticle['custom_n']` to avoid such clashes.

Yes, changing the location of existing assets looks problematic. I'd start by moving `plugins` there, since it does not look clean to keep a writeable directory inside `textpattern` folder.

Yes, everything 'custom' should be taken out of `textpattern` and go to a common directory. Easier for txp updates too. We also probably have `tmp` and `setup` to move?

`format="flat.link"` and `format="flat.url"` produce two different outputs for me. Are you sure your editing software has not inserted a space after the dot as they sometimes tend to do?

I get this when copy-pasting, both on Pete's `release` [demo site](https://release-demo.textpattern.co/) and in my local `dev` branch: ``` ``` No clue why you are always getting flat paths. What if...

As I [get](https://w3c.github.io/html/textlevel-semantics.html#the-cite-element) it, `cite` is more than just italics: > The cite element represents a reference to a creative work. It must include the title of the work or...

> What about using double double-quotes or double single-quotes wrapping the text? It's fine from "writer" pov, but a bit risky in txp context. Something like this could be broken:...

As long as a new txp release is fully compatible with the previous one (as for 4.9), I see no urge in upping PHP version, unless the code requires it....

Patched since ages, left as a reminder, closing.

I have tried counting local files lines, it's quite fast. Sure, if a user alters some core language file, the %age will be biased, but I don't think many do,...