[@hnla Participant 15 years, 12 months ago]

@pcgs51 please don’t post questions twice it’s considered bad form and will not get attention any quicker and causes us unnecessary work.

Locking this thread please continue in the other one you started:

i-would-like-to-hide-my-members-usernames

[@hnla Participant 16 years ago]

And why are you not simply using the backend ‘Profile Field Setup’ to add new profiles fields for users to complete, is there some particular requirement you have or is this a plugin you’re writing?

[@hnla Participant 16 years ago]

You could definitely make the news less prominent, perhaps half the width and use the other side for mission statement or use it has a featured ‘shop’ or ‘shops’ that you could offer for a small premium?

[@hnla Participant 16 years ago]

@justbishop That’s a very interesting post, and raises a valuable point in the creation of community sites, it would be nice to see further discussion flowing from your initial post.

Your re-working looks as though it makes a lot of sense, I’m thinking you’re going to have much better results

[@hnla Participant 16 years ago]

You need to compare the theme you want to use and one of it’s files i.e page.php or index.php to one of the newly created BP ones like /member/index.php the BP files need to mirror the html markup and class/ID’s structure that your chosen theme files have e.g if your theme file has an element named ‘content-main’ and the BP file has ‘content’ then the BP one needs to change to match.

I’m afraid that if it’s still ‘all gibberish’ then things will be difficult, adjusting a theme to work with BP does require a degree of coding knowledge albeit at a basic level you must be comfortable modifying files and working with HTML markup.

[@hnla Participant 16 years ago]

It is an artifact of the text-shadow property on #footer.
The only reason you are experiencing this issue th way you are cross browser is because of mal-formed markup which you are going to need to fix.

`

powered by punjabi community<a

`
Is Operas attempt to fix broken mal-formed markup and isn’t that great leading to the issue you are experiencing.
The markup is hopelessly wrong and forces the browser to use it’s tag soup rendering engine to try and correct the broken DOM or at least build some semblance of a workable DOM structure, There never were any rules laid down to govern how browsers dealt with tag soup code as you can’t build a Standard and then account for non standard behavior therefore browsers interpret what was intended and try and correct FF 3 gets this pretty close to correct and closes the anchor and moves the closing footer, Opera makes a mess of it or can’t figure out what to do.

What is causing this? Sadly can’t answer that and is where you will need a little coding experience to sort things out – it may well be the javascript error Tammie alluded to what is clear is that there is a huge amount of scripting taking place and a fair few markup errors too many really and is the inherent weakness in a 3rd party plugin based application.

[@hnla Participant 16 years ago]

@electroman we can’t give you a step by step guide this is not a paid support forum however we can help but you will need to have first ensured you have followed all the steps outlined by the template pack and read the help guide linked to earlier, bear in mind that the template pack doesn’t do all the work for you and there is a degree of coding skill and understanding of WP theme files required.

You will need to provide a link to your site that works – if that is your site that you linked to it’s throwing PHP errors and exposing your server path structure which isn’t a great idea – then someone will hopefully be able to spot what elements you may not have replicated in your BP files.

The 404 error is possibly that you haven’t set a permalink structure, and you will need to visit the permalink page in the backend and select a structure and save – the assumption is made that you are running mod_rewrite and able to write to the .htaccess file i.e permalinks work under plain WP?

[@hnla Participant 16 years ago]

I think the issue is that template pack gives the impression that it’s a fully automated click process, and the fact that there will be manual editing seems to get overlooked.

[@hnla Participant 16 years ago]

So I asume – without testing so to speak – that the:
`
remove_filter( ‘xprofile_get_field_data’, ‘wp_filter_kses’, 1 );
remove_filter( ‘xprofile_get_field_data’, ‘force_balance_tags’ );
remove_filter( ‘xprofile_get_field_data’, ‘stripslashes’ );
`
Are now redundant and can be removed, but that the rest of the thread and code examples will work as shown?

[@hnla Participant 16 years ago]

As modemlooper says the plugin route will be easier for you but to answer the question the parameter you refer to takes a page id (found if you hover a page title in backend lists) you can set a series of id’s comma separated e.g

exclude=1,2,3,’

the parameter can also be change to one of ‘include’ which is more practical if you have a specific page in mind and not likely to want any others or where you create many pages but don’t want them all to appear automagically – using ‘exclude’ means that pages are added as they are created and if not wanted you would have to go in each time and add the page to the exclude list.

[@hnla Participant 16 years ago]

Is there a reason for that approach? is not the aim to replicate the original themes layout for better or worse, not that what you have suggested doesn’t work but does leave a mix of markup layout between files?

