montepente

Follow-up in case someone else gets this:

It might be caused by any cache you are using (APC, Memcached, etc). You can try to restart those.

If this doesn’t work, you could try restarting elasticsearch as well

If all that fail to work, you could do a clean install. Remove the fantastic-elasticsearch folder, then go to WP extension page and add it again from there.

I have the same problem, some warnings and then it ends in a fatal error, this happened when I tried upgrading from 1.2.3 to 2.1.0 in WP extension page :

PHP Fatal error: require_once() [function.require0]: Failed opening required ‘…/wp-content/plugins/fantastic-elasticsearch/lib/nhp/options/options.php’ in …/wp-content/plugins/fantastic-elasticsearch/elasticsearch.php on line 32

Here is a quick solution to add the not_analyzed index to elasticsearch via wordpress. I’m doing it here on the init to make sure it is taken into consideration. This is just an example, you can add some conditions to make it better performance-wise :

if ( is_plugin_active('fantastic-elasticsearch/elasticsearch.php') ) :
	add_action( 'init', 'prepare_mapping' );
endif;

function prepare_mapping()
{
	$index_exists = elasticsearch\Api::option('server_index');
	if ( $index_exists ) {
		try {
			$elasticaType =  elasticsearch\Api::index(true)->getType('post');
			$mapping_data = $elasticaType->getMapping();
			$mapping_data = $mapping_data['post']['properties'];

			$mapping_data['your_field']['type'] = 'string';
			$mapping_data['your_field']['index'] = 'not_analyzed';

			$mapping = new \Elastica_Type_Mapping();
			$mapping->setType($elasticaType);
			$mapping->setProperties($mapping_data);

			$mapping->send();
		} catch(Exception $e) {
			//Do nothing, just make sure the error is not showing
		}
	}
}

Running WordPress 3.5.2 with the plugins 0.9.2.11.

I get the same problem that you have, except, my unsuccessful transfer queue only contain my minified files. All other files are getting correctly to my self-hosted CDN. I have been looking for a solution for this bug for a week now.

Has anyone found a solution yet?

I’m experiencing the same problem here. I’m using WordPress 3.5.2 with the version 0.9.4 of the plugin.

At first, it says my tables need to be optimized. When i check the optimization checkbox and the process, it seems to do something. After a moment, it says my database has been optimized, every table have the notice that says they were optimized too.

But when i load the page again, by going in the WP Optimize tab, a notice by each tables says it still need to be optimized. The database is also the same size, nothing has changed.

So basically, it says it works, but it does not seem like it does anything at all for me. I get no error or anything.