[@hnla Participant 15 years, 9 months ago]

*sigh*

[@hnla Participant 15 years, 9 months ago]

That is why mercime linked you to the codex page! Please read it for the answer to your question.

First port of cal on lists and boards are the archives and with apps the documentation pages if there are any.

[@hnla Participant 15 years, 9 months ago]

Said this before, but worth saying again, this setting does NOT technically increase the memory It adjusts the ‘Limit’ of memory available, it’s a safeguard feature that prevents scripts from consuming too much memory, increasing it blindly is NOT a good thing to do as the point of the exercise is to do what is being seen here, that of killing the script trying to run and bring down the system. If you – in theory – increased the limit to the max the box provided you could then run a script which infinitely looped, and that in turn would crash the box and all sites running on it requiring a re-boot to get the system back up. I would expect any good hosting service to preempt users trying to change this setting.

Following Ray’s advise to disable plugins should be attempted in the first instance.

[@hnla Participant 15 years, 9 months ago]

This is a support forum for a WP plugin, BuddyPress – you are asking a question related to WP blog posting, you need to take this to the appropriate forum https://wordpress.org/support/ but before you ask check through their Codex pages to ensure that the question you ask isn’t already covered by a guide and also search the forum for previous related threads in case your question has already been covered there.

[@hnla Participant 15 years, 9 months ago]

why would anything have happened to the WP default theme?

Unless Suffusion has done something screwy overall I don’t get what the issue is, and Suffusion is removed isn’t it?

“Trying to use WP themes modified for BP always seems to have issues, really best not done” – Hugo mused to himself.

[@hnla Participant 15 years, 9 months ago]

No ; if you need to deactivate by re-naming and have ftp access do it that way, as long as the plugin is renamed and nothing else running then you ought to be back in business with WP – I’d be surprised if BP was running or needed renaming but for the sake of it rename it ‘buddypress-deactivated’ then you ought to be able to log in to the dashboard, but do ensure WP is running correctly before returning buddypress to it’s correct name so that it may be activated on the plugins page.

[@hnla Participant 15 years, 9 months ago]

Six posts back??!!

I’m not really sure what you are having a problem with here, but please re-read that post I wrote earlier.

If Buddypress is deactivated and no other themes are installed & running then WP should fall back to using twentyten default theme.

[@hnla Participant 15 years, 9 months ago]

Already explained that! in the crudest base sense you can rename a plugin to force deactivate it. No plugin would have made any changes to another plugins core files, thus buddypress files would have been fine unless you had modified any.

[@hnla Participant 15 years, 9 months ago]

If you can’t get to the dashboard – rename the buddypress plugin navigate to the dashboard /wp-admin/ – login – go to themes ensure that a /the WP default theme is selected check the site and confirm before doing anything that WP is running correctly (check things such as permalinks are functioning correctly) if all is good rename BP to correct name navigate to plugins – activate BP and select the bp-default theme check once more that the site now running BP is looking correct.

[@hnla Participant 15 years, 9 months ago]

Had a feeling it was due to the taxing stuff, wasn’t testing on 3.1 as /groups/my-group/ is page not found, but can reach it from member/admin/my-group/home/ sadly all a bit stresfull at the moment trying to work with latest revison of 1.3/3.1.

Notice in older trunk group creation I have step 5 “The HTML for my creation step goes here.” but in latest revision of trunk it does not appear haven’t a clue why that is though.

[@hnla Participant 15 years, 9 months ago]

In theory you can deactivate any plugin or theme simply by renaming it via ftp or other means.

[@hnla Participant 15 years, 9 months ago]

Running pretty smoothly on a oldish checkout of Trunk (1.3) and 3.02 though.

Might be too early a concern? created a new member joined a group with an existing doc and am allowed to immediately start editing that doc, ought there to be a level of security along lines of either ‘current_user_can(‘trash_a_doc’) ‘ or perhaps under the group admins ‘Manage Member’ options: ‘kick & ban’ ‘promote to Mod’ ‘Edit Docs’. Conversely perhaps it’s sufficient really to rely on revision history if needing to step back, restore earlier versions.

