NanoWisdoms

I have not had time to upgrade the website as there is a lot of custom code and plugin modifications I have to test when I upgrade. I hope to do it this year.

Any suggestions about if this can be done with Contact Form 7 and if so, how?

Thx

Contact Form 7 v5.1.1
Wordpress v4.9.6

I have 2 forms on this page where I want to use reCAPTCHA:

https://ismailidigest.org/contact-suggest-a-link/

I have other private pages with forms where I do not want to use reCAPTCHA because reCAPTCHA always rejects them and says they are spam.

• This reply was modified 2 years, 7 months ago by NanoWisdoms.

WP-Pipes should not update posts unless you run the pipe manually in the browser in update mode. There is an undocumented way to run a pipe in update mode from a cronjob (adding a “u” parameter to the URL), but I doubt you’re using that.

Assuming you’re using a cronjob to activate the pipe, it will continuously fetch all new articles from the website, including one’s it’s already processed. But to speed things up, it will not actually go to the website if it finds a copy of the article in its own cache.

It then checks the post title and post slug of every article fetched against what is stored in the database (i.e. your blog). If EITHER matches a post in the database, it assumes the article has already been loaded and ignores it. Otherwise it will assume it’s a new article and create a new post.

If you’re familiar with PHP check function “store”, in wp-content\plugins\wp-pipes\plugins\adapters\post\post.php (around line 70)

store will call checkDuplicate, and if checkDuplicate finds a post that matches the slug OR the title of the new article, store just returns without doing anything more unless you’re running in update mode (i.e. manually). If a post is not found, or you’re running in update mode, then store calls storeContent which will create a new post or update the existing one found.

Hope this helps.

Something is not making sense to me.

“aga” works (7307 published posts according to WordPress Admin search):
https://ismailidigest.org/?s=aga

“finder” works (9,532 published posts according to WordPress Admin search):
https://ismailidigest.org/?s=finder

BUT “aga finder” does not work (6,658 published posts according to WordPress Admin search):
https://ismailidigest.org/?s=aga+finder

How can these words be “too popular” when they work on their own but not together?

I am unable to report how many posts Relevannsi has for these words, because after I put some stop words, it is no longer recommending stop words.

The default operator is AND, and OR fall back is disabled.

Hi,

but on the other hand, if the search term returns over 11000 posts, I don’t think anyone’s going to go through all of those in any case – at that point the searcher should introduce more keywords to narrow down the search anyway

Of course a user would add additional key words, but the problem is adding additional key words to narrow the results doesn’t work. If the search includes keyword(s) that fail, additional keywords don’t help and the search still fails even though it’s a narrower search.

For example, if I add “indonesia” (which occurs 116 times by itself), to the above 2 word search (that doesn’t work … “aga khan”), to narrow down the search, it should just return 101 posts (according to the WordPress Admin Posts search), but this more narrow search, with the additional keywords, doesn’t work either:

https://ismailidigest.org/?s=aga+khan+indonesia

Or, if I add use “Yogyakarta” instead (which should return just 9 posts), it still doesn’t work:

https://ismailidigest.org/?s=aga+khan+Yogyakarta

The stranger thing is that the word “Aga” appears in 6647 posts (according to stop-words count) and the word “Khan” in 6996 posts (according to stop-words count). However, these keywords don’t fail when searched on their own, but fail when used together as “aga khan” (which should narrow the results).

Similarly, other words like “finder” which occurs in 10,003 posts (according to stop-words count) doesn’t fail on its own, but does when used with “aga” (as in “aga finder”).

So in these cases the single words are working but the narrower search with more keywords is not!

• This reply was modified 5 years, 11 months ago by NanoWisdoms.
• This reply was modified 5 years, 11 months ago by NanoWisdoms.

Hi,

I’m sorting results by date, and so “throttle searches” is disabled.

Ok after much testing here’s what works and what doesn’t.

What works in v5.0.6:

• Add the following snippet to the end of the functions.php file of your active theme:
  update_option( 'su_option_do_nested_shortcodes_alt', true, false );

  WITH

• double underscores for 3rd level nesting (as in v5.0.3).

In other words, by adding this line of PHP AND keeping everything as it was in v5.0.3 (i.e. double underscores for 3rd level nesting), v5.0.6 works like v5.0.3.

What doesn’t work:

• Anything else.

Nothing else works because the developer says 3rd level nesting was never supported and just a “mistake”. In my view, a very happy and useful mistake that should be officially supported.

Ok thanks, I will do that.

I think you should officially support it. The code already works and it’s very useful. Many are using it and there’s really no need to restrict it 2 levels.

So then how do you do 3rd level nested accordion if it was invalid?

Look closely again. That is a 3rd level nested accordion. It worked fine in 5.0.3.

3rd level needed two _ not one _.

As I explained in that thread with the “solution”, I’m using the correct syntax, so there should be no need to make any changes to functions.php.

Look closely at the code above. The syntax is correct. It used to work in v5.0.3 and stopped working in v5.0.4.

Did you change the syntax from v5.0.3 to v5.0.4?

I am using the correct syntax. Please see the link above. All my code is there. It worked fine until 5.0.4. Others, using the correct syntax, also reported no problems until v5.0.4 also.

Did you change the syntax from v5.0.3 to v5.0.4?

FYI here is my syntax from v5.0.3.

And here is the result (not working in v5.0.4 – v5.0.6):

Here is it working in 5.0.3:

• This reply was modified 6 years, 2 months ago by NanoWisdoms.
• This reply was modified 6 years, 2 months ago by NanoWisdoms.
• This reply was modified 6 years, 2 months ago by NanoWisdoms.