blankpoint

Agreed. With thousands of posts and thousands of comments per day, I don’t want my front page purged every time a comment is posted. I *do* want it purged when I post new content or edit posts.

Please break these options down into separate choices as suggested above.

Also very interested to get an answer to this. Everything is switching to InnoDB, and this plugin should support full-text index with InnoDB asap!

Another request here… huge traffic and a noticeable improvement in db response time when we change the format of the posts table from MyISAM to InnoDB. Now that 5.6 supports it, can you pleas let YARPP support full functionality with InnoDB posts tables?

Thanks, Chouby. I’m relieved that the bug has been caught. I’ll hold off and stay with 0.8 until you release 0.8.4. Hope that’s coming soon.

I’ve tried a bunch of different things, but no matter what, when I upgrade to 0.8.3, this bug keeps returning. Could it be because I am going from 0.8 straight to 0.8.3. I had the buggy intermediate versions installed, but reverted back to 0.8. Maybe the bug only manifests that way?

Anyway, do you have any suggestion for getting things working normally? I would delete the plugin and its tables completely and start from scratch, but I have a lot of custom strings defined already, and so I’m not keen to do that.

+1 for putting custom string management into the gui.

Thanks.

By the way, 0.8 does correctly link to https://www.example.com/en/

The error exists in a slightly different form in 0.8.3.

Permalink structure is /blog/%postname%/

Using pll_the_languages, the language switch works on all pages EXCEPT FOR THE FRONT PAGE. The front page, say in default language (French in my case, but I have default language info hidden in URLs), is https://www.example.com .

When I click the link to switch to English, I get https://www.example.com/blog/en/ , which throws a 404. The correct link for the home page should be https://www.example.com/en/ . When I manually go to this URL, it does show the homepage in English.

In case it matters, my home page shows most recent posts.

Thanks for letting me know. Would prefer to stick with the “official” releases. I assume the fix will be in the next proper version? Is 3.4 changing permalink handling or what? I can’t find any reference to that.

Andrea, just to clarify — is the following setup possible?

1. MAIN SITE –> https://www.maindomain.com

2. maindomain.com and maindomain.com/whatever will redirect to https://www.maindomain.com and https://www.maindomain.com/whatever, respectively

3. secondary.maindomain.com for multi-site blogs

4. alternate domains for selected multi-site blogs, with www –> https://www.anotherdomain.com (anotherdomain.com would redirect to https://www.anotherdomain.com)

Hope these questions are clear. Thanks for your work.

Well, it looks like it just took about an hour and things were working with the updated number of posts. Maybe you can bring back the message that it is re-building the cache, so we know things are churning in the background?

Oh, I am using the latest version of the plugin, and have tried deactivating and reactivating. PHP5 and MySQL5.

I’m having the same problem, and there are several forum posts that indicate other people have the problem, with no offered solution. Anyone? It was working fine for me and suddenly started doing this in 2.7.1.

I’m having the same problem, and there are several forum posts that indicate other people have the problem, with no offered solution. Anyone? It was working fine for me and suddenly started doing this in 2.7.1.

I’m having the same problem, and there are several forum posts that indicate other people have the problem, with no offered solution. Anyone? It was working fine for me and suddenly started doing this in 2.7.1.

I finally solved the problem on my own.

My host is 1&1 and by default, PHP version 4 is used. Go to the root directory of the site and if there is an .htaccess file, add the following line to it:

AddType x-mapp-php5 .php

This will make PHP 5 the default for .php files. This plugin then works.