Forum Replies Created
-
In reply to: [Resolved] CSS Customization
@rickdickinson that first codex page clearly states it’s in regard of the older bp-default setup, this doesn’t mean don’t follow it but you would only do so if you were already working with that themeing approach.
the second link is the one to follow for new install/themes, yes you do need to create a child theme IF you’re working with an existing of the peg theme, if you’re writing your own then you simply overload your files in either /buddypress/css/ or /community/css/ (either labelling works and both folder structures are applicable whether a main theme or child one)
If you overloaded the entire buddypress.css file and your changes didn’t work it’s just possible you hit the 2.1 issue of naming convention, which will be fixed in 2.1.1, so try renaming your file to buddypress.min.css.
In reply to: Functions.php and buddypress-functions.phpYes you can!
A better question would have been to explain what you are ‘hacking’ and why and how best to achieve this.
buddypress-functions.php is not necessarily a straightforward functions file, if you overload it you then have to be responsible for ensuring any core changes are copied over, or perhaps you just need to extend the theme compat class rather than hack buddypress-functions with your own class?
Good point – doesn’t exist, MS is a law unto it’s self.
You may need to write a function hooked to the registration process that changes the user role then.
Using FTP or your hosting panel access start renaming any BP plugins you have running until you regain access to your install, renaming effectively deactivates the plugin, this will also tell you what plugin is causing the issue.
>But a problem remains: How can I make ‘Subscriber’ not being the standard user role anymore?
That is a wp setting – settings>general ‘New User Default Role’ You should be able to select any new role created from the dropdown.
In reply to: Am I on a BP page vs plain WP page?You can test for various screens such as bp_is_user() for user account screens, or bp components or directories, groups etc, the Codex is your friend initially for these sorts of things then we can help further in refining that if need be.
In reply to: How to change required fields on registration formRead also https://codex.buddypress.org/getting-started/customizing/buddypress-in-your-language/
Try explaining what exactly your are trying to do here as the title can be read a few ways.
In reply to: Password Strength Meter is not workingYou need to have a javascript file enqueued for this to work so depending on how custom community theme approaches things that may not have been either updated in buddypress-functions.php if that is overloaded or simply not exist if CC theme uses BP templates in the older bp-default manner, might be worth checking if CC is planning an update?
In reply to: Okay – £10 to whoever can think of a solution@chester99 the solution to this distinct & particular issue for the OP is mentioned.
Please start a new thread detailing your particular circumstances, setup, issues etc.
closing this thread as it was resolved.
In reply to: Can’t create Buddypress child themeAs the error message says – have you installed the parent theme?
Your import path looks wrong for that stylesheet.
More importantly are you sure you want to use the older bp-default theme or did you just land on that particular guide?
If you want the bp-default theme to show up you may need to add this line to bp-custom.php or functions.php:
add_filter( 'bp_do_register_theme_directory', '__return_true' );I would consider whether you do really want to base a theme off bp-default, it will become an unsupported theme, well is already really but just still bundled in the core package.
In reply to: Cannot able to see the funtioning of home pageFirst thing you should do, if you haven’t already, is read through the getting started section of the codex, ensure you are as familiar with BP’s components and pages as possible.
Secondly you’ll need to know how your theme handles it’s home page as nothing technically should have changed, so you may not have a BP compatible theme? Helping with third party themes is limited though as we have no access to them but it won’t hurt to list your sites details here such as theme in use.
not really help but nudges in the right direction 🙂
wpautop($data)was all you needed.However there something niggling away about these bp functions and point at which the xprofile functions gets passed through the WP ‘wpautop’, not sure that the get function shouldn’t be parsing breaks to paragraph tags regardless but hey ho.
In reply to: Reinstall BuddyPress without 404 errors?@whiteeagle1985
Actually it’s more yourself not understanding @bphelp post, I read the response to explain about backing up prior to installing a plugin not to mean that you were ‘installing’ but general advise that would ensure a safe restore point, regardless of whether it was the right advice please be clear that when people do attempt to offer help & advice it’s common practise to thank them not admonish them 😉As your OP stands I too don’t really understand why you are ‘reinstalling’ BP, do you actually mean reinstalling or reactivating?
Your comments about 404’s which is all we can read as being your issue is in reference to an event you experienced having reinstalled your whole WP installation! Why would you do that?
The problem with your post at the moment is that you need to clarify why you are doing these things what is the actual root issue not the issue when you proceed with a process that seems unnecessary.
However do read the links above regarding permalinks as those are vital to the correct operation of BP as are the BP empty placeholder pages for components.
🙂 Sounds like you tried to tackle a heap of things far more complex than the actual solution you need!
> What I think I need to do is edit echo $data; to somehow include wpautop but I am not finding a way to do that…
er…
Henrywrights link?
You did read that page didn’t you? 🙂
Sorry not being mean 🙂 but your solution is there to be read, if you really don’t get it or for whatever reason once tried it fails to produce results (do, though, ensure data has double line breaks) post back with code tried and we’ll look further.
Then you will need to extend the functionality. There are filters on these types of functions and a recent ticket where I pushed through additional attributes to be allowed and discussed adding the style attribute for adding css properties inline, that was agreed a step too far, the status updates coyuld start to look ghastly and issues might arise in activity stream entries if not careful. At the end of the day the status update functions is not intended as a post it’s more a throwaway simple comment
If you have specific requirements for the status updates fair enough but you’ll need to write that extended functionality or get a developer to.
In reply to: Buddypress pluggin ruined site@mockiboo
>But it is nice to see how you divert the topic away from the issue which is that your plug in doesn’t plug in well with wordpress themesNo I / We are not diverting the issue, I asked you to provide some level of detail I also made the comment that BP is not from experience born over a few years a destroyer of sites, if we could provide a clue as to what might have happened we would / will despite the fair certainty that this is not something that is inherently BP’s fault.
BP is coded to exacting strict WP standards the core developers are extremely experienced in working with WP code, BP fits to any theme that is also coded to the same API standards.
More importantly have you managed to restore your sites functionality? It is highly unlikely that any DB Tables have been deleted so your data is there somewhere or should be, failing that restore from a prior to the change DB backup.
In reply to: Buddypress pluggin ruined siteNever heard of BP destroying a site before. BP has evolved through many releases, tried and tested in many situations and setups and performs without causing such issues under normal WP installs.
If you want some help in determining what may have happened you will have to provide some actual detail and data.
Also a little word of advise if you are running a business, and ergo a production server, you never ever test ‘stuff’ on it you do that on your local development setup or staging server environment which you do have don’t you?
In the intervening 10 days what have you actually tried though?
Stating I’ve tried a few executions isn’t very helpful as it tells us nothing about what exactly you have tried, or shows us code attempts that may have errors. Without knowing what you are trying it’s not possible to give any sort of useful help, as things stand given the code you showed originally and henrywrights response there’s the answer ( wpautop() )and it’s relatively simple to apply.
Instead of us speculating at what’s wrong and throwing up a multitude of possible code scenarios that might work which is wasteful of time and energy, provide some useful data to work from please, especially if you’re a developer.
In reply to: How to decide who to report an issue to?Fixed your links for you, they do need text string to display.
Not really clear on why you thing this may be a BP issue or that others might say that. Thus far there is no real info to debug on.
You need to start some more basic testing such as disabling all plugins, changing themes, deactivating BP, enabling php error reporting etc; start to build up something to work from narrow the issue down, as things stand there is little other help that can be offered and nothing to suggest this is something for this forum to cover really. Do report back though when you have a little more info.
In reply to: [Resolved] Remove member last activeCopy the template to your theme and then simply remove the markup and function call.
If the core app need to maintain a backwards compatible path on things then it needs to and we are talking here about core files, the process of slowly and eventually removing such baggage is a job the core has to tackle over time, regardless this is mainly in terms of various functions that become deprecated in favour of new functions or classes but are retained so that plugins or custom templates making use of those functions don’t suddenly break.
As we are talking about core files, again, it must be pointed out that you cannot modify those if you wish to be able to upgrade cleanly and easily to new versions, of course you could maintain your own set of core files and then do manual updates when new versions are released but I wouldn’t like to try that.
This leaner version of BP you allude to is , I think, something of a pipe dream, you’re not going to get a suddenly better performing BP, faster, smarter, stronger.
In reply to: wp_enqueue_script issue on activity page@henrywright yep just blame me if asked 🙂
In reply to: wp_enqueue_script issue on activity page@albert101 try henrywrights code but you may want to change:
add_action( 'wp_enqueue_scripts', 'my_dequeue_script', 100 );to:
add_action( 'wp_print_scripts', 'my_dequeue_script', 100 );The latter should work.
In reply to: wp_enqueue_script issue on activity page@@shanebp @henrywright ah ok if that is the case then it perhaps ought to be mentioned, did wonder about the hook priority but seen other examples of ? de-registering in that manner but perhaps that would run on that hook – Sorry Henry might have got that wrong then.
In reply to: wp_enqueue_script issue on activity pageThanks but I’ve done my share of updating docs today 🙂
