Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'Hide Admin'

Viewing 25 results - 726 through 750 (of 915 total)
  • Author
    Search Results
  • #88978
    Beck B
    Participant

    @jonnylons, are you looking for something that lets users write blog posts for their sites? Somebody pointed me to a few good front-end blog post plugins. If that’s what you’re looking for, say the word, and I’ll dig ’em up.

    Or, now that I look more closely at the link @footybible offered, sweet. And he mentioned the front-end approach already. I have no current need of this solution myself, as I’m not running multisite, but I am definitely bookmarking that guide in case it comes up in the future….

    So, sounds like it just depends on how much control your users need and how much time you want to invest in setting that up.

    #88975
    footybible
    Participant

    @jonnylons I had a similar goal to you. I ended up instead creating a highly customised, edited backend. Whether you are interested in doing this completely or maybe just checking out some of the things I learnt, you may want to check out my guide to the matter here:

    http://buddydress.com/forums/topic/customising-the-user-backend-and-default-blog-format-tutorial

    #88972
    jonnylons
    Participant

    @pcwriter and @Beck_B thanks! I am trying to find a way to add something to the adminbar of Buddypress that would allow members, when logged in, to write for their sites. At the same time, I don’t want the backend of sites exposed to members who are not writing for that site. Can’t seem to find a simple solution. Maybe these work.

    #88795
    pcwriter
    Participant

    @hnla Well now, great progress!

    I remember writing at some point that it’s often the most obvious that escapes me… Turns out I hadn’t “actually” selected any files to upload to subversion… I was just going through the motions and clicking buttons (doh!). The first version of the plugin is up and I just updated it with a whole bunch of cool new stuff. Code here: http://pastebin.com/Qquwe9pH

    Thanks to your examples, I created 3 new custom configuration options: in addition to hide/show the main nav, users can now choose to hide/show the site name/logo, the Login/Signup links, and the Visit Random dropdown. I’ve also completely revamped the readme with a detailed FAQ, and added a fully commented stylesheet with the rules I use for my site to help get folks started on customizing their new admin/navbar.

    Thanks a whole bunch for your invaluable help and instruction on this project! I can now say I’ve popped my plugin cherry! :-)

    Now we just have to wait for subversion to update………

    #88741
    Hugo Ashmore
    Participant

    Good spot, that’s why second eyes are vital, also the $hideMainNav doesn’t need to be globally scoped as the function sits outside pages() and the variable is already in the main page scope so no global required for it.
    Not sure how the process works for uploading plugins but would guess it hasn’t been approved yet?

    If I have a minute I’ll add the config variable for ‘Community’ link then you can run things through their paces when your back.

    #88728
    Hugo Ashmore
    Participant

    new adjustments:
    typo corrected;

    http://pastebin.com/TA4vGHT5

    Config section created at top of file – labels all set from that point by user

    Hide main nav links function created to add embedded styles via add_action dependent on user setting $hideMainNav = true

    Hiding the main nave through CSS isn’t really the best option as it leaves the markup there, it would be better to remove altogether you may want to change default to true(hide)

    This is somewhat of a stopgap solution to user parameters.

    As always check over thoroughly for any other typos I may have missed :)

    #88615
    Hugo Ashmore
    Participant

    @pcwriter

    I’ve had to do a fairly extensive rewrite on the function for a number of reasons:

    1/ There was a significant degree of malfomed ul child nesting which prevents drop down aspects working correctly primarily I’ve removed the opening and closing UL elements as they are not required and cause issues.

    2/ Not sure how the wp_list_pages was intended to work but with the parameter ‘title_li’ declared as empty you correctly remove the wrapping elements but would need to add UL elements manually wrapping the function call for the dropdown to function correctly.

    3/ Added back in the wp_nav_menu function calls but wrapped them in a check to see if WP 3.0 is running i.e are the new menu available if not hide altogether.

    Also added a reverse check to remove the wp_list_pages function if using the new menus as there is little point in both and the new menu system serves better.

    4/ Changed region and menu top link names to ‘pages’ but this area is a fundamental issue as it cant be known what the user sets as menu names, ideally one shouldn’t hard code values but retrieve them from the admin menu area, but this proves far too hard to work out (asked a question on WP support but haven’t had a reply and I don’t expect one – sadly there is little codex documentation of any depth on the new menus.)

    This issue applies to the wp_list_pages as well as you can’t really pass any values for ‘include’ and ‘exclude’ as these values can’t be known so you ought to remove those values you have hardcoded (I have left them in).

    If I can get some guidance on how to fetch values from the menu backend view such as menu names then it will be possible to make the menus far more effective but have spent quite a while trawling through the core WP files for nav-menu and it’s not obvious and too time consuming.

    I have copied the revised code to this pastebin page, give it a check over, but don’t assume I have things all correct, run it as plugin copy 2

    http://pastebin.com/trUDaPEP

    Driftless
    Participant

    OK. I know this is not inherent only in Buddypress, but is a larger philosophical question that Buddypress has the power to Revolutionize!:

    What is the difference between an Activity Post, a Forum Topic, or a Blog Post? And I’m not talking schematic / programmatic differences, I’m talking at the basic fundamental.

    To illustrate, let us play a guessing game. Which of the three am I describing?

    1) A user submits some information / a story / a bit of news / a question
    2) Other users respond with comments / answers / reactions / more questions

    I find that many users to my Buddypress site (a captive / motivated audience mind you) get confused – posting forum topics in Activity streams, or blog posts in forums… Are they just plain ignorant, or are the unwashed masses just more enlightened than us system Admins? Are we trying to artificially create a difference where there is none? Or is the difference there – Buddypress is just not making it clear enough?

    Permit me to add fuel to the fire —
    1) I find Buddypress.org’s support forums to be virtually un-navigable. Compare that to bbpress, or even the WordPress support forums – which are clean, intuitive, and user-friendly (and in the case of bbpress, dying a slow death). So Buddypress is not a forum. But it has that potential.
    2) Buddypress hides blogs in the sea of sameness — basically taking over your entire WordPress site and subjugating the blog to the needs of the community theming. So Buddypress is not a Blog.
    3) Buddypress theming is so complex that only the brave dare tread there. Whereas I could bang out a unique wordpress theme in under an hour, Buddypress essentially locks you in to a handful of themes or days of tweaking…

    Don’t get me wrong. I think Buddypress is AWESOME! And has so much potential. I think, as others have pointed out, it suffers from an Identity crisis. So, what is Buddypress?

    Buddypress is a VITAL but SEPARATE part of the blog community. Buddypress is a way to connect. It is NOT a blog. It is NOT a forum – but a way for Forum users and Blog readers to connect with one-another. So – why not take that idea, and put Buddypress in its own room – the cocktail party happening next to the lecture seminar and just down the hall from the AA meetings.

    Proposal (largely a strategy of theming):
    1) Blogs are blogs – let them look like blogs.
    2) Forums are forums – let them look like forums (subjects, topics, you know… like forums)
    3) Buddypress is Buddypress – when people enter the social area of buddypress- lets knock their socks off.

    But trying to mesh them all under one Tabbed upon sub-tabbed menu system only whitewashes the whole deal into one bland sameness. And confuses our users.

    Discuss amongst yourselves. I think I posted this in the right place.

    -Driftless

    ** Forgive me, I wanted to post this on the What is Buddypress forum topic, but I couldn’t find it again… (see fuel #1)

    #88398
    Beck B
    Participant
    #88390
    pcwriter
    Participant

    @jonnylons

    Don’t know about the post, but here’s the plugin:
    https://wordpress.org/extend/plugins/adminimize/

    #88388
    jonnylons
    Participant

    And that old post is located where exactly? Cmon people – share!!! ;)

    #14116
    Driftless
    Participant

    I am experiencing strange User Role behavior with Groupblog:

    I created a private (or public) group and group blog (with links to the blogs front end) with default role pairings (user=author, mod=editor, admin=admin) — the blog was created successfully, and invitations were sent out.

    But my subscriber had only a subscriber role on the MAIN BLOG — When they try access http://www.example.com/blog1/wp-admin they get sent to http://www.example.com/wp-admin/?c=1 (which incidentally kills my dashboard hide script…)

    THEN, I changed the member/subscriber to moderator (by the groups admin page) and this gave them Author privileges… ON THE MAIN BLOG! No role for the group blog.

    WP: 3.0.1
    BP: 1.2.5.2
    Groupblog: 1.4.4

    (originally posted here: http://wordpress.org/support/topic/plugin-buddypress-groupblog-two-error-reports?replies=3 but figured this might be a better area to seek help)

    #88317
    Beck B
    Participant

    I was going to do the remove thing, too–so thank you all for the tips–but then I decided I might as well just hide the admin bar from logged out users, as that was my bigger concern with the random visit.anyway. (I don’t think it’ll be especially useful, and our groups are mainly private, but I don’t have any other plans for the top right portion of the screen, so…might as well leave it for now.)

    #88203
    Driftless
    Participant

    @intimez – good info – thanks.

    I also came across this code: https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/removing-members-ability-invite-others-to-a-group/#post-48304

    Which promises to hide the “invite friend” links (haven’t had success yet…)–

    Or you can create a child theme that removes the links from your template… Though really, I agree the system should be more set up like this:

    Public — anything goes
    Private — only mods and admins can INVITE (not just approve)
    Hidden — same as private – only others can’t see

    Cheers

    #88202
    Trivikrama
    Member

    Hi, I too want a solution for the same problem just like you. I want to hide admin and sitemanager from the members list. I was searching everywhere for it. If you know something about it just send a message to me to my profile. Waiting for your reply…..Plz….

    #87968
    imjscn
    Participant

    In general settings, “Hide admin bar for logged out users? ” , I select “No” , and when I log out, I can see the Admin Bar, but there’s no “SignUp”
    ???

    #87870
    JackTheKnife
    Participant

    Ok, I found an old post with good plug in to Adminimize this :)

    #13992
    JackTheKnife
    Participant

    Is there any way to hide /wp-admin for all non-admins? Thanks

    #87623
    intimez
    Participant

    @marianbuchanan

    Try this:
    Dashboard – Buddypress – General Settings
    Hide admin bar for logged out users?: YES

    #13781
    en0ch
    Member

    I was a little surprised to note that, with the admin bar enabled, a visitor who’s not logged in to my site can successfully visit a random member. As far as I can tell there’s no way of turning this off. Granted, they don’t get a link to the member’s e-mail address; but I can think of plenty of people who would be uncomfortable about even just their name being available to all and sundry. (And that’s not to mention danger for children online, etc … )

    Now of course you can turn this off by simply selecting the general setting to hide the admin bar from anyone not logged in. But that hides other stuff that would be useful to have sometimes. So I’d like an optional setting to block this access. Maybe it could be done by making the hide admin bar setting more sophisticated – so you can select parts of it to show or hide from users who are not logged in?

    justbishop
    Member

    I have a sitewide tag search blog up using the Sitewide tags plugin for WPMU. I have a special BP child theme that I’m using to integrate it inot the main site. My question is how could I hide the “Blog Owners” menu item from the admin bar for ONLY this child site (so that it looks exacly like my main site’s bar)?

    I tried doing display:none; on #bp-adminbar-authors-menu in the CSS, but that didn’t do anything. I know it’s way wrong (because it didn’t do squat when I tried it), but I also tried adding this to my child theme’s functions.php

    function bp_adminbar_authors_menu() {
    global $bp, $current_blog, $wpdb;

    if ( $current_blog->blog_id == 12 || !function_exists( ‘bp_blogs_install’ ) )
    return false;

    Anyone know how I’d do this?

    #86599
    Sofian J. Anom
    Participant
    #86595
    B.
    Participant

    Looks like I spoke to soon. Peters Login Redirect Plugin (https://wordpress.org/extend/plugins/peters-login-redirect/) takes advantage of the filter added in 2.6.2. You can read an article about the plugin here http://www.theblog.ca/wplogin-redirect. If anyone else has other ideas let me know. For now I’m just going to send all subscribers to edit profile page upon login from the wp-admin section.

    Vera Schafer
    Participant

    I was having a hard time trying to find the .htaccess file on my iMac, until I figured out that it is a hidden file (I’m working on MAMP Pro). If that is your case (Mac) , you have to unhide it.

Viewing 25 results - 726 through 750 (of 915 total)
Skip to toolbar