Mishkin said:

Hi again,

There seem to be a conflict between Role Scoper and qTranslate. Upon activating Role Scoper qTranslate no longer is able to parse multilingual titles in Parent Page-dropdown in Write Post, get_page() function call and a couple of other places.

My guess is Role Scoper is executed before qTranslate and somehow breaks qT's parse function.

Is there a fix for this?

Can you give me some QTranslate configuration help? What exactly does it take to reproduce the multilingual Page Parent bug?

Okay, I see what you mean. I just hadn't taken the time to read the disclaimer about activating the QTranslate editor. Now I see the symptom and will look into it.

Mishkin said:

There seem to be a conflict between Role Scoper and qTranslate. Upon activating Role Scoper qTranslate no longer is able to parse multilingual titles in Parent Page-dropdown in Write Post, get_page() function call and a couple of other places.

My guess is Role Scoper is executed before qTranslate and somehow breaks qT's parse function.

Is there a fix for this?

Okay, the page parent translation conflict is now resolved in the updated Role Scoper development snapshot.

Feel free to give me more details on the other symptoms if they're still there.

Mishkin said:

I have tried your patch and it seems to fix the problem for administrators but not for users with page restrictions…

The language tags are also visible in the Role Scoper administration pages. This could be solved by applying the "the_title" filter on page and post titles which includes the qTranslate parser function.

Due to Role Scoper's low level nature, there are several situations where it directly queries the database for pages, terms, or (in bulk role administration) posts. These were the sources of non-translation. I've now accompanied each of those direct queries with a filtered query which allows translated titles to be preserved. See the updated Role Scoper development snapshot. Let me know if I missed anything.

Again, thank you for your time! I donated a couple of dollars as a token of my appriciation.

Thank you!

Mishkin said:

On the profile pages under Scoped Roles, it still prints language tags but except for that it seems to work fine.

Okay, that too is now corrected in the updated Role Scoper development snapshot.

Mishkin said:

Hi Kevin,

I've just discovered that the name of drafts aren't being parsed by qTranslate in the post parent drop down.

On a side note, you can stop QTranslate from putting the language list in every custom column by adding the following code to qtranslate_hooks.php:

add in the top of function qtrans_languageColumn:

if ( 'language' != $column )
	return;

Kevin said:

Mishkin said:

Hi Kevin,

I've just discovered that the name of drafts aren't being parsed by qTranslate in the post parent drop down.

---

Hmm, are you referring to the page parent dropdown on the Edit Page form? If so, the filtering is working for me. What versions are you running?

Actually, I can confirm this in version 1.0.4.1 but I've already fixed it in the development code. If you don't want to run that, 1.0.5 should be released within the next few days.

Mishkin said:

Yes, it's the page parent dropdown on the right side when editing a page. I'm using WP 2.8.2, qTranslate 2.4.1 and the Role Scoper 1.0.5-alpha3.

Strangely this is happening on our development site, just the live one.

Can you think of any other differences in the blog configurations?

It shouldn't be any difference at all. They are both running on the same server with their database cloned, same plugins and same theme.

Only things is the live site is running on main domain while the other one on the subdomain dev.

Mishkin said:

Version of the plugin says alpha3 in WordPress admin. I downloaded it using the link suggested in post #10.

Just recently or back when post 10 was made?