jauburn
Well-known member
Just feature a resource discussion thread.
Ah, I see.
Just feature a resource discussion thread.
I'm not sure what you're suggesting.
You can already feature as many threads as you want, up to the limit you set in the ACP.
The display is already randomised each page view.
I would recommend reading the release notes for all three versions
Each page load of the forum list will display a random thread from the list of available threads.
If there are no threads available, the block won't display.
The maximum number of threads which can be featured at any one time can be set in the options.
I can't see the purpose of that personally.
The featured threads are going to constantly change based on the threads being featured and the duration.
So it's not really like dismissing a static notice.
I will however add it to the list for consideration.
If it is implemented it will just be a check box to completely remove all featured threads, not selectively dismiss each one.
I'm not sure I understand the first problem as smilies aren't parsed in the overlay, they just appear as the replacement text.
Can you post an image to show what it is you mean?
I checked the text in my previous screenshot and it is 717 characters so already below this (though there are 5 blank lines too). The issue seems to have arisen because of the additional Do not change feature duration option plus the two lines of who/when featured and current feature duration text in the overlay when editing a featured thread (as you can see from the previous screenshot) which makes the overlay bigger than the overlay that is used when first featuring a thread.As for the second issue, the overlay uses the standard code which is used elsewhere in XenForo, in that it automatically expands to a maximum of 300px high if there is enough content to warrant it.
The simplest solution would be to reduce the amount of characters pulled from the post - it is set to 1,000 by default. Try changing it to 800 or so and see if that works.
<dd><textarea name="message" class="textCtrl Elastic" autofocus="true" id="ctrl_title_feature_thread_message" rows="@ctaFtOverlayContentRows" style="max-height: 250px">{xen:raw $featuredThread.featured_message}</textarea></dd>
Please don't remove smiley parsing on my account. I just thought I would mention it in case there was something I was missing or something that could easily be done. I'm happy to just remove smilies from my Featured Threads due to my large smilies so that others with standard sized ones can use them.Oh so it is
I removed smiley parsing - it must have snuck back in after I changed the code to parse URLs but I never tested it again
I can't really do much about that as the smiley height is much larger than the standard line height for text.
Whatever you do is going to have an impact depending on whether there are smilies or not and how tall they are.
That was why I originally stopped them parsing, so I will have to update the code to stop that once again.
It does seem odd behaviour for one of these overlays to 'misbehave' and the other not.For the overlay, the 300px max height is the standard elastic css so you can either edit that or you can edit the cta_featuredthreads_edit template and add a max height to the overlay, like so:
Rich (BB code):<dd><textarea name="message" class="textCtrl Elastic" autofocus="true" id="ctrl_title_feature_thread_message" rows="@ctaFtOverlayContentRows" style="max-height: 250px">{xen:raw $featuredThread.featured_message}</textarea></dd>
I'll see if I can add some additional style properties for the max overlay heights for each template.
I'm making it an option so the admin can decided whether to display smilies or not.Please don't remove smiley parsing on my account.
Which browser and OS are you using?Now I might be wrong, but I wouldn't think that this is expected behaviour?
- Delete most of the text, leaving just 3-4 lines
- Click on Feature Thread
- Now in Thread Tools click on Edit Featured Thread
- Type in some text and the it will grow as expected
- Continue to type in more text. This time, the Save Changes and Cancel buttons disappear off the bottom of the page.
We use essential cookies to make this site work, and optional cookies to enhance your experience.