A place for Extension Authors to post and receive feedback on Extensions still in development. No Extensions within this forum should be used within a live environment!
This is a very nice extension! But... I realize, I'm looking for another feature.
I have older, dated content that I would like to move into an active subforum (e.g., posts about car events that happened several years ago). I would like to arrange my content in reverse chronological order - i.e., most recent posts, first. While I can order the content I am moving into a subforum in reverse chronological order, because it has a priority, it precedes any content already in the forum that has a default zero priority - even if the migrated content is older. And I don't want to have to constrain *every* post in the subforum to have a priority, in order to keep most recent posts ahead of older ones.
For your consideration: What if you could assign negative priorities, so that posts with a default priority of zero always precede them? And posts with the most negative priority, would be furthest down the list?
Just a thought. This is a very nifty extension. Thanks!
Dan
Last edited by shortmort37 on Sun Mar 03, 2019 5:04 pm, edited 1 time in total.
shortmort37 wrote: ↑Sun Feb 10, 2019 8:05 pm
What if you could assign negative priorities, so that posts with a default priority of zero always precede them? And posts would the most negative priority, would be furthest down the list?
That it is not what the client has paid for (and that he has made all this available free of charge).
Therefore you should ask for an extension that can fulfill your specific desire.
If folks should find that they would like to use this most excellent extension to decrease a topic priority, as well as increase it - I submit for the author's consideration, the following two tweaks.
Open [board]/ext/phpbbstudio/tcs/styles/prosilver/template/event/posting_editor_subject_after.html and find:
3Di wrote: ↑Mon Mar 04, 2019 12:04 am
I will not support code not explicitely approved/merged by us in the master (for future readers)
That's fine, and I understand. But as I explained in my previous post, what I asked for is a very useful enhancement to me; and I presume to others, which is why I disclosed what I did in order to provide the enhancement. But I do think you ought to consider incorporating it in your extension, because it may indeed prove to be useful to others. That is, of course, entirely up to you.
3Di wrote: ↑Mon Mar 04, 2019 12:04 am
Though a question arises:
Is the any particular reason to leave that COLON : there if you are not bound to use the display width attribute?
I'm not a phpBB expert; but, it's the only signed integer data type option I see in [board]/phpbb/db/tools/tools.php (except for bigint), and it includes the ":":
Yeah removing such colon will lead to a disaster.
Using it that way instead correctly set it to its default value int(11) [0] ( -2,147,483,648 to 2,147,483,648 )
Odd enough IMO, that's by design though.
Side note, I have never seen it used that way (no occurencies within the core code's migration files too).
Those database types with a :%d should be declared specifically by the extension, so while it may default to 11, you should specify it.
All occurrences of :%d should be replaced by an actual integer of how many numbers you want.
mrgoldy wrote: ↑Tue Mar 05, 2019 7:25 am
Those database types with a :%d should be declared specifically by the extension, so while it may default to 11, you should specify it.
All occurrences of :%d should be replaced by an actual integer of how many numbers you want.
I'm unclear on exactly what this means. Should I declare something like this, instead?
'topic_priority' => array('INT:11', 0),
Where does -2,147,483,648 come from, anyway? I know that the least negative number that can be represented in 16 bits (base 2) is -32,768. The least negative number for 11 digits in base 10 would be -99,999,999,999 - no?