Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'code'

Viewing 25 results - 20,476 through 20,500 (of 32,517 total)
  • Author
    Search Results
  • #34841

    Topic: something useful

    in forum Installation
    AaronIsaac
    Member

    Okay, first thing’s first… if this is the forum on the bbPress site itself, it really needs to be a bit more of a better example. As it is, when I get to the forum I’m first faced with a giant tagcloud, then I have to scroll all the way down past a huge list of posts to get to the actual individual forums such as this one. Of course, I could hit the button to start a new topic at the top of the top of the page but not only is that counterintuitive, it’s a really bad idea in general that will get people just Pcoming in and posting without looking at other posts first. I’d hoped the layout would have been changed by now at least.

    Second problem, and this is one I’ve had on the wordpress forums as well but never bothered to ask about it. At the bottom of the post box it lists allowed tags (shortly after mentioning “Enter a few words (called tags)” with a link to the tagcloud rather than a definition of tags), but what gets me is “Put code in between backticks.” I’ve been running forums since before ISPs could offer residential Internet connections and yet I have absolutely no clue what that means. Unless this software is only meant for WordPress users (which I’m one of, btw), it would be best to get a bit more accessible to ordinary people in terms of language/jargon.

    My other large beef is that the forums read like blog comments rather than forum discussions. Threading would be my number one request if I intended to use it. I guess my number two request would be integrating said threaded comments into the comments section of blog entries for those using it with a WP blog, though that’s a lot more complicated. I’d want to start off with the other way around by having the blog able to automatically display posts from certain sections such as Announcements and such. I’m not sure if that functionality exists yet, so apologies if it does. If not, I suppose a workaround could be reading the rss feed from that section into the blog section, but aggregating your own feeds is a fairly silly notion.

    That’s it for initial feedback right now. I may come take another look when the software has matured a bit… by that I mean the core, it shouldn’t have to depend on plugins and themes to have very basic funcionality on its own.

    #91589
    _ck_
    Participant

    It’s hand coded, probably into the template system.

    It’s parsing the readme.txt file.

    Far too custom that you’d ever find a plugin for it.

    It’s probably using in part some of the code from Mark Jaquith who designed the readme.txt format for Matt/Automattic and implemented by mdawaffe (Michael)

    http://wordpress-plugin-readme-parser.googlecode.com/

    hpguru
    Member

    I think bbPress standalone is dead in 2010.

    Matt Mullenweg: Non-plugin bbPress development is going to continue until we have a perfect importer so people will be able to bring their content out of the legacy codebase.

    bbPress 1.1 may be here.

    Greg
    Participant

    I guess one could also use the check on BBP_VERSION (or equivalent) to print an error message when the plugin refuses to activate.

    But a user would still need to install the plugin or look in the code (or read the README if the plugin author was good enough to mention the dependency).

    @_ck_

    Thanks a lot :)

    I am gonna ditch v1.0+ and start using 0.9 from now on. Will downgrade my other installations too.

    #91364

    In reply to: Registration Email

    _ck_
    Participant

    Oh sorry, I lost track, too many things going on everywhere.

    Save it into a plugin (ie. custom-registraton-email.php) put it into your my-plugins/ directory and activate.

    Gautam Gupta
    Participant

    One can easily do a check on activation if BBP_VERSION is defined and optionally a version_compare check too, and if it doesn’t satisfy the condition, then the plugin should deactivate itself.

    Greg
    Participant

    Hmmm. Seems that even the mod is hijacking threads on bbpress.org these days… :)

    Feel free to start a different thread to talk about the specific performance aspects of bbPlugin versus bbStandalone.

    One more attempt to focus this thread on the original question: I am interested in a discussion on the relative merits of evolving bbStandalone and bbPlugin independently versus in a coordinated fashion, NOT the relative merits of bbStandalone versus bbPlugin.

    Repeating the advantages of both, with one additional pro that I thought of for the coupled roadmap.

    Advantages of a coupled roadmap:

    – Higher quality for standalone (benefitting from the larger installed base of the plugin)

    – Better performance for the plugin (benefitting from the big standalone sites)

    – More tight WP integration is likely for standalone

    – Easier “cross-grades” between plugin and standalone version

    Advantages of independent evolution of the plugin and standalone versions

    – More flexibility in release roadmap for both versions

    – No compromises for either version

    #91527
    deadlyhifi
    Participant

    The plugin is Add bbPress Default Role. It’s three lines of code so you may be better just writing it into your functions.php file.

    _ck_
    Participant

    <cite>ashfame</cite>

    I guess all your plugins are tagged https://bbpress.org/plugins/tags/_ck_

    right?

    And I believe even your updated plugins support 0.9 ?

    Unfortunately the plugin section is still broken and does not import tags so the _ck_ tag is no longer complete there (update: someone appears to have fixed it in the past 24 hours)

    For now this is the only way to find them all:

    http://bbshowcase.org/forums/topic/_ck_-plugin-catalog-index

    Virtually 100% my plugins will support 0.9 (except ones specifically made to “fix” 1.x)

    <cite>Mark McWilliams</cite>

    Not with WordPres 3.0 anyway, 1 install, multiple sites! :)

    Well, multiple BLOGS, I am not sure if they can get multiple forums going on the first version, we’ll see. But I am sure it’s a goal of Matt’s so they can use it on WordPress.com

    _ck_: As far as I could guess, you’d have to install multiple copies of WP.

    Not with WordPres 3.0 anyway, 1 install, multiple sites! :)

    #91462

    In reply to: Front-end editing

    Erlend
    Participant

    @Ryan: I had JS enabled but.., aha, I never noticed the double-click edit upon mouse hover before. Neat :)

    Now, the thing I encountered in both the P2 theme and Justin’s forum plugin is: Neither (seems to be able to-) take advantage of WordPress’ own in-built rich text editor.

    I probably did not make this clear enough in my first post. My main point sort of ended up in the second to last paragraph:

    What I’d love to see is rich front-end editing based on the native WP editor

    What I’m inquiring about is:

    How to achieve front-end editing with WordPress’ native rich editor?

    The main question is of course ‘how will bbPress go about doing this?’, but clearly this method is still unbeknown to many plugin authors who could greatly benefit from it.

    (Disclaimer: My project relies on the bp-wiki plugin, and I am indeed curious as to the possibility of a a more conventional approach to rich front end edits in the future.)

    One ‘almost’ example I found is this one:

    https://wordpress.org/extend/plugins/tinymce-excerpt/

    It grabs the native editor and displays it somewhere new. However I suspect it can only do so because it’s still within the confines of the admin backend. Posting and editing content from front-end can clearly be achieved, but apparently with severe limitations. It’s getting functions that are normally limited to the backend (tinymce editor, file upload, etc) to the front-end that is awkward.

    Speaking of which, feasibility image/file uploads would make for an excellent follow-up question, but maybe you’d rather have me start a new thread for it?

    Erlend
    Participant

    Alright, appreciate the response. I think we’ve exhausted this discussion then ;)

    Matt Mullenweg
    Keymaster

    Non-plugin bbPress development is going to continue until we have a perfect importer so people will be able to bring their content out of the legacy codebase.

    #91264
    Matt Mullenweg
    Keymaster

    Greg, I think we agree, just have different ideas about where that line is drawn. I’ve laid out the core philosophy as a framework for discussions above. I have never advocated making every plugin a core feature, and conversely I doubt you’re suggesting making every line of code in bbPress a plugin.

    Balancing between the two is how development happens, and is best navigated in the context of a specific anchor (feature) rather than in abstract.

    Greg
    Participant

    I can see strong arguments for both a wp plugin and a standalone forum.

    Also, the reality is that both will exist in the future. The WP team is very passionate about “bbPress as plugin” and at the same time some existing large installations will see to the continuation of standalone version in some format.

    So it might be good to frame this decision differently than plugin versus standalone… The real question is: to what extent do we want the plugin and standalone versions of the bbPress code base to evolve independently versus in a coordinated way?

    Simplistically, the two options are:

    1. coupled roadmap with coordinated releases or periodic rev/fwd integrations

    2. independent roadmaps that diverge over time (the current plan of record)

    Both options (coupled roadmap and independent roadmap) can work, but it would be better for this decision to be the result of thoughtful discussion.

    To kick things off, here are some pros of a coupled roadmap:

    – Higher quality for standalone (benefitting from the larger installed base of the plugin)

    – Better performance for the plugin (benefitting from the big standalone sites)

    – More tight WP integration is likely

    And some pros of independent evolution of the plugin and standalone versions

    – More flexibility in release roadmap for both versions

    – No compromises for either version

    Another more subtle effect to consider is the impact on dev resources invested in the code base. For example, I think that there are currently a lot of “silent” but significant resources being invested in standalone bbPress development. It would be great to pull more of that work into the official project, but I fear that opportunity will go away once the move is made to “bbPress as plugin”.

    #91263
    Greg
    Participant

    Regarding Matt’s “”As for bundling multiple plugins with core — ultimately it’s a cop-out. If something is good enough to be included with the core download, put it in core!””

    I agree with everything johnhiler said on this, plus I would add that the advantage of core plugins is that their coupling with the real core will be more well defined and probably minimized. Making something a plugin puts a clear boundary around the set of features that it adds. It also guarantees that the real core can work without this functionality.

    Without this to enforce discipline on the design, things are far more likely to become highly coupled spaghetti.

    A related issue is core bloat. Something like Windows or WordPress adds features in every release and seldom removes them. The result is that the code base is monotonically increasing in size and complexity. It will ultimately collapse under its own weight. This means that significant rewrites become necessary from time to time.

    The Unix “small and decoupled is beautiful” approach is maintainable for much longer for this reason.

    Higher coupling does have its advantages (performance, UX), but they are usually short term gains, winning the battle but losing the war.

    #91544

    In reply to: Plugin alternatives?

    zaerl
    Participant

    Assuming that you are using the Kakumei theme open /bb-templates/kakumei/topic.php. The plugin instructions: https://bbpress.org/plugins/topic/live-comment-preview/installation/ suggest a good place for inserting that snippet of code. Right after <?php post_form(); ?> (line 45 in Kakumei topic.php template file.)

    Remember: Never touch core files.

    #91543

    In reply to: Plugin alternatives?

    Joe Gibson
    Member

    Z – I got to thinking and decided I’d better double-check and found “topic.php” in the root directory, so I presume that’s the one he meant. I tried slapping all five lines of code into it in three different places and got a ‘Parse Error’ when clicking on a comment each time, so obviously I’m still missing something. Thoughts?

    Joe

    #91542

    In reply to: Plugin alternatives?

    Joe Gibson
    Member

    Z –

    Thanks for the replies.

    “So I don’t see a reason why it should not function with my plugin.”

    And, if I’d actually activated the dang thing, nor would I. Sorry about that. The activation process somehow slipped by me. Works terrifically in both browsers.

    “zaerl URL preview”

    No thanks to that, but I know people are going to start bitching about not having a ‘Preview’ button.

    The only hitch (so far) with “Live Comment Preview” is that I can’t understand his instructions. Maybe you could set me straight:

    __________________________________________________________

    <?php add_live_comment_preview(“View Preview”); ?>

    to your topic.php file, where you want to show the preview’s area.

    ie. before the post form something like that

    <?php if ( topic_is_open( $bb_post->topic_id ) ) : ?>

    <?php add_live_comment_preview(“View Preview”); ?>

    <?php post_form(); ?>

    <?php else : ?>

    __________________________________________________________

    1. First off, assuming he’s referring to the bbPress file, it’s “topics.php”. And it’s a fairly long file. Would you have a suggestion on where the first line of code should be stuck?

    2. And are the last 4 lines supposed to be part of it? His breaking up a block of code with commentary was somewhat unorthodox.

    Much thanks,

    Joe

    #91453

    why not no need of “www”? reason?

    We’ve known that using “www” during installs has caused issues in the past. Especially if you used “www” for one isntall and not the other.

    Cookies are/were (been a long time since i looked into this) using the full URL so “www.bbpress.org”‘s cookie would be different from “bbpress.org”‘s cookie if you didn’t specify.

    99/100 it makes no difference. 1/100 it does :)

    .

    .

    You are right that there was no need for the salts when bbPress1.0 was released, but we’ve had 3 WP releases since then. I find its better to be safe than sorry.

    So I’m confuse why we need two separate authentications for both wp and bbP.

    In theory: You do not.

    In Practice: It doesn’t hurt at all.

    Request:

    Can you please create two demo files for wp-config.php and bb-config.php with authentication keys, and make live them to pastebin.com & paste links here?

    Sure, i’ll do that tonight when I get home.

    Am off to see Toy Story3 in 10 mins.

    #90556

    Yes, there’s a plugin but It works only with older release bbPress

    As do most plugins.

    It’s just where we are I’m afraid :(

    #91451

    Well I can see some things I’d change. Will they make a difference? i don’t know, probably not, but again, they’re what I use.

    (I wish the search function here was half decent so I could find the post I went into this in detail in…)

    1) Get your authentication Keys from https://api.wordpress.org/secret-key/1.1/bbpress/salt/

    2) Copy your WordPress authentications into your bbPrefig file

    define('AUTH_KEY',         '5G#If&OQrV:MfrjuU2;NKhfw|Z:|iU>@hw^LLTxv|~8KPC9S;-+r#J&|T=DS%#X8');
    define('SECURE_AUTH_KEY', 'u.p|C]A*s*@M%VGr4;_Cc-*d|I:QjTT&p6kcTL:^X+tzUT)7k-S]h)q^c|||$uy;');
    define('LOGGED_IN_KEY', 'xA+j,OZKD_*, 6|Jb7C6rS*3(oT4{-Y)R.E/|!xNtb8,GYzp,X-?i[HtTRE|81h=');
    define('NONCE_KEY', '4h035-4lx6-W.>dtZzRtA=XA+&G5v)llX[B>4--:>hX0h:Ey$afw|&[r_1zHQnZ^');
    define('AUTH_SALT', '+/poE0c>eRr#l54-r@:S.4HD^s3Zr%w-S;s++d,[ku5#Aj{N6g6T;.P>/UB8bIUn');
    define('SECURE_AUTH_SALT', 'ck.^(0_T5tON$lTy>dkPZ#]1wZ~yKBkE0m>60H_FRG r6yXd#E|dhJAVvPDu5Kf.');
    define('LOGGED_IN_SALT', 'Fz^)*aj<U[RxO3A][1K=pXX6a-4-<R7=[fe$1[hT5d!e-_onpNrk^t|j%!~a+;KP');
    define('NONCE_SALT', 'TEdXdR+g]&YY9/YtZX^[,e{_U+^fSGcgt JqKB<[sh:3Jg<7RG~f_.xLX(9e5FXV');

    define('BB_AUTH_KEY', 'f@X, B|4rcQ?sv#[]q+x;r =KO{r}i<|h%0=?>!/f|0A#[qzh9pNWdnZR8XadkFH');
    define('BB_SECURE_AUTH_KEY', 'X0*%@*wpp(A[/(4RD(TWAnW7N[:gYBZ:@r}-z;w),|fptIbt5 Ro}8Tr?}-c-y+m');
    define('BB_LOGGED_IN_KEY', 'cbal+zxea.]|C!ZsWQ6}cKy+?!eSs?@(t)qCz=H*4CDrZlXoC+-X#[h5Hl37LU~/');
    define('BB_NONCE_KEY', '4{ZC+__k{]MPr[I{~q$Muta#XghduMPBRQvNZqFIm-~-4-DaH|vH$6W~)wD!^92X');
    define('BB_AUTH_SALT', '?v&+?5?vnXoIPuc&%OQMNN#QP_Xf&ZA0J:FO;tY:JdEjT5xt^k$,-q!XvVS,E)$1');
    define('BB_SECURE_AUTH_SALT', 'n(M15M~Y<qg(A!x8ov,7]:+HZ>q0ajV3!feD){dLPhn2upN?;fIRE.@~14xH?v!8');
    define('BB_LOGGED_IN_SALT', '{Lu=[hq;BCEu j>n[Ejv%]w-k y?$@*sK@VcB<7E)wR/mrUIGj%9@*Q>.v]P|~#x');
    define('BB_NONCE_SALT', '*9Dv~}=@+k<g-w$WIsEXdxULL0yz0D{]!9@HY/e$7Ru|^dv?QF$gy!}dcLIC>@5P');

    3. With no disrespect to that screencast, it is 19 months old, and we’ve had a whole new version of bbPress since then. For integration I always use http://wpbbpthemes.org/integration/ as a starting guide.

    4. Check you’re not using “www” anywhere in the URLS you specify in the database, or that you installed any of the bbPress/WordPress systems while using “www”.

Viewing 25 results - 20,476 through 20,500 (of 32,517 total)
Skip to toolbar