Hi Guys,
I am just researching Cloudsearch as an alternative for the soon the be defunct Google Site Search. Your plugin looks very interesting, however there is one thing that concerns me for the particular site I am looking at.
The site uses the WordPress REST API to get all of its content from a ‘feeder’ site. That means that in the WordPress database a particular page has only the Title, Excerpt and a custom field that is used to retrieve the required content. This content comes into the page as a JSON feed and is then reformatted to display on the page.
I am just working through the video you did with Amazon at https://www.youtube.com/watch?v=TQ96Rrys4Ks. At about the 15 minute mark you mention the schema. There are a couple of questions I have from that: –
Is our case too special to really get your plugin to work effectively do you think?
Thanks
]]>Hi!
I try to setup this plugin but I can’t save my keys. An error appears but I have no idea what is going on. Check out: https://screencast.com/t/l0biouYSQem
I have set the AWS policy for full access to Cloudsearch. And: I have tested my API keys successfully with another similar Cloudsearch plugin, but I want to use Lift!
Looking forward to your reply. Thanks!
]]>Hello. Some of you know tell me if you can configure the plugin to search in other wordpress installation (domain and different server. Not multisite)?
Currently I can do it with the Google Custom Search (CSE). But Google’s solution costs me almost $ 1,000 per year ??
Is it possible to search for custom fields with Lift Search for WordPress? I’ve created a custom field (foo_field) to a post and want to include it in the search.
]]>I have Lift search installed and running well. Thanks for the great plugin.
However, new posts are not being uploaded automatically. When I go to the lift search plugin page in the backend and click sync queue it uploads the posts, but if I don’t they just sit there. Is there anything I could look at to begin the debug process.
]]>1 validation error detected: Value ‘uint’ at ‘indexField.indexFieldType
]]>You have version 1.9.10 on the WordPress repository, but in GitHub, you’ve updated the version to 1.10.0, which appears to support the 2013-01-01 API for new users.
Two questions. Can you put a WP-ready version up on the plugins site to match what is in GitHub?
I tried to use the current GitHub master, but I need some pointers on how to build the .js and .css files from your source. Neither are present and the plugin chokes at displaying any admin information without them.
]]>Hi,
When we try to sync we get the error message message, is anyone able to assist please?
We tried resetting lift and still the same message appears, would appreciate a response.
403 Forbidden
Request forbidden by administrative rules.
event_log - (/nas/wp/www/cluster-2792/website/wp-content/plugins/lift-search/wp/lift-batch-handler.php:418)
send_next_batchAfter successfully activating the plugin, I am unable to view the configuration screen. The page /wp-admin/options-general.php?page=lift-search is empty. The WP core is there, but no content, nothing to configure. PHP 5.5.
]]>I get this message in Recent Errors, what is going wrong and how do i fix it?
Array
(
[code] => InvalidType
[message] => Invalid statement: Empty Principal List and Empty PrincipalGroup List
)
event_log - (/opt/www/wordpress/wp-content/plugins/lift-search/wp/domain-manager.php:200)
apply_access_policy
]]>Hi,
For some reason the documents in the queue are not being indexed and are stuck there.
How can I find out the reason this is happening and how to fix this, I did have a look at the error logs “voce-error-log” but there are no real indications.
Tried resetting lift, re-indexing but nothing works.
Hope to receive a reply sooner rather than later.
By the way, what does “Override Search” mean? Wish there would be better documentation for this plugin.
]]>I can see this error has been reported here before. I have provided the correct access key and secret key yet lift-search fails to accept them. They are 100% verifiable correct keys used in other scenarios like aws-cli.
How can I troubleshoot this issue? Is there a way to turn on logging?
Kind reagrds
Meint
Hi there!
I’m wondering if you can help me – I want to customize the search filters that show up in the UI, but I can’t figure out how to use the WordPress filters you provide. Are the docs on your website comprehensive, or are there more somewhere else you could provide a link to?
Thanks so much!
]]>I’m doing some testing of the plugin, but it seems that almost nothing is styled as pictured in some of the documentation. Did a bunch of css get dropped at some point in favor of us styling the filters ourselves? In particular I was looking at:
https://plugins.svn.www.ads-software.com/lift-search/tags/1.8.1/css/style.css
Which used to have a lot more code for absolute positioning of the filter boxes and things like that:
https://plugins.svn.www.ads-software.com/lift-search/tags/1.5.2/css/style.css
I’m not opposed to styling the boxes, but I wanted to make sure this was the intention?
]]>Hi guys!
I was trying to install and activate Lift today and got this error when I tried activating:
Warning: require_once(lift-core.php): failed to open stream: No such file or directory in /var/www/html/wp-content/plugins/lift-search/lift-search.php on line 12 Fatal error: require_once(): Failed opening required 'lift-core.php' (include_path='.:/usr/share/pear:/usr/share/php') in /var/www/html/wp-content/plugins/lift-search/lift-search.php on line 12
I see lift-core.php in the git repo, but I don’t see it in the zip download or in the plugins folder on the web host. Thoughts?
P
]]>I see my site inside admin panel and no configuration of plugin.
]]>First-up, thanks for developing what appears to be a great plugin for AWS Cloud Search. We’re trying to get set-up so that we can evaluate, but we’re having some issues getting our content indexed.
1) We have a wordpress site with 40,000 posts which we would like to search over. After installing and activating the plugin the liftsearch admin page found 1,101 documents to sync; pages, posts, attachments. We synced them and can successfully search over them. However, there are ~100,000 posts, pages, attachments, so we’re missing ~99,000 which do not appear in the queue. We’ve tried manually updating a post to trigger it to get into the queue, but that had limited success – we managed to get 1 additional post in the index by doing that way, but attempts for other posts haven’t worked. Our posts go back over 10 years and we’re wondering if the publish date has any effect on what is queued to index? Also, what about the volume of posts we’re trying to index; would that be an issue? How can we force all of our posts to get into the queue to be synced?
2) For our search we just want to search over our ‘Posts’ (related post meta, categories and tags). So we restricted the post types to just “post” as per the documentation (in our functions.php):
add_filter('lift_indexed_post_types', function( $post_types ){
$post_types[] = 'post';
return $post_types;
});This doesn’t appear to have any effect on (1) the queue of documents to be synced (if we add a new ‘Page’ we still see it in the queue) (2) the front-end search still picks-up ‘Pages’ in the results. Do we have to use the ‘lift_loop();’ and/or ‘lift_search_form();’ functions in combination with the ‘lift_indexed_post_types’ filter to get the front-end search to honour the post types?
Any insight/help would be greatly appreciated. Lift Search looks like a great way to get a good search working on WordPress and we’re hopeful this is the right solution for our needs.
Thanks in advance for your assistance.
– Richard
]]>I don’t yet have Lift working! But when I do, I’d like to use it for faceted search. I can’t find any docs on how this is possible. Can someone point me in the right direction?
]]>My posts are never leaving the “Documents to be Synced” queue, and the domain I specified doesn’t appear to exist, at least according to my CloudSearch dashboard. The ‘last synced’ time is always n/a.
I tried resetting Lift and setting the domain to a domain I created manually on CloudSearch, and it recognized that the domain existed when configuring Lift, but no documents were ever added to the CloudSearch index. In this case the ‘last synced’ time changed as the ‘sync’ happened, but there was no content in my index, and search always returned zero results.
I’m running this on a local development server, so if Amazon needs to actually visit the pages to index them, then this could be a problem, but I don’t know if this is the case.
]]>Hi There,
I’ve located the 2 files containing the endpoint variable to N.Virginia (cloud-config.php and cloud-config-api.php) and changed it to https://cloudsearch.us-west-1.amazonaws.com.
But everytime that I try to enable to plugin, it still creating the cloudsearch instance in Virginia.
Any tips on how to make it work for N.California?
Cheers,
]]>When I save Amazon key, it show Json error at lift-search/js/admin.js
var errors = $.parseJSON(resp.responseText).errors;
Please help
Hey guys,
First, thanks again for Lift, we’re using it in production now (at https://rhrealitycheck.org) and have received a lot of positive feedback from our audience and content creators.
Had some strange behavior after updating to 1.4 today. Search was only returning posts before about 2009. I reverted back to 1.3 and the results were again displayed as expected. I’m guessing it had something to do with our site in particular since that behavior wouldn’t have passed testing.
The only thing I can think of right now that makes content on our site before 2009 different than content after 2009 was the addition of a two taxonomies that no posts before it have and all after do. Do you guys have any ideas why that might have happened?
I updated our staging site to 1.4 so you can see the behavior here:
https://rhrealitycheck.staging.wpengine.com/?s=birth+control
Thanks,
Brady
When I try to activate the plugin, I receive the following message.
Plugin could not be activated because it triggered a fatal error.
Parse error: syntax error, unexpected T_FUNCTION in /…/plugins/lift-search/lift-search.php on line 85
]]>I completed all of the steps in the setup and config documentation (with success confirmation messages) but when clicking the button to view the lift dashboard, I’m redirected to the first configuration screen.
Any thoughts on what the issue could be?
]]>I cannot set it up. Allways getting this error:
There was an error authenticating. Please check your Access Key ID and Secret Access Key and try again.
Also tried to create new key pair, and the result is the same…
am I missing somtehing?
Cheers!
]]>I’ve been working on implementing Lift Search for a couple of days, styling, etc, but just now clicked on the second page of search results for the first time to find a white screen.
I have modified the results page, but I tested without any modfications and clicking to another page of results still gives me a white screen.
You can see here on a test server:
https://rhrealitycheck.wpengine.com/?s=rick+perry&date_end=1359663078&date_start=&lift_post_type=&orderby=relevancy
Is there anything else I can provide that might help debug?
]]>Can you provide an example for how I might use lift_filters_default_fields?
Can I use it to present category and/or tag filtering options to the user?
Thanks again!
Brady
]]>Just a note to say that Lift Search is queueing and sending posts/pages from the trash to be indexed… not sure if that is the desired behavior or not, but I’m guessing no.
]]>In version 1.2 it seemed the plugin only indexed pages and posts by default and I could add custom content types to index with, for instance:
add_filter('lift_indexed_post_types', function( $post_types ){
$post_types[] = 'audio';
$post_types[] = 'video';
}In version 1.3 the plugin indexes every content type by default.
I had to do this to limit to just the content types I wanted indexed:
add_filter('lift_indexed_post_types', function( $post_types ){
unset($post_types);
$post_types[] = 'audio';
$post_types[] = 'video';
$post_types[] = 'post';
$post_types[] = 'page';
return $post_types;
});It seems to work, is this correct?
Brady
]]>First, thanks for the great contribution to WordPress.
In testing Lift Search, it seems that the author name is not being sent to CloudSearch. Here’s an example of a result from the CloudSearch dashboard:
post_author_name:
comment_count:
id: 74
post_author: 2
post_date_gmt: 1357873243
post_title: Couple Refused Emergency Contraception Because of Pharmacist’s Personal Beliefs
The post author id is populated, but not the name, but I need to be able to search on the author name field.
We sometimes have coauthors for posts on our site, so we use the Coauthors Plus plugin, and that may be interfering.
https://www.ads-software.com/extend/plugins/co-authors-plus/
Can you point me in the right direction to find where the post_author_name is populated by the plugin so I can try to figure out how to fix it? Or any thoughts you might have would be great.
Thanks again,
Brady