Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 25 replies - 2,751 through 2,775 (of 3,962 total)
  • @hnla

    Participant

    No you removed the wrong one!

    The reason 1.2.5.2 didn’t show the issue was that it didn’t change until 1.2.6. The button is rendered via the do_action now but both still will work thus the duplicates.

    There were a few threads on this in the last couple of days so please check the forum posts first in case issues have been covered.

    @hnla

    Participant

    Good point if your logs aren’t being rotated you’ll end up running out of disk space completely, I forgot about rotating a log tried to open it in my editor to scan through, it editor wasn’t happy at all.

    @hnla

    Participant

    Not familiar with Zeus.

    Can it not be asked to use mod_rewrite

    A lot of threads on this issue:

    http://www.google.co.uk/search?q=zeus+and+mod_rewrite&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-GB:official&client=firefox-a

    @hnla

    Participant

    The permalinks screen would say if it could write if it couldn’t it would present you with what needs to be copy/pasted to the file manually.

    What server? IIS?

    There are threads on the forum that deal with this pathinfo situation iirc but granted sometimes they can be hard to track down.

    @hnla

    Participant

    Setting the permalinks, but can you confirm they were written.

    What server are you running on?

    Have you run through the WP codex guide that lph2205 linked to above.

    @hnla

    Participant

    Thanks @lph2005 that makes me look ever the meanie ;) :)

    @hnla

    Participant

    Not a single solution? really?

    Have you honestly scoured all the docs pages here and the WP codex ones, have you searched the posts in the support groups here?

    I know that this issue crops up often enough that there are many posts that have covered this aspect or issue, there is also WP
    codex pages on permalinks and how to deal with them which essentially is the issue you are experiencing by the sound of things.

    One last point this isn’t really a BP issue , it’s a WP one WP handles this aspect and it’s important to get WP working correctly before moving on to activating BP.

    @hnla

    Participant

    I think the ‘afaik’ would need to be confirmed wouldn’t it? otherwise we are simply being asked to speculate based on little actual information.

    What do you mean by ‘web folder space’ ?

    Was this change apparent after an update to 1.2.6 or did it simply happen for no apparent reason.

    Logs are always a good place to start looking for answers.

    @hnla

    Participant

    Under the “Add a reply” textarea there is a line of text that reads thusly:
    “To display code, put it between `backticks`”

    Ok so the fact that the function is run for logged in users tells me that the check on the ‘disable adminbar for logged out users’ actually simply checks to see if the value has been set ‘true’ or ‘false’ not whether that function is in current operation as it were so there needs to be a further query to see if the user is logged in so the ‘if’ statement needs to include something like:

    `&& !is_user_logged_in() `

    added to the line at the end.

    @hnla

    Participant

    Ok then skip back to the other thread where I think I suggested trying my original snippet of code but replacing ‘#header’ with ‘body’ and give that a try, is this not the issue that you are trying to loose that gap and that that gap is padding, the only padding I noted in your custom theme was on the body element.

    In reply to: Buddypress roles

    @hnla

    Participant

    Already doing that personally, you can run a check on current_user_can to see what capability they have. Roles and capabilities are handed down to all users regardless by WP or am I missing the point?

    @hnla

    Participant

    I’m attempting to point out how this is becoming a rather confused issue and gain clarification for all concerned :)

    Is the issue that you ARE disabling the admin bar for anonymous, non logged in users but doing so leaves a blank space?

    What is your definition of a ‘Guest User’ normally ‘Guest’ and Anonymous are one and the same thing and refer to someone browsing your site without being logged in.

    @hnla

    Participant

    After updating to buddypress 1.2.6 from 1.2.5.2 , my site does not show admin bar for guest user(as admin is disabled for loggedout users) , instead inplace it shows a white space …

    Logged in users can view the admin bar correctly , but non-loggedin users or guest users cannot see the admin bar , instead of the admin bar there is a white space in place … !!!

    What I don’t understand is why CAN I see the admin bar when I visit your site?

    As this is a custom theme have you actually tried asking the wpmu guys for support? as per my suggestion on the other thread.

    As I presume the other thread is finished with and my snippet of code of no use I will close that thread as it only serves to confuse if it runs on.

    In reply to: Buddypress roles

    @hnla

    Participant

    yep groups and forums are not roles in the strict sense of WP roles and capabilities, which is what I guess I meant in my initial comment.

    In reply to: Buddypress roles

    @hnla

    Participant

    Roles and capabilities are a WP factor not BP, as far as I’m aware BP does not create any roles or specific capabilities.

    If you want a good role manager plugin I would suggest Justin Tadlock’s one ‘Members’ however ‘capsman’ may well suit your requirements.

    @hnla

    Participant

    @anindyaray I still don’t really get what your actual issue is looking at your site as a logged out /anonymous user shows the adminbar but beside that , and obviously as you state above, you are using a custom theme so no my fix won’t work for you I and most of the others can only provide solutions based on default BP theme or core actions we or this forum can’t really support custom themes especially premium custom themes you must take issue with those themes to the original authors.

    However the padding in you case is on the body so perhaps you need to revise the code I wrote for you and substitute ‘body’ for ‘#header’ and see if that works?

    @hnla

    Participant

    If only people didn’t believe that Email protocols and services were such a simple thing, the post above by deadpan10 gets closer than most to understanding some of the potential issues and that it’s NOT necessarily a WP/BP one.

    Correctly set up email with correct and proper dns records might go some way to resolving issues many have, interestingly it’s pointed out that even given a correct SPF record Hotmail still appears to have issues, I have no answer to whether it’s the activation link but it’s an interesting notion.

    @hnla

    Participant

    Then you’re doing something wrong! Without actual detail on what you have done or tried to do it leaves it to us to have to makes guesses which generally is wasteful of time and resources.

    Rather than simply state it didn’t work describe what you tried to do with the above code, also we have little detail on what setup you are running i.e custom theme etc

    @hnla

    Participant

    Possibly because there are is a mix of issues, if you referring to the remaining padding-top then that is a property being declared in default.css on the #header ruleset and will be there regardless of the state of the adminbar:

    I have only time to suggest a quick fix for that in lieu of a new ticket raised on the overall issue for 1.3

    You can try dropping this into a function.php file in a child theme (you will need to add opening php tag as your file structure dictates)
    `
    function cancel_header_padding_for_no_adminbar() {
    if(defined( ‘BP_DISABLE_ADMIN_BAR’ ) || $bp->doing_admin_bar = false) ?>

    /**/
    <?php
    }
    add_action( ‘wp_head’, ‘cancel_header_padding_for_no_adminbar’ );
    `
    It would also probably work in bp-custom.php to ensure it was picked up for all possible bp themes.

    Note: I do not suggest this as an answer it’s a hack to get around the issue, but not a good approach all in all

    @hnla

    Participant

    Oh well, beaten to it :( :)

    @hnla

    Participant

    It is likely padding creating the white space as you see it to preserve an area for the adminbar, sadly it’s difficult to help further with a static image, you will need to probably contact the theme authors? and see if they are aware of the issue, whether they have fixes or an update for the theme.

    @hnla

    Participant

    As that guide is written b y Boone I guess it must be possible, if it hasn’t worked for you you need to review carefully what you have done and that you have followed all steps explicitly, and yes it might be a case that you need the css in which case test that theory by dropping the adminbar css file into your header for the top level site.

    There is a means of deactivating the activation and there will be threads on the forum and – I think – a plugin so have a hunt around.

    Don’t do this just to circumvent an issue you are having though; to want to remove activation because as you say “the verification email is being marked as spam most of the time” should be telling you that there is something wrong, email servers only apply filters based on sets of rules, you do have to ensure that when email servers look at incoming mail that they can verify it’s origin in other words perhaps you need associated dns mx records for your domain?

    Email isn’t necessarily something that just works or something that WP magically deals with, all WP does is simply use a faux email relay such as sendmail it doesn’t know or care whether your emails report themselves correctly.

    @hnla

    Participant

    Yeah but to quote Otto [who he?]
    If you disagree with me, then no, I’m not interested in arguing this point with you; you’re just wrong, period, end of discussion.

    A man of firm convictions!

    @hnla

    Participant

    You will need to feed us a little more detail, you shouldn’t have any issues, the adminbar works fine on 3.01 and 1.2.6.

    You need to tell us if you are using a child / custom theme and if so revert to standard bp-default to see if the problem persists if not then problem lies with the child theme.

    Have you any plugins running that could affect things? Same principle disable any plugins other than BP to test whether it’s a plugin issue.

    @hnla

    Participant

    reset? what exactly do you mean? I trust you’re not going to tell us you edited the default styles directly are you? if you did, then rename your adjusted files to default-custom.css and copy a fresh set of default files in from a new download, then you can remove them afterwards and revert back to your custom files.

    Later you will want to create a child theme so reverting can be done by changing themes in the backend.

Viewing 25 replies - 2,751 through 2,775 (of 3,962 total)
Skip to toolbar