Sorry, Sam. I am Linux on the desktop and Linux on the webserver. I supposed I could just try it too. I guess the issue is that now that I’ve already install bbPress and updated it once, do I need to start with a new checked out version and make my changes manually to that?
Thanks,
Chris
Ok thanks…
I installed that plug in for the wrong headed slashes but it is still same.
I cant see my site styled on FF2…
<link rel=”stylesheet” href=”http://chezmauricekusadasi.comyeniforum/bb-templates/kakumei/style.css” type=”text/css” />
There is no activation required. Any .php file in the my-plugins folder will just work.
So says Trent (and I believe him):
https://bbpress.org/forums/topic/714?replies=9#post-4462
You don’t have to activate plugins – you will have to do that with a later release, though (scheduled for version 1.0?)
Maybe you can copy us what your slashes are?
I have created a directory named “my-plugins” in the bbpress root directory and put the file named “path-to-url.2.php” into that directory. I think i have to activate that plug-in but i dont know how to do it ? Could you please help me…
Note: I checked config file and other files like it, there seems to be no problem with the slashes…
Thanks for your help…
I’m trying to test a new deletion routine in the Memberlist plugin, but the problem is I don’t have a WPMU integrated site to test with. I usually use Trent as my tester, but he de-integrated.
So if a few of you who use the plugin and are integrated and are willing to test something, let me know. The problem being addressed is how currently the plugin does not delete usermeta data when deleting the user, which causes errors in the backend user pages (particularly when the user is a bozo). I have already tested it using non-integrated bbpress, I just need one or two people to let me email them an updated file to test with WPMU. You’ll need to know how to look in your database to make sure the data is being deleted.
Thanks!
This fix is what chrishajer is referencing. The ticket is gone, but the fix is still there:
https://trac.bbpress.org/attachment/ticket/575/path-to-url.2.php
Trent
The relevant section that would affect those slashes, in the config, is this part:
// If your bbPress URL is http://bbpress.example.com/forums/ , the examples would be correct.
// Adjust the domain and path to suit your actual URL.
// Just the domain name; no directories or path. There should be no trailing slash here.
$bb->domain = ‘http://my-cool-forums.example.com’; // Example: ‘http://bbpress.example.com’
// There should be both a leading and trailing slash here. ‘/’ is fine if the site is in root.
$bb->path = ‘/’; // Example: ‘/forums/’
What do your slashes look like there?
Hello chrishajer,
I’m definitely seeing the () error when I look at the source.
I have installed the latest xampp, wordpress and bbpress locally for testing purposes. My config is as follows:
$bb->wp_table_prefix = 'wp_';
$bb->wp_home = 'http://localhost';
$bb->wp_siteurl = 'http://localhost';
I really don’t think I should be getting this error, so must I configure something else? Any help would be greatly appreciated. Thank you.
Yes, that’s the reason your site is unstyled when vieweing in FF. If you check with IE, you will see that the stylesheet is found. Are they typed like ( ) that in the config.php or is this an issue with bbPress?
<link rel="stylesheet" href="http://chezmauricekusadasi.comyeniforum/bb-templates/kakumei/style.css" type="text/css" />
This is the site
Could it be the reason that i see my site unstyled on Firefox2 ? You can see the slashes arent arranged in order. Some of them head to left and some of them right ?
Have you updated to the 0.8.1 version of bbPress yet? If you upgrade, you will see the checkbox to unedit the BOZO portion as chrishajer has suggested above with screenshots. Just make sure you overwrite all the files so that you are using the most recent version of each file and then test it again with and without the Akismet turned on.
Trent
There. Now I think I’m happy with it. I just had to change tactics to resolve the problem. The download link has been updated on my blog post with the updated version.
Do let me know if there are any other suggestions for improvements.
I am using the allow images plugin Version: 0.7.1 and it apparently does not allow images if the filetype extension is in CAPS. So, this will work to insert an image into a post:
http://www.appraisercitywide.com/xsites/appraisers/appraisercitywide/Content/UploadedFiles/Heurtley.jpg
and this will not:
http://www.appraisercitywide.com/xsites/appraisers/appraisercitywide/Content/UploadedFiles/Heurtley.JPG
If the image is hosted on a Windows server (or I guess any server where case does not matter for filenames/URLs) you can change the extension to lowercase, and it will work within the plugin just fine: the hosting server knows what to do. If the image is hosted on a Linux server, or any server where case does matter, you can’t do that and the img tag gets stripped out of the post if you insert it in uppercase like JPG. (i.e. if you tried changing it to lowercase, the tag would remain in your post, but would result in a 404 since the hosting server would not have a file by that name.)
Can the plugin be updated to allow upper, lower or mixed case filename extensions?
Thanks
I’ve committed and tagged version 1.2.
Moving it to version 2.0 seemed a bit excessive to me. I even considered 1.1.1 for a second there…
Anyway, the plugin site should have this updated soon.
I’ve just updated the previous patch file to address the WordPress integration/function naming issues.
Download from here – categories-build701.patch
You should read the relevant comment about the updated patch.
Thanks for the info. That makes sesne that it would only be used for initial setup. I wasn’t sure though because I’d changed the admin email address under the admin profile, then set up a normal user account with the same email address as what was listed in config.php and after I updated to v0.8, the email address for the normal user showed as “1” in the Admin panel. Just wanted to make sure I wouldn’t break anything if I changed the address in config.php for future updates or anything.
Ah. So is it just an updated version? Are there any new changes?
My guess is that the email in the config.php is used for setup only. Afterward, I changed mine in my profile and it gets updated in my WordPress user table. I changed the email address in my WordPress user table, and it’s changed in the profile in bbPress. None of those changes affected the setting in config.php. I requested a new password with the forgotten password link, for admin, and it went to the email address in the user profile, not the one in config.php.
I am pretty sure the email that is used on an ongoing basis is the one in the profile, and the one in config.php is used for setup only.
That’s my best guess. For consistency, I think I would update both, even if only so that when you do an upgrade in the future, the one in config.php is still accurate.
It’s really annoying and it only happens in my recently updated Ubuntu Edgy … with Firefox 2.0 (ie, it only happens in firefox 2.0 for ubuntu edgy)
I have no idea whether its something i did wrong with my Avatar adjustments to the style.css or whether “desmond” is just forcing me to take an eyetest.
It’s annoying.
oh yeah…if you haven’t noticed i am running 0.80
Yeah, I just figured out that the problem originated from bad header information in the stylesheets. Once I fixed that, both templates showed up just fine.
Let me understand this. The blank screenshot issue is because you have to take a screenshot of your template and add it to your theme folder. Double check the name of the default theme, but I think it works if you create a screenshot and call it screenshot.png.
As for the by and name of the template, that is derived from the information at the top of your style.css. If you edit file in your theme directory, it will show up. If you don’t have a style.css in your theme and are using the default theme’s style.css, download it as is, change the information at the top and upload it to your theme directory.
I think that is all the troubles you are having at first glance.
Trent