[slee]

Thanks for the info I see ill be having some fun getting all this to work over he next few days.

Can you tell me the plugin names of the plugins you mention?

Many thanks

[Mark McWilliams]

_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!

[Erlend]

@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]

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

[r-a-y]

The alternative is to block bbPress registration and redirect to WordPress’ registration page.

[Ashish Kumar (Ashfame)]

I doubt if performance of bbPress as a plugin can ever proved to be better than a standalone version of 0.7-0.9

Any comments on the scalability of 0.7-0.9 branch?

[johnhiler]

“I am supremely interested in the performance aspects and confident we can make the plugin scale better than bbPress does today or did in the 0.7-0.9 line.”

I would be really amazed if this came to pass! WordPress leaves quite a footprint, so adding plugins to the mix would seem to increase that even more?

That said, I’m definitely excited to see how you increase performance and scalability!

[Matt Mullenweg]

Just for the record, as someone who runs several large bbPress installs with millions of posts between them, I am supremely interested in the performance aspects and confident we can make the plugin scale better than bbPress does today or did in the 0.7-0.9 line.

[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.

[Matt Mullenweg]

Check out how P2 does front-end editor, it’s even slicker than bbPress. Actually check out a bunch of the features of P2 like the real-time post updating, etc.

[Matt Mullenweg]

Since the stated roadmap for whatever is going to be called “bbPress” and live at bbpress.org is to build on the success of WordPress if you disagree with that direction it’s probably best to fork at that time.

[Matt Mullenweg]

Plugin directory is broken in a bunch of ways, might take a few to fix.

[Matt Mullenweg]

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]

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”.

[deadlyhifi]

This is entirely possible. You’ll need to do the integration thing to get the common cookies for login, etc. There are plenty of posts on how to do that so do a search and a read and have an experiment with that.

You’ll need to consider that both WP and bbP have a registration screen and user account page. As you want to allow blog creation I presume you’ll want to let WP handle the registrations, but you’ll need an element of the bbP user screen for forum activity history.

If you have registration though WP you’ll need to make sure that bb_capabilities is set in the wp_usermeta table when they register. There is a plugin for that.

Facebook connect will be a WP plugin so affects the WP signup process, as long as the bb_capabilities, as mentioned above, are set it doesn’t matter how their account was created – standard WP registration or otherwise.

I hope that makes sense. Start by getting the integration working, then remove the bbP signup page. Provide links to the user’s forum history/favourites page, and make sure bb_capabilities is set when registering through WP.

Good luck.

[_KB_]

ok kevinjohngallagher, I’ll wait, till then I’ll try for new integration with no “www”.

[Matt Mullenweg]

johnhiler, the assumptions are indeed an active core. In the WordPress world, people who were active in the plugin arena also become active in core. In bbPress, they haven’t. Maybe that will change now.

[Matt Mullenweg]

wtfmatt*, please don’t force me to more permanently ban you. Either make a real account with real information, or go away.

[zaerl]

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.

[Joe Gibson]

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

[kevinjohngallagher]

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.

[_KB_]

kevinjohngallagher two more things?

why not no need of “www”? reason?

will exact formate be

https://bbpress.org/?

or

bbpress.org (even no need of http:// ?)

Second I was thinking there was no need of authentication keys from https://api.wordpress.org/secret-key/1.1/bbpress/salt/ because we copy keys/hashes from wp-config into bb-config, So I’m confuse why we need two separate authentications for both wp and bbP.

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?

I’ll be very thankful,

Cheers

[kevinjohngallagher]

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

[XU3E]

1) Yes

2) There’s a plugin for this for just over 2 years.

1) Why is it hard to made?

2) Yes, there’s a plugin but It works only with older release bbPress. _ck_ doesnt support new releases because his own branch.

[kevinjohngallagher]

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”.