Forum Replies Created
-
In reply to: RSS Cloud
I was looking for a plugin, glad that there is one! Going to have to check it out!
I forgot one more patch, and thats for BuddyPress.
I haven’t submitted it yet (i’m beat…)
When you have applied everything I’ve submitted above, you need to be in an HTTPS session to edit/submit anything.
For instance, after logging in and going to your activity list you will see the login form again. This is because the cookies set are secure cookies. If you were to go in your browser and change the scheme to https, you will see that buddypress will mark you as logged in and you can change whatever settings you need. This is what I was trying to achieve, complete HTTPS sessions for when it is flagged.
And also, thanks to R-A-Y for #979.
I think after 979 + this new patch, SSL will be complete for buddypress (famous last words)!
I have a feeling though a backpress update may be in order though..(me ranting)
In reply to: Make your own custom BuddyPress pageI like it! So simple!
Can we should sticky this?
I have to say that using the multi-site plugin (paid vesion) + some creative rewrites can help achive 90% of what you want.
You can have two installs running. Of course, they have to be put into two different locals, used with a different database owner, etc…
The biggest problem you would run into would be if your server can handle the ram requirements.
I would not try this and expect performance ‘good enough’ unless I was on a dedicated hosting.
On a grid like ours, SOMETIMES we have to do a full on separate install. In these cases we also worry about our entire caching structure which bloats up considerably. A mitigation for this would be using S3 for storage, and we are moving our entire grid to the clouds. Our grid has been processor focused than storage (we started out as a high computational structure). Sorry for the off-topic.
In reply to: Details About the New Theme Architecturesince your doing the digging..
I posted a scheme (http,https) security patch for the depreciated and new theme logins @ https://trac.buddypress.org/ticket/960
In reply to: Plugin request: Removing "create a blog" optionsI believe something could be wrong with your implementation.
The link should be removed with the code from the patch.
Make sure that if your using supercache to clear it or disable it to test.
In reply to: Plugin request: Removing "create a blog" optionsThe patch will only remove the ‘Create a blog’ link which shows up in the buddybar, if blog creation has been disabled from within WPMU. Thats all really.
In reply to: Plugin request: Removing "create a blog" optionsI just tested this again and I’m not seeing what your seeing.
Try clearing out your cache, and restart your server.
Then re-try.
In reply to: Plugin request: Removing "create a blog" optionsThanks!
One less thing to compare (Mu+BP+BB)press to Anahita with when they launch.
I can smell the write-ups now…
…Right now would be a great time to release Channels for BB…
In reply to: Plugin request: Removing "create a blog" optionsI posted something similar on trac around 8-22 with a patch
In reply to: Will BuddyPress work with Multi-Site Manager PluginSome more tid-bits,
Doncha isn’t really liking the Multi-site plugin as it has a few issues and not actively maintained. Also, the multi-site doesn’t handle xmlrpc.
Right there that kills it for buddypress.We may not see this patch included even though it has a milestone, and those reasons are that the Domain Mapper already has it’s teeth into wp-config. So there is intent right there.
Having said this, I have buddypress working with my wpmu setup. At least it looks like it’s working! LOL! Haa! ::[ok back to work]::
In reply to: Will BuddyPress work with Multi-Site Manager PluginI think I’m getting names mixed up, but Doncha did write the domain mapper.
In reply to: Will BuddyPress work with Multi-Site Manager PluginJust re-read, Domain mapper is what you want.
However buddypress is sitewide as is bbpress.
I am working on a domain mapper compat bbpress seperation.
Keeping bp unified is still recommended.
In reply to: Will BuddyPress work with Multi-Site Manager PluginI think for many cases the core is still setup for single domain. Not really 100%.
Even the last bit of code I pushed Doncha gave me three test cases he wanted, tld root, subdomain, and subfolder. No combination. So just on that point it’s not an intended usage.
You may be better off with Doncha’s domain mapper. It will require a patch if your using bbpress. I’ll have upload that to him. Otherwise this allows more segregation yet the backends are tied (an using the same bb and bp press apps)
Hope I understood the question!!
In reply to: Details About the New Theme Architecture==bugs==
I suggest using trac for any bugs.
==user blogs & design==
User blogs are run by MU. If you want to retain a ‘similar’ design you could:
- draft a wp theme using similar colors etc…
- perhaps use a global footer or manually add in some sidebar widgets to force show some site-wide bp content
- flag this theme as the default
- flag this theme as the only theme ‘turned on’ via site-wide admin
==1 Package==
I agree, yet also disagree on your suggestion.
It wold be very efficient to have a turn-key bundle. It would surely make many people’s lives easier. However to do so now would be very difficult for the existing devs. Now it absolutely doesn’t stop anyone else from doing it however.
Having a bundle offered by the .org sends the message that all apps are 1 wholly integrated unit. That will also require webserver, php, mysql integration for a turnkey solution (how many times do we see “i need help with X re-write”.) Also on support, this type of product would deserve a single forum, a single user group, plug-in pages, etc… At the moment It’s now quite there yet. As I understand it, this is a goal for the .org long term. Not to sure about the backend integration however.
As you, I also see the many frustrations which users do experience. I try to help support the community as much as possible, may it be cross app integration, patches, other info, and in some cases monetary and personnel donations to many of the backends I just described.
This is what makes open source great, it allows users such as yourself who come up with an idea which benefits the community to start working on it. I no doubt believe a project such as this would get support from various existing communities and users.
Go for it!
In reply to: For those still using 2.7.1Again, this is for those that are staying with 2.7.1 MU and I know your out there
In reply to: problem with ie6 and rtlYou will spend eternity trying to have everything work between IE6-7 and all the new web engines.
We’ve stopped developing for IE6 and IE7 entirely.
Our minimum browser must pass ACID2.
IE6 Test Results: http://en.wikipedia.org/wiki/File:Ieacid2.png
IE7 Test Results: http://en.wikipedia.org/wiki/File:Ie7acid2.png
Nice! Listen to r-a-y.
Before I chime in, when we run our unit tests with users; we:
- When testing an upgrade, I always delete a test user of mine: qauser
- sql delete, and php register the user again after the upgrade.
- I leave one user, qaeditor around. This user stays with the upgrade.
- Allows me to know if perms were set across apps, if new users are good to go, and if old users are ok.
- We flip roles too, but thats another test.

