Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'theme'

Viewing 25 results - 18,976 through 19,000 (of 31,073 total)
  • Author
    Search Results
  • #112597

    In reply to: Forum Tags are HUGE!

    Hugo Ashmore
    Participant

    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.

    #112594
    Hugo Ashmore
    Participant

    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?

    #112591
    Paul Wong-Gibbs
    Keymaster
    #112588
    Paul Wong-Gibbs
    Keymaster

    No, no; don’t start hacking WordPress or BuddyPress core files. You will cause yourself problems with upgrades in the future. This thread was 1.5 years old before ivanoats replied to it; ivanoats, I’m going to close this thread, but could you please make a new post with fuller details of what you’re trying to do, what you’ve done so far, the error you’ve got, the theme you’re trying to use, and the version numbers of BP and WP. Thanks.

    Paul Wong-Gibbs
    Keymaster

    Again — the group blog plugin requires multisite. You can enable BP Group Blog all you want, but unless you have multisite enabled, you will always get this problem. Yes, this means the BP Group Blog plugin isn’t very well written, but that’s not core’s fault.

    #112582
    1stAngel
    Participant

    BuddyPress Theme Compatibility

    #112576
    Virtuali
    Participant

    Have you modified any files in your theme, or the plugin in any way?

    #112573

    In reply to: Double Trouble

    Virtuali
    Participant

    1st angel, do a favor for me. Testing this out to see if it fixes the problem.

    Go into your FTP or wherever you can access your files from, and go into the plugin folder “template pack”, and open the file called “bp.css”, it should be a CSS file sheet. Open the file, and **BEFORE you do anything, copy all the contents and paste them in a notepad or wordpad document.

    Now, delete everything in the CSS file, and save it. Go to your site, you might notice some things are changed on your bp elements.

    Go to the friends directory, and tell me if it fixes it.

    If it doesn’t, go into your theme’s members/members-loop.php and delete:

    #112571
    @mercime
    Participant

    @1stAngel I have not used the Atahualpa theme but try adding this to your theme’s style.css file :

    `/* Inherit the default theme adminbar styles */
    @import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/adminbar.css );

    #112567
    Ivan Storck
    Member

    Hi John, could you please elaborate on this error and how to include bp-sn-parent? I am seeing a similar error on a site using Arras theme and thought I had followed all steps to convert it to BP. The error I am seeing is Fatal error: Cannot redeclare class PHPMailer in /home/northat/public_html/wp-includes/class-phpmailer.php on line 34

    #112564
    1stAngel
    Participant

    @mercime I didnt but some strange things have happened recently and I had to remove some plugins. I have a feeling they have messed me up somewhere.

    I have a job to make sense of my theme as it is Atahualpa but I will go see, thank you

    #112562
    @mercime
    Participant

    == but suddenly the admin bar is in a list under my site ==

    @1stAngel Did you change/edit your theme? Check if adminbar.css is still being called – look at header.php source code.

    #112549
    ARHistoryHub
    Participant

    Okay, I gotcha. In order to place pages before the default buddypress menu tabs, you need to modify your theme’s header.php file. Look for some code that looks like this and paste it just after code that looks something like this <div id="header"><h1 id="logo"><a href=&quot;" title=""></a></h1>

    Now your pages will appear before your buddypress menu items. If there something specific you want, you can just hard code in the header.php file with good ole fashioned html.

    Oh, and that Exclude Page plugin will allow you to easily hide pages you create from being added to the menu.

    thanks

    Paul Wong-Gibbs
    Keymaster

    Not just you! We know about it and, in fact, it is being looked at by top men. Top. Men.

    http://www.youtube.com/watch?v=yoy4_h7Pb3M ;)

    #112545
    1stAngel
    Participant

    I have the in footer.php and did not do anything to the theme but suddenly the admin bar is in a list under my site.
    Please help someone… it’s a long way down :(

    #112543
    ARHistoryHub
    Participant

    1. Go to members/single/profile/edit.php in your theme.
    2. Find and delete this line `

    `
    3. Paste this `

    ` after each instance of this line ` `.

    And it’s a similar sort of process for the register.php – found in the registration folder in your theme.
    Sloppy, but oh well.

    #112530

    In reply to: help with ads pleases

    ARHistoryHub
    Participant

    @dubsel Are you using the BuddyPress sidebar plugin? Or perhaps widget logic? If using those plugins still don’t allow you place widgets where you want on the specific pages you want, you could always roll up your sleeves and do some customization with your buddypress theme and what it calls for the sidebar on specific page templates.

    #112529

    In reply to: Page level privileges

    airpilot
    Member

    Hi pcwriter:

    Actually, I want to do the reverse of what you outlined – I want to allow a S2Member #1 (contributor) member to have the expected read-only access to the entire website, EXCEPT I want that same member to also have edit capability on two pages of the website only. In other words, I don’t wish to restrict this member from any pages, but instead I wish to grant that member edit access to two pages he would ordinarily would only be able to read, as well as read access to the rest of the website.

    I appreciate your help. I’ll also query the primothemes forum, thanks.

    You call this fun??? ;^))

    Airpilot

    #112527

    In reply to: Old Buddypress theme

    @mercime
    Participant

    @djpaul Got delayed but working on it :-)

    #112512
    dainismichel
    Participant

    i think studiopress genesis theme framework + genesiconnect has this as a theme setting

    Paul Wong-Gibbs
    Keymaster

    The group blog plugin requires multisite. To fix for now, rename /wp-content/plugins/ and then visit /wp-admin/plugins.php in your web browser. Then you can rename the plugins folder back, then you’ll have to reactivate your original plugins again.

    Hugo Ashmore
    Participant

    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.

    #112462

    In reply to: Old Buddypress theme

    Paul Wong-Gibbs
    Keymaster

    Yes, but I don’t think it will work on the current version of BP. However, I think @Mercime is working on creating the same style for the current version

    #112440

    In reply to: Page level privileges

    pcwriter
    Participant

    @airpilot

    The easiest way to set this up with s2member would be to go to the user’s profile in your WP backend and assign that member the “Role” of “s2member Level 4”. Then go to edit the page you want to restrict access to and, in the “s2member” section at top-right, select “Require Level #4” at “Page Level Restriction?”. I haven’t tried this myself, but it should work to restrict access to that page to only those members who have a Level 4 membership (whether paid or not, doesn’t matter).

    For even more granular control, see the following 2 sections under “s2member” > “API/Scripting”:
    “Using Advanced Conditionals” & “Custom Capabilities”.

    If you need more help with this plugin, the best place to go is their support forum: http://www.primothemes.com/forums/viewforum.php?f=4

    Have fun! :-)

Viewing 25 results - 18,976 through 19,000 (of 31,073 total)
Skip to toolbar