krasentomov

How you’ve resolved this? I’m experiencing the same problem, but with titles instead. I was using:

$object = new WPSEO_Frontend();
$removed_text = $object->title( false );

And then I’ve echoed the desired title, but now I get “Fatal error: Call to protected WPSEO_Frontend::__construct() from invalid context in ….”

I get that with 1.7.3.

Edit: Same problem with 1.7.2. I’m back to 1.7.1 until the problems are resolved.

So here is the old versions – fmag1.com
Wordpress 2.9
Wordpress subdomains 0.6.9

In the admin panel the only option I’ve selected is “Make all Subdomains” and when you select from the sidebar one of the categories, you get the archive template.

Hi there!

I’ve tried everything you’ve proposed but still no joy. What happens is when I put the tick on “Subdomain Roots as Indexes” – the main menu disappear.

You can see it live currently at provik dot bg. I have two categories with two posts test1(post) in test1(category) and test2(post) in test2(category). The menu shows correctly in the main domain but not in the categories, but it show when you enter in the post – for ex. test1 post.

Moreover if I put debug mode to true I see lot’s of errors:

Notice: Trying to get property of non-object in /***/public_html/wp-content/plugins/wp-subdomains-revisited/plugin/classes.php on line 437

Notice: Trying to get property of non-object in /***/public_html/wp-content/plugins/wp-subdomains-revisited/plugin/classes.php on line 438

Notice: Trying to get property of non-object in /***/public_html/wp-content/plugins/wp-subdomains-revisited/plugin/classes.php on line 439

How the plugin worked before it was revisited:
When you activate the plugin and put the option for categories to be subdomains – it would make every category on its subdomain asking the template to give the category.php template for the corresponding category so if you are in test1 category, you will see only posts from test1. If you mark “Subdomain Roots as Indexes” it would give you only posts from test1 category but it would use index.php of the template, instead of category.php

If you would like I could setup test installation with old wordpress and the old version of the plugin?

Thank you for your replies!
Regards,
Krasen

First of all I appreciate your efforts to give the community a working version of the plugin. Maybe I haven’t made myself clear. Sorry about that.

The tick on Subdomain Roots as Indexes means that the plugin won’t use the archive template, but the home page of the template for every subdomain right? I am saying if it’s not marked – no matter what template you are using, even the default one. You’ll get all the posts in every subdomain no matter on which category you are.

Here are some screenshots

Index page
Subdomain Test 1
Subdomain Test 2

As you can see every subdomain shows all the posts, not as it’s it is in the category archive of the page without the plugin.

Test post 1 should be only visible in test1 subdomain and Test post 2 should be only visible in test2 subdomain. This is not a problem with the custom layout builders, because this is one of the default themes with wordpress – Twenty Eleven

So I thought it was something with the queries, because if you tick the “Subdomain Roots as Indexes” option it would filter the posts and will show me only the posts for a specific categories, so it’s something with the query with the archive templates that the plugin do.

I’ve installed the plugin 30 minutes ago, so I can’t say much.
It looks nice and it’s logging correctly.

Positive!

[root@vps plugins]# find . | xargs grep ‘sort_both.png’
./seo-crawlytics/include/resources/base.css:.sorting { background: url(‘../images/sort_both.png’) no-repeat center right; }

As I see there is new release from 13th this month, but there is no option to select other taxonomy than categories.
Do you plan to implement such a function in the near future?
Thanks

Thenk you for the great fix alanna.scott it worked like a charm for my custom post type.
But now I have another problem – it simply doesn’t work for custom taxonomies.
Does someone know a fix for it too? It is crucial for me and I believe for many others. Too bad that the plugin haven’t got any update for the last year and a half.