[@hnla Participant 15 years, 4 months ago]

Yes good point; accessibility requirements dictate that links should be clearly marked as ones that open off site links/new windows.

[@hnla Participant 15 years, 4 months ago]

couple of old classic links there

@andrewbuzz the table aspect for layout has been mentioned, but I really need to just labour a point, tables for layout are absolutely not the way to markup pages, it’s taken a few years to get everyone on board with this but nowadays you wil no one creating layouts this way. I suspect that you have ‘designed’ your layout in PS? and then have used a tool such as DW? to construct a layout.

I would urge you to stop and reconsider before you go too much further, table layouts are highly inflexible, next to impossible to re-factor (one of the main points with CSS-P ) not search engine friendly and a whole heap of other reasons.

Are you preparing this layout for a client or is this an existing layout the client has come to you with?

[@hnla Participant 15 years, 4 months ago]

Closing thread then.

[@hnla Participant 15 years, 4 months ago]

While I understand your desire in this respect it ought to be pointed out that this is frowned on practice, although I have always kept a script snippet in library files for this purpose to hook onto rel=”ext” links, opening new windows or tabs has NOTHING to do with the web author/ developer it is NOT their concern how a user wants to have pages open in their browser, it is entirely a User based function and as responsible developers we do not attempt to impose on how a users browser functions. As a user nothing will displease me more nor have me leaving a site faster than a web site that attempts to modify my browsing habbits.

Having said that I always set new windows to open as a new tab, oh and the reason new windows are particularly bad? A new window has no browsing history thus no back button , a new window tends to open exactly overlapping the previous one, this can be extremely confusing for very many less experienced web users especially the older generation.

[@hnla Participant 15 years, 4 months ago]

kenny you are going to have to just get stuck in and explore the BP file structure and files, we have given a fair bit of advice on this subject across ~ 3 separate threads

Activity stream directory is /activity/activity-loop.php look through that file and identify the sections that output the actual update content or whatever bits you want to hide and wrap them in the code example above, give it a go and if you get stuck tell us what file you have tried to edit and show us the code you have edited and we’ll help you get it right.

[@hnla Participant 15 years, 4 months ago]

want to create a NEW tab in GROUPS bar to direct user’s to group activity page

Not sure this makes sense?

the link ‘home’ points to the activity stream for the group and is the displayed landing page by default.

[@hnla Participant 15 years, 4 months ago]

If you want to do that then you’re best to revert back to the code example that was given on one of the other threads and work on the individual files.

Or try removing the concatenated slug for the register page and just redirect to whatever is shown as your home or index page.

Yes bp-custom.php doesn’t exist it has to be created, this code should also work in functions.php.

[@hnla Participant 15 years, 4 months ago]

In case it helps there are options to the above you could try; you can add:

bp_is_directory() to allow access to all the main BP dir pages ‘Activity’, ‘Members’, ‘Blogs’, ‘Groups’ but trying to drill down any further on links in those pages would result in redirecting to register page:

`if( bp_is_register_page() || bp_is_activation_page() || bp_is_directory() )`

[@hnla Participant 15 years, 4 months ago]

Closing this thread as an example of the ‘sh_walled_garden’ I mention above is given in this duplicate thread:

https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/members-privacy-how-can-i-hide-members-profiles/?topic_page=2&num=15#post-102785

[@hnla Participant 15 years, 4 months ago]

@pinhit Kenny this is what I mentioned on your other thread and is now an example of where there are too many posts revolving around the same question . This solution (read the whole thread linked to above for full understanding) will work to limit access to directories or in the version above it permits access to specific pages and if not in that list of allowed directs to the signup page. I think this is your best solution rather than to try and restrict drilled down aspects of pages.

I’ll close the other thread as it is redundant now.

[@hnla Participant 15 years, 4 months ago]

@pinhit the expresion ‘lever advise’ is not a good choice of terms nor is ‘misguided ‘ the support forum is voluntary; people help out where they can, there is no SLa that advise is correct it’s the best that a member might be able to offer.

If you have found your own solutions to problems then that is great and you are on the road to learning – keep it up.

As for the question I’m afraid it is pretty much a repeat it’s in essence the same question as follows: “how can I restrict views of a particular page/element/component”. The code was provided that enables this , there are many conditional template tags that allow for simple logic queries such as “is the user logged in? then allow else send them elsewhre or post a message” you will use the same process for different situations.

However you may benefit from simply blocking logged out users using a small snippet of code that I think was named ‘Walled garden’ or something similar.