[@hnla Participant 16 years ago]

Can you provide a little more detail, like what theme? Is it a custom one?

Simple answer: you can wrap the sidebar call on pages in conditional queries that test to see what page is being displayed, check out the BP codex you’ll find a list of conditional tags you can use or even simpler answer remove the locate_template function in the file for the page you don’t want the sidebar appearing on.

[@hnla Participant 16 years ago]

Lets take a wild stab in the dark… actually lets not, instead why not try and provide some detailed info about your setup, versions, themes, plugins etc along with as much information as you think may be helpful to troubleshoot your issue – that sort of detail is basic and mandatory on any tech support/help forum.

First thing you could do before posting back is disable BP and any plugins and see if you can register users on the plain WP install – this will just establish it’s a BP issue or not, if a BP issue then enable BP but disable all plugins and see if that allows regitration, if so then enable plugins one by one checking each time until culprit is found.

[@hnla Participant 16 years ago]

I presume you have used the template pack to prepare BP pages under your chosen theme, Template pack will require that certain elements are added from the original theme markup to the new bp pages, looking at the layout shows that the original theme uses a nested element under #container called #left-div which is floated right and given a fixed width allowing room for the left sidebar. it looks as though this is missing from your bp pages and will need to be added in manually.

It may help you to open and reference one of the original theme files like ‘index’ , ‘page’, or ‘single’ and compare it’s main markup structure to the bp files and ensure that they match.

[@hnla Participant 16 years ago]

Then you have done something wrong and need to review the code – missing php tags or something?

Without any actual detail it’s difficult for us to provide you with any help, maybe a link to the site or some description of exactly what you put where.

[@hnla Participant 16 years ago]

Try visiting -simply visiting – the permalinks page and see if that updates your permalinks.

If that doesn’t help then you might ned to think about what event or change may have occurred ‘Yesterday’ to suddenly cause things to stop working , an upgrade? new plugins? also report your actual BP version would love to think it was at 2.4 but that won’t be for quite a while yet

[@hnla Participant 16 years ago]

@paulhastings0 Paul have you had a look at where those two values are being derived from, determining that and comparing the functions in the core files may give a clue and help narrow down what’s happening.

[@hnla Participant 16 years ago]

Display:none is an accessibility no no, left:-999em ought to be used, not so much a IE thing.

My concern was more for the inability of IE6 to grok :hover on anything but anchor elements, adminbar covers this aspect so I added / submitted a patch to add sfhover class so any hover styles need to be grouped with the class selector .sfhover so IE6 can function.

tbh it shouldn’t really be a question of whether BP is supporting IE6 although naturally if that’s the descision it wants to make for bp-default then that’s fine, I have on a to do list and promised a while back a IE6 CC stylesheet and will get around to it at some point soon? hopefully

[@hnla Participant 16 years ago]

Did raise that a while? back, not sure it inspired much interest, but you would need to define whether one was dealing with general UX /UI or the default theme, from a theming point of view not child theme necessarily , but full on theming some UI / UX is merited along with other issues such as identifying markup that needs removing from core if applicable and aspects such as better handling of activity_action which isn’t fun to deal with from a frontend perspective.

[@hnla Participant 16 years ago]

The thread is in reference to 1.3, I think that the styles just need to be worked up and then submitted as a patch. I had issues using trunk on a fairly clean MS install not sure why but lots of odd issues had to install on a plain WP copy in the end.

[@hnla Participant 16 years ago]

@DJPaul what are you after Paul? I think everyone might be a little lost as to what actually needs doing? is it just the styles that need sorting, As for my earlier question regarding changes to nav menus for 3.1 and as much as it may be irrelevant? I managed to track down a ticket correcting the issue of not being able to remove parent ul elements which is helpful but couldn’t spot anything dealing with child pages and nesting thereof

[@hnla Participant 16 years ago]

More a WP MS question than a BP one can you not use the ‘Recent Site Wide Posts’ widget?

[@hnla Participant 16 years ago]

Just a case of checking carefully through the various backend screens, look at super admin > options at the bottom there is a check box to allow administration menus with a single selection for plugins.

[@hnla Participant 16 years ago]

You’re pulling in the original one, if you made changes in a copy then they won’t be applied.

path is :
_inc/css/

if you copied the default structure to a child theme.

[@hnla Participant 16 years ago]

Are you sure your @import paths are correct, are you actually calling the right adminbar.css? There are only a few rulesets that will govern these dimensions, Firebug is a extension for Firefox that will allow you to observe which rulesets are applied to an element when you hover the element in the viewport.