woltis

Thanks for the answer.
So there is only the way to exclude a tag with a certain id or class and not a tag in general like “blockqoute”?

Thank you, Thimo!

I just opened the form and clicked on the setting of the text-field and noticed, that the regular expression has been split up. The original value ^(.|\n){0,5600}$ became a \n){0,5600}$| (pipe at the end!) in the regex-field and the fragment ^(. appeared in the field “Standard value”.

I recreated the original expression and saved the value again. Called the field-settings again and everything appeared correctly.

I tried to reproduce the split-error, but wasn’t able to. Now the form seems to work.

• This reply was modified 7 years, 6 months ago by woltis.

@jrvidaud

Deleting the folder changes nothing – except all whitelisted urls are gone from the firwall-setting.

The best solution is: do nothing!

It’s a false alert.

@wfasa

I deleted the folder as requested, it is recreated immediately by the plugin – and the file attack-data.php looks exactly the same, including the strange NUL values.

So deleting the folder changes nothing – except all whitelisted urls are gone from the firwall-setting. I would not recommend to delete this folder.

On one side it seems to be a false alert, on the other hand it might be useful to find out, where those strange NUL values come from.

• This reply was modified 7 years, 8 months ago by woltis.
• This reply was modified 7 years, 8 months ago by woltis.

Thank you for this topic!
I also had the problem, that css and scripts were not loaded, when enabeling friendly urls.

Just inserting the line

RewriteBase /wp-content/plugins/bwp-minify/cache

into the file

./wp-content/plugins/bwp-minify/cache/.htaccess

Has made everything work! Changing the .htaccess in the /min/ directory was not necessary. Thank you, Kokers!

@khang Minh: It would be great, if that line would be inserted automatically.

Hello Mikko,

thank you for confirming this solution!

Hello,

I looked around in the Relevanssi knowledge-base and found the following issue:
https://www.relevanssi.com/knowledge-base/custom-post-type-filtering-produces-empty-results/

So with trial and error I just put the second filter into the functions.php

add_filter('relevanssi_search_ok', 'relevanssi_disable_filter');
function relevanssi_disable_filter($ok) {
    global $wp_query;
    if (empty($wp_query->query_vars['s']) || $wp_query->query_vars['s'] == " ") {
        return false;
    }
    else {
        return $ok;
    }
}

With this code the items are shown in the podcast feed of Podlove.

But, well, I have no idea what I really did or what other unwanted things this filter might cause. So far I haven’t noticed any other bugs coming up and even Relevanssi seems to work.

Any comment, if this solution is a good solution would be helpful ??

Thank you!

Any news here? When will this bug be repaired?

Thank you for this honest evaluation. I disabled the WP Comments feature and returned to the normal comment form.
I also disabled the TAF-feature.
So now I updated to version 14.11.4.

Now 14.10.1 is back again and the ajax-comment-form works like a charmw ??

Just disabled Wordfence, but 403 remains. Must be another reason for this.

The change to non-Ajax only is sad, because ajay is the main reason why I use cforms for comments. without Ajax cforms would not make sense.

I will switch back to 14.10.1 in a minute.

There is no change after deleting the code.

Wordfence is installed.
Are there any changes with the GET-parameters? 14.10.1 had no problems.