[Closed] Bizarre conflict with WP3.2.1 for Joomla & Joomdle

Joomdle .054 working flawlessly.
I then installed Wordpress for Joomla MU 3.2.1 on our Joomla 1.5.23 test site. All seemed well, except when I went to enter the WordPress component from the Joomla BACKEND just to change some default WP settings, it tries to redirect me to this:

www.oursite.com/moodle/auth/joomdle/land...8382e9150157e46556bf

Looks like the joomdle auth plugin in Moodle is trying to take over, but I have no idea why it would do so on a Word Press back end component link.

joomla site is www.oursite.com/edu
joomdle is www.oursite.com/edu/components/joomdle .
WP install is www.oursite.com/edu/blogs
moodle is www.oursite.com/moodle .

I have absolutely no idea why this would happen in the back end of Joomla. When I turn off the Joomdle component and its plugins, the WordPress component link goes back to normal.

I'm stumped again.

For some reason, the forum is cutting off the last section of the link

www.oursite.com/moodle/auth/joomdle/land.php ?
username=admin&token=6ae5b4d5b6151780b18eae84012609d8
&use_wrapper=0&
create_user=0&wantsurl=%2Fedu%2Fblogs%2
Fwp-admin%2F%3Fh%3Dc292de5e51a68382e9150157e46556bf


All one, just trying to get it all to show.

I have not seen WP for Joomla for some time. Does it still require a Joomla to WP user sync or does it remove the WP user security and config entirely now?

I also believe WP requires mod_rewrite, SEF and XML-RPC. Perhaps there is some conflict here?

I would try turning off SEF and/or mod-rewrite to see if there is any difference.

You say you turn of the Joomdle component. What does this mean as Joomdle has no on / off switch? Do you mean you disabled some plugins? Which ones?

Absolutely correct Chris. WP for Joomla MU version requires SEF and mod_rewrite marked YES and there are still authentication and user plugins installed along with the component. There's no XML-RPC for WordPress as far as I can see. I hesitated to even install WP4J due to it's special requirements but then I read somewhere in this Joomdle forum that people have had success with SEF On as long as it was the stock Joomla version.

Indeed, everything runs flawlessly in the front end, both Joomdle and WP for Joomla work quite nicely with no apparent issues with mod-rewrite and SEF on. The only blip is the back end WP4J component link (which really isn't an issue for me since the WP backend dashboard can be accessed by an administrator from the front end. It might be confusing eventually for the person who will be using the system, but there are workarounds for that. ie A warning: Don't touch the WP component from the Joomla back-end or face certain death.)

By saying turning Joomdle off, I mean disabling, the component and all the plugins. Cleans up the WP component issue.

I talked to the WP4Joomla people. I think before I go any further I'm going to start with a fresh install of everything, move Joomla to the server root, clean up a bunch of components that won't be used (but were tested) and see where I'm at. I might be asking too much to have all these apps running together through one SSO happy dashboard. If that's the case, I'll let the client decide which they prefer to have with SSO and leave the others as external links with their own logins. It's what they have now anyway.

OK sure. I'll speak with Antonio next week to see if there is anything that rings an immediate bell. I would hate to think we could not have a J, WP for J and Joomdle all running nicely. In fact I hope to have this myself and rid of myblog perhaps next year.

I agree. It's a nice combination. You don't have the flexiblity of themes and plugins that you would have on a standalone WP config, but the integration with JomSocial is nice and the default theme takes most of its formatting from the website so it dovetails well. It's a breeze for people (teachers) to register their own blog. I have heard that Wordpress MU likes to be on the root (impossible for a Joomla install) but I think I stretched it too far by burying it multiple folders deep. Once I clear that up I'll give it another go.

It's very possible this redirect is related to turning mod_rewrite On, SEF On, plus WP4J needs to use an .htaccess file that could be an issue as well. The weirdest thing is that WP4J runs with its user-wordpress plugin OFF. Turn it on and I get another conflict with logouts. I'm betting it's my installation. Joomdle itself runs fine either way.

Cheers

You should have no issue with it in a root. In fact this is the way some extensions prefer such as the nooku framework using links. Joomdle is fine with .htaccess and with SEF. Perhaps the mod rewrite needs a parameter to exclude your backend ?

Hi.

It seems what is happening is that WP is triggering the "onLoginUser" event when you click that link, and Joomdle SSO code is executed.
Joomdle's code is designed not to run on back-end, so maybe WP is doing some trick for their SSO that makes it bypass this check.

As for a solution: I don't know, as I don't have access to their code to see what is really going on.

Thanks Antonio, no worries. 99% of the time people will be doing their WP blog maintenance from the front end anyway (that's kind of the idea of multi user blogs anyway so that users can manage their own rather than rely on IT staff.)

I just made a little reminder to the admins to go into WP from the front end. The good news is that Joomdle and WP Blogs behave wonderfully together on the front end where it really matters!

Cheers
Jeff

(Considered closed.)