[@hnla Participant 15 years, 6 months ago]

Grabbed a ticket and patched

[@hnla Participant 15 years, 6 months ago]

You do not need PHP skills, it’s simply a copy paste operation in reality, an understanding of markup is required though.

In essence you are comparing those two files and using your current themes file as the baseline and ensuring a BP file matches it in markup structure. Not sure what that second file is meant to be as it appears to want to display a video which my current browser is not enabled for..

This walkthrough might help you better.

[@hnla Participant 15 years, 6 months ago]

BP-Default 1.3?s CSS is mine. @mercime has recently identified a number of issues which I am working through; if anyone wants to look at it with me, get in contact soon.

Drop me a line Paul, give us an idea of the issues that have been identified.

[@hnla Participant 15 years, 6 months ago]

I can see immediately that there is a div mismatch with a stray closing div, you perhaps have closed wrapper before sidebar or something along those lines. In fact your sidebar is simply in the wrong position altogether it should live within #ftstemplate and it’s outside, so you just need to check over your markup a little more carefully.

[@hnla Participant 15 years, 6 months ago]

There has to be, then, a fundamental difference in the markup you have in one of your original files Vs that of a BP file it’s a matter of spotting it?

[@hnla Participant 15 years, 6 months ago]

Ok managed to track the function down and it looks as though it accepts arguments so you can try:

(‘smallest=10&largest=42&sizing=px&limit=50’)

These are the defaults I’ve shown so adjust to requirements also you only need pass the required parameter not all if not desired so ( ‘largest=32’ )

[@hnla Participant 15 years, 6 months ago]

Yep sorry forums tag is a widget one of a handful provided and hardcoded into the sidebar.php however the shame is that it calls on bp_forums_tag_heat_map() to generate the tags and the tags are sized using inline pixel values which means it’s almost impossible to override them short of hacking the source code, I can’t locate bp_forums_tag_heat_map() which is odd my search across files should have found it but couldn’t.

[@hnla Participant 15 years, 6 months ago]

You appear to be preventing logged out users viwing these pages? at least you have an odd url parameter at work on the index page when selecting bp pages, you might want to check that it’s possible to view these pages before posting the link?

Yes there will be a stylesheet controlling the tags which one will depend on your theme, with bp-default the styles will be in default.css.

You can identify where by using a tool such as Firebug for Firefox and use it to highlight the element/s which will show you the applied styles, stylesheet path, and line number to locate the ruleset. in the lower pane on the right hand section.

[@hnla Participant 15 years, 6 months ago]

Going to be hard for any of us to guess at possible causes really, you would need to post as much detail or any detail you can really. It’s always best to start a fresh post rather than dragging up old ones that appear to address similar issues.

[@hnla Participant 15 years, 6 months ago]

I’m afraid that it’s not CSS issues you are having. Your issues are – forgive me for being blunt – a case of hopelessly mal-formed markup. The use of the general DocType used to declare an HTML5 conforming document doesn’t preclude well formed markup, at the moment it’s anyones guess as to how browsers will attempt to interpret what it has to parse as tag soup code.

Generally helping to fix up the presentational styles of a document is considered pointless with a mal-formed DOM as CSS is applied to the markup and that markup must make sense to it, the general advice is to correct and then validate the markup before troubleshooting styling aspects s often these perceived styling issues are actually corrected simply by fixing the markup.

What I can tell you is that you have clearly got mis matches between template files as I can see a padding div on ‘Gallery’ but not on ‘activity’ I can see two #containers on the activity page where only one should exist (an page or document can only declare an ID once on each page)

The other markup issues are more serious but are going to prove tricky to fix probably but they do need to be looked into you have markup elements strewn through what is the ‘head’ section of the pages with a consequence that the page body start is declared in error as it’s already open the closing head tag is redundant as it’s assumed that body has already been opened.

Sorry to be the bearer of bad news but the issue here is one of mal-formed markup firstly and secondly possibly a few elements not translated between your theme and BP when making them compatible using the theme template pack?

[@hnla Participant 15 years, 6 months ago]

Sounds to me like an issue of mixed content when in https/SSL the image path is is calling on a non https path and the browser is throwing an warning to this effect, not sure with WP how one deals with this though.

[@hnla Participant 15 years, 6 months ago]

not particularly odd the normal approach is to make the default web directory in htpd.conf extremely restrictive and from there one allows more specific directories relaxed permissions, it is odd however for that general rule in the vhost container to be there and so restrictive. The workaround in the link is not a hack as such I would set up my directories with main rules in this way. Control panels do have a habit of having to impose some strange conditions due to having to have control over files and of needing often an unusual structure in order to work. personally I prefer not to have control panels making a mess of servers.

[@hnla Participant 15 years, 6 months ago]

sorry can I have my patience back please, need it for something else that’s causing me stress.

[@hnla Participant 15 years, 6 months ago]

Having index.php in the url path is a pretty meaningless exercise especially as part of the point of permalinks is to produce a url that is human readable and aids search engines by providing keyword rich urls rather than index.php?p=267 which is fairly obtuse.

Out of interest what server are you running on and what type of access to it do you have?

[@hnla Participant 15 years, 6 months ago]

None that I can think of that don’t get far more technical than the WP page, the WP page is about the simplest series of pointers and explanations. Did you try creating a custom structure? i.e adding in ‘index.php’ prefacing what ever %day%%decade%century% structure you wanted, although I’m not sure that that doesn’t create issues with BP

[@hnla Participant 15 years, 6 months ago]