[@hnla Participant 15 years, 4 months ago]

This appears to have been corrected for 1.3 which doesn’t show the group in members account until accepted; so if you can hang on until 1.3 is released which shouldn’t be too long now.

[@hnla Participant 15 years, 4 months ago]

the answer to what file was provided earlier in this thread:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/re-word-whats-new/#post-102510

the file you need to edit lives in either the bp-themes folder within the buddypress plugin /bp-themes/bp-default/activity/post-form.php or in a child theme where the structure should be /wp-content//themes/your-theme-name/activity/post-form.php and as has been advised you ought to make edits only on copies of these files in a child theme.

look for lines ~29 & 31 `printf( __( “What’s new in %s, %s?”…`

[@hnla Participant 15 years, 4 months ago]

Have you looked through the Codex for any hints.

[@hnla Participant 15 years, 4 months ago]

It’s not a php file . CSS styles are contained in files ending .css either styles.css in the theme root or files in the folder /_inc/css – however don’t edit core files if you can avoid it copy required files to a child theme folder; a guide on doing so can be found in the BP codex.

[@hnla Participant 15 years, 4 months ago]

Yes there are a few other bits to it though but I guess Template: is the important one

When you copy files over to it to work on you MUST keep the exact same directory structure they had in the BP folder so /members is the top level directory and that must exist in your theme and it must contain the folder /single if you want to edit account/profile pages. In these two folders you may copy any or all, as few or as many of the files as you need to, BP checks when asked to fetch a file to see if it exists in a child theme before it reverts to looking in it’s own folders.

themes/
my-theme/
index.php
page.php
/members
home.php
/single

[@hnla Participant 15 years, 4 months ago]

Where are your main site files located Kenny?

Looking through those folders would answer the question. On a Web server you can only serve public site files from one directory the web root variously referred to as ‘www’, ‘public_html’. All your WP files are in there WP themes are held in the directory ‘themes’ under ‘wp-content’ you must create a new folder called whatever you like in that you create a file named style.css and in that file you add the text shown in the guide and from this point on you need to follow the guide explicitly.

You might be wise to allocate a little time to a quick read of some of the basics in the WP codex which may help your understanding of how WP works ( child themes are a WP construct)

[@hnla Participant 15 years, 4 months ago]

I’m closing this thread as you have received the answer on the other, if the code pcwriter has shown you foxes you please ask in that thread for further explanation.

For the record try not to open duplicate posts on the same question as it can cause confusion and is wasteful of forum resources.

[@hnla Participant 15 years, 4 months ago]

@pinhit

You’re not going to get told off again but I’m afraid you are asking coding questions, questions about how to adapt and modify a site and that requires a little coding knowledge, not everything is plugin based – although a lot is.

Sorry pcwriter but don’t link to W3Schools it’s not that great a site and we forbade it’s mention on csscreator years ago One of the best resources for frontend coding is htmldog

[@hnla Participant 15 years, 4 months ago]

If you have enabled ‘blogs can be created’ then the form elements will appear on the bp registration page – unless that is you have a custom theme which has modified things? if so you will need to contact the authors.

If you mean you cannot find the option to allow blogs to be created then you need to understand how WP works now with two separate section for ‘Site Admin’ & ‘Network Admin’ look in the top right corner of the dashboard for the Network Admin link

[@hnla Participant 15 years, 4 months ago]

Have you installed the BP template pack and modified the BP files to match your themes markup?

Best place to start is to read over this guide:
https://codex.buddypress.org/theme-development/bp-template-pack-walkthrough-level-easy-2/

[@hnla Participant 15 years, 4 months ago]

This is more an aspect of WP rather than BP and there are plugin managers available that allow you to control the availability of plugins to multi site blogs

[@hnla Participant 15 years, 4 months ago]

Firstly searching the site will possibly throw up past threads on the subject, try: ‘private profile’

Or you could check how certain aspects of bp work that only kick in when the user has logged in ( look in sidebar.php for examples of logic that checks if a user is logged in) using that logic you could take the main home page for members profiles and wrap it a conditional query that says ‘show: member profile if user is logged in else: write a polite message explaining profiles are restricted to members and provide a link to registration page.

[@hnla Participant 15 years, 4 months ago]

Silly question perhaps but you have set your theme as a child of BP?

[@hnla Participant 15 years, 4 months ago]

@pinhit You have effectively asked this question twice, please try and keep to one thread .