[@hnla Participant 15 years, 10 months ago]

Please do not create a new topic on the same subject, continue in the existing one, creating a new thread simply serves to fracture all that we have asked and discounted thus far in trying to help you and will have members asking all the same questions over again which is a pointless exercise and wasteful of resources.

Please post a request for further help in the existing thread you started on this issue in order to bump the thread.
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/please-help-no-group-creation-option-in-groups-1

Closing this thread

[@hnla Participant 15 years, 10 months ago]

@residentcusano this will be the second post I’ve closed. Please don’t create more than one post on the same subject. Continue this one in the other which has received a response in.

[@hnla Participant 15 years, 10 months ago]

https://buddypress.org/developers/nuprn1 rich! etiviti wrote a suite of plugins one of which is ‘BuddyPress Restrict Group Creation’
Don’t allow your members to sign up and instantly create groups set a time period they have to wait, spammers won’t wait, genuine members will not mind if it’s clear to them they have to wait a few hours, a day or whatever.

[@hnla Participant 15 years, 10 months ago]

it’s no solution and pointless running as yet one more plugin, this is simply a Order Allow Deny Apache directive and would be placed in you httpd.config file preferably or in your .htaccess and then list IP or domains to deny. Blocking IPs isn’t something that should be done lightly as it can have repercussions and is only effective on domains if there is one specific troublemaker these spam bots use spoofed domains they will change on the fly so little point trying to block them.

Preventing spam is a multi faceted approach and the many areas and things that need to be done covered at length on the support forum, you need to use all of them to effectively reduce spam and if possible don’t let people sign up for blogs from the sign up page

[@hnla Participant 15 years, 10 months ago]

This feels very much like a duplication of this post:

https://buddypress.org/community/groups/creating-extending/forum/topic/someone-know-a-plugin-acting-like-groups/

Please avoid double posting topics, if necessary after a ~24 hour period bump your topic if it’s received no replies.

I have to admit that a few of your topics so far have left me non plussed as to what you’re after so please describe your requirements in as as much detail as possible, I also think that it may be possible that you are seeking to do things that require a degree of experience with BP and fair knowledge of PHP.

Closing this thread, please continue in the one you started, linked to above.

[@hnla Participant 15 years, 10 months ago]

You said earlier:
good idea! I will do some copy and pasting from 1.2.5.2 into 1.2.7 to see what file is causing it..

Did you actually do that? as 1.2.5.2 wasn’t fixed for this issue and you would have introduced the problem not solved it and no setting would change that fact.

[@hnla Participant 15 years, 10 months ago]

Hmm have to say I’ve never set it other than by using the UTC settings, just tested changing to city ‘London’ and it didn’t produce any problems on my live test server.

[@hnla Participant 15 years, 10 months ago]

Look in members/index.php but make your changes in a child theme (if not sure what a child theme is please check the docs codex of this site for guidance)

How to write this is another matter are you talking about simply adding some markup? then you use elements as you need them firstly ‘p’ elements then a div if necessary to group the paragraphs, more than that it’s not really possible to tell you without more detail.

[@hnla Participant 15 years, 10 months ago]

the answer to the first part is that this is a consequence of using Ajax and a good reason not to use it frankly – Ajax is loved because it seems cool and indeed is to a large extent but it is really something that was never meant to be, the browser is not meant to be able to directly pass data to and from the server side, in effect what happens is that the browser doesn’t really now anything has happened and can’t keep a history state thus your back button does not go back one page as that page was never loaded by the browser or requested, hitting back button simply takes you back out of the members page altogether regardless of what page depth you had loaded. For page lists like this my personal view is it’s better not to use Ajax to load in the data.

[@hnla Participant 15 years, 10 months ago]

@Bigjimmysisco how do you mean patch is outdated? The patch was to correct an issue found and it was rolled into 1.2.7 as part of the reason 1.2.7 was released to push through a few important fixes in advance of 1.3. If you are running 1.2.7 then that patch should be merged in to 1.2.7 so you shouldn’t need to change anything but if those lines are missing then there’s something odd at work.

@all I’m afraid that without someone providing access to an affected machine it is really hard for anyone to fix the issue or track the issue down.

