Forum Replies Created

Viewing 15 replies - 241 through 255 (of 407 total)
  • Thread Starter codejp3

    (@codejp3)

    I did not see any other forums tied to bbPress on your site, so I’d have to know where those user forums are.

    If those user forums are part of the main bbPress root index (did not appear to be so when I looked at your site), then it means you have more than one forum after all, and this method won’t work for you.

    If those user forums exist somewhere else besides the default bbPress root index, then they will continue to function as they did before you apply this method.

    Thread Starter codejp3

    (@codejp3)

    Sure. You can make it step 2, or step 10. Doesn’t matter. The point is – until you change the slug from “general forum-2” to “forums” or whatever you decided in step #1, it won’t work.

    I chose the order of the steps for the walkthrough because the first few steps deal with setting up the new structure. The middle steps deal with applying that structure to bbPress, and the last steps deal with frontend URLs. It makes the most sense to do each step, fully/completely, in the order I specified, and that is what I recommend. However, as I said in the last reply, the order of the steps doesn’t really matter and if you really insist on doing #2 last, then fine.

    It’s the entirety of all steps combined that produce the desired result. Once ALL steps are done, you have the desired end result. If even a single step is not done, the desired end result will not work.

    Thread Starter codejp3

    (@codejp3)

    Honestly, step #1 has to be first for obvious reasons. The rest of the steps could be done in any order as long as they’re all done.

    Thread Starter codejp3

    (@codejp3)

    That’s fine. If I could edit the post, I would, but since I can’t, here’s some clarification:

    The page title can be whatever you want. I used “General Forum” as the example so that it would match your only forum name.

    The important part of Step #2 is that the page slug matches the slug you decided on in Step #1.

    Make sure you use the slug from Step #1 in EVERY step after that. They MUST match in every step. If you decided on something other than “forums” that I used in the example instructions, then you MUST use THAT slug in every step instead of “forums”. To keep is simple, I’d suggest using forums as the slug. But it’s your site, your call.

    Thread Starter codejp3

    (@codejp3)

    UPDATED REDIRECT CODE SNIPPET:

    AFFECTS STEP #9 & STEP #10 ABOVE!

    It won’t let me edit the above post, so I’m posting an updated code snippet here.

    Change:

    The only change is that “wp_redirect” and “exit” has been added directly to each specific redirection condition check instead of setting a flag and waiting until the end to do the redirect.

    Reason For Change:

    After more testing of the code, I found that in cases where multiple redirection conditions are ture, the $redirect_url value was being overwritten with the wrong redirect-to string.

    // function to handle custom redirection for single forum permalinks
    // needed to remove default bbPress forum root index and use custom "fake" forum root index
    function custom_single_forum_redirect() {
    	
    	
    		/*
    		 * Setup Variables. Should be the only part of this code you need to modify
    		 */
    		$original_forum_index_slug = 'forums';
    		$original_single_forum_slug = 'slug-for-the-one-and-only-single-forum';
    		$new_slug = 'forums';
    		$single_forum_slug_base = bbp_get_forum_slug();
    		$redirect_old_forum_root_index = false;
    	
    	
    		/* DO NOT MODIFY ANYTHING BELOW THIS LINE UNLESS YOU HAVE A REASON AND KNOW WHAT YOU'RE DOING! */
    	
    		// only do this code if on the frontend of the site
    		if ( ! is_admin() ) {
    
    				// let's dissect and check the requested URL
    				if ( isset( $_SERVER['HTTP_HOST'] ) && isset( $_SERVER['REQUEST_URI'] ) ) {
    					
    						// does the URL request start with the single forum permalink slug and the only single forum slug? 
    						// we want to redirect /forum/slug-for-the-one-and-only-single-forum to /forums
    						if ( strpos( $_SERVER['REQUEST_URI'], '/' . $single_forum_slug_base . '/' . $original_single_forum_slug ) === 0 ) {
    								// set redirect flag to true so we do a redirect
    								$redirect = true;
    								// build out new URL to redirect to
    								$redirect_url = is_ssl() ? 'https://' : 'http://';
    								$redirect_url .= $_SERVER['HTTP_HOST'];
    								$redirect_url .= str_replace( '/' . $single_forum_slug_base . '/' . $original_single_forum_slug, '/' . $new_slug, $_SERVER['REQUEST_URI'] );
    								wp_redirect( $redirect_url, 301 );
    								exit();
    						}
    					
    						// does the URL request start with the old forum index slug and single forum permalink slug and the only single forum slug? 
    						// we want to redirect old /forums/forum/slug-for-the-one-and-only-single-forum to /forums
    						if ( strpos( $_SERVER['REQUEST_URI'], '/' . $original_forum_index_slug . '/' . $single_forum_slug_base . '/' . $original_single_forum_slug ) === 0 ) {
    								// set redirect flag to true so we do a redirect
    								$redirect = true;
    								// build out new URL to redirect to
    								$redirect_url = is_ssl() ? 'https://' : 'http://';
    								$redirect_url .= $_SERVER['HTTP_HOST'];
    								$redirect_url .= str_replace( '/' . $original_forum_index_slug . '/' . $single_forum_slug_base . '/' . $original_single_forum_slug, '/' . $new_slug, $_SERVER['REQUEST_URI'] );
    								wp_redirect( $redirect_url, 301 );
    								exit();
    						}
    					
    						// handle redirects for the old forum root index, but only if flag set to true and the original/new slugs do not match
    						if ( ( $redirect_old_forum_root_index === true ) && ( $original_forum_index_slug !== $new_slug ) ) {
    								// does the URL request start with the old forum root index slug? 
    								// we want to redirect /old-forum-root-index-slug to /forums
    								if ( strpos( $_SERVER['REQUEST_URI'], '/' . $original_forum_index_slug ) === 0 ) {
    										// set redirect flag to true so we do a redirect
    										$redirect = true;
    										// build out new URL to redirect to
    										$redirect_url = is_ssl() ? 'https://' : 'http://';
    										$redirect_url .= $_SERVER['HTTP_HOST'];
    										$redirect_url .= str_replace( '/' . $original_forum_index_slug, '/' . $new_slug, $_SERVER['REQUEST_URI'] );
    										wp_redirect( $redirect_url, 301 );
    										exit();
    								}
    						}
    					
    				}
    			
    		}
    }
    
    // hook into init to process redirection before header
    add_action( 'init', 'custom_single_forum_redirect' );

    Also marking as resolved for forum support statistics reason, but feel free to ask questions if you are attempting this override of default bbPress behavior and get stuck.

    @hellsbrigade

    Italian:

    Voglio solo essere chiaro che Style Pack offre attualmente il reindirizzamento dopo l’accesso, ma al momento è piuttosto limitato e consente solo di specificare un singolo URL specifico a cui reindirizzare.

    Quello che voglio cambiare è consentire opzioni selezionabili per il reindirizzamento a “ultima pagina visualizzata”, “home page del sito”, “home page del forum”, “profilo WordPress”, “profilo bbPress”, “profilo BuddyPress” o “URL specifico”.

    Fino a quando non verranno aggiunti questi miglioramenti, puoi comunque reindirizzare al profilo BuddyPress digitando l’URL in “2.Login/logout” > “Logged in redirect” nella scheda delle impostazioni “Login” ( wp-admin/options-general.php? page=bbp-style-pack&tab=login ).

    Lavorerò anche per ottenere presto anche una traduzione automatica in italiano che potrebbe aiutarti a navigare un po ‘più facilmente nelle impostazioni.

    English:

    I just want to be clear that Style Pack currently offers redirection after logging in, but it’s fairly limited right now and only allows you to specify a single specific URL to redirect to.

    What I want to change is to allow selectable options for redirecting to “last viewed page”, “site homepage”, “forum homepage”, “WordPress profile”, “bbPress profile”, “BuddyPress profile”, or “specific URL”.

    Until these enhancements are added, you can still redirect to the BuddyPress profile by typing that URL within “2.Login/logout” > “Logged in redirect” on the “Login” settings tab ( wp-admin/options-general.php?page=bbp-style-pack&tab=login ).

    I will also work on getting an Italian machine translation done soon too which may help you navigate the settings a little easier.

    @mikelt68 – vous vous demandez si cela a été corrigé ou si vous avez encore besoin d’aide ?

    English:

    wondering if this has been fixed or if you still need help with it?

    What’s wrong with the “red” “green” “blue” “purple” colors I used in my code snippets? You didn’t use them! 🙂

    Seriously though, I thought it looked fine before but I think it looks slightly better now, just because there’s subtle contrast between the elements that it didn’t have with your default styling. Even though that particular red for widget titles doesn’t seem to be used anywhere else on your site that I could see….it works pretty well.

    As for suggestions, you could add subtle transitions to make the hover/active links change colors with a subtle effect. Just a thought.

    There’s really no limit on what you can style with CSS other than what CSS can/can’t do. It’s a balance between how picky you are and if it’s worth the time to make the changes you want. If your goal is more about the learning experience than the end result, then really dig into CSS documentation and play around with it.

    Good deal 🙂

    @cj74 – looked at the site.

    1.) the :hover : active :visited appear to be working properly.

    However, like I said above, the “visited” may confuse people and not look right with your site, so I would probably remove that, or make it a different color to distinguish it apart from hover/active links. Here’s a revised version of that:

    /* Topics & Replies Widget Links */
    ul.bbp-replies-widget li a.bbp-reply-topic-title, ul.bbp-topics-widget li a.bbp-forum-title {
        color: #3a3a3a;
    }
    
    /* Topics & Replies Widget Links Hover/Active */
    ul.bbp-replies-widget li a.bbp-reply-topic-title:hover, ul.bbp-replies-widget li a.bbp-reply-topic-title:active,
    ul.bbp-topics-widget li a.bbp-forum-title:hover, ul.bbp-topics-widget li a.bbp-forum-title:active {
        color: #010203;
    }
    
    /* Topics & Replies Widget Links Visited */
    ul.bbp-replies-widget li a.bbp-reply-topic-title:visited,
    ul.bbp-topics-widget li a.bbp-forum-title:visited {
        color: red;
    }

    2.) The title will work, but requires adding “!important;” on the end of the value like this:

    /* ALL Widget Titles */
    aside.widget h2.widget-title {
        color: red !important;
    }
    
    /* ONLY Replies Widget Title */
    aside.widget_display_replies h2.widget-title {
        color: red !important;
    }
    
    /* ONLY Topics Widget Title */
    aside.widget_display_topics h2.widget-title {
        color: red !important;
    }
    
    /* BOTH Topics & Replies Widget Titles */
    aside.widget_display_replies h2.widget-title, aside.widget_display_topics h2.widget-title {
        color: red !important;
    }

    I won’t be around much for the rest of the day. Dog-watching for someone and have a doggy emergency to tend to. 🙁

    taking a look now…

    Update:

    Took a look real quick.

    “ul.bbp-replies-widget li a.bbp-reply-topic-title:link” does work to target unvisited links.

    “ul.bbp-replies-widget li a.bbp-reply-topic-title:hover” does not work.

    “ul.bbp-replies-widget li a.bbp-reply-topic-title:active” does not work.

    “ul.bbp-replies-widget li a.bbp-reply-topic-title:visited” does not work.

    Not even any basic standard “a:hover”, “a:visited”, or “a:active” target elements are working. That’s very telling that something isn’t right.

    It’s as if you have something preventing/overwriting specific pseudo elements. Will look into it a little more tomorrow, but it’s time for me to get some sleep tonight.

    • This reply was modified 3 years, 2 months ago by codejp3. Reason: added update

    @cj74 – got it!

    Checked out your website to see the changes myself. Here’s my feedback. You can apply it, or ignore it. Your site, so do what you think is best.

    1.) Widget Titles
    I did not see any changes made to the widget titles. Ideally, they should match the title of all other widgets (which they currently do). If you did want to make any changes to those in the future these are the CSS elements to target:

    /* ALL Widget Titles */
    aside.widget h2.widget-title {
        /* styling code goes here */
    }
    
    /* ONLY Replies Widget Title */
    aside.widget_display_replies h2.widget-title {
        /* styling code goes here */
    }
    
    /* ONLY Topics Widget Title */
    aside.widget_display_topics h2.widget-title {
        /* styling code goes here */
    }
    
    /* BOTH Topics & Replies Widget Titles */
    aside.widget_display_replies h2.widget-title, aside.widget_display_topics h2.widget-title {
        /* styling code goes here */
    }
    

    2.) Topic/Reply Authors
    You asked about it in the email, and I don’t see any changes made, so if you wanted to make any changes to those, here are the CSS elements to target:

    /* BOTH Topic/Reply Author Avatar */
    aside.widget span.bbp-author-avatar {
        /* styling code goes here */
    }
    
    /* BOTH Topic/Reply Author Link */
    aside.widget a.bbp-author-link {
        /* styling code goes here */
    }

    3.) Topic/Reply Links
    I do see changes here. Specifically #2A3439; for reply titles, and #010203; for topic titles.
    Here, I have a suggestion.

    First – Links typically change color when hovered over, or visited, or active. That’s simply a matter of adding pseudo elements on to the targeted element ( :active, :visited, :hover ) and defining the values you want for those pseudo elements.

    Second – Make the title colors match between both widgets. Then use the hover/active/visited pseudo elements to achieve the contrast.

    For your site/theme, the standard font color for paragraphs is #3a3a3a; I would use this as the default color, and then use either #2A3439; for a subtle contrast, or #010203; for a more drastic contrast with the pseudo elements. Turning this into usable CSS code would look something like this:

    /* Topics & Replies Widget Links */
    ul.bbp-replies-widget li a.bbp-reply-topic-title, ul.bbp-topics-widget li a.bbp-forum-title {
        color: #3a3a3a;
    }
    
    /* Topics & Replies Widget Links Hover/Active/Visited */
    ul.bbp-replies-widget li a.bbp-reply-topic-title:hover, ul.bbp-replies-widget li a.bbp-reply-topic-title:active,
    ul.bbp-replies-widget li a.bbp-reply-topic-title:visited,
    ul.bbp-topics-widget li a.bbp-forum-title:hover, ul.bbp-topics-widget li a.bbp-forum-title:active,
    ul.bbp-topics-widget li a.bbp-forum-title:visited {
        color: #010203;
    }

    Or whatever you see fit. Maybe remove the “visited” target elements since that may confuse some people, or not look right with your theme. You have complete versatility to change these styling elements however you see fit.

    I’m going to mark as resolved since it looks like you’ve got the hang of it, but feel free to ask any other questions you may have.

    • This reply was modified 3 years, 2 months ago by codejp3.

    @cj74 – I just sent you an email with screenshots to try to help clear up how CSS is applied.

    I’ll mark this as resolved once you’ve figure out how to accomplish the color changes you want to apply. Feel free to ask any questions you need to.

    I will be asking some questions but you can answer them here (quote me if you like), so that others can also benefit from it.

    Here we go!

    The questions that arose from your post which included the code snippets is where do i place those snippets?

    The CSS code snippets can go in ANY enqueued CSS file. That can be a theme file, custom styling file, or by-far the easiest way – the “Custom CSS” tab within Style Pack ( wp-admin/options-general.php?page=bbp-style-pack&tab=css ).

    If you include the code snippets within a theme file or custom styling file, it MUST be enqueued for the CSS code to be applied to the front-end of the website. If you choose to include them within a theme, you MUST setup a child theme to hold all of your customizations, or they will be lost if the theme is ever updated by the theme author.

    If you include the code snippets in the “Custom CSS” tab within Style Pack, it will automatically be included and enqueued within the generated styling file. Simply paste your CSS snippets in there and click “save”. Done.

    For these reasons, it is recommended to just use the built-in Style Pack “Custom CSS” tab.

    Are there any other places at the server level like say “theme.php” or something similar that may even work better and be more permanent in sense of future changes?

    As I said above, if you’re going to post them within the theme style.css file(s), you MUST setup a child theme to hold your custom styling or they will be lost whenever the theme is upgraded.

    Beyond that, no, it does not matter HOW you include your custom CSS code snippets.

    CSS works according to the HTML DOM hierarchy. The more specific the targeted CSS element is, the higher the priority it is given/rendered. It doesn’t matter which file the CSS code is included in, or the order it’s included. CSS works according to the targeted CSS selector. The more specific the targeted CSS selector is, the higher the priority those styling values are given/applied.

    For example, targeting:

    a {
        color: red;
    }

    That is very generic and will give ALL <a> HTML tags the color red…. UNLESS a more specific element is targeted like:

    a.bbp-reply-topic-title {
        color: blue;
    }

    When the page is rendered with those 2 code snippets, ALL <a> HTML tags would be red EXCEPT for <a> tags that have the class “bbp-reply-topic-title”, because those were specifically targeted (higher priority) and given the color value blue.

    It doesn’t matter which file(s) these CSS code snippets are included in. The specificity of the targeted selector is what determines the styles that get applied.

    To further complicate it, you have a caching plugin that takes all CSS code, caches it, and injects it into the web page as “inline” code at the very beginning of the HTML output. All of the CSS code shows as “inline” as the source….which is fine because like I said, it doesn’t matter which file the code lives inside, the targeted CSS element is what determines how the page is rendered, and which styling elements are given higher priority.

    The easiest way to see what CSS code is being rendered and the file(s) that contain the CSS code is by using the built-in developer tools available in most browsers today. Right-click on any part of the page you want to inspect, and then click “dev tools”, “developer tools”, “web developer”, “inspect”, or whatever it may be called for the browser you’re using.

    Going on that note, for YOUR SITE, the CSS code snippets would be slightly different based on the specific theme you’re using. Instead of “section”, you’d use “aside” like so:

    /* Replies Widget Title */
    aside.widget_display_replies h2.widget-title {
        color: red;
    }
    
    
    /* Topics Widget Title */
    aside.widget_display_topics h2.widget-title {
        color: green;
    }

    In the screenshot of the general forum you see the topics – I understand the font color for that can be easily changed by thestylepack, correct?

    Style Pack does not offer any direct changing of any styles for the bbPress widgets (what you originally asked about). That requires CSS code like the snippets I posted above.

    But, it does offer styling for the Style Pack “Latest Activity Widget” (which you appear to be using on your site) ( wp-admin/options-general.php?page=bbp-style-pack&tab=la_widget ). That will allow you to change colors and other styling aspects without even having to use any custom CSS code snippets.

    [email protected]

    Ignore the auto response. It’s an auto spam filter public email. I’ll get it as long you don’t include spammy words in your email.

Viewing 15 replies - 241 through 255 (of 407 total)