@robin-w – Busy for the next few hours, but then I will try to replicate this on my test server.
@blinkweb – I would also like to clarify that you are indeed referring to the main forum/topic indexes, not shortcodes or widgets. Also, are there actually topics within the forums that show the “no topics/replies” message? Or are they empty?
Looks like Robin is on it, but I did want to say thank you for posting a detailed description of the issue, what you’ve tried, and relevant settings.
It is a strange issue. Before digging in to code or the Divi theme, it sounds like something related to the criteria used for which topics are counted as “new”. @robin-w – let me know if you want a second set of eyes looking into this.
Thank you for providing the pictures. It provided the clarity I needed since “sidebars” are something completely different. You want to hide the COLUMNS for Voices/Topics/Replies/Freshness (for forum indexes and topic indexes) .
Perhaps we will add an option for this in the future, but neither myself nor @robin-w have ever mentioned it as a “upcoming feature”.
Whether we add that as a feature in the future or not is still TBD. But you can easily hide those columns with the following CSS code snippet:
@kigazw – Robin is releasing the next version within the next 24-48 hours, and it will include this new feature for “selective profile links for quoted usernames”.
You will find this new option in the “Quotes” tab > “10. Quoted User Profile Links”
This was a little tougher than I had anticipated due to the complexity of nested quotes (quoting another quote), but I managed to work it out. Quoted usernames will follow your settings, and can be changed at any time, providing full backward/forward compatibility with all quotes (top-level and nested) regardless of your past/current/future setting value.
I’m marking this topic as resolved, but feel free to follow-up if you have any questions or issues with this new feature.
@ajtruckle – Robin is releasing the next version within the next 24-48 hours. This “topic subscribe button prefix” addition will be included.
You can access it in the “Forum Buttons” tab > “2. Activate Subscribe Button” > “Topic Subscribe Prefix”
Check the box to enable a customized prefix, and then fill in the text area with that you want the prefix to be. If you’re happy with the spacing of a single space like the temporary hold-over code snippet above, you will want to put in that text area:
which is the ASCII code for a single space.
I’m going to mark this topic as resolved, but feel free to follow-up if you have any questions or issues with this new feature.
The “ | ” in question is actually built into bbPress as the default prefix to show before the topic subscribe button.
I’ve added the custom functionality you requested to the next upcoming release of Style Pack….but here is a simplified version of the new changes that will hold you over until the next release:
// temporary function to remove the | pipe character from before the subscribe button
function chuckie_topic_subscribe_filter( $html ) {
$pattern = '/ \| /';
$replace = ' ';
$html = preg_replace( $pattern, $replace, $html );
// return the customized button html
return $html;
}
add_filter( 'bbp_get_topic_subscribe_link', 'chuckie_topic_subscribe_filter', 10, 1 );
The code will replace the “space | space” before the subscribe button with just a single space ( ), which should you give you the desired visual appeal.
A pure CSS solution wasn’t realistic, but this simple PHP code snippet is.
You can keep this even after the next Style Pack release, or delete it and just use the new options I’ve added within Style Pack. They won’t conflict….but the above is hard-coded, while the next release of Style Pack will give you an input box to update/change this in the future easily.
Bad News – After inspection of the actual code, the only element that could be targeted uses a unique ID PER TOPIC (eg – “subscribe-11395” where 11395 is the ID of a single topic). In order to use a pure CSS solution to hide the | pipe, every single topic ID for every single topic within your forum would have to be targeted individually. You’d need to know the ID’s for every topic, add CSS for each current topic, and would have to manually add CSS for any new topic IDs as topics are created. Basically not realistically do-able or manageable. Looks like I can’t give you a temporary solution to hold you over for now after-all 🙁
Good News – You will only have to wait a few days until the permanent solution is available in the next release.
I am currently pool-side, but I will reply with a thorough solution in a little bit.
There is a way to do it with CSS using the :before or :after pseudo classes and I will post a code snippet later today for you…. however, it would seem to make more sense to add an input option for “button separator” to allow you to use any characters you want (or none in your case). I’m releasing an update within the next few days and will include this new option.
The code snippet I will post later today will hold you over, until the next release which will have a permanent solution for you.
I want to apologize to @se9wv22 – My own ignorance regarding bbPress already following the WP display-name-as setting escalated it. I was basically thinking that we had to alter code for what WP already does. Truthfully, I’ve never used anything other than usernames in bbPress, so I lacked that knowledge. Big thanks to @robin-w for clearing this up!
Yeah, that’s what I mean by “a TON of places within Style Pack where the change would have to implemented”.
I think the only way to handle it properly is with an option to choose what you want to be displayed: bbP nicename, WP username, WP display name, WP first/last name, WP nickname. Then EVERY PLACE in bbPress and Style Pack follows what you set.
A lot of changes to Style Pack, plus new code for bbPress to make that happen. Not a simple modification we could kick out quickly. It will take some time, but I think it’s a useful/worthwhile change we could do in the future.
Maybe @robin-w will chime in with additional input, but as it stands now, the answer is no. bbPress uses the “nicename” which is a URL friendly version of the username. Style Pack currently follows that bbPress default.
What you’re requesting could be added, but there are a TON of places within Style Pack where the change would have to implemented, and all of those places would have to be linked to a new settings option value for choosing which name to use.
There are also other parts of bbPress that new code would have to added to override the nicename for consistency reasons.
With that said, I do see the value in your request, and would like to implement it in the near future….but that may be a little while.
Viewing 15 replies - 211 through 225 (of 407 total)
