Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 25 replies - 751 through 775 (of 1,007 total)
  • In reply to: BuddyPress Spam

    @rogercoathup

    Participant

    @tedmann – and changed the default text on the register page?

    @rogercoathup

    Participant

    @footybible Yes, good spot by @govpatel

    Of course, that file is not going to be BuddyPress aware, so won’t know about BP_REGISTER_SLUG

    It’s not really a good choice for the registration / login screen for a BP site. If you are stuck working with that, rather than the standard BP login area, then you will have to hack your wp-login.php as @govpatel suggests

    @rogercoathup

    Participant

    @johnjamesjacoby – What are you thoughts on changing: bp_blogs_record_activity( ) to make use of the featured image if one has been set for the post, rather than trawling the content and thumbnailing images?

    @rogercoathup

    Participant

    Giving this one a bump – as I want the feature!

    The challenge: display the featured image (post_thumbnail) from the latest site blog posts

    The solution that comes to mind is: an activity stream loop to extract the blog post activity; get the blog id and post id; switch to the blog; query based on the post id to get the post_thumbnail

    However, the switch to blog route strikes me as quite inefficient.

    Does anyone have a better solution to this? Oh, and of course, a perfect working infinitely flexible code snippet to share

    Thanks, Roger

    p.s. the function bp_activity_thumbnail_content_images is being passed the blog post content, so doesn’t have access to the feature image (post_thumbnail)

    @rogercoathup

    Participant

    @footybible –

    Ok, I don’t know the theme, but it looks like the designer has ‘gotten lazy’ and coded in a hard link to register.php rather than the register slug.

    You’ll have to get in there and find which template file it’s using, and change the link code to the register slug. The code you’ll be inserting is something like: http://pastebin.com/4n20tpx9

    Might be worth asking the theme designer to make the change.

    @rogercoathup

    Participant

    @footybible – What’ve you changed your slug to? What does the link point to that is failing? Essentially, they need to be the same thing.

    Which page is giving you the problem? Is it a standard WP login screen as opposed to a BuddyPress one? Which theme are you using?

    Based on this, you can just go in and edit the appropriate template file to point the link to the right place. You won’t have to touch ‘actions’ – certainly not ‘register_post’ … which is something completely different.

    In reply to: Sidebar Tabs

    @rogercoathup

    Participant

    @janismo – do you mean widgets aren’t working in your sidebar? Or, do you mean specific plugins for displaying the widgets in tabs aren’t working?

    If it’s a simple problem adding any widget, then try with the default theme, disable other plugins, and see if the problem still exists. [note: in general, if you have a widget / plugin that is supposed to be compatible, but isn’t working – it’s a good idea to strip back to basics and try to identify whether it’s something in your theme, or perhaps a clash between two of your plugins]

    If you want to create tabs manually, you are best to look at some of the Javascript libraries, e.g. jQuery, that have components already built for creating tabbed interfaces. You would then edit your sidebar.php template file to ensure your components are added, and that the markup is correct for the Javascript tabbing script.

    @rogercoathup

    Participant

    @hitler – they are coming – I guess partly as a result of end users tearing their hair out – group forums has some interesting technical / logical reasoning behind it, but the user interface experience was far from perfect.

    Check out @johnjamesjacoby post on the imminent new approach: https://buddypress.org/2010/08/buddypress-and-bbpress-the-future/

    Note: now the presentation / interface features should be back in the hands of the theme developer. You can clutter / un-clutter as much as you like, use groups / not use groups, standalone / not standalone, etc. – it should be much more flexible, allowing you to craft better and more exceptional websites.

    In reply to: Release for 1.2.6?

    @rogercoathup

    Participant

    @svetka812 forums are due to change totally.. See this post: https://buddypress.org/2010/08/buddypress-and-bbpress-the-future/

    @rogercoathup

    Participant

    Does it work if you switch to the bp-default theme?
    If so, the fault is in your theme. Give that a try, then provide more info on the error message.. can you register and login ok on your machine?

    @rogercoathup

    Participant

    @porscheheritage – exactly!

    If you are happy with the content being produced by the template files, then yes, just create you own style.css (and other css files) in your child theme, and modify to meet your needs.

    I quite like the bp-default folder structure for images and css files, so you might want to copy that.

    @rogercoathup

    Participant

    @crashutah – that all depends how much you’ve specialised your child theme away from the default. It also depends if there are new features you want to take advantage of – in which case dig around and see how they are being used in the default, and ‘steal / adapt’ as necessary.

    Remember for the most part, a theme is about presentation rather than underlying function / features. That said, this can be blurred as you dig into the activity loops and directory template files.

    We typically derive our child themes from the bp-default theme, but make very considerable changes – chopping out big chunks of the over heavy markup, and making somewhat dramatic changes to the layout. By deriving, we do however get to make use of some of default templates especially within the social loops, etc.

    For some of our newest sites, where you would struggle to know BuddyPress was even there, we are building our own themes from scratch.

    @rogercoathup

    Participant

    @porscheheritage: have you read this article on child theme development: https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/ ?

    That’s the best starting point.

    You don’t copy the BP-default theme – instead in your child theme, you create new templates where you want to override the default ones, and simply inherit the others. A directive you add to your child theme’s style.css file identifies which theme is it’s parent.

    In reply to: BuddyPress Spam

    @rogercoathup

    Participant

    @mark211 – You can change the slug just by adding the one line to wp-config.php

    define( ‘BP_REGISTER_SLUG’, ‘join-up’ );

    This thread tells a little more about potential problems: https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/defining-new-register-slug-not-working/

    ON the View problem – I think you have posted the wrong URL – it gives a 404 error

    Ask this question as a separate thread in support though. Search the forum first of all though, because I think there are some existing threads on this type of problem (view permalink)

    In reply to: Blogs on my BPsite

    @rogercoathup

    Participant

    Ah yes, as @djpaul points out – making sure the permalinks work in the base install sans BuddyPress is important. @djpaul – are there any other ‘easter eggs’ lurking under the skin?

    In reply to: BuddyPress Spam

    @rogercoathup

    Participant

    @mark211 – did you change the register slug in BuddyPress as well? Also, changing the default text that appears on the register page?

    @intimez – I think there should only be one register.php, in your theme’s (or the defaults if inheriting) register folder

    @rogercoathup

    Participant

    @lordsnake – At the risk of sounding patronising: –

    1. are you sure it’s the single.php template that is being used to render your page? Give it a little tweak in the bp-default theme (you can change it back afterwards) and let us know if it’s being picked up.

    2. are you sure your new single.php (child theme) has been published to your server?

    3. what happens if you try to override your index.php, does that get picked up?

    Failing that: post your folder structure, header from your style.css, and your single.php file for us to check.

    Oh, and which version of WP and BP

    In reply to: More Core Committers?

    @rogercoathup

    Participant

    @r-a-y – yes, it was :-) There’s a bit of follow up on my profile about it. I’m worried about the effect it has on the OP.

    In reply to: BuddyPress Spam

    @rogercoathup

    Participant

    everyone wants a plugin to solve this. Remove that register.php in the bbPress folder… go on, trust me, it really helps! :-)

    In reply to: Blogs on my BPsite

    @rogercoathup

    Participant

    Try reinstalling your WP3.0 system again, and see if that works in multisite setup.

    Once that’s fine, try installing BuddyPress using the install automatically option in plugins

    Did it really say “cheatin, uh?”

    @rogercoathup

    Participant

    If you let us know which thing / part of your site it is you want to change , someone might be able to give you a better idea which file to look in.

    In reply to: BuddyPress Spam

    @rogercoathup

    Participant

    @tedmann – have a search on your install for the bbPress folder and remove the register.php file. I guess it doesn’t have to be activated for the file still to be there and therefore usable by the spammers.

    It worked like a treat for myself and @footybible

    @rogercoathup

    Participant

    @jimhellas – yes, I find myself using “find in files” a lot in my editor :-)

    Finding time to write sections on the API in the documentation is step 2!

    @rogercoathup

    Participant

    @boonebgorges is @kebdarge meaning there isn’t one for this site?

    In reply to: More Core Committers?

    @rogercoathup

    Participant

    @djpaul – I saw one closed this week, that had been open just a day or so. I think you closed it. The guy was referred to another old thread, which didn’t reach a conclusion on how to solve the problem.

    I’ve also seen a user, albeit an irritating user, blocked from using the site for the ‘crime’ of arguing with a core developer. That really isn’t good practice. The user was being abusive, but not overly so; the core developer arguing with him was being equally petty though.

    Amend: apology, @djpaul it wasn’t closed by you, but it was closed and pointed to a thread that finished without a working answer

Viewing 25 replies - 751 through 775 (of 1,007 total)
Skip to toolbar