I have checked my live test install and that is running 1.2.6 with the omgpiza patch manually applied and I see no issues, which tends to bring me back to thinking it’s a server timezone issue – not the time itself but the timezone the server thinks it’s in, however I’m perplexed by the fact that posting a WP comment reports correct time.

[@hnla Participant 15 years, 10 months ago]

All there is to be done now is to let Boone get on and investigate what’s happening. if and when a solution is found no doubt a patch will be produced that affected installs will have to add to their core files.

Considering a pretty lengthy amount of time spent on the time stamp issue I’m amazed that there is this issue still.

@boonengorges doubt this helps but the last time this issue reared it’s ugly head was noted in this thread:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/time-offset-still-present-in-bp-1-2-6/

and resulted in additions and patch on this ticket:
https://trac.buddypress.org/ticket/2203/
(omgpizza.patch)

Thought that would really be a final end to this matter

[@hnla Participant 15 years, 10 months ago]

Erm Yes I can guarantee you that Paul knows that snippet of code, if I do he certainly does it’s a common bit of code available in the Codex!

[@hnla Participant 15 years, 10 months ago]

This isn’t a paid support forum and as such comments like I am waiting for a solution… do not go down well!

Also bear in mind that technically this isn’t or is unlikely a BP or WP issue but a server configuration one.

[@hnla Participant 15 years, 10 months ago]

It’s been discussed often there is a means, can’t recall if a plugin, no links to hand I’m afraid but have a hunt through the archives for posts on the subject.

[@hnla Participant 15 years, 10 months ago]

and ask your web host whether the owner/group permissions are correct to allow the server or user to write to directories. This issue is not just about chmod and the continual advice from general quarters around the web and from hosts to set directories to world writable 777 is starting to get irritating.

P.S We understand it is urgent but you mustn’t state that in a post it’s not our problem I resolved this kind of issue by sitting down with Linux guides and a test server until I had a fair grasp of things – note only fair though still get confused by much

[@hnla Participant 15 years, 10 months ago]

Minor note for all: please never state ‘urgent’ in a thread title, thread titles on tech support forums are meant to be descriptive of the nature of the issue only

[@hnla Participant 15 years, 10 months ago]

Ask your host whether the PHP GD extension is installed and loaded

[@hnla Participant 15 years, 10 months ago]

Well there you go!

@fellowchirps now you know what plugin you installed that caused this if you have follow up questions on it please post them to the plugin authors group:

https://buddypress.org/community/groups/bp-my-home/

[@hnla Participant 15 years, 10 months ago]

I’m afraid based on the info you have provided it is impossible for us to make any stab in the dark, not even sure this is a BuddyPress issue. You will simply need to look at your plugins and see which looks like the most promising culprit, and/or check through your widgets and see which appear to have more than one that need activating.

[@hnla Participant 15 years, 10 months ago]

this page in the codex explains how the adminbar functions:

https://codex.buddypress.org/theme-development/modifying-the-buddypress-admin-bar/

[@hnla Participant 15 years, 10 months ago]

Well it’s hidden! can’t say why as it’s a custom theme.

if you want to see if it works enclose the ruleset in comments

`
/*
#wp-admin-bar, #wp-admin-bar.padder {
height: 0;
display: none; /* Hide it- not required. */

}
*/
`
Of course this will depend on whether the original styles for adminbar are being called and whether they suit the layout as to whether anything is seen.

[@hnla Participant 15 years, 10 months ago]

It wouldn’t hurt to try and up the script mem limit – 64M or 96M are safer values. How did you install BP plugin, manually or through plugin page?

[@hnla Participant 15 years, 10 months ago]

The issue is really why it’s not displaying in the first place, does footer.php have that hook I mentioned above? Problem is that we have no particular knowledge of what this custom theme has done or whether you have followed all the steps with the template pack to make a BP ready set of files including a certain amount of hand editing of files – although judging by the fact you mention no other issues you likely have.

[@hnla Participant 15 years, 10 months ago]

here’s me pointing to the codex

Post back if that doesn’t help or if I’m too cryptic )

[@hnla Participant 15 years, 10 months ago]

I would be surprised if that was the reason though but noticed a few plugins showing this warning and on some of the better known and reliabal ones so it’s odd @DJPaul probably knows why or perhaps@boonebgorges does