BuddyPress.org

I might actually be able to help out with this one. I was getting the same errors. Apparently this is because your wp-config.php is reading the default memory allocation of about 8meg that your host usually sets up by default. Once I edit my wp-config file to allocate 64 or 96 meg with the below instructions it popped back up fine.

https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

Hi Dr Mikel Brown
This sounds like an htaccess issue. Please see this post.

https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/404-on-every-link/

To summarise, you should have a file in the root directory of your folder that is called .htaccess (there is a fullstop at the beginning of the file name). The contents of the .htaccess file should contain the following:
# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

Hope this helps
Rob G

> ALL Full Names were suddenly replaced by the username field data, seemingly deleting full name data

What’s your evidence for that? It would be *very* surprising if it were true. Probably the correct diagnosis is that some logic was causing the username to be displayed instead of the display name.

Do you have the Extended Profiles component enabled?

I’m not sure that my problem is exactly the same as Juan’s, but obviously it’s very similar.

I upgraded an existing Buddypress 1.2.10 installation to 1.5. Upon doing so, ALL Full Names were suddenly replaced by the username field data, seemingly deleting full name data. Rather than deal with this problem, and a variety of broken plugins, I decided to disable all plugins and delete 1.5 and reinstall the previous version to see if I could avoid a total recovery from a back up.

After reinstalling 1.2.10, Full Names were only partially restored. I’m not sure exactly why some Full Names were not restored. Here is an example of the problem – http://www.arhistoryhub.com/members/knash/. Pretty bizarre. At no point did I receive an error or anything indication the 1.5 upgrade wizard did not complete successfully.

I’ll probably work on upgrading to 1.5 again over the next week or two, I’ll come back to this thread and update whether this same problem reoccurs.

I can’t reproduce it on my installations. The changeset that you point to as having fixed the issue has not been rolled back, so there’s no obvious reason why it should have stopped working.

Just to be clear:
– I changed the name of profile field #1 to something other than ‘Name’
– I went to Edit Profile on the front end, made a change to the field, and saved
– Everything saved correctly. I got no errors, and the name is properly saved.

https://codex.buddypress.org/troubleshooting/navigation-links-return-404-errors/

You need to change every file that is listed on the step 3 page.

Can somebody sum up the problem in a sentence or two? I’m confused by this thread.

I don’t know how to make this work on Windows. It’s not really a BuddyPress problem – I’m guessing that a normal WP installation won’t work either, if you turn on pretty permalinks. Have a look at https://codex.wordpress.org/Using_Permalinks#Permalinks_without_mod_rewrite

The Header and footer and sidebar and content area are usually in every WordPress template. You need to edit the BuddyPress files added to your theme to match the structure of your theme.

Sometimes the content area is called container or wrapper or something else. You need to match the containing div around the content to the BP files.

In step 3 it shows you a diagram of div markup. If you have never edited code you may need to hire someone to do this. On complex themes it can be a challenge.

== I assume that this means that I am having a plugin problem? ==
Yes it does.

== now what do i need to do? ==
– Since you’ve been able to access your wp-admin, you can now rename wp-content/plugins-x to wp-content/plugins
– Activate BuddyPress
– Use bp-default theme in the meantime
– Do not activate maintenance mode plugin yet – it sometimes messes up with BP plugins
– Activate BP plugins one by one and see which one is messing up with your login. There’s a list of plugins compatible with BP 1.5 – https://codex.buddypress.org/releases/1-5-plugin-compatibility/

@enderpal444 you mentioned there is a plugin for this I assume to get it in a users profile?

And, for what it’s worth, the idea of a “component” is not one with clear demarcations. Both you and @modemlooper suggest some useful criteria:
– if your plugin creates new data objects, it’s probably a component
– if your plugin needs to have a top-level directory, it’s probably a component (and, in this case, a special kind of component called a “root” component.

In BP 1.5, the idea of a “component” has a little bit more technical fleshing-out due to the BP_Component base class. A quick look at that class and its more important methods (setup_globals(), setup_nav()) will give you sense of when it’s useful to think of a plugin as a component. But again, there are no hard-and-fast rules.

In general, when in doubt, I would suggest using the BP_Component class. Sometimes your component won’t need some parts of the component infrastructure – sounds to me like your “up vote” plugin doesn’t need dedicated navigation items, for instance – but in that case, you can just leave those methods out. Using the BP_Component class just makes your life a bit easier by hooking you into the BP load order in the appropriate places.

Try the buddystream plugin

Hey echoman,

I just stumbled across your questions through Google and thought I’d offer you a little help. Do you see in your Fatal error where it says “is_site_admin()”? That’s where your problem is. You will need to open the bp-album-core.php file, scroll down to line 305 where it says “is_site_admin()”, and replace the word “site” with the word “super”.

is_super-admin()

Closing this topic.