Search Results for '"wordpress'
-
Search Results
-
Hi Ashfame,
First: i feel your pain in integrating WP2.7.1 and 0.9, i’m sure alot of us do – that said though, it’s definitely possible.
Second: it’s definitely possible to achieve site wide login using either _ck_ or Ann’s plugins. Without a doubt using _ck_’s is far easier, as Ann’s comes with no documentation and there are steps required that no-one’s written out. It took me about an hour of searching and playing with Ann’s to get it to work, but once it did, it worked brilliantly.
Basically follow the steps given on the 3rd page of the integration forum posts (hey dont expect documentation for something a sought after as this to be on an actual page – like the integration one – or even at the start of a post so it’s easily found). Then add in
define(‘COOKIEPATH’, ‘/’ );
define(‘SITECOOKIEPATH’, ‘/’);
define(‘COOKIE_DOMAIN’, ”);
to both the WP and BB configs. Obviously you can change the values.
The other thing that really helped me, after alot of trial and error, was to set up WordPress first. Activate Ann’s plugin. It then automatically boots you our of the WP admin area. you have to go to/wp-login.php?action=logout and then entirely clear your cache and cookies.
Then re-log in. The cookie WP sets will now be recognisable.
Install BB AFTER this step to make life alot easier; as bbpress will recognise the admin cookie right form the word go
Third: Ann’s method overwrites the ‘new’ wordpress cookie method, so the theory is that it’s future proof. at least throughout this WP2.7 branch. The bad news is, according to an automattic post i read yesterday, that the OpenID integration in WP2.8 may require a rewrite of all authentication in WordPress. If this happens then there is a good chance that all authentication in Automattic systems will have tot change, there’s just no way of future proofing against a company wide re-write. But if that doesn’t happen, then Ann’s plugin should work for a long time.
Fourth: A the risk of reading form the _ck_ bible, there’s very little reason across the board to upgrade from WP2.5.1 to WP2.7.1 . There are no known security issues in 2.5.1. I’ve yet to come across a WP plugin that doesn’t work for 2.5.1, it’s a damn site easier to use, and it’s faster and more lightweight. Obviously, you may have different requirements that we don’t know about, but I would look long and hard at not using 2.7.1 if i were you.
Good luck, Kev
I think I’m going to have delete my WordPress instance now and reinstall.
Thanks Chris for your help, but bbPress has really messed things up. I used the installation process to set the config files, so it’s not entirely clear what I need to do. I have cleaned up the wp-config.php file back to how I think it should have been, but still no go.
I think changes may have been made to the db tables for which I’m not sufficiently skilled to reverse.
So that’s that. Thanks again for you help though.
Topic: WordPress integration help
Hey,
So I am having a few issues while integrating with wordpress.
My first question is, in step 2 when doing the cookie integration it asks for the SECRET_KEY” in the WordPress wp-config.php file. I am using wordpress 2.7.1 and I cant find the SECRET_KEY in the file. How do i get the SECRET_KEY??
Also i want to know if me creating a separate database in step 1 of the installation was the right thing to do?
Thanks for any help.
HttpOnly cookies are a security advancement that is finally supported now by all major browsers (Firefox eventually got it right in 3.1, while IE 7 still has a bug but it generally works).
HttpOnly means a cookie cannot be read by javascript in the browser, only by the server (via PHP, etc.) This practically stops XSS exploits and makes it much harder if not impossible in most cases.
HttpOnly may “save your bacon” when a plugin has a security hole (like Private Messaging and bb-Reputation 0.0.5) and prevent a malicious script from forwarding your keymaster cookie to someone else via a XSS script.
I manged to get them to include HttpOnly in WordPress 2.7 and bbPress 1.0 but it’s still not in older WordPress or bbPress 0.9 because they worried about backward compatibility with some WordPress plugins that try to directly read the cookie (bad technique) instead of using server-side helpers.
However there are NO bbPress plugins that direct read the auth cookie and very few WordPress plugins still do this. I am not 100% positive how it will affect ajax but it shouldn’t because it’s still authorized on the server-side via PHP.
So if you’d like to try out HttpOnly on your bbPress 0.9, here’s how, it’s as simple as a mini-plugin. Note that if you are already using a cookie replacement plugin like my “Freshly Baked Cookies” or “Year Long Cookies” you will need to edit them instead of using the following (you can only use one cookie replacement plugin at a time).
I’d appreciate any feedback or experiences with this, especially if it causes problems:
Save this as
_HttpOnly.phpand upload into yourmy-plugins/directory:<?php
/*
Plugin Name: HttpOnly Auth Cookie
*/
function wp_set_auth_cookie($user_id, $remember = false) {
global $bb;
if ( $remember ) {
$expiration = $expire = time() + 1209600;
} else {
$expiration = time() + 172800;
$expire = 0;
}
$cookie = wp_generate_auth_cookie($user_id, $expiration);
do_action('set_auth_cookie', $cookie, $expire);
setcookie($bb->authcookie, $cookie, $expire, $bb->cookiepath, $bb->cookiedomain. '; HttpOnly' );
if ( $bb->cookiepath != $bb->sitecookiepath )
setcookie($bb->authcookie, $cookie, $expire, $bb->sitecookiepath, $bb->cookiedomain. '; HttpOnly' );
}
?>To prove it’s working, you CANNOT use the Firefox webdeveloper plugin because that looks at the cookie in Firefox’s chrome, not at the user level. What you have to do is
1. prove you can see your bbpress/wordpress cookie by typing or copying this to your browser address bar
javascript:alert(document.cookie);2. install the plugin
3. log out and then log in
4. again type or copy this to your browser address bar
javascript:alert(document.cookie);5. if it’s working, you should NOT see your wordpress/bbpress cookie in the alert
Currently the only plugin I am aware of that tries to read the cookie directly in WordPress is the
WP-UserOnlineplugin from GamerZ, and he may have even fixed that by now in the newest versions. However there may be others, so test your setup.Hello,
Next days (or weeks) I sill start a new project. It will take long to develop and probably it will be finished later this year. I think it will 6 months or a bit more. It must be integrated with the latest version of WordPress.
So, I’m thinking about starting the project with the 1.0 alpha versions. I know it’s not as stable or secure as 0.9.x but hope it will be later this year. I’ve seen there are lots of changes from 0.9 to 1.0 and perhaps will be easiest to merge the new 1.0 versions than 0.9 to 1.0…
What’s your opinion? It’s the best idea to start the project with the alpha version ? Or you would start it with 0.9x and in the future you will make all arrangements to upgrade it? Consider that it will be finished this year fall.
Thanks for your comments,
Txanny.
