Forum Replies Created
-
In reply to: Role Integration Problem
The problem is definitely the lack of a WordPress table prefix.
The path of least resistance is to rename the WordPress tables adding a prefix, and change your configs to reflect the new table names.
In reply to: Prblem upgradingSorry, that should have been:
$bb->wp_table_prefix = 'wp_';In reply to: using bb_users with integrated setupJust set up the “user role map” in the “WordPress integration” section of the bbPress admin area.
In reply to: How to get BBPress to use wp_users tableIn reply to: Plugin problemWow, as I read your description of the problem initially I thought to myself, “sounds like a caching issue”.
A good note for the future. I assume you are loading WordPress inside bbPress then?
In reply to: Prblem upgradingIf bbPress and WordPress are in the same database then hopefully all you should have to do is add this line to your bb-config.php after the database definitions:
$wp_table_prefix = 'wp_';In reply to: bbOrg?In reply to: Cookies not shared between 0.9 and 2.5OK, so it looks like you have matched the domains and paths correctly. Have you matched the bbPress “BB_SECRET_KEY” in bb-config.php to the WordPress “SECRET_KEY” in wp-config.php?
Do the secrets stored in each database match?
In bbPress it is the “secret” meta_key for topic “0” in bb_topicmeta.
In WordPress it is the “secret” meta_key in the wp_options table.
(Keep in mind that the cookie contents aren’t meant to be the same as they are hashed against the login time.)
In reply to: Gravatars and 0.9 needs plugin?In reply to: Newbie: Query re step 2 wordpress integration.You should skip step 2 unless you are specifically integrating your bbPress installation with a WordPress installation.
If you don’t know what a blog address is, then you don’t have one. There are lots of notes in the installer telling you exactly what the options are.
In reply to: Gravatars and 0.9 needs plugin?It’s native and built-in to the default Kakumei themes. Other themes can be quite easily adapted to use them too.
In reply to: Cookies not shared between 0.9 and 2.5I notice a long expiration date, so I assume you checked the “remember me” option in both instances. Does it happen when you don’t check “remember me”?
Thanks so1o, that’s the quick an dirty fix. That code uses jQuery methods, and jQuery is not available in topic pages.
It didn’t get picked up because that code falls back to non-ajax requests when it fails.
We are half way through removing all prototype in favour of jQuery, and this snuck under the radar.
Were you getting an error message when it didn’t work? It would be useful to know it if you did.
In reply to: WP-mu and bbPress 0.9User role mapping may not work. I’m not entirely sure of similarity differences between WP and WPMU roles.
In reply to: WP-mu and bbPress 0.9It should work. But I haven’t tested it. Database integration should be fine. Cookie integration will almost certainly work if you only have one domain that you run wpmu on. e.g. WPMU main site = example.org, WPMU blogs = *.example.org
In reply to: “I could not find the file bb-config-sample.php”Is the file there? Does it have permissions that allow the webserver to read it?
In reply to: bbPress 0.9.0.1 releasedLooks like you got the $bb_table_prefix wrong when you installed, it should have been different to the wordpress prefix.
Change
$bb_table_prefixfrom “wp_” to “bb_” in bb-config.php then rename you bbPress tables thusly:wp_forums -> bb_forums
wp_tagged -> bb_tagged
wp_tags -> bb_tags
wp_topicmeta -> bb_topicmeta
wp_topics -> bb_topics.
Do not rename
wp_posts,wp_usersorwp_usermeta!This will still leave you without a
bb_poststable. So if you have a way to browse your database (e.g. phpMyAdmin) then go into thebb_topicmetatable and look for the row with ameta_keyofbb_db_version. Change themeta_valueof that row from1234to1233. Login to your bbPress (hopefully it works) then go to the admin section. You will be asked to upgrade, do so and check the log. You should see a log entry where yourbb_poststable is created.That should do it.
In reply to: Installation TroublesWe don’t overwrite tables if they are there already, so the wp_user/meta tables should still be there.
It’s really hard to tell what’s going on for you. Perhaps you should try and do a non-integrated install first just as a test.
In reply to: PRIORITY #1: ImageFile AttachmentsIf someone writes a plugin, and that plugin is popular enough, we might add it to core. But it would have to have a bazillion downloads or something.
The fact that nobody has written the plugin yet is telling though.
In reply to: bbpress 0.9.0.1 > 30 queries per pageWordPress.org forum is about 500Mb of data.
In reply to: bbpress 0.9.0.1 > 30 queries per pageUsing one server will only ever get you so far no matter how lean the application you are running is.
Massive query caches are no use if you don’t have the data to fill them. WordPress.com forums (all languages) doesn’t amount to more than 200Mb of data. So even a 1Gb query cache would be mostly empty or stale. WordPress.org wouldn’t be much bigger (and may be smaller). I don’t actually know what the query cache size is on the servers by the way. Query caching is great. Massive query caches aren’t anything special IMHO.
In reply to: cannot find secret key and database secretAnswer to the first question is that you need to add a SECRET to your wp-config file.
https://codex.wordpress.org/Editing_wp-config.php#Secret_key_for_salting_password
In reply to: How To Make WordPress Integration a LOT EasierIf only it were that simple.
There are more variables than just the URL, the solution you describe only covers the simplest integration scenarios.
We are only starting to bring integration out into a more user friendly space, so there a bound to be a few things which need to be re-addressed based on user experience, but a certain amount of an integration setup is always going to be manual.
I appreciate far-reaching and big ideas, but right now I think we need more of an idea of what is a problem with what we have now. If it isn’t simple yet, then let’s fix and tune what we have. At the moment we need to remain realistic about how much we can achieve in this area. There has been a considerable amount of time spent to achieve the current solution and with limited community resources we simply don’t have time to devote to a complete rewrite (of something that was just completely rewritten).
I did consider your suggestion as a possibility when I started to bring integration into the install process, but the amount of time I would have spent writing routines to detect exceptional cases could not have justified the perceived benefit. Don’t get me wrong, I appreciate your input, but I would have liked that sort of input when I started rebuilding the installer (a process which was publicised in the dev channels) and perhaps a hand to make it a reality at the same time.
I hope I don’t sound too defensive by the way. I honestly like to hear feedback, I just want to give you an honest response and reasoning behind the decisions that were made with regards to the new installer.
In reply to: WordPress cookie secret key – why don’t I have one?You need to create the Secret Key in your WordPress config.
Read the WordPress Codex for more info.
https://codex.wordpress.org/Editing_wp-config.php#Secret_key_for_salting_password
