[@burtadsit Participant 17 years, 10 months ago]

Yep, you’re right wardeh. I’m doing all sorts of whacky things to get rid of the 404 problem with directories. Never thought of doing that. I gotta try it.

Back in the day, I created a bunch of pages in mu and bp had major problems with them. Caused all sorts of havoc. Guess it’s been resolved. Thanks!

This is a forest and trees thing with me. I just moved on to other pressing problems and the directory 404s just became normal.

[@burtadsit Participant 17 years, 10 months ago]

@nicolagreco I haven’t forgotten about you nicola On my way…

[@burtadsit Participant 17 years, 10 months ago]

Howdy people. Download is available for the community blogs plugin now.

http://burt.ourcommoninterest.org/2009/01/02/community-and-group-blogs-in-a-can/

I also setup a group with a support forum on my site for this:

http://ourcommoninterest.org/groups/commoninterest-code/home

[@burtadsit Participant 17 years, 10 months ago]

Howdy, can I jump in for a sec? Go to Plesk > Domains > ‘yourdomain’ > log manager

There’s an option there in the middle ‘Lines of log file to be displayed (from the end of the file)’. Put in 100 or something resonable. Then select error_log.

[@burtadsit Participant 17 years, 10 months ago]

Thanks. I also realize that just doing do_action() on the menu doesn’t do what I intended. At 4am things kinda get hazy. I have to do a complete browser refresh to get the intended results. Oh well.

On another note, this js stuff is cool. I can do things that would have been ugly, painful or just plain impossible with it. I’m becoming dangerous now.

[@burtadsit Participant 17 years, 10 months ago]

I understand. There is also javascript associated with the widgets to do ajaxy type things. That doesn’t get queued up thru code. You can do it manually though before the widget call.

[@burtadsit Participant 17 years, 10 months ago]

The standard widgets don’t have a cooresponding templatetag yet. At the moment they don’t parse args supplied in code. They can only be used by hooking them up to a sidebar in the mu backend.

[@burtadsit Participant 17 years, 10 months ago]

When I enabled Thesis, I had to manually add pages for News, Blogs, Members & Groups. Everything appears to work until you click on one of the created Pages. (Blogs, Members & Groups mainly)

I’m not sure what ‘manually add pages for…’ means. You don’t need to add anything except the files plugin-template.php and plugin-sidebar.php which come with the bp home theme. Look in the home theme dir for those two. Just drop them into your theme’s directory.

Those files have action triggers in them that display whatever directory your user chose. Members, Groups…

If you are not running the bp home theme then within your theme you provide links to all the directories you want to be available. The urls would be:

yoursite.org/members

yoursite.org/groups

yoursite.org/blogs

You don’t have to create pages for these. bp hooks those urls and tries to display the appropriate directory using the plugin-template.php file.

What you’ve done is create mu pages with slugs that mimic the bp urls for the directories. Clicking on what you expect to be a page in your theme, fires off one of those urls. bp sees that it’s a bp internal reserved name for one of the directories and tries to oblige by displaying the directory. It can’t find that template file plugin-template.php and complains loudly.

Ya just can’t have pages named those things.

What you will have to do is override/skin the css for the directories if you want them to display in accordance with your theme.

[@burtadsit Participant 17 years, 10 months ago]

@oceandoctor the real question is why didn’t it work and what are the implications of that?

[@burtadsit Participant 17 years, 10 months ago]

This is an Andy question. Modifying bp core is of course a pain to maintain. You, of course, can do anything you like. But…

[@burtadsit Participant 17 years, 10 months ago]

Have you seen this?

https://bbpress.org/plugins/topic/support-forum/

Turns a forum into a support forum.

[@burtadsit Participant 17 years, 10 months ago]

Let’s kinda narrow down the prob a bit. Can either of you upload images in posts and have them work properly? Insert them in posts. Posts show on the site?

@oceandoctor ??

@seanzyville you are experiencing image probs in mu, not in relation to av cropping

The guns say it’s a permissions prob. Probably the upload dir or below blogs.dir

apache and linux are very picky about dir and file rights. apache *has* to have rights in the upload dir and in everything below blogs.dir

