Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'test'

Viewing 25 results - 7,851 through 7,875 (of 11,607 total)
  • Author
    Search Results
  • #91805

    Works for me on latest Firefox and Chrome on Windows (XP i think, am at a client site)

    #91739

    In reply to: Facebook Connect Help

    Try uploading a file named fbtest.php with the following content in the folder where your WordPress resides.

    <?php
    /* You can delete this file safely.
    It was just to check if its conflicting with other WP stuff - Ashfame */
    require 'wp-load.php';

    if ( function_exists('jfb_output_facebook_btn') )
    {
    jfb_output_facebook_btn();
    jfb_output_facebook_init();
    jfb_output_facebook_callback();
    }

    ?>

    This should bring up the FB button if everything is fine at WP side.

    #34874
    zthornto
    Member

    Hey All

    Looking for a way for the admin to approve any newly registered users using the latest version of bbpress.

    I know there’s a plugin out for this, but it doesn’t seem to work past version .9

    Has anyone figured out a way to do this (or a workaround) that works for version 1+?

    This is very vital to the forums I’ve set up so I’m really hoping there’s a fix out there!

    thanks in advance for any insight

    #91769
    chrishajer
    Participant

    1. The warnings are from using PHP 5.3 on Windows (normally.) If you can use PHP 5.2 that would be better. If not, you can download the latest trunk version instead of 1.0.2 as the warnings will not occur with that version.

    2. If bb_ tables are present in the database you are using when you go to reinstall, the installer will complain that bbPress is already installed. So, drop the bb_ tables or use a different database.

    3. Where is your forum actually installed?

    http://www.happybod.com/happybod_web/forum/

    or

    http://www.happybod.com/forum/

    I am guessing it’s the 2nd location since the first looks like it contains the file system path from your host. Your WordPress files are probably installed in the happybod_web folder and accessible at http://www.happybod.com/ (right?) If so, and you placed a “forum” directory inside happybod_web, at the same level as wp-config.php, then your forum will be located at http://www.happybod.com/forum/

    #91629

    Ash mate, you know how much I like you and your work, but that poll is never going to give even close to an accurate figure. To start with you don’t know why people are voting for each one, or how often, or who’s voting.

    I mean, Matt came on here and said that 0.9’s not been looked at in a long time and BAM 1.1 starts to get more votes. Matt forgets to mention, the 1.0 branch has had the same number of releases in the last year as the 0.9 branch: namely 0 !!

    How much the 0.9 version has actually gone through testing and how much we can be confident it being secured.

    Well it’s had 2 years more testing than 1.0 in the wild, and generally (apologies in advance) by people who are happier coding/debugging/ working without a GUI than the folks using 1.0 branch. Plus, the WP forums were running 0.9 until last August (at least), so it was known to be very secure then.

    I know it may contain bugs, any code can but my curiosity lies in the testing & use it has gone through already.

    A sh*t load more than 1.0.

    Rememebr 1.0 was (another) rewrite decreeed from “above”, and we cancelled all Beta testing, and it took 10 alphas to even get useable (pres Alpha6 isn’t compatible with after-alpha-6), and broke most plugins etc. The process of getting 1.0 out the door also led to some of the real wizards leaving the project behind (see Chip Bennet, Justin Tadlock, JJJ, _ck_ etc), and released it in a week, and we released an update to 0.9 at the same time as 1.0’s last update :)

    In my opinion, as someone who uses both; 1.0 only has 2 things going for it: The Admin section and it has more Actions/Filters.

    Replicating actions/filters into 0.9 is easy. As _ck_ said, getting a nice looking UI into 0.9 is a mini project.

    ==============================================

    1.1 has some good work, nae, some great work.

    It also has some rusheed work, to get it out the door for testing.

    It has at least 1000 lines of changed code last I checked (and that wasn’t today or yesterday) and we still have 10 tickets open – all before we release for Alpha testing, and all before we get a new package of BackPress released (in theory) after WP3.0.1’s release.

    If we finished all of those tickets this week, and packaged an Alpha testing release for Monday, there is no way 1.1 will be released before September. Infact, we’re looking at a late-September/October release at a minimum, unless we skip testing and bug fixes (again).

    Lets take our time and look at 0.9 objectively when 1.1 is close to coming out. Rushing into forks is just as dangerous as rushing into WP-reliant plugins :)

    Ash mate, you’re a very smart guy. Go grab a busy forum and duplicate it on your machine, and convert to 0.9. You’ll very quickly see some of the small issues with it, but you’ll also be amazed at just how quick and robust it is.

    #91627

    @_ck_

    How much the 0.9 version has actually gone through testing and how much we can be confident it being secured.

    I know it may contain bugs, any code can but my curiosity lies in the testing & use it has gone through already.

    If considered a fork, I think we need a few people on whom the people can count on for security updates.

    What do you think?

    #91724
    XU3E
    Member

    For example “test” and it find nothing…

    [solved] It looks like it was fault at user role capabilities. But I am not sure.

    #91753

    _ck_,

    More truly excellent work.

    I offered a different solution though, it’s a geneology plugin thats currently with a few folks for testing. It is far from as elegant as this (though it’s scope is wider).

    One of the things that I’ve “diskiked” about bbPress is lack of support for heirarchies. I know you’ve written some excellent code for finding the last poster for forums with sub forums before, but like the code above, they’re all workarounds.

    It also makes it difficult for theme developers to get on board when wanting to call basic API functions for “last poster” for a forum or topic etc. At some stage, I’d love a discussion on small things like this where we could improve bbP0.9

    #34860
    _ck_
    Participant

    I’ve noticed that depending on the site configuration, many times plugins or template designs will require information about the first poster in a topic or the last poster.

    The problem is that bbPress unfortunately (even in 1.1) only caches the post authors that are on the physical page you are on. So it causes two “out of flow” queries (one for user, one for usermeta) for each of those authors (first, last).

    This means up to four needless queries are added depending on the topic page number (not first or last is the worst hit).

    Even worse there is no direct filter/action on that process so it cannot be affected directly.

    However I’ve come up with a workaround using a trick,

    by catching the actions before and after the process.

    I’ve only tested this on 0.9, but in theory should work in 1.1

    if (is_topic && !is_bb_feed()) {
    add_action('bb_topic.php_pre_db','usercachefix_load');
    add_action('bb_topic.php','usercachefix_unload');
    function usercachefix_load() {add_action('get_forum_where','usercachefix');}
    function usercachefix_unload() {remove_action('get_forum_where','usercachefix'); global $posts; unset($posts['first'],$posts['last']);}
    function usercachefix($x) {global $topic,$posts; $posts['first']->poster_id=$topic->topic_poster; $posts['last']->poster_id=$topic->topic_last_poster; return $x;}
    }

    Make it into a mini-plugin and give it a try.

    You really only need it if you are showing info about the first and/or last poster on every page of the topic.

    You should see the query count go down by two to four queries on the page.

    Or use bb-benchmark to more closely examine the queries and look for multiple calls to the user-table and usermeta-table.

    #91517

    In reply to: Better Profiles….

    nickaster
    Member

    So… anyone got a clue what might be missing here? Here’s the test forum – http://www.triplepundit.com/forum … I suspect I’m missing something in one of the templates?

    #34858
    XU3E
    Member

    Filtering (searching) of users in admin is not working properly… Yeah, is not working at all.

    The Latest version with BP and WP 3.0.

    #91567
    Marius-
    Member

    Smartest thing I´ve ever said.

    #91560
    Marius-
    Member

    So Social It is what causes this problem?

    How come all other topics looks okay? But this topic suffers, and all others created afterwards?

    I just created three test topics which all suffered from the same bug.

    #77641
    zaerl
    Participant

    Of course. I was ironic.

    #77640

    Well, bbPress as a plugin is official bbPress fork. ;)

    Ha :)

    It’s really not.

    It’s a totally new progam with the same name.

    #77639
    Milan Dinić
    Participant

    There’s an official bbPress fork?

    Well, bbPress as a plugin is official bbPress fork. ;)

    #34850
    WP Realty
    Member

    I’ve installed an integrated WordPress 3.0 (NOT MU) and the latest BBPress. When users register with WP they can not add any reply or start a new post in the forums.

    I tested this with the default unaltered theme and same thing.

    Looking in the DB I see that each member is a “member” in WP but there is no BB_METAUSERS table for bbpress. I think this isn’t required when an integrated solution is installed.

    Any idea why all new members are set to “Inactive”?

    J

    #77638
    zaerl
    Participant

    offical bbpress fork

    There’s an official bbPress fork?

    #77637
    XU3E
    Member

    This is realy good plugin but Its not working properly with new versions bbpress. _ck_ doesnt support it anymore because his own branch for 0.9.

    Its fantastic oportunity for someone skilled to take this for keeping update with offical bbpress fork.

    Perhaps… it should be implement in bbpress core or bb-plugin.

    #91464

    In reply to: Front-end editing

    Erlend
    Participant

    @Gautam

    By that you mean front-end posting with the native WP editor, right? Not an included, new editor, the way bp-wiki or scribu’s editor currently does it?

    Because when I’ve applied a plugin to extend the WP editor, that should apply to the front-end editing as well.

    Thanks for the hint about image uploads with P2, I hadn’t noticed the feature. I’ll probably have to do a fresh test install though, because it’s buggy on my current one. Will report back my experiences later.

    #91265
    Greg
    Participant

    Matt, you are partially correct. A lot of this is about where the line is drawn. But I guess I also added another line. This has been the topic of discussion in WP before, but I think the concept of a *core plugin* is important.

    A core plugin is released along with the real core and is held to the same release criteria (testing) as the real core.

    Maybe this is semantics and you would just call a core plugin part of core. If so, that’s great, but I would still suggest that we talk about three things…

    1. the real core

    2. core plugins

    3. general plugins

    Referring back to your original framework, I think two of the criteria for core apply to the real core:

    – essential for robustness

    – something we want to promote

    If it is something the majority (80%+) will appreciate then it could be released in the real core OR as a core plugin (e.g. akismet).

    The benefit of a “real core + core plugins” approach is that it eliminates the conflict when something has both majority appeal AND connects to a service (again, akismet example).

    It also eliminates a lot of the angst people have about additional bloat in the real core, or about the quality concerns for important plugins.

    Bottom line: you can have your cake and it it too. A core plugin does not add bloat, AND it is released with all the QA of a feature in the real core.

    #91450
    _KB_
    Participant

    @kevinjohngallagher thanks dear, I’ve done it already, its a part of integration, But I really surprised why its won’t work for me??

    but I’m curious that may be _ck_ tell me new thing.

    OK, I’m going to disclose my config files and cookies, check it dear buddies….

    for wordpress,

    http://pastebin.com/embed_iframe.php?i=hPpMiDyZ

    for zptest students

    http://pastebin.com/embed_iframe.php?i=jcS2377M

    If you need more things, I’ll share it..I really want to fix it….Thanks

    #91055
    Joe Gibson
    Member

    Z – I got on a bbPress plugins page and found your ‘Open in new window’ plugin but the rascal doesn’t seem to work. Tried it in both ‘bb-plugins’ and ‘my-plugins’. It activates just fine. Is there a trick I’m missing?

    Thanks,

    Joe

    #91054
    Joe Gibson
    Member

    Z – Thanks, the ‘s’ did it. Very appreciated.

    The one last thing that would really make this editor the cat’s ass would be opening links in a new window. Is there a PHP version of “Target=_blank” we can slip into the code?

    Joe

    yetanotherlogin
    Participant

    To have WP send my admin password, I edited php.ini to use my ISP’s SMTP server instead of “localhost” (no SMTP server on this test host), restarted PHP-FastCGI, and clicked on the WP “Lost your password?”, but I get this:

    “The e-mail could not be sent.

    Possible reason: your host may have disabled the mail() function…”

    So can’t get the admin password back. Anyway, since it doesn’t complain about the password and just loops back, I assume it has to do with the WP/bbPress integration?

Viewing 25 results - 7,851 through 7,875 (of 11,607 total)
Skip to toolbar