Is it intentional that I see the same set of docs, or all created docs across all groups or is that something yet to be worked on or a symptom of the install I have? To make a rash, possibly ill thought through, comment I wouldn’t want all docs created appearing in every group would I?

[@hnla Participant 15 years, 9 months ago]

Sounds great, tried to give it a test run but guess it won’t run on slightly earlier versions of trunk (Call to undefined function bp_is_current_component() ) and my other copy of latest 1.3 revision won’t create forums and won’t find group pages so can’t test on that

[@hnla Participant 15 years, 9 months ago]

Sorry mercime you snuck in just ahead of me, I’m closing this thread as one is sufficient.

[@hnla Participant 15 years, 9 months ago]

Thanks for starting a new thread on your issues as requested.

I’m going to close this thread as you do not really need two running and your other one covers both your issues so please continue in that one:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/installing-themes-and-activating-forums/

[@hnla Participant 15 years, 9 months ago]

Thanks I’ll update the codex page to make it clearer.

[@hnla Participant 15 years, 9 months ago]

Start a new thread please and supply details about your setup.

[@hnla Participant 15 years, 9 months ago]

Files don’t look ok when I view source of a page, you did adjust the copy of activity/index.php that lives in your child theme rather than in the original bp-default folder inside the BP plugin.

[@hnla Participant 15 years, 9 months ago]

It doesn’t ‘come’ with BP. you must create an empty file to use.

What page of the codex were you reading as it’s worth just updating and clarifying that aspect.

[@hnla Participant 15 years, 9 months ago]

@grow-stories this is an 8 month old thread you have dragged back up. please, in future, if you have an issue you require help with you must start a new post/thread and describe the problem in detail along with any applicable info such as version numbers , custom themes, plugins in use.

You activate the plugin in the usual place for plugins, you visit the BP menu section and configure any options you want such as forum install, extended profiles etc, then visit the theme section and activate the bp-default theme or suitable BP compatible theme you might have.

[@hnla Participant 15 years, 9 months ago]

Think you missed one ML

[@hnla Participant 15 years, 9 months ago]

Exactly it always helps to have the original to compare to rather than just looking at a mess trying to remember what it was and what has changed. Although of course half the point of CVS is that you can always revert but sometimes a pig to do.

[@hnla Participant 15 years, 9 months ago]

perhaps take care and don’t update that actual checkout but move to a fresh install with fresh checkout of BP trunk and move your theme / plugins in as I think there will have been changes that may not sit well initially?

[@hnla Participant 15 years, 9 months ago]

but it’s still prone to being buggy. I’ll say

It’s reasonably stable for judicious development on while mentally noting areas that appear buggy, but one caveat , progress with it’s development is fast and furious :0 so update your repo checkout often to keep up with fixes as I experienced recently.

@DJPaul can you just confirm or settle that confusion on what platform 1.3 will require as far as I’m aware it’s simply the WP 3.* stream rather than 3.1

Edit// hmm just viewed that twitter link, slightly confused now. I have 1.3 albeit a trunk checkout prior to John Jame’s changes that runs on 3.0.4 what has changed or did it really never run ‘fully’ on 3.*. Also wasn’t aware Nacin was a BP developer how is it he knows better than you what BP will run on

[@hnla Participant 15 years, 9 months ago]

And I thought BP 1.3 just required 3.*

I have a test install of BP 1.3 running on WP 3.0.4 and another running 1.3 on WP 1.3 RC 2

@DJPaul will need to confirm that comment in the thread you link to.

As for release date, you should note the blog post by John James where he announced he was proceeding with some major refactoring of the core, the open tickets is not really indicative of the amount of work left to complete with this particular cycle, I doubt that 1.3 will be ready this side of Feb and ought to go to a RC stage for a little more rigorous testing for this particular release.

I would have thought regardless of release dates one can and should be starting to test ones themes / plugins under 1.3/3.1