Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'code'

Viewing 25 results - 20,826 through 20,850 (of 32,481 total)
  • Author
    Search Results
  • #89921
    _ck_
    Participant

    Plugin: Allow additional or custom profile fields

    Adding Custom Profile Fields

    Add New Fields to User Profile?

    Customizing Profile Fields

    Help with Basic Command to Add New Profile Fields

    http://google.com/search?q=site%3Abbpress.org+extra+profile+fields

    Since bbPress doesn’t have a dropdown generator, it’s obviously going to need custom code. You can’t set it as a profile key because bbpress won’t properly handle the output/input.

    There is an action hook do_action( 'extra_profile_info', $user->ID );

    which appears at the end of the regular profile block.

    That’s where the data has to be shown.

    However the data will not be saved by bbpress because it’s not in the profile keys.

    What could be done is the profile keys could be unset when actually on the profile edit page, but exist otherwise – there is a sanitize filter that can be used:

    $$key = apply_filters( 'sanitize_profile_info', $_POST[$key], $key, $_POST[$key] );

    Or sanitization and saving could be done manually at do_action('profile_edited', $user->ID); by checking $_POST

    So it’s a non-trivial amount of work which is why dropdowns are not already done via a plugin.

    If I get through tomorrow without a migraine I might show you how to do a Male/Female dropdown.

    Hi Taeo,

    You’re absolutely right.

    I doubt anyone here has a problem with Automattic making the best choice for them in the long run. Even if it’s not ideal for everyone; if the good outweighs the bad for a large percentage of people and it gives Automattic another feature to give their users then I can totally see why they’ve come to this decision.

    The issue I have personally, isn’t with the decision (or indeed any decision that Automattic have made), but rather the way that information is passed along (or, ususally, not passed along).

    To delete the bbpress0.9 milestone and decide to go back on your word to support it for 2010 without telling anyone – even weeks after you deleted it, is symptomatic of how Automattic treat the people involved with this project.

    Matt’s word carries alot of weight, especially with WordPress users, so to make dispariging / negative / insulting comments about us in his KeyNote speech is poor. I realise that he was answering a question, and not a prepared statement; and we’ve all answered questions badly before, but it was a slap in the face to those of us who’ve given up our time.

    Given that the 1.0.3 milestone has a year’s worth of bug fixes, and NOW isn’t going to be released until all the 1.1 bugs are finished AND a new backPress is released – though thats not been communicated to anyone yet; it makes it hard for those of us who have gotten behind bbPress to draw a line under it.

    It’s also why this talk of a Fork is premature. Because when 1.1 gets released, there will be a swell of “bbpress is not dead” euphoria – much in the same way there was when Matt came back in December and when the new theme got uploaded. For me, I just want to get my current forums patched up to work the way bbPress1.0 was meant to and be treated like an adult until that happens.

    BTW Taeo, I miss not being able to recommed your UI ;-)

    #90046

    In reply to: How can I do this?

    Yes, it’s possible, but you’d have to entirely code it yourself.

    It’s not a plugin thing or something we could write for you.

    Also, unless its very particular and of interest to the people taking the quiz, it’s a horrible thing to do.

    Taeo
    Member

    He even admitted that right now, it would be better off to use another plugin rather than bbPress.

    I agree that this seems very insulting but you have to keep in mind Matt’s target audience. Matt and Automattic are concerned first and foremost with WordPress. And the vast majority of WordPress users are not the people involved in this thread – they are bloggers and publishers with very little knowledge of code. For them, the easiest forum solution is a WordPress plugin. We know better here at bbPress.org but we make up a very small (albeit vocal) minority.

    Knowing this, it is difficult to imagine the future of bbPress (under Automattic) as anything other than a “core” WordPress plugin. I think your concerns with this, Zaerl, and Kevin, are completely reasonable. It will absolutely be less lightweight than bbPress is now. I have no doubts of that although I am confident the WordPress team will minimize the hit in every way possible.

    However, for me personally, the good outweighs the bad. I basically make a living off of customizing WordPress templates for people and I will be very happy to have an easily implemented and officially supported forum solution to offer my clients. I am almost sure this is how the majority of WordPress users also feel.

    Unfortunately for those of you who want bbPress to remain a standalone solution I think your time is limited. Even if Automattic wanted to keep bbPress as a standalone solution I don’t think they have the developers to do it. If this is what you really want I think the only choice is to do it yourselves. Whether that means forking or taking some of the core and rebuilding completely – one of you will simply have to take charge on your own and forget Automattic.

    I know that sounds harsh – I’m not trying to mean – I totally understand where you guys are coming from. I just think this is the unfortunate state you are in.

    Rootside ::

    Has anyone considered the possiblity that Matt is keeping his eyes peeled on the current efforts of some people trying to use nothing but WordPress’ core functions to build a simple forum?

    He might be mate, but probably not, as doing so isn’t that difficult at all. I creted a “theme” for WordPress that made it look/work like a forum in essence back in 2008. The same time I made and released the phpBB theme for bbPress. Both were availible on the bbProgress website (which closed last year but there should still be some links on t’internet).

    And Justin’s coding one based on the new Custom Post features, which will work alot better than mine did (he actually build one last year too, but had a hard drive crash and lost it).

    Basically though, a blog and a forum are different in their “n to n” nature. WordPress relies on a huge amount of caching to try and keep it’s memory intake down, and a customised caching mechanism is essential once you hit any form of modernday traffic. That sort of feature works well on “1 to many” software, but a forum is different. It has to call data differently, and handle multiple parent/child relationships.

    Rootside ::

    I’m guessing that any WP plugin which makes that kind of thing easy to set up and enhances its functionality would be really lightweight.

    No, no way mate :( The opposite.

    I understand the desire to make a WP plugin that is a forum, I can see Matt’s viewpoint on that, but in comparison to bbPress as it stands, it’ll be far from lightweight.

    Not only will it struggle with the caching that WP relies on, but you’ll have all the overhead of loading everything in WordPress before hitting any actual forum content (including the WordPress admin sections and plugins).

    It’s basically going to be very similar to the BuddyPress “bbPress” plugin, as thats a hacked/stripped version of bbpress1.0 (in general terms it removed BackPress and rewrote the function calls to call WP/buddyPress functions directly). But in order to get it to work, every page has to load WordPress then BuddyPress then bbPress forum module.

    Lightweight it ain’t!

    Even if the very clever people that work at Automattic and contribute to the community manage to pull a great number of rabits out of hats, there is no way that it will be anything but bloated.

    But you know, 90% of folks won’t care. Take Marius (poster above me), he runs a forum about Michael Jackson with aboot 100+ users and maybe 50 topics started a week. He’s not that uncommon to alot of the folks that pass through here (other than that he is allergic to manners). They won’t care in the slightest about the small hit as the chances of them noticing it are going to be slim, and they get access to all the good stuff that comes with WordPress, heck for the most part they’ll get the stuff they think they should from bbPress/Wordpress integration now. For a percentage of people, there will be no downside, even if it’s far from lightweight.

    I realise that software moves on, and I realise that as it grows there will be some bloat. Thats the reality of where we are, and WordPress does a really great job of being quick despire it’s bloat. But the sheer difference between a bbP0.9/WP2.5 deeply integrated forum (which has MORE features than we have now) and a bbP1/WP3 deeply integrated forum is unbelievable. Bloated, slower, more prone to errors and less features.

    I see why Matt thinks things have to change, i don’t agree with the direction and thats cool, i don’t have to agree, nor does anyone :)

    But really the history of this project has taught us one thing repeatedly: Heading in a direction without planning or a roadmap will definately lead us somewhere else, but we’ll be just as lost. Who knows though, 40 years later he may just lead us out of the desert ;-)

    Hopefully on Matt’s way up to Montreal he’ll see a burning bush ;-)

    #89684

    I can answer that Chirs.

    If you type in , you get a [code] HTML output.
    If you type in a [backtick] you get a [code] wrapped in a [pre] tag (which is right so formatting is preserved as well).

    The [pre] tag is the one that has the cool style on it.

    #bborg-discussion #thread div.post pre {
    background-color:#FFFFFF;
    border:1px solid #EAEAEA;
    display:block;
    overflow:auto;
    padding:10px;
    width:528px;
    }

    Don’t you just LOVE this new untested theme with all these wonderful hacks?

    [code], you get a HTML output.
    If you type in a [backtick] you get a [code] wrapped in a [pre] tag (which is right so formatting is preserved as well).

    The [pre] tag is the one that has the cool style on it.

    #bborg-discussion #thread div.post pre {
    background-color:#FFFFFF;
    border:1px solid #EAEAEA;
    display:block;
    overflow:auto;
    padding:10px;
    width:528px;
    }

    Don’t you just LOVE this new untested theme with all these wonderful hacks?

    [code] HTML output.

    If you type in a [backtick] you get a wrapped in a [pre] tag (which is right so formatting is preserved as well).

    The [pre] tag is the one that has the cool style on it.

    #bborg-discussion #thread div.post pre {
    background-color:#FFFFFF;
    border:1px solid #EAEAEA;
    display:block;
    overflow:auto;
    padding:10px;
    width:528px;
    }

    Don’t you just LOVE this new untested theme with all these wonderful hacks?

    [code] wrapped in a [pre] tag (which is right so formatting is preserved as well).

    The [pre] tag is the one that has the cool style on it.

    #bborg-discussion #thread div.post pre {
    background-color:#FFFFFF;
    border:1px solid #EAEAEA;
    display:block;
    overflow:auto;
    padding:10px;
    width:528px;
    }

    Don’t you just LOVE this new untested theme with all these wonderful hacks?

    #90020

    There have been a huge increase in the number of reported WSoD reports with WP3.0, and thankfully the WP team are taking notice.

    These plugins ( https://wordpress.org/support/topic/411649 ) are definately causing issues. HeadSpace2 is the biggie there as it’s a very popular plugin. I’m quietly confident that it’ll hit alot of people

    WPtaven has an article on it, though right now there’s alot of people saying how it was flawless for them (how that helps those who it wasn’t flawless for i’ll never know). You can find that here:

    WordPress 3.0 Upgrade Woes Starting To Come In

    Zaerl has written a plugin found here ( http://pastebin.com/JhJzLjvQ ) that solves one of the problems with WP3/bbP tha was brought up in this thread ( https://bbpress.org/forums/topic/wp-30-beta-2-integrated-user-registration ).

    Having seen the hit my servers are taking from WP2.9.2 -> WP3.0RC3 my first guess would be memory. Deep integration of WP3 and bbP1 appears to be a nightmare, especially when I look at my one site thats still running bbP0.9&WP2.5.

    Furthermore, I do believe we should start a “WordPress3.0 FAQ thread” that compiles what we know in the first post as a sticky. We’re going to face alot of questions in the next week or so, and maybe we could learn from some past mistakes :)

    #89998

    Eliminating the freshness column is easily done by the method Chris highlights, but it probably won’t have the affect you desire.

    Content is king on the web, regardless of when it was written :)

    Anyway, i piped up because you’ve an error in your CSS. In style.css on line 62 you have the following code:

    #wrapper {

    background:url("images/page_header_tile.png") no-repeat scroll 0 0 #FFFFFF;

    }

    you’ll want to change that to

    #wrapper {

    background:url("images/page_header_tile.png") no-repeat scroll center top #FFFFFF;

    }

    As currently the background image stays the same place while the forums are centered. Basically it looks broken on a bigger monitor, and it’s a quick fix :)

    Good luck with your forum!

    #90014
    zaerl
    Participant

    Not the access log (access_log), the error log (error_log).

    Marius-
    Member

    I think Matt sounded very smart. Like a young Steve Jobs.

    If what he say is true about BBpress just copying a bunch of wordpress code, making it hard to update, I think a plugin sounds greater.

    I dont see why this future plugins should be incompitable with my current installation though.

    As a user, I expect a future edition to carry on what I have now built.

    Themes is okay to renew, but my forum posts and users, I would very much like to keep.

    #90013

    Woah! That would be a lot of work.

    I tried this on my host and it seems that the problem is to do with WordPress 3.0 only cuz if I tell it to load wp-load.php from a 2.9.2 install, it works fine.

    But I have seen someone in some other topic running a deep integration with WP 3.0 :/

    @zaerl

    117.196.240.192 - - [19/Jun/2010:02:53:39 -0700] "GET /forum/ HTTP/1.1" 500 - "-" "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3"

    #90011
    _ck_
    Participant

    500 error might be from a looping redirect that never resolves.

    At this point if I was debugging it, I would put exit points in the code and find out exactly where it was failing. But it might take you hours to trace it that way.

    3.0 is so new and probably buggy, there could be a dozen reasons why it’s failing.

    #90009
    _ck_
    Participant

    This is just a complete guess in the dark but WP 3.0 is a memory hog and you might easily be running out of memory with deep integration. In theory you should get an error about the memory problem but maybe not.

    Try this in your config (probably wp-config.php and not bb-config)

    ini_set('memory_limit','64M');

    define('WP_MEMORY_LIMIT', '64M');

    also turn on all errors temporarily

    error_reporting(E_ALL);

    and make sure you try “view source” on that blank screen as there may be something you can’t see on the page.

    #34527

    I am deep integrating bbPress with WordPress 3.0 and I am encountering this white screen of death. I have done several integrations this way and never got stuck.

    I use this code above database constants in bb-config.php

    if ( !defined('ABSPATH') & !defined('XMLRPC_REQUEST')) {
    define('WP_USE_THEMES', false);
    include_once(dirname(__FILE__) . '/../wp-load.php' );
    header("HTTP/1.1 200 OK");
    header("Status: 200 All rosy");
    }

    I checked the logs and there are no 500 errors, all are 200.

    I loaded the WordPress in a separate php file which works fine, so I guess something is conflicting in between WordPress and bbPress.

    bbPress has no plugins installed but WordPress does have some and its a live site.

    I am going to check for any conflicting plugins.

    Any pointers?

    #34526
    NikonRumors
    Member

    Has anyone tried to install VigLink (http://www.viglink.com) affiliate program in bbpress?

    Where should I insert the script? The instructions are:

    This code should be inserted at the very end of your pages, just before the [/body] tag.

    The code needs to be present on every page where you’d like VigLink to work. The best way to install this code everywhere is to add it to your site’s template.

    Thanks!

    #89610
    wtfmatt
    Member

    @_ck_, okay. I’ll fork if you fork. Seriously. You have the power to get 50 of us following after you, and I know at least 2 big coders who would probably follow. I’m a nobody, please remember.

    @mr_pelle, EXACTLY.

    @zaerl, sounds like you support a FORK too?

    SCREW TRAC. SCREW IRC LOGS.

    And screw trying to heal bbpress’ relationship with Matt, it will never happen guys. WAKE UP. The man-child has too much pride to apologize and fix this mess. He will let it die on purpose, or suddenly delete this whole site and turn bbpress into a plugin of WP and remove all access to the old bbpress code and repositories if we let this crap continue.

    We need to mirror this entire domain’s code and plugins onto another server before its too late.

    Even if we wanted to harass Matt into giving us answers, he still wouldn’t do it. Seriously if bbpress is going to survive as a forum software, we need to FORK IT NOW.

    WimTibackx
    Member

    I think that with the new 3.0 Custom Post Type functionality, a lot could be done to simplify the current WordPress as blog vs. WordPress as CMS vs. Buddypress vs. bbPress clutter. It seems to me that there is no good way of combining them all at this very moment. In wordpress you can’t change nor delete the default post types. If you want bbPress you need to link it up and such. I think it would be better if the current project group evolved into (but who am I in the community ^^):

    *BackPress, which contains the whole base (a lot of things it doesn’t contain atm from WordPress)

    *Wordpress, which could just be no more then a plugin to BackPress (on the download page you should have the option to either download the plugin or backpress+plugin)

    *bbPress, (see wordpress)

    *BuddyPress, (see wordpress)

    This way, wordpress can evolve in a stable, clear and usefull cms. This way, development teams could be handled much more flexible (a team for backpress, and teams for the other projects only having to worry about the plugin).

    This would make it more clear for users and certain wanted features could be implemented much quicker. There should be, however, the functionality of having “plugins on plugins”, thus, plugins on wordpress, …

    Also, this way of working would permit developers to use the backpress/wordpress codebase without having the mess of the current post types. It would also ease combining these projects a lot.

    Last but not least, it would give the teams the oppertunity to clean up codebases (raise spec to php 5, more object oriented way of handling things, …)

    What do you guys think about it?

    As a final note, I’d like to say the following to the developing teams : work with the community, not against.

    Edit : And if there would be interested in starting such an initiative from the community, as automattic isn’t likely to do this, I’d be willing to help developing. If I’d had more time, I’d probably already started something like this, but I haven’t got the time to lead such a big thing.

    ckeck
    Member

    Long live bbPress — can’t the community just fork this project? I’d be more than happy to donate $ to this cause in lack of my development skills. I just want to see some MOVEMENT =

    #89996

    In reply to: Download location

    WimTibackx
    Member

    Thanks!

    Got it installed atm and works fine :)

    #89681
    chrishajer
    Participant

    Oh well :-(

    Trying


    <?php
    if (function_exists('phpinfo')) {
    phpinfo();
    }
    ?>

    [code]

    <?php

    if (function_exists('phpinfo')) {

    phpinfo();

    }

    ?>

    #89680
    chrishajer
    Participant

    Wow, backticks in this post actually formatted the code sort of nicely (with a white box.)

    TEST:

    <?php
    if (function_exists('phpinfo')) {
    phpinfo();
    }
    ?>

    #89679
    chrishajer
    Participant

    Throw the “folder” below WordPress.

    You should put it inside a FOLDER in the root of your WordPress site. The name of that folder determines the URL where the forum will be accessible on the Internet.

    So, if your WordPress site is at http://www.example.com/ , and you create a folder called bbpress in your WordPress root (and put all the bbPress files in there) then your bbPress forum will be accessible at http://www.example.com/bbpress/

    If you don’t want bbpress in your url, call the folder where you put the files something else. For example, here it’s called “forums”. You can use forum, discussion, community, etc. That will be part of the URL where you access the forum.

    /var/www/html/wordpress/wp-content/
    /var/www/html/wordpress/wp-admin/
    /var/www/html/wordpress/bbpress/

    That is where the folder will go; on the same level with wp-content and wp-admin. It is at the same level.

    #89995

    In reply to: Download location

    chrishajer
    Participant

    Your best bet is to download it via subversion. Grab the trunk release revision r2434.

    svn co -r2434 http://svn.automattic.com/bbpress/trunk ./forums

    That will check out revision 2434 which is very stable, into a directory called forums on your server.

    #89987

    In reply to: Password Problem

    johnhds
    Member

    Quite a few:

    allow images 0.9

    auto add favorites 1.0

    avatar upload 0.8.3

    bavatars 0.4.1

    bbcode buttons toolbar 0.0.9

    bbpress attachments 0.2.7

    bbpress recent replies 0.1b

    bbpress signatures 0.2.0

    bb wysiwyg editor 1.2.0

    custom rotating ads 0.1

    google sitemaps 0.1

    hot topic 0.0.1

    human test for bbpress 0.9.2

    image resizer 0.2

    prvate forums 5.0

    subscribe to topic 0.0.6

    social it 1.5

    terms of service 0.0.3

    topic icons 0.0.5

    user photo for bbpress 1.1

    xili new post notification (xnpn) 0.9

    Thanks

    I hope Matt just renames it to something else to prevent massive confusion.

    In the way he didn’t do with bbPress for BuddyPress?

    :(

    Why on earth it wasn’t called “BuddyPress forum plugin – based on bbPress” or an equivalent i’ll never know. All that does is make this community and this product look worse; as we fail to answer support questions over and over.

Viewing 25 results - 20,826 through 20,850 (of 32,481 total)
Skip to toolbar