greeso

Thanks. What about MariaDB? I am assuming the same.

Thanks.

Thanks.

Thanks and cheers. You are awesome.

I do not think converting to MyISAM is a good idea if you are using Amazon Web Services (AWS). Because if you use RDS to create a MySQL, then the backup service would not work. Amazon is moving away from MyISAM and supporting InnoDB. Their backup service works with InnoDB. So, if you want to take advantage of AWS, and I think backup is a necessary feature, then the solution above that converts the table from InnoDB to MyISAM is not good.

Bottom line, please fix the plugin to support InnoDB.

Why leave the origin empty? Isn’t that supposed to be the S3 bucket that we created?

Thanks.

Thanks for the great response gecko_guy. I have a question though.

Why leave “origin” empty, shouldn’t I choose the S3 bucket I created as the origin?

Thanks.

gecho_guy:

Can you explain to me how you setup CloudFront? I am having that exact same problem. No documentation ??

I am in the same situation as you, I think I will look for something else. This plugin used to be OK, however lack of support and lack of listening to customers is driving everyone away. If you read the discussion, there are a lot of requests for InnoDB, but no response.

Thanks. It worked. This is a workaround, however it convert the wp_posts table to MYISAMM. I think I will do that for the time being, however I think this is not the right solution. A correct solution should keep the enging InnoDB, and be able to work with it because InnoDB does support full text indexes now.

@toddzebert

Sorry, I am not sure what you are referring to, can you elaborate please? I could not find what you were talking about.

@gennady Kovshenin

Which button is that? Where is the “Create fulltext indexes” button? Can you please elaborate?

I have the same exact problem. This is a serious issue. Ajax will only work if you are logged in to the backend. Once you log off, Ajax will stop working.