Search Results for 'wordpress'
-
AuthorSearch Results
-
October 20, 2011 at 6:04 am #122815
In reply to: WordPress Failure Notice
@mercime
ParticipantBasic troubleshooting for “WordPress Failure Notice ” – https://wordpress.org/support/topic/wordpress-failure-notice-3#post-1981247
October 20, 2011 at 12:10 am #122202Boone Gorges
KeymasterYes, it’s a change: https://buddypress.trac.wordpress.org/ticket/3378#comment:2
The plugin you’re using is using for search is using core functions to render the dropdowns. That’s great, of course. But, in all the ways that the dropdowns are used in BP core, it does *not* make sense to have a null option for required dropdowns. So, while it’s inconvenient and I wish it had been raised at an earlier point, I think it’s incumbent on the plugin to create the fields in the way necessary for the plugin’s functionality to work right.
Alternatively, I would be happy to see a patch for BP that allows bp_get_the_profile_field_options() to take an argument along the lines of show_null_value_for_required (maybe not that wordy, but you get the idea). That way, we could default to false (1.5 behavior) but allow the 1.2.x behavior optionally, at https://buddypress.trac.wordpress.org/browser/trunk/bp-xprofile/bp-xprofile-template.php?annotate=blame&rev=5230#L431. It would be an easy patch to write; I encourage you to do it yourself, or at least to open a ticket for it.
October 19, 2011 at 9:38 pm #122012derusion
MemberSo, I think I’m figuring things out here.
It appears if a NON-ADMIN creates a group, even though “enable forums” is checked, the forums are NOT enabled until a wordpress administrator unchecks the box, saves, checks the box, saves.
How can I make it so that all users can enable forums without making them admins?
October 19, 2011 at 5:25 pm #122828Keymaster@valuser Yes, that’s it. I’ve opened a ticket https://buddypress.trac.wordpress.org/ticket/3697
October 19, 2011 at 12:00 pm #123278In reply to: Issues with BuddyPress 1.5.1 and some historic ones.
Keymaster> rant/opinion
Yeah. You could have just asked “Why can’t I delete the ‘name’ field?” and been done with it. There is an argument for why the field is required, which has to do with the fact that BP uses display names all over the site to identify users, but the ad hominem nature of your rant/opinion makes it less pleasant to offer up the explanation.
> Why release 1.5 and not make it compatible with bb 2.0?
The 1.5 release had been held up for too long already. bbPress 2.0 integration is not trivial.
> And again, when setting up the forums why the whole endless loop of “install bbpress but it’s already installed” it’s rather confusing.
Not sure I understand the question. Once you have set up bbPress, you don’t have to install it again. You have an option to reinstall it, but only if something has gone wrong.
> Why does it keep asking for a valid “activation key” even if people click on the validation key received by the system?
This usually means that the user has already activated his account. Use a plugin like https://wordpress.org/extend/plugins/unconfirmed/ to do some more research.
October 19, 2011 at 11:52 am #123276In reply to: How to grab xprofile data?
Damian
ParticipantHi Guys im trying to do the same on a custom wordpress page but it seems that
if ( bp_has_profile() ) always returns false and i dont know why.
I even tried to put this on my custom page.I need to load any file or globalize a variable?
I just need to make this work inside a custom page within wordpress.
Thanks for all the helpOctober 19, 2011 at 7:31 am #122939CJ Kruger
ParticipantHere’s the plugin, im open to suggestions and improvements.
`Adds two additional/optional fields to your BuddyPress groups – let groups link to an external website and extra field you may define.`
Its the initial release, still have to clean up a few things but it works
October 19, 2011 at 7:10 am #122937In reply to: Buddy Press Back End Lost to Fatal Error
Paul Wong-Gibbs
KeymasterMercime means inside the WordPress admin area (/wp-admin)
October 19, 2011 at 6:57 am #123266In reply to: https for user registration
KeymasterThere is no need to re-post this. I saw a thread with the same message the the other day, and if I wasn’t on my phone, I’d find it and close this one.
I am guessing that there would probably need to be a bunch of changes in BuddyPress core to do this, so you probably couldn’t do it with just a plugin. If you end up changing BuddyPress, consider contributing your changes as an enhancement request on http://BuddyPress.trac.WordPress.org
October 19, 2011 at 6:50 am #123264In reply to: Child User Accounts
KeymasterWordPress can’t handle “linked” user accounts like this. Multisite sort of lets you do this, but you’ll end up with a lot of seperate sites.
Creating a group when a user is registered is much more simple, however. You could look at how the Welcome Pack plugin works and use it as a starting point for a custom plugin in your site.October 19, 2011 at 2:15 am #123269In reply to: Forums with Buddypress install
thetbasket
MemberI couldn’t see how to edit my post, but here is the version information:
Wordpress 3.2.1 Clean install on the root directory (CentOS – Host: Webhostingbuzz)
Buddypress: 1.5.1
bbpress: 2.0 (installed through the buddypress installtion process)
Artisteer theme
Have not messed with core files.I can go the the bbpress forums via the usual forum lint: http://www.mydomain.com/forums/, but I had articulated in the buddypress setup that discussion forums were to go to http://www.mydomain.com/families, and even though I have created a “families” page, the link does not appear on the menubar, and when I attempt to navigate to that page it is not merely blank, but I get a 404 not found, and in the addressbar there is just the domain: “mydomain.com”.
Best,
JamesOctober 18, 2011 at 11:25 pm #122023KeymasterRe (2): The “bump” is by design. See https://buddypress.trac.wordpress.org/ticket/2546 Can’t reproduce the ‘caption’ issue.
New blog posts and comments are working fine for me.
October 18, 2011 at 7:48 pm #123185In reply to: Buddy Press Back End Lost to Fatal Error
r-a-y
KeymasterTo restore your WP admin dashboard, login to your WordPress install via FTP or cPanel and rename the “buddypress-classifieds” directory to something else like djoep recommended.
—
BuddyPress Classifieds is an older plugin that hasn’t been updated for BP 1.5.
For BP 1.5 info, you should read these articles:
https://codex.buddypress.org/releases/1-5-plugin-compatibility/
https://codex.buddypress.org/releases/1-5-theme-compatibility/
https://codex.buddypress.org/releases/1-5-developer-and-designer-information/October 18, 2011 at 7:44 pm #123184In reply to: WordPress Plugin Not being applied
KeymasterDepends on what you mean by “single” in BuddyPress.
If you mean a user’s profile page, that would be `bp_is_user()`; for a group page, it would be `bp_is_group()`.
October 18, 2011 at 7:37 pm #123181KeymasterThis is a reported bug:
https://buddypress.trac.wordpress.org/ticket/3687Keep your eye on that ticket for updates.
October 18, 2011 at 4:02 pm #121775In reply to: WordPress Plugin Not being applied
djoep
MemberWhich begs the question… when if ever is is_single() true in bp 1.5 and what should be used instead to test for pages where text areas might appear?
October 18, 2011 at 3:45 pm #121773In reply to: WordPress Plugin Not being applied
Memberwhoops! found it, fixed it, behavior was due to plugin testing for “is_single()” which apparently was false for all of the buddypress pages.
joeOctober 18, 2011 at 2:34 pm #121815MemberI posted something that might be helpful over on the bbpress forum. WARNING, it is NOT simple! It is not without possibility of hazard. I would strongly recommend that you do all of your trial and error in a development environment, not on your live site!!!
Why have both group forums and site wide? I think it makes a lot of sense in some cases. For example, a site wide forum can have a completely hierarchical structure without regard for any group. At the same time, a group can carry on a conversation that would be of no interest to the larger population. So a knitting group could have hundreds of posts about yarn, needles, etc, that are not visible on the site’s forum while the site’s forum could have announcements, talk about the local community, etc that are of general interest but not associated with any particular group.
BTW, it appears (to me) that the “site wide” option installs the bbPress 2.0 plugin which uses wordpress custom post types, custom taxonomies, etc, while the group forums appear to use a version of bbPress 1.x that uses separate db tables. I could be mistaken in this.
joeOctober 18, 2011 at 12:53 pm #122877In reply to: Buddy Press Back End Lost to Fatal Error
MemberIf you change the name of the plugin folder, through cpanel or by other means, wordpress will automatically deactivate the plugin and you should be able to get back to wordpress. I had the same thing happen with a theme.
joeOctober 18, 2011 at 1:16 am #122065ParticipantPlease post your query at https://wordpress.org/tags/buddypress-ajax-chat?forum_id=10 which plugin dev usually checks out.
October 18, 2011 at 12:03 am #123172In reply to: Change text color
ParticipantBuddyPress is version 1.5.1 at this time and I see BuddyPress is not activated in your site. You most probably mean bbPress 2.0. Having said that, I do not see bbPress activated in your site as well.
WP.org forums- https://wordpress.org/support/
October 17, 2011 at 11:14 pm #122173skartar
MemberDone, thanks Paul, here’s the ticket: https://buddypress.trac.wordpress.org/ticket/3692
for now, can I edit the register.php in my child theme for a workaround? I’m thinking if I can make the text box localised I can edit the field label instead in a .mo file? Any guidance on how I could edit the code to make that happen please?
October 17, 2011 at 10:18 pm #123170mmln
MemberIts is multi site (WPMU) installation but I only have one site. here is my .htaccess file
# BEGIN WordPress
# BEGIN ANTISPAMBLOG REGISTRATION
RewriteCond %{REQUEST_METHOD} POST
RewriteCond %{REQUEST_URI} .register*
RewriteCond %{HTTP_REFERER} !.*http://mywebsite.com/bp/.* [OR]
RewriteCond %{HTTP_USER_AGENT} ^$
RewriteRule (.*) http://die-spammers.com/ [R=301,L]
# END ANTISPAMBLOG REGISTRATION# protect wpconfig.php
order allow,deny
deny from all#uploaded files
RewriteRule ^(.*/)?files/$ index.php [L]
RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*
RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L]# add a trailing slash to /wp-admin
RewriteCond %{REQUEST_URI} ^.*/wp-admin$
RewriteRule ^(.+)$ $1/ [R=301,L]RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule . – [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*.php)$ $2 [L]
RewriteRule . index.php [L]SecFilterEngine Off
SecFilterScanPOST Off# END WordPress
October 17, 2011 at 10:05 pm #123168KeymasterI see that you can’t. We should fix this. Can you create an enhancement request ticket on http://buddypress.trac.WordPress.org/, and we’ll get it into 1.6. Thanks.
October 17, 2011 at 8:25 pm #122060In reply to: when setting ” register ” page as the homepage
Keymasterhttps://core.trac.wordpress.org/ticket/18971 (with a patch)
-
AuthorSearch Results
