Hello Support,

I’m contacting you to let you know were having issues with your plugin. We are currently running version ?2.12.0 and on March 27th all of our locations had stop updating on the same date. We are running the same verison on another one of our sites on a different server and it is updating fine. Below was the following response from aws support team.

—————————————————————————————————————-

The internal team has further investigated the issue and their comments suggests that a client side issue might be preventing the documents to be uploaded properly. For instance, the information about fields are missing form the documents.

Please note that the third party plugin that you are using is not officially supported by AWS.

However, the internal CloudSearch team has requested if you could kindly inspect the logs on your end to ensure that the documents are uploaded as mentioned in the documentation [1].

On a further note, another indication that suggests the issue is occurring as a result of how the plugin works is the 400 errors occurred as a result of not well formed requests.

Please do let me know if you require further assistance upon inspecting the client logs so that I can continue the investigation of the issue with CloudSearch internal team.

Feel free to reach out to me if you have any further questions or concerns. I’d be happy to help.

—————————————————————————————————————

Any advice would be appreciated.

Trying to setup this plugin and index documents. I am able to get a number for indexes but getting errors when Syncing.

Here’s what I see

Searchable documents?Error loading searchable documents: error reading searchable documents
Site documents?Error loading site documents: error reading site documents

And here’s the error I get when I “Test Connection”
Error: Error executing "Search" on "2013-01-01/search"; AWS HTTP error: cURL error 6: Could not resolve host: 2013-01-01 (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for 2013-01-01/search

I am running it on a Wp-engine Staging server with a staging generated domain.

Any help would be greatly appreciated!

What PHP Versions does the plugin support? Is it PHP 8.0 compatible?

Hello, I am wondering for giving the Amazon Cloud Search a try, but I find it way tooo complicated to get just an estimation what costs would come with it for an “average” web page or shop.

Maybe you can give some idea, if we might talk about 5 or 10 or 100 or even more USD per month?

I had tried Google Search before, there I ended with less than 5,- Euro a month – but I was not happy with the search itself.

THANK YOU!
Sandra

hallo Andrea, thanks for develop this great plugin but I have problem, how to change load more button to pagination numbers? I just want to using my template search result with pagination numbers, if I using your plugin that pagination numbers changed by load more button that very annoying if you load hundreds and hundreds result of post and will disappear if your refresh it.

Thanks for help

• This topic was modified 1 year, 8 months ago by hargums.

Hello, I am wondering if this plugin might work for a product search in WooCommerce, too?

Is there an option to choose “products” as type?

And what I do not really understand – how do I then implement the search form into my page? Is there a shortcode or a widget? – Or is the plugin replacing the existing one? (which would be fine!)

Thank you!
Sandra

hello, i am installing new Wp. I have made all the settings as they should be, but the wp_admin login page view is opening with problems. When I log in as an admin, I get a not secure warning and the administration panel does not open.
After the error, I automatically installed the Wp application application in Wp Cpanel add software, this time the wp management panel opens, everything works as normal, but the theme preview does not appear and plugins such as Elementor do not work.
The SSL Certificate is available on the domain.
I’ve installed Wp many times, but I can’t get past this problem.`

The information you are about to send is not secure

Screenshot

• This topic was modified 2 years, 3 months ago by halilerdogan77.

Hi, we are looking for a plugin which can be used in multiple wordpress websites. We want to index all the wordpress sites pages,posts in one cloud search domain, so that we can display results from which the user is searching and also from the other sites. is it possible using this plugin? I see that this is working with one wordpress site and one cloud search domain. But not with multiple wordpress sites + one cloud search domain.

waiting for your reply.

Hello,

We have been getting a lot of random 500 errors on results page. The plugin has been updated as well. Everything is was configured and had worked prior Any help would be appreciated.
Thanks,
Shawn

Using the plugin is simple enough! However, it is a bit unclear on the proper configuration of the CloudSearch domain index and its fields.

The fields which the plugin posts within documents must match the fields expected by the search domain index. CloudSearch offers some defaults for HTML such as:
content
content_encoding
content_language
content_type
description
generator
keywords
resourcename
title

Does there exist a list of the fields and their names which the plugin uses, including WooCommerce.

Thanks much!

Hello, I’d like to know if this plugin allows PDF or Doc indexing. If it doesn’t out of the box, is there a way to achieve this? Thanks.

We have followed all the steps mentioned on the plugin page to set up the plugin on the website.
but when we are searching results on ‘Run test search’ on AWS Cloudsearch, it does not give me results for all custom fields like checkbox, select list, radio buttons, etc.

We have created different custom fields on website as per this screenshot.

we can see indexing of above-mentioned custom field has done correctly on Cloudsearch. see screenshot here

But when I am searching this post on Clousearch it is not returning results for custom fields and showing empty data in facets as well. refer this screenshot

Can anyone support us here to resolve this issue?

• This topic was modified 3 years, 5 months ago by TeenLife.
• This topic was modified 3 years, 5 months ago by TeenLife.

Hello,

In the schema, we have CloudSearch set up to only include posts and pages that have been published. However – SERP shows posts with draft links (for example: https://www.genengnews.com/uncategorized/152290-revision-v1/) instead of the final published url (in the above example, this is the final published post’s url: https://www.genengnews.com/news/human-airway-basal-stem-cells-created-from-patients-cells/). However, to find the final published post, you need to search for part of its title. It does not always come up if you search for a category it is tagged on even if that category is mentioned in the post.

Also, the SERP includes links to media file, but we have cloudsearch plugin set to only index and return posts and pages not items in the media library

I re-indexed and ran a cache invalidation in case the SERP results were cached, but the results set still includes the above mentioned items when it shouldn’t.

How do I get the plugin to only index and display what’s set in the schema (only published posts and pages)?

Hello, when trying to activate the plugin we are getting the following error:

Fatal error: Can’t use method return value in write context in …\wp-content\plugins\cloud-search\actions\cloud-search-action-manage.php on line 262

Any help would be appreciated

Hi I am facing an issue with issue with the keyword highlighting on searched results.

When we search multiple keywords for example “advanced and basic” it fetched all the posts with these two keywords but it does not highlight the these keywords in the searched result page.

Also what is the best way to find the occurrence of searched keyword in the searched post?

Thanks in advance.

Hi Mate,

Could you share some information about suggester fuzzy matching?

https://docs.aws.amazon.com/cloudsearch/latest/developerguide/getting-suggestions.html

As I notice currently your plugin does not support it. Correct?

Thanks
Harshad

While it is possible to specify a non-production cloudsearch domain to index/search using a constant in wp-config,(WP_ACS_SEARCH_DOMAIN) it would be good if there were a way to be disable indexing for dev/staging sites while still being able to search the production domain.

I am using this to search products, and I want to be able to use the product_visibility taxonomy to control what products show up in search.

I think I had hardcoded something to modify the filterquery a while back and forgot about it.

I have included this taxonomy in the indexed fields, but there doesn’t seem to be any way to add such a filter to the search query.

To get the desired effect, I have added the following to actions/cloud-search-action-search.php:275

$search_args['filterQuery']= '(and ' . $search_args['filterQuery'] . "(not ct_product_visibility:'exclude-from-search'))";

Adding a filter hook to this element of the array would be very useful.

• This topic was modified 4 years, 7 months ago by bheadrick.

Hey guys first thanks for great plugin. I just found one issue with cloud-search.min.js?ver=2.8.4 file that when we set the template for no result the data in not append by following line:

jQuery(ACS.params.container_result_items).append(result.data.message);

Because the response come into the .items, not in .message, I have updated this line to

jQuery(ACS.params.container_result_items).append(result.data.items);

and it’s working. Please make the little change in your great plugin.

• This topic was modified 4 years, 8 months ago by harshadmishra2807.

Hi,

First of all thanks a lot for such a great plugin.

I’m running multiple WP sites that are separate (both server and content-wise). I was wondering if it’s possible to use your plugin in a way, that all my sites would use one CloudSearch instance?

Thanks,
Tony

• This topic was modified 4 years, 9 months ago by T0ny. Reason: typo in title

I cannot save the options under Schema Settings on the Settings page. If I, for instance, put a check mark next to “Pages,” in the “Post Types” section, when I click the Save button, the page reloads and the check mark is gone from “Pages.” This is true even on a brand new test site: new DB, WP5.3.2, TwentyTwenty theme, and only Cloud Search plugin activated.

So, this is probably pretty simple but I can’t activate the plugin…

wp plugin activate cloud-search
You don't have the permissions to perform this operation.%

Of course, I checked the permissions and I do have rwx.

I also tried activating/deactivating other plugins (no problem there — issue is with this plugin only).

I also tried it from the plugins page in wp-admin. That also failed to activate.

Hi,

Been using this plugin for awhile now (over a year) without issue but it’s suddenly giving a warning when you click the search button (or hit enter):

“This is a non-secure form.
This form will be sent in a way that is not secure. Are you sure you want to send it?”

Then when you click send, it takes you to a blank search results page.

That above error is from Safari, Chrome does not show an error but it does also take you to a blank search results even if you search for something you are sure is in the database (on this site I use “compost” as I know there are multiple posts with that word).

Any ideas on how to fix?

Thank you for this module!

Jen

Hi there,

(Thanks again for a great plugin!)

I discovered what I think is a small bug today which took ages to track down. At the moment, if you use the acs_exclude custom field to exclude items from the index, it breaks the sync all functionality.

The sync all code currently reads a chunk of 100 posts, and processes them. If the number processed is equal to the chunk size, then it gets the next chunk and all have been sync’ed. However, for example, 1 post is acs_excluded, then the number processed would only be 99 and so it thinks it is finished prematurely.

This is the code in the sync loop that doesn’t increment the count in this case:

if ( ! isset( $excluded ) || empty( $excluded ) || $excluded != 1 ) {
    // Prepare and add document
    $prepared_doc_array = acs_prepare_document( $item );
    if ( ! empty( $prepared_doc_array ) ) {
        $docs[] = $prepared_doc_array;
        $count = $count + 1;
    }
}

I’m tempted to say the fix should be to increment the count outside the if statement? The count should be the number of docs that we considered for indexing, not the actual number indexed?

Thanks!
Jon

Hello,

Hello,

When I want to ‘run index’ it does not index any field to me and it throws me the following errors:
Error loading searchable documents: error reading searchable documents
Site documents: Error loading site documents: parsererror

And when I want to ‘update / create index’, it shows me the following error:

1 validation error detected: Value ‘[site_id, blog_id, id, post_type, post_status, post_format, post_title, post_content, post_excerpt, post_url, post_image, post_date, post_date_gmt, post_modified, post_modified_gmt, post_author, post_author_name, post_extra, category, tag, cf_zona, cf_mapa, cf_imagenes, cf_subtítulo, cf_categoria_de_precios]’ at ‘fieldNames’ failed to satisfy constraint: Member must satisfy constraint: [Member must have length less than or equal to 64, Member must have length greater than or equal to 1, Member must satisfy regular expression pattern: ([a-z][a-z0-9_]*\*?|\*[a-z0-9_]*)]

How can I solve this problem?
I await your answer as soon as possible.

Regards,
Damian

Hi there,

Firstly thanks for this plugin – it’s really great.

I was wondering if you could add support for Date types in addition to int, double or literal ?

Thanks
Jon

I noticed that you’re using admin-ajax for the suggestions / live search.
This could be way faster if you used an api endpoint instead.

Also, I noticed that the filter string is hardcoded as just blank.

It would be nice to be able to inject a filter string there (along with applying the same filter string on the main search) – either through another option field or with a filter hook.

To fix this, I changed this

else $field_sort = $result_field_filtered[ 'Options' ][ 'TextOptions' ][ 'SortEnabled' ];

to this:

 else if(isset($result_field_filtered[ 'Options' ][ 'TextOptions' ])) 
	    	{
	    		$field_sort = $result_field_filtered[ 'Options' ][ 'TextOptions' ][ 'SortEnabled' ];
	    	}

All of my “sortable” fields are empty.

Hey I’ve been using this plugin for awhile now and it’s been working great.

However, just ran into an issue I can’t seem to figure out.

Using the Settings panel for the plugin I added some additional post types to the list of ones I wanted indexed.

The Create/update index command.

And followed that up with Run indexing.

Everything finished with no obvious issues.

However, when I was searching some of the post types don’t seem to have been indexed at all. I confirmed this by running some queries directly from the AWS panel using the “matchall” query with a post_type filter and while I can retrieve a few of the post types a number of them return no results at all.

I’m on the latest version 2.5.0.

Any way I can facilitate you taking a look into this would be great.

We have our wordpress site powered by an AWS EC2 instance which serves our entire site through the cloudfront CDN. The EC2 instance is the origin for the cloudfront distribution. With our set up and site serving through cloudfront CDN, we need to set in our cloudfront settings which headers to allow through to our origin EC2 server. Which specific headers and their values do we need to enable/whitelist to make your cloudsearch plugin work on this setup? Please also see the error screenshot here: https://app.box.com/s/lnmq16lycoxmffiq0utaidhkp6trmvef

I have gotten your cloudsearch plugin working fine (and it works great!) with our cloudsearch instance on our sandbox website which runs on an EC2 server. The only difference is our sandbox site doesn’t get served out through the cloudfront CDN. The only other thing I can think of is we have another wordpress plugin running on our production server that connects to AWS services specifically for clearing cloudfront caches when we update content on our site, so maybe that is not allowing your plugin or the AWS plugin to talk to AWS at the same time? Any help or insight would be greatly appreciated as I really want to get your great plugin working on our production website.