Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'wordpress'

Viewing 25 results - 11,326 through 11,350 (of 32,679 total)
  • Author
    Search Results
  • #181814
    Anonymous User
    Inactive

    hello @megainfo,

    You’re right. I think the problem you described in #5569 is a side effect of #5553.

    Anonymous User
    Inactive

    Thanks for your feedback, can you confirm this patch is solving your issue ?

    #181811
    bp-help
    Participant
    #181792
    meg@info
    Participant

    Hi @imath, @boonebgorges,

    I think the problem is caused by bp_update_to_2_0().
    https://buddypress.trac.wordpress.org/ticket/5569

    #181791
    @mercime
    Participant

    @eddieb12180 Did you even try adding the styles I provided above? Of course you can make some changes in the registration page’s markup. Copy over the register.php file from https://buddypress.trac.wordpress.org/browser/tags/2.0/bp-templates/bp-legacy/buddypress/members/register.php into yourchildthemefolder/buddypress/members/ folder and make the changes you want to html tags available there.

    #181765

    In reply to: 2.1 top features

    SK
    Participant

    Ok, looks like the iron’s hot https://buddypress.trac.wordpress.org/query?group=status&milestone=2.1 , so while the core team is enjoying a pizza and relishing a job well done (2.0), sneak in your wishlist…this appears to be a short cycle…

    #181760
    Livsy
    Participant

    I am using a non multisite WordPress.

    #181758
    Anonymous User
    Inactive

    @livsy

    I registered a new user by myself a minute ago. And I saw in his profile – he has no role for my site

    This shouldn’t happen.

    What is your config ? The upgrade problem concerns a non multisite WordPress. Is it your config ?

    “Viewing the sql tables” means that you’ll need to export it using PhpMyAdmin for instance and send it to me.

    By the way, i’ve tested BP Disable Activation Reloaded and it’s not the cause of the problem. It’s “someone” else.

    #181756
    Anonymous User
    Inactive

    @livsy if you try to register a new account, this account should have the role you defined in WordPress settings.

    I’m very curious about what happened during upgrade. If it were possible i’d really like to view the users, usermeta and signups tables!

    Can you see the users with no role in your users list ?
    If so, you can batch create roles for these users using the “change role to” select box on top of the users list.

    i’m going to test BP Disable Activation Reloaded to see if the problem was linked to this plugin.

    #181754
    Livsy
    Participant

    Hi! I am using BP Disable Activation Reloaded plugin. I deleted it (and all other plugins, except BP). But problem with user role still exists.
    I set author role for new members in wordpress settings. It was a long time ago, before update to 2.0

    #181748
    Anonymous User
    Inactive

    @livsy

    Just tested in WP 3.9/ BuddyPress 2.0, the role set for a new user is the one that is defined in the WordPress setting (wp-admin/options-general) > New User Default Role dropdown field.

    #181744
    Anonymous User
    Inactive

    hi @livsy

    How were you doing before ? Once a user registered, you were changing the role before he activated his account ?

    Or are you choosing a role different than Subscriber in the WordPress setting (wp-admin/options-general) > New User Default Role dropdown field ?

    About the upgrade difficulties, were you using a plugin that was dealing with registrations, and if yes which one ?

    Thanks for your feedback.

    #181731
    Livsy
    Participant

    Hi! I have the same problem with admin rights. @boonebgorges ‘s fix helped me a lot. But I have another problem. This fix can’t help users which get a subscriber’s role after registration. I set an author role for all new members of my site in wordpress settings. But it had no effect.

    #181728
    #181722
    careb
    Participant

    Yes, using the filter to disable mentions solves the problem above, but then mentions are disable. It’s not a desirable outcome.

    Other plugins – Network:
    Advanced Access Manager
    Akismet
    BackWPup
    Blue Login Style
    BP Sticky Groups
    BuddyPress
    BuddyPress Docs
    Enable Media Replace
    Enhanced Media Library
    Hashtag
    Multisite Global Search
    Multisite User Management
    Network Shared Media
    TinyMCE Advanced
    User Groups
    User Switching
    WordPress MU Sitewide Tags Pages
    WP-CMS Post Control
    WP-Mail-SMTP
    WP-Memory-Usage
    WP Better Emails

    Other plugins – Local:
    Broken Link Checker
    Disable Sitewide Tags (Single Blog only)
    Eyes Only: User Access Shortcode
    Google Doc Embedder
    HTML Editor Reloaded
    Subscribe2
    Unified Media Folder
    WP-Polls
    WP Native Dashboard

    #181714
    @mercime
    Participant

    @ksample Thanks for posting back about the plugin conflict. If you like the plugin might I suggest informing the developer about the issue so he can update it https://wordpress.org/support/plugin/buddypress-like

    Marking this as resolved.

    #181713
    r-a-y
    Keymaster

    I just tried mentioning 11 users on P2 and couldn’t duplicate your issue.

    It appears this issue only occurs when you view the post on the frontend since you state that the correct content shows up when you edit the post.

    Try the recommendation I listed in the ticket you opened:
    https://buddypress.trac.wordpress.org/ticket/5565#comment:1

    If that doesn’t work, what other plugins are you using?

    #181701
    r-a-y
    Keymaster

    Hi Djsix,

    The problem occurs because a check is added to see if a user is logged in before the activity comments block is displayed.

    I’ve created a new ticket about this here:
    https://buddypress.trac.wordpress.org/ticket/5567

    In the meantime, you can override the specific template by copying wp-content/plugins/buddypress/bp-templates/bp-legacy/buddypress/activity/entry.php to your theme.

    The file should reside here – wp-content/themes/YOUR-THEME/buddypress/activity/entry.php. Then, make the file change listed in the patch linked in the ticket above.

    #181697
    ksample
    Participant

    Since the WordPress 3.9 and Buddypress 2,0, I have to disable the Buddypress plugin to upload media, place links on pages, access themes, and place/modify widgets. Everything works on the Buddypress stream including uploading pictures but the rest of the blog is affected when the plugin is activated. I changed themes (after disabling Buddypress) and same problems. Also portfolio slideshow does not work when Buddypress is activated. Any ideas?

    careb
    Participant

    Wordpress 3.8.1 (multisite with subdirectories); buddypress 2.0; P2 1.5.3;

    http://teambox.dongguk.ac.kr/debug/

    When using more than 10 @username in a post, BuddyPress freaks out and repeats one of the mentions and adds incremental numbers after the @username, like:

    @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia
    @steve @jake0 @jake1 @jake2 @jake3 @jake4

    If I try to edit the post, the correct @usernames are there without the numbers. Everything looks normal. When I publish, the numbers reappear. Notification emails do not go out to users after the names begin repeating or the numbers get added.

    How do I know it’s BuddyPress 2.0?

    I’ve been using BuddyPress 1.9.2 for almost a month without this issue. To be sure though I used the filter to disable mentions the problem went away completely.

    How do I know it’s P2?

    When I use another theme, the problem goes away.

    To really see how bad it is, I made a test post with more than 25 @usernames:

    @amber @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber0 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber1 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber2 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber3 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber5 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber6 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber7 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber8 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber9 @barney0 @barney2 @barney3 @barney4 @barney5 @barney6 @barney7 @barney8 @barney9 @beth0 @beth1 @barney0 @beth2 @beth3 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber3 @amber @beth4 @beth5

    what what typed:
    @amber @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber @johnwendel @calebx

    #181675
    jillsessa
    Participant

    I’ve updated to BP2.0 and now when I am trying to add a new user and am getting this error:
    WordPress database error: [Table ‘lml_members04092014.wp_bp_groups_members’ doesn’t exist]
    DELETE FROM wp_bp_groups_members WHERE group_id = 3 AND user_id = ’93’ LIMIT 1

    I have no idea how to solve this, any help is appreciated, thanks!

    #181663
    Boone Gorges
    Keymaster

    @blankpoint Sorry for the troubles. The upgrade routine necessary for BP 2.0 is fairly large.

    I’ll work in the upcoming weeks on improving it, but in the meantime, a few things to try:

    1. Your memory limit issue is due to the fact that WP will not allow you to exceed 256M per pageload without explicitly saying you want to (regardless of your php.ini settings). You can put the following into wp-config.php to override for the admin only:

    define( 'WP_MAX_MEMORY_LIMIT', '1024M' );

    2. Just to get up and running, you might also consider running the heavy migration manually: from the mysql command line.

    INSERT INTO wp_bp_activity (<code>user_id</code>, <code>component</code>, <code>type</code>, <code>action</code>, <code>content</code>, <code>primary_link</code>, <code>item_id</code>, <code></code>
    date_reco
                      SELECT user_id, 'members' as component, 'last_activity' as type, '' as action, '' as content, '' as
                      FROM wp_usermeta
                      WHERE
                        meta_key = 'last_activity'
                        AND
                        user_id NOT IN (
                          SELECT user_id
                          FROM wp_bp_activity
                          WHERE component = 'members' AND type = 'last_activity'
                        )
            );
    

    You could split this up with a LIMIT clause in case you need to run it a few times.

    The other problematic bit of the upgrade routine has to do with migrating your old signups to the new signups schema. (I’m assuming you have open registration + non-multisite.) That migration is not necessarily mission-critical, so you could skip it altogether. So, in other words, once you’ve run the ‘last_activity’ migration, you could comment out line 351 and lines 355-395 here: https://buddypress.trac.wordpress.org/browser/tags/2.0/bp-core/bp-core-update.php#L351 and then reload your admin to mark the migration as complete.

    Again, sorry about the difficulties. You’re running a very large BP site, and the migration tools were not up to the job.

    Then, you could comment out this line: https://buddypress.trac.wordpress.org/browser/tags/2.0/bp-core/bp-core-update.php#L351

    #181656
    danbp
    Participant

    hi @tsabar

    code is located in buddypress/bp-core/bp-core-widgets.php

    BuddyPress Login widget

    Maybe read here also ?

    #181655
    sharmavishal
    Participant
Viewing 25 results - 11,326 through 11,350 (of 32,679 total)
Skip to toolbar