Tiki Website Gardeners' Blog

This code was removed on doc.tiki.org on the header_custom_css pref

/* Display first paragraph of wiki pages as a leading text */
#page-data > p:first-of-type, .wikipreview .wikitext > p:first-of-type {
    font-size: 120%;
    padding: 2rem;
    background: #f0f0f0;
    border-radius: .5rem;
    box-shadow: rgba(50, 50, 50, .15) 0 3rem 3rem -2rem inset, rgba(50, 50, 50, 0.1) 0 -1rem 2rem -1rem inset;
}
#page-data > p:first-of-type > br:first-of-type, .wikipreview .wikitext > p:first-of-type > br:first-of-type {
    display: none;
}

We can revisit later.

These are new default security preferences but they don't change on upgrades in case someone needs lower security.

https://gitlab.com/tikiwiki/tiki/-/merge_requests/1684

There was a category tree for areas with 4 categories: info, community, suite, translation. Now gone.
Theme control is no longer used at all.

There was a failure of link to Join Tiki in footer of doc.tiki.org so Gary deleted the "Registration page key" content:
"on tiki-admin.php?page=login, which was "RandomString", so "Key required to be on included the URL to access the registration page " is no longer specified but tiki-register.php can be accessed again."

tiki.org has strong provisions to prevent registration spam. Gary and I reviewed all these to make it easier for humans, using a similar strategy to wikisuite.org (which is dealing OK with spam)

Let's keep an eye on this

The Perspectives feature is a little shaky, and using Areas is downright buggy. And when you add Domain redirects, Multi-domain Configuration (mapping the domain name to the perspective ID), there are all kinds of edge cases. And it's difficult to debug because we can't easily reproduce a multi-domain configuration.

Victor and Jonny proceeded to a bunch of fixes from 2023-07-31 to 2023-08-02 on 26x: https://gitlab.com/tikiwiki/tiki/-/commits/26.x

I think we should stop using perspectives and areas on tiki.org, and if do use them, it should be on dev.tiki.org, with perhaps:

• developer docs
• issues
• translations
• security

All the info is kept up to date Pre-Dogfood Server

https://themes.tiki.org/blogpost72-Site-upgraded-to-branch-26x

comments_archive : enabled
feature_inline_comments : enabled

Looking to add some documentation, I was reminded of the old and completely useless pages that should be filtered out of sight in some way so, in line with the proposal here — Proposal for Handling Old Pages — I added Retired and Archived categories at doc.tiki.org. Retired is admin-accessible-only and is for pages that no longer have useful information, and Archived is Registered-accessible-only and is for pages that may still have some value but that it's better for casual visitors and search engines not to see.

Probably most pages that will be affected by this sorting will go into Retired, but I thought the Archived category might be useful for borderline cases.

Of course many of the remaining pages have sections that are out of date, etc., but need to stay public. On these pages, I suggest that information referring to old Tiki versions that are no longer supported should be deleted from the page, if the information is counter to current practices or otherwise not helpful. It still exists in the page versions history if anyone needs to see it. A note could be added on the page explaining that, but this might just be more clutter so maybe it's better not to bother.