• 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!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Andrea Landonio

    (@lando1982)

    Hi! I’ve not totally understood your question… I’m sorry.. the plugin creates a basic set of fields on CS automatically (for standard WordPress fields like id, post_title, post_content, post_date, etc) then, you can, using the settings page in the plugin, choose another set of custom fields (postmeta) retrieve from your site db.
    In the settings page you can set how to search postmeta fields on your DB, for example, providing a prefix, a starting char, or more…

    I’ve never using the plugin with WooCommerce unfortunately, so I’m not sure if there is a limit with that…

    Thread Starter wpuserepi

    (@wpuserepi)

    Hello there! Thanks for your reply here Andrea. I realized that during setup of the CloudSearch domain within AWS one can simply choose to define the index later; thus allowing me to complete the creation of the search instance.

    If I learn anything useful regarding the integration of WooCommerce I will share it here.

    Thanks

    Plugin Author Andrea Landonio

    (@lando1982)

    Awesome!! Thanks a lot!!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Configure CloudSearch index properly’ is closed to new replies.