-
Author
-
October 26, 2016 at 07:46 #141329
jwchameleoncorp
ParticipantHello,
After creating a Buddypress Group, I receive an error on the Group home page (see snapshot).
Suggestions what might be wrong?
Thanks!
Attachments:
You must be logged in to view attached files.October 26, 2016 at 12:48 #141381Laura
ModeratorHello, try to deactivate some plugins and check if it works 🙂
Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solutionLaura Solanes - Graphic Designer and Web Designer
Please be patient as I try to answer each topic as fast as i can.
If you like the theme or the support you've received please consider leaving us a review on Themeforest!
Always happy to help you 🙂
October 30, 2016 at 01:40 #142069jwchameleoncorp
ParticipantHi @laura
I deactivated and reactive all plugins. No change. I still get this error:
Warning: Creating default object from empty value in /home/swiftbus/public_html/5firemen.com/wp-content/plugins/buddypress/bp-groups/classes/class-bp-groups-member.php on line 1122
See attached snap shot.
Thanks for your help. 🙂
Attachments:
You must be logged in to view attached files.October 31, 2016 at 21:25 #142300Laura
ModeratorHello, do you have any custom code at the child theme?
Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solutionLaura Solanes - Graphic Designer and Web Designer
Please be patient as I try to answer each topic as fast as i can.
If you like the theme or the support you've received please consider leaving us a review on Themeforest!
Always happy to help you 🙂
October 31, 2016 at 22:35 #142316jwchameleoncorp
ParticipantNovember 2, 2016 at 01:34 #142476Laura
ModeratorHello, i’m going to assign this to Radu as i think he would know better than me 🙂
Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solutionLaura Solanes - Graphic Designer and Web Designer
Please be patient as I try to answer each topic as fast as i can.
If you like the theme or the support you've received please consider leaving us a review on Themeforest!
Always happy to help you 🙂
November 2, 2016 at 01:49 #142479jwchameleoncorp
ParticipantOkay, thanks @laura
Have a great day. 🙂
November 2, 2016 at 20:34 #142588Radu
ModeratorHi
Just I’ve created a test group and those notices/warnings not appears :
Let me know if you have figure out what going on
Cheers
R.Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solutionNovember 2, 2016 at 23:34 #142612jwchameleoncorp
ParticipantNovember 3, 2016 at 17:52 #142732Radu
ModeratorWhat have you done to can see the errors now ?
Do you have somehow the WP_DEBUG true ?
Anyways that is caused by BuddyPress core.
Try to set in wp-config.php
define( ‘WP_DEBUG’, false );
define( ‘WP_DEBUG_DISPLAY’, false );Let me know
Cheers
R.Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solutionNovember 3, 2016 at 19:10 #142749jwchameleoncorp
ParticipantHi @radu
I don’t do anything to see the errors. I simply login, go to Nav Menu > Communities > Groups > and select your Test Group from the Groups Display.
I looked at the wp-config file. Here’s what I originally had:
define(‘WP_DEBUG’, false);
define( ‘WP_MEMORY_LIMIT’, ‘128M’ );
define( ‘WP_AUTO_UPDATE_CORE’, false );So I added your line, define( ‘WP_DEBUG_DISPLAY’, false );
Now it looks like this in my wp-config file:
define(‘WP_DEBUG’, false);
define( ‘WP_DEBUG_DISPLAY’, false );
define( ‘WP_MEMORY_LIMIT’, ‘128M’ );
define( ‘WP_AUTO_UPDATE_CORE’, false );Is that correct?
Thanks!
November 3, 2016 at 20:10 #142766Radu
ModeratorYes it’s correct, but now i saw that there isn’t a theme bug it’s a BuddyPress issue
You can report the bug on the buddypress support forum : https://codex.buddypress.org/participate-and-contribute/reporting-bugs/
Cheers
R.Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solutionNovember 10, 2016 at 00:07 #143629manueldo
ParticipantHi @radu I have the same problem. Asked in buddypress forums for help and the moderator gave to me this “solution” but I can´t understand what I have to do.
Could you please help us with this issue?He said: Well, you now have to control your child theme and custom functions (if any).
Seems that changes made in BP 2.7, 2.7.1 and 2.7.2 won’t apply to your case.Read also here https://codex.buddypress.org/themes/updating-custom-themes/template-updates-2-7/
And if it doesn’t help, go to kleo support and ask there.
Thanks in advance!November 10, 2016 at 17:52 #143762Radu
ModeratorThis problem it’s caused by BuddyPress itself in the displayed photo it’s used default wp theme not kleo, try to update to bp 2.7.2.
You can try to activate the wp default theme to can test it to see how it looks
Cheers
R.Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solutionNovember 10, 2016 at 18:19 #143774jwchameleoncorp
ParticipantYeah, I already tried using the default WP 2016 theme, and I’m using Tha latest version of BP, but the problem still persists. It’s not a KLEO issue.
I also posted a ticket for help in BP support but did not receive any support. I posted the issue in other forums too, but still do not have a solution. The problem still persists.
Frankly, I don’t know what to do about it at this point, and I can’t launch my site until is resolved. Very frustrating.
November 10, 2016 at 19:03 #143792Radu
ModeratorHi,
You can turn off PHP notices until they fix this but this isn’t recommended, but if you really need to release your site … as you wish
Cheers
R.Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solutionNovember 10, 2016 at 20:54 #143797jwchameleoncorp
ParticipantHi @radu
I don’t know how to do that. If I did, why is it not recommended. What could go wrong?
Thanks my friend.
🙂
November 11, 2016 at 16:13 #143898Radu
ModeratorBecause one of your scripts fails no error/notice will be displayed until you enable back the error reporting, nothing else other than this.
http://stackoverflow.com/questions/2867057/how-do-i-turn-off-php-notices
You should use php.ini method and also to have wp debug false in wp config
Cheers
R.Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solutionNovember 15, 2016 at 00:18 #144216pauldyke
ParticipantI also have this error message since updating to BuddyPress Version 2.7.2
I’m running Sweetdate theme.
Thanks for raising the ticket @jwchameleoncorp on BP Forum.November 18, 2016 at 21:01 #144728jwchameleoncorp
ParticipantNovember 21, 2016 at 15:45 #144872Radu
ModeratorCheck my suggestion : https://archived.seventhqueen.com/forums/topic/buddypress-group-error/#post-143898
Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solutionNovember 21, 2016 at 15:49 #144876manueldo
ParticipantHere is the main discussion about this error, in the buddypress site, but I can´t follow 100% because I am not a technician, so I am waiting for the final solution.
https://buddypress.org/support/topic/group-header-file-problems/
November 21, 2016 at 17:38 #144893jwchameleoncorp
ParticipantHi @Radu
Yeah, I know can turn it off, but as you mentioned, it’s not advised. You would never find out if something else is wrong with your site.
And, it still doesn’t solve the underlying problem. Would rather get it fixed.
Dunno why it’s so difficult to find the issue.
I’ve contacted two people directly on the Buddypress team, who write and maintain the code for BP core. Still haven’t heard a thing.
Cheers.
November 22, 2016 at 19:53 #145031Radu
ModeratorYes,
You can try this add this line at the start of the PHP file immediately after http://php.net/manual/ro/function.error-reporting.php
Cheers
R.Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solutionNovember 22, 2016 at 21:02 #145057jwchameleoncorp
ParticipantNovember 23, 2016 at 17:37 #145113Radu
ModeratorNo problem
Cheers
R.Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solutionDecember 6, 2016 at 07:27 #146177jwchameleoncorp
ParticipantHello All!
Some interesting news with this. Per suggestions in other forums (i.e. Buddypress Support, etc.), they thought the issue might be related to my host’s caching, so I wrote Site Ground Support and asked them to check into the problem. Her reply is below:
“I was able to load the page in Mozilla and Safari with no resolving errors. However, once I opened it with Google Chrome, the error appear. I have cleared the application cache and deactivated plugins, however, to no avail. The issue is not server related it is an issue with the code”
After receiving her reply, I went and tested her findings for myself. Indeed, she was right. However, the investigation with different browsers must have caused a “break thru” with Chrome, because it no longer shows the error. This is true for multiple sites I manage that had the same issue.
Not sure why that solved the problem, but thought I’d let you guys know about it.
Thanks for taking the time to help.
Cheers.
December 6, 2016 at 11:59 #146188pauldyke
ParticipantThat’s awesome @jwchameleoncorp! Thanks for sharing. We too use Siteground. Turning off the Memcached setting in the SuperCacher setting and then turning it back seems to have resolved the issue for us.
December 6, 2016 at 12:04 #146189pauldyke
ParticipantSorry correction. Turning memcached back on does return the error.
December 6, 2016 at 14:24 #146197jwchameleoncorp
Participant@pauLuke did you try other browsers? That was the key for me.
May 15, 2017 at 09:45 #161398graphite
ParticipantHi @jwchameleoncorp
Thank you so much for the approach, it works perfectly for me as I use SiteGround as well.
I turn off Memcached and test on all explores mentioned above, they all work properly. -
AuthorPosts
The forum ‘Bugs & Issues’ is closed to new topics and replies.