Whereas I can well imagine what prompts such an article, I’m not sure it’s apposite, The snippet ” I can only be honest and say not much has changed for almost a year” is a little unfair and a surprising comment to make really, a fair bit has changed over the last year and lets not forget A/ how complicated this kind of app is and B/ that there are only three core commiters to the svn trunk.

Of course I don’t want to judge Bowe’s post given I can only read a small section of it, I will however tend to agree that there has been a slow up in plugin development and perhaps the plugins authors have exhausted their honeymoon period with BP and are not able to devote so much time to it.

For the record I will point out once more just how much work is involved in coding and testing/debugging plugins and constructing themes- for those that are not aware – it’s a huge amount of time and we must not forget that this is an open source project despite WP’s involvement and all the work that is done is given freely all the long hours are given with little expectation of any return apart from the gratitude of the community – yes it’s true that some coders do manage to monetize their work too an extent but they are a small fraction of those that have contributed their work -. The pace of the project is governed strictly by the time that people are prepared or are able to put in, allied to that fact we have a situation where we have simply three core coders doing 90% of the work, these three all have paid jobs and are not able to commit to full time ( it’s surprising how much time is given though! ) on the project, understandably.

What I would wag my finger at and offer a generalised admonishment to is the wider community for it’s lack of direct involvement at any level. An open source project is carried by it’s community they drive it along and sadly I see very little participation from them, there are those that are pretty active in using BP have experience and knowledge yet are seldom seen on this site. There are many levels at which people can help, checking patches out and reporting back ( if one has a localhost dev environment ) reporting bugs to the trac system, adding to the codex which could really do with some tlc, many ways of contributing and at various skill levels we do not all have to be of the caliber of Boone, Paul or JJJ to help out and push things forward. ( oh and I consider myself one of those that could be helping more fwiw, time and pressure of earning a scant living though )

I have always been one who was vocal – at least early last year – when changes did need to be effected and things seemed to be in slight turmoil or turpitude, some of those changes came to be some didn’t , there are still many things that could be improved with this project and hopefully they might happen with time as for pushing for those things a lot has been said publicly and privately and there is little point going over old ground.

[@hnla Participant 15 years, 6 months ago]

And what message if any did you see when setting permalinks? If you saw a lot of code that is suggestive that WP wasn’t able to update your .htaccess file and is showing you what needs to go in the file. You’ll need to confirm that you actually have mod_rewrite working correctly, perhaps first disable BP and ensure that WP works correctly with permalink structure for posts.

Edit// I note that you have a url structure with that dreaded index.php in, ‘Almost pretty permalinks’ ? I think that you perhaps ought to read the WP codex page on permalinks to arm yourself with a little further understanding of this area and how to deal with it, you may have to add a custom link structure adding in the index.php/year/month/etc

https://codex.wordpress.org/Using_Permalinks

[@hnla Participant 15 years, 6 months ago]

Not necessarily an easy fix with so little info to go on. Default is to show the adminbar all the time so setting ‘yes’ to hide it for logged out users isn’t going to change things for logged in users.

Usual questions must be asked now: Are you running a custom theme? If so then can you revert to bp-default and see how that performs.

[@hnla Participant 15 years, 6 months ago]

What other plugins do you have running that might affect things like members or profile displays, pseudo privacy type plugins?

[@hnla Participant 15 years, 6 months ago]

@DJPaul but that was to fix the incorrect nesting of elements, the paragraph tags still exist for the bp_the_profile_field_value()

would not something like xprofile_get_field…() be better?

[@hnla Participant 15 years, 6 months ago]

No not normal behavior so you must have some customizations in place or displaying the widget within an area such as ‘sidebar-me’ within sidebar.php that is wrapped in an if( is_user_logged_in()) conditional as an example only, as I would have thought it unlikely you were rendering the widget there as it’s a hardcoded section not widgitised.

You’ll need to read through your files carefully and determine where and how the area your widget is rendering in is working.

[@hnla Participant 15 years, 6 months ago]

Not sure why your ‘site’ redirects to facebook but in that it does it’s not especially helpful in order to see the issues to which you refer

[@hnla Participant 15 years, 6 months ago]

@psivait

re spam: I would do a little research as there have been some lengthy posts on this question /issue here so dig those up and give them a good read, there are plenty of steps you can implement to reduce spam, however be aware that there isn’t much you can do about human spammers and they account for a good deal of time wasting these days especially if you allow for blogs to be created at signup (something I don’t personally think a good idea).

As for approving multisite blogs as a single super_admin I’m not sure you can or should, multisite blogs are meant to be fully fledged blogs in their own right and the user that creates the blog is the admin. There are however steps you can take as the multisite admin to restrict what can be done on user blogs but that is more a question for WP than BP. If your meaning that you will have members on your primary blog that is running the multisite install and you want to elevate them above ‘Subscriber’ level to say ‘Contributor’ so they can post then that can be done and can and submissions will be ‘awaiting admin approval’ which you will see if you run through the options in the dashboard with perhaps a test user with a ‘Capability’ higher than ‘Subscriber’

[@hnla Participant 15 years, 6 months ago]

Sounds like the wp_nonce_field() kicking in, suggests that it’s not seeing the correct referer to allow the form submission to proceed. I’m not that familiar with W3 Total Cache but perhaps – if it is – it shouldn’t be caching the sign up page ?

[@hnla Participant 15 years, 6 months ago]

? what plugin is this, but unlikely you can add a map to a WP post or page but you will need to explain a little further.