Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#25 2013-10-04 12:54:41

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 11,271
Website GitHub

Re: Eventual forum upgrade plan

Gocom wrote:

and some new ranks so that we all aren’t omegas.

Fabulous stuff. Gives me something to aim for again to try and catch up with Els :-)


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

#26 2013-10-04 13:08:44

uli
Moderator
From: Cologne
Registered: 2006-08-15
Posts: 4,304

Re: Eventual forum upgrade plan

Thanks for all your work, Jukka and Phil!

“Post quoting” reminded me of something: Back when the tweet links were introduced they took the position of the post numbers, which in return vanished. It’d be great if we could we have these back, there are lots of users who referenced in-topic posts with only numbers. These references are now “broken”.


In bad weather I never leave home without wet_plugout, smd_where_used and adi_form_links

Offline

#27 2013-10-04 13:41:45

els
Moderator
From: The Netherlands
Registered: 2004-06-06
Posts: 7,458

Re: Eventual forum upgrade plan

Bloke wrote:

try and catch up with Els :-)

What you need is a FluxBB plugin that splits lengthy posts into several short ones ;)

(And post more silly OT remarks like this one…)

Last edited by els (2013-10-04 13:44:05)

Offline

#28 2013-10-04 14:14:59

Gocom
Developer Emeritus
From: Helsinki, Finland
Registered: 2006-07-14
Posts: 4,533
Website

Re: Eventual forum upgrade plan

uli wrote:

Back when the tweet links were introduced they took the position of the post numbers, which in return vanished.

As we are going away from mods, these numbers are going to be back. We are probably going to leave the repeating Tweet links out and only have one for the topic, which uses the topic title as the tweet message. Posts are bit too long for a tweet.

Last edited by Gocom (2013-10-04 14:22:52)

Offline

#29 2013-10-05 12:35:44

uli
Moderator
From: Cologne
Registered: 2006-08-15
Posts: 4,304

Re: Eventual forum upgrade plan

Gocom wrote:

As we are going away from mods, these numbers are going to be back.

Great, thanks.


In bad weather I never leave home without wet_plugout, smd_where_used and adi_form_links

Offline

#30 2013-10-06 18:34:06

candyman
Member
From: Italy
Registered: 2006-08-08
Posts: 684

Re: Eventual forum upgrade plan

Offline

#31 2013-10-06 19:09:45

Gocom
Developer Emeritus
From: Helsinki, Finland
Registered: 2006-07-14
Posts: 4,533
Website

Re: Eventual forum upgrade plan

candyman wrote:

esoTalk

Looks shiny, but it currently doesn’t have stable releases, and those gammas are tagged far and between. We aren’t really looking into changing the platform we are using, and if we were, one requirement would be a stable release.

Last edited by Gocom (2013-10-06 19:12:01)

Offline

#32 2013-10-06 19:10:20

philwareham
Core designer
From: Haslemere, Surrey, UK
Registered: 2009-06-11
Posts: 3,564
Website GitHub Mastodon

Re: Eventual forum upgrade plan

@candyman

We are not changing software, just updating and improving what we already have (and doing a new theme).

EDIT: ok Jukka already posted, I should read the whole thread next time!

Last edited by philwareham (2013-10-06 19:11:34)

Offline

#33 2013-10-07 05:55:00

colak
Admin
From: Cyprus
Registered: 2004-11-20
Posts: 9,012
Website GitHub Mastodon Twitter

Re: Eventual forum upgrade plan

Are we keeping the topic search?


Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.

Offline

#34 2013-10-07 08:18:36

Gocom
Developer Emeritus
From: Helsinki, Finland
Registered: 2006-07-14
Posts: 4,533
Website

Re: Eventual forum upgrade plan

colak wrote:

Are we keeping the topic search?

In topic search is a modification (a hack), so it’s not going to stay. What FluxBB doesn’t offer, and we can’t implement without modifications, doesn’t exists (only exception to this rule being Textile). The only search field visible on pages is the one that takes you to Google’s custom site search. We are currently experimenting with automatically prepending the topic title to search field, which will give you more relevant results.

Offline

#35 2013-10-07 10:49:10

colak
Admin
From: Cyprus
Registered: 2004-11-20
Posts: 9,012
Website GitHub Mastodon Twitter

Re: Eventual forum upgrade plan

Gocom wrote:

In topic search is a modification (a hack), so it’s not going to stay. What FluxBB doesn’t offer, and we can’t implement without modifications, doesn’t exists (only exception to this rule being Textile). The only search field visible on pages is the one that takes you to Google’s custom site search. We are currently experimenting with automatically prepending the topic title to search field, which will give you more relevant results.

Hi Jukka, I hope that this method will work. With some topics exceeding 200 pages it will be impossible to use the search function productively and effectively if the particular functionality is removed.


Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.

Offline

#36 2013-10-07 11:02:19

philwareham
Core designer
From: Haslemere, Surrey, UK
Registered: 2009-06-11
Posts: 3,564
Website GitHub Mastodon

Re: Eventual forum upgrade plan

colak wrote:

With some topics exceeding 200 pages…

It could be argued that if a topic has over 200 pages then maybe a new thread should be started, regardless of whether an in-topic search is implemented.

An example being the ‘MLP – The Multi-Lingual Publishing Pack’ thread which is almost impossible to follow even with topic search.

Offline

Board footer

Powered by FluxBB