Search Results for '\"wordpress\'
-
Search Results
-
What would you like me to say?
You haven’t told me what’s you’re expecting teh code to do, and what it does wrong instead?
Please, I want to help, but “it takes me to localhost” gives me nothing to work with
it takes me to local host… and my code was..
<?php
if ( is_user_logged_in() ) {
echo ”;
} else {
echo ‘
<table width=”480″ height=”90″ border=”0″ align=”right” >
<tr>
<td align=”left” >
<form class=”login” method=”post” action=”http://www.mysite.com/forums/bb-login.php”>
<div>
<label> Username
<input name=”user_login” type=”text” id=”quick_user_login” size=”13″ maxlength=”40″ value=”” tabindex=”1″ />
</label>
<label>
Password
<input name=”password” type=”password” id=”quick_password” size=”13″ maxlength=”40″ tabindex=”2″ />
</label>
<input name=”re” type=”hidden” value=”” />
<input type=”hidden” name=”_wp_http_referer” value=”/” />
<input type=”submit” name=”Submit” class=”submit” value=”Log in” tabindex=”4″ />
</div>
<div class=”remember”>
<label>
<input name=”remember” type=”checkbox” id=”quick_remember” value=”1″ tabindex=”3″ />
Remember me
</label>
</div>
</form>
</td>
</tr>
</table>
‘;
};
?>
<?php } ?>
@kevinjohngallagher please did not say this time “write your own code”
There isn’t even labels or text boxes for auth_salt, secure_auth, and logged_in_salt in the actual wp-admin/options.php page when you view it from the admin area. There’s a bunch of other options but I’ve looked through them and used Find, but I don’t see them
WordPress Integration Settings for bbPress admin even gives me a direct link to the options page that it says those settings are, but they aren’t there. Here’s what it says for each of the 3 required salts:
“This must match the value of the WordPress setting named “auth_salt” in your WordPress site. Look for the option labeled “auth_salt”.”
“This must match the value of the WordPress setting named “secure_auth_salt” in your WordPress site. Look for the option labeled “secure_auth_salt”.”
“his must match the value of the WordPress setting named “logged_in_salt” in your WordPress site. Look for the option labeled “logged_in_salt”.”
I guess I wasn’t involved with the community long enough to feel the burn from the back and forth decisions you mentioned. That does sound pretty shitty!
This is just pure speculation here but maybe the information from Automattic was so inconsistent because they weren’t sure what direction they were going themselves. I don’t know the whole history of BackPress but it sounds like it was a pretty big undertaking that would have had implications for WordPress as well. Going off my knowledge and what Matt said in the keynote it sounds like the BackPress project just didn’t work out in the long run but it was too late to take it back from bbPress.
Again, thats pure speculation so treat it with a grain of salt
BTW Taeo, I miss not being able to recommed your UI
Heh sorry about that. It was too much work to maintain between patches
I’ve posted some new stuff on my new website ( http://www.wowuigallery.com/topic/taeo-333-ui ) but it doesn’t have all the auto-config bells and whistles of the original.For an good looking, easy to setup UI I usually recommend TukUI to people. I helped him build his site (WordPress and bbPress of course).
Hi Taeo,
You’re absolutely right.
I doubt anyone here has a problem with Automattic making the best choice for them in the long run. Even if it’s not ideal for everyone; if the good outweighs the bad for a large percentage of people and it gives Automattic another feature to give their users then I can totally see why they’ve come to this decision.
The issue I have personally, isn’t with the decision (or indeed any decision that Automattic have made), but rather the way that information is passed along (or, ususally, not passed along).
To delete the bbpress0.9 milestone and decide to go back on your word to support it for 2010 without telling anyone – even weeks after you deleted it, is symptomatic of how Automattic treat the people involved with this project.
Matt’s word carries alot of weight, especially with WordPress users, so to make dispariging / negative / insulting comments about us in his KeyNote speech is poor. I realise that he was answering a question, and not a prepared statement; and we’ve all answered questions badly before, but it was a slap in the face to those of us who’ve given up our time.
Given that the 1.0.3 milestone has a year’s worth of bug fixes, and NOW isn’t going to be released until all the 1.1 bugs are finished AND a new backPress is released – though thats not been communicated to anyone yet; it makes it hard for those of us who have gotten behind bbPress to draw a line under it.
It’s also why this talk of a Fork is premature. Because when 1.1 gets released, there will be a swell of “bbpress is not dead” euphoria – much in the same way there was when Matt came back in December and when the new theme got uploaded. For me, I just want to get my current forums patched up to work the way bbPress1.0 was meant to and be treated like an adult until that happens.
BTW Taeo, I miss not being able to recommed your UI
Rootside ::
Has anyone considered the possiblity that Matt is keeping his eyes peeled on the current efforts of some people trying to use nothing but WordPress’ core functions to build a simple forum?
He might be mate, but probably not, as doing so isn’t that difficult at all. I creted a “theme” for WordPress that made it look/work like a forum in essence back in 2008. The same time I made and released the phpBB theme for bbPress. Both were availible on the bbProgress website (which closed last year but there should still be some links on t’internet).
And Justin’s coding one based on the new Custom Post features, which will work alot better than mine did (he actually build one last year too, but had a hard drive crash and lost it).
Basically though, a blog and a forum are different in their “n to n” nature. WordPress relies on a huge amount of caching to try and keep it’s memory intake down, and a customised caching mechanism is essential once you hit any form of modernday traffic. That sort of feature works well on “1 to many” software, but a forum is different. It has to call data differently, and handle multiple parent/child relationships.
Rootside ::
I’m guessing that any WP plugin which makes that kind of thing easy to set up and enhances its functionality would be really lightweight.
No, no way mate
The opposite.I understand the desire to make a WP plugin that is a forum, I can see Matt’s viewpoint on that, but in comparison to bbPress as it stands, it’ll be far from lightweight.
Not only will it struggle with the caching that WP relies on, but you’ll have all the overhead of loading everything in WordPress before hitting any actual forum content (including the WordPress admin sections and plugins).
It’s basically going to be very similar to the BuddyPress “bbPress” plugin, as thats a hacked/stripped version of bbpress1.0 (in general terms it removed BackPress and rewrote the function calls to call WP/buddyPress functions directly). But in order to get it to work, every page has to load WordPress then BuddyPress then bbPress forum module.
Lightweight it ain’t!
Even if the very clever people that work at Automattic and contribute to the community manage to pull a great number of rabits out of hats, there is no way that it will be anything but bloated.
But you know, 90% of folks won’t care. Take Marius (poster above me), he runs a forum about Michael Jackson with aboot 100+ users and maybe 50 topics started a week. He’s not that uncommon to alot of the folks that pass through here (other than that he is allergic to manners). They won’t care in the slightest about the small hit as the chances of them noticing it are going to be slim, and they get access to all the good stuff that comes with WordPress, heck for the most part they’ll get the stuff they think they should from bbPress/Wordpress integration now. For a percentage of people, there will be no downside, even if it’s far from lightweight.
I realise that software moves on, and I realise that as it grows there will be some bloat. Thats the reality of where we are, and WordPress does a really great job of being quick despire it’s bloat. But the sheer difference between a bbP0.9/WP2.5 deeply integrated forum (which has MORE features than we have now) and a bbP1/WP3 deeply integrated forum is unbelievable. Bloated, slower, more prone to errors and less features.
I see why Matt thinks things have to change, i don’t agree with the direction and thats cool, i don’t have to agree, nor does anyone
But really the history of this project has taught us one thing repeatedly: Heading in a direction without planning or a roadmap will definately lead us somewhere else, but we’ll be just as lost. Who knows though, 40 years later he may just lead us out of the desert
Hopefully on Matt’s way up to Montreal he’ll see a burning bush
There have been a huge increase in the number of reported WSoD reports with WP3.0, and thankfully the WP team are taking notice.
These plugins ( https://wordpress.org/support/topic/411649 ) are definately causing issues. HeadSpace2 is the biggie there as it’s a very popular plugin. I’m quietly confident that it’ll hit alot of people
WPtaven has an article on it, though right now there’s alot of people saying how it was flawless for them (how that helps those who it wasn’t flawless for i’ll never know). You can find that here:
Zaerl has written a plugin found here ( http://pastebin.com/JhJzLjvQ ) that solves one of the problems with WP3/bbP tha was brought up in this thread ( https://bbpress.org/forums/topic/wp-30-beta-2-integrated-user-registration ).
Having seen the hit my servers are taking from WP2.9.2 -> WP3.0RC3 my first guess would be memory. Deep integration of WP3 and bbP1 appears to be a nightmare, especially when I look at my one site thats still running bbP0.9&WP2.5.
Furthermore, I do believe we should start a “WordPress3.0 FAQ thread” that compiles what we know in the first post as a sticky. We’re going to face alot of questions in the next week or so, and maybe we could learn from some past mistakes
Woah! That would be a lot of work.
I tried this on my host and it seems that the problem is to do with WordPress 3.0 only cuz if I tell it to load wp-load.php from a 2.9.2 install, it works fine.
But I have seen someone in some other topic running a deep integration with WP 3.0
117.196.240.192 - - [19/Jun/2010:02:53:39 -0700] "GET /forum/ HTTP/1.1" 500 - "-" "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3"I am deep integrating bbPress with WordPress 3.0 and I am encountering this white screen of death. I have done several integrations this way and never got stuck.
I use this code above database constants in bb-config.php
if ( !defined('ABSPATH') & !defined('XMLRPC_REQUEST')) {
define('WP_USE_THEMES', false);
include_once(dirname(__FILE__) . '/../wp-load.php' );
header("HTTP/1.1 200 OK");
header("Status: 200 All rosy");
}I checked the logs and there are no 500 errors, all are 200.
I loaded the WordPress in a separate php file which works fine, so I guess something is conflicting in between WordPress and bbPress.
bbPress has no plugins installed but WordPress does have some and its a live site.
I am going to check for any conflicting plugins.
Any pointers?