Anyways, Camel Case not supported for login.
Lowercase was put in back in 05.09 https://trac.mu.wordpress.org/changeset/1770
In trunk here is the snipit:
571 function _fill_user( &$user ) {
572 global $wpdb;
573
574 // WPMU uses lowercase logins
575 $user->user_login = strtolower( $user->user_login );I can confirm i have a similar issue, but ONLY with trunk (with no XMLRPC errors).
1.0.3 works fine for me.
In reply to: Ajax areas not working correctlyWith these types of scenarios it helps to temporarily use jQuery inplace of $(‘<attribshere>’) usage.
ajaxurl gets populated via root_domain + _SERVER[‘SCRIPT_NAME’]
As soon as I saw that I knew what had happened.
As some of you know, we’re working on our nginx modules which necessitates some custom phpfpm alterations (which we hope to contribute pending our modules). During this, we had to temporarily turn off our fastcgi_params script_name reference and well the rest is history.
Moral of the story, make sure your php backend is stable before you mess around.
This thread is now resolved/closed.
Looks like when the jquery post() is run, wpmu/bp looks at the location and pulls the corresponding theme locations from the backend based on ‘ajaxurl’ (one of args to post).
When I alter the ajax url to ‘http://example.com/groups’ from htttp://example.com’ it works propertly.
Now I have to find out why ajaxurl is being written without ‘groups’.
To Clarify futher, it’s the ajax search. The top-level search works fine.