sporadic image probs can be related to images being created for user x. me going in and fixing user x with chmod and chown for that dir. along comes user y and y creates another new dir for y. apache cant play with the y dir now.

[@burtadsit Participant 17 years, 10 months ago]

@seanzyville I replied to you in your other thread. Why don’t you tell us what exactly is happening, or not, with the av crop tool. Did you upgrade mu or bp? The crop tool is a mu thing.

EDIT: hmmm. bp seems to override it’s functions in some way. looking…

[@burtadsit Participant 17 years, 10 months ago]

Can you be more specific? What errors in thumbs and imgs? How is this related to bp? Now the av crop tool I wanna hear about. Can you be more expansive on the av crop problem?

[@burtadsit Participant 17 years, 10 months ago]

Hey guys what is this ‘made by dbDelta’ stuff?

It’s in both his err logs near the charset collation spec. That seems to be what mysql is complaining about.

In code it just appends ‘{$charset_collate};’ where did this come from?

[@burtadsit Participant 17 years, 10 months ago]

I and others have had problems with non-bp plugins/widgets loading older vers of js libs and causing whacky conflicts. Anything else using js?

Does the cropper.js lib use cookies to store temp info? I know something in the realm of all this js does. Can’t remember what though.

Now that I’m looking at it, the cropper.js lib has a companion cropper.css file. You getting that. Got firebug? Go see.

Permissions on: /wp-includes/js/crop/<stuff>

[@burtadsit Participant 17 years, 10 months ago]

@arcon9 ya gotta get apache to have write/creation access to that /tmp dir.

The sessions were introduced awhile ago and I started getting these msgs. I’m on a DV also. Had to track down my session.save_path in the php.ini and go chown to apache:apache on the silly thing.

From what I can gather bp only uses sessions when redirecting and during signup. That’s what the comments say. So you’ll only get that error during those instances.

[@burtadsit Participant 17 years, 10 months ago]

The big guns have arrived. (whew)

[@burtadsit Participant 17 years, 10 months ago]

You’ll have to talk to your host about this issue then.

[@burtadsit Participant 17 years, 10 months ago]

The error logs I was referring to were those directly after your recent install of bp on 1and1. bp will try and create the tables. If it can’t there will be some evidence of it in the error logs. Perhaps why also.

[@burtadsit Participant 17 years, 10 months ago]

I played with the widgets in the member theme for a couple of hours. I couldn’t get it to work. The problem seems to stem from the fact that the member theme code can’t register a sidebar or then call it again.

I tried registering a sidebar in my theme. Shows up fine. I can add widgets all day long. However when you call dynamic_sidebar(), dynamic_sidebar doesn’t think there are any sidebars to give to the call. The var $wp_registered_sidebars is empty and it just returns.

I didn’t have a chance to track down $wp_registered_sidebars and find out why it’s confused. The sidebars are associated with a particular blog id. So I tried just using switch_to_blog(1) before dynamic_sidebar() and that didn’t work. Evidently that isn’t enough to populate the $wp_registered_sidebars var during the call.

[@burtadsit Participant 17 years, 10 months ago]

nope. sorry. The php.ini file is probably in /etc

The directory in question is /tmp

[@burtadsit Participant 17 years, 10 months ago]

I just looked over your initial post. I must be tired. The error msg says where the dir is.

It’s /tmp for you.

Check the permissions and user/group. I had problems with this also due to stupidity on my part. I had to make the apache user owner of the sessions dir.

For more than you’ll ever want to know about the subject:

google ‘Warning: session_start() [function.session-start]:’

google ‘linux chown’

google ‘linux chmod’

google ‘linux file permissions’

Your host may be able to help you also.

[@burtadsit Participant 17 years, 10 months ago]

That means that apache/php doesn’t have creation rights in a specific dir. In my case it’s: /var/lib/php/session

Look in your php.ini file and see what the option ‘session.save_path’ says. That’s the dir that apache needs to have access to. Apache runs as a specific user/group and it needs to have write access to that dir.

[@burtadsit Participant 17 years, 10 months ago]

It’s a bug. Been reported in trac.