Forum Replies Created
@winstart I can’t replicate any issue with avatar or cover image uploads, can you ensure you have any third party plugins disabled and test again with a plain WP/BP install preferably running a Stock WP theme i.e 2017.
I’ve closed the trac ticket for the moment, that’s more suitable when there is a proven issue.
edited// although it still tests ok on my install – not really sure why – r-a-y is right the function should pass a default value, and has patched.
Can you give a literal example of a password that fails, are you suggesting “just a /” or single digit password?
@sourfew Thanks for pointing this out, the trunks readme.text file stable tag had been inadvertently reverted, but it’s corrected now.
We may need to be clearer on the steps to replicate this as…
With a twentyseventeen theme, BP trunk, stable bbpress no other plugins.
With an index page displaying the forums list shortcode & search input I can search for forum topics quite happily, returning results to the page showing bbp results.
However tested on single site not MS and use of directory MS rather than sub-domain might be a factor.
Editing either the templates or customizing the backend functions managing user name display are the only means to achieve this, I’m sorry you’ve had issue with applying php solutions as in the other post but practise makes perfect, or contract a developer to do the work you need for your site.
P.S No using CSS to hide anything is not the correct way forward! 🙂
Note: Please do not provide a .php fix. I edited the php a couple days ago to apply a fix (unrelated to this one) and it crashed my entire site. I will not be editing the php.
I suggest then that you consider contracting a developer to do this for you or contact memberpress to provide a solution.
We are a volunteer help forum for buddypress, the best we can really do is provide code that might help you but doing that while bearing in mind offering code is more than should be expected on these sorts of forums.
I can do that. However, I haven’t found any documentation to that effect, and it seems to be much more complicated than the template hierarchy documentation implies:
Hmm I was 99.999% sure I had or we (r-a-y & I wrote the two main codex pages for template hierarchy) had explicitly mentioned this point about full templates but I checked the other day and failed to find it, so our apologies for that omission. I will try & rectify that with a codex update on relevant pages when I have time.
@kalico when you create thse template files for index they must be full templates not partials i.e they must include the WP get_header(), get_footer() and any other markup structures representing your themes structure.
🙂 we might have spotted that – regardless you’ll need to approach the theme authors to update their theme or find a new theme.
@paripari it’s the weekend so help is likely to be a little slower.
Based on what you show it’s going to be quite hard to suggest what’s wrong apart from the obvious & from a jpg without any other detail of the events surrounding the problem almost impossible.
I can just about see that your using a custom theme ( I have quite good eyesight but that text is really small!) and that you have the issue referenced as occurring from the sidebar.php of the theme, I’m guessing a custom bp loop or widget. You’ll need initially to approach the theme authors and ask them if they can help out, if not then re-post here but supply a little detail about your setup and the sidebar file contents.
Helps to know what theme you’re using, we haven’t done anything in particular to styles, majority of style work was for companion stylesheet 2017 theme.
A link to the live site would let someone test with tools to see where the issue lies.
We load the styles in the BP functions file automatically when we detect that the 2017 theme is in use. By and large these companion styles are not necessarily stand-alone styles they are built to work in conjunction with the WP theme styles so how they would work with a custom theme is impossible to say as we have no knowledge of the themes parent styles or markup.
If you wanted to try you would need to do something like enqueue the stylesheet in a child theme of your custom theme in the functions.php file or ask the themes authors how you might use the stylesheet with their theme.
You need to define ‘responsive’ in this context; what are you seeing as the issue?
Running BP under twenty seventeen I see no particular issues for profile edit screens, but that is a cursory check, one theme, one browser.
This is an announcement thread, please post any support issues in the main forums.
We’ll consider a possible solution or ‘hack’ 🙁 to avoid the issue.
Check use cover image option is checked in the buddypress options screen, if it is you should see the tab to add or change cover image on the manage screen in your group.
This isn’t really a Trac ticket subject, and is best handled in a forum setting really, I did pass comment though on Trac.
On members loop last active simply states that when user last active the meta display is for last member status update not general site activity for a user id.
This being looked into on:
There was/is a plugin called something like ‘Anouncement Groups’ that was as name suggested informational only , maybe not quite what is asked for as it joined all site members automatically but didn’t allow direct commenting / interaction but was read and notify only iirc
and if you need a code example of how you might do this look at danbp’s reply here:
bp_displayed_user_id();will display the user id on BP screens/loops – but yes user ID’s are WP user ID’s
The codex though does list basic template tags functions so always check through that first to see if what you need is available.
@venutius I’ve just updated the repo files, updating the example enqueueing functions as they needed improvement( although I consider that snippet as being a temp provision) and also updated the styles to add min-height and spacing improvements, not sure if that helps your situation but you can further modify those style if needed (just edit the .css version)