John O

I too came to post about a similar issue – I have been having a similar issue with Advanced Custom Fields datetime picker width since the latest Yoast update, I suspect it might all be related. :-/

Fab, thanks for letting me know – it makes sense to be included in register_post_type() like you say. ??

Hi – so if I read that right, the Tweet count functionality has been deprecated by Twitter themselves? How do I remove a Tweet count zero from showing in your plugin? Is this possible? Thanks. ??

Ignore me – I am being daft!

Ok – maybe i should find a different plugin – or is it just certain aspects of iThemes that don’t work?

Got it – replied. ??

Great thanks so much for all your help.

Can you explain what you did to make it work?

Is there any way to bring this to the attention of other iThemes users? Some people might be happily storing their db backups without checking they actually work.

It works! Sorry for the false alarm.

Database backup imported with no errors. A cursory look around the site and everything looks ok. Thank you so much. ??

Is it worth telling iThemes that you have fixed this bug? I submitted a bug report and pointed them at this thread, so I am assuming they will fix things eventually?

Is there anything I need to know about the edited file? Is it ok to deploy on a live site or would you suggest waiting for iThemes to fix this?

No hang on – I didn’t create the backup with your new file in place. Sorry, long weekend. Watch this space…

Hi – tried it this morning. Still getting the same errors. ??

i have submitted a bug report, referencing this forum thread.

I will try your solution on my dev server and let you know how it goes.

Thanks again for all the help.

Hi,

Sorry I misunderstood, I thought you were an iThemes support chap! I will report the bug.

What should I write in the bug report to make sure it is clear what the problem is?

And thank you again for all your help with this.

Hi – just to clarify, when you say:

Testing fixed Backup code as we speak …

Does this mean there will be an update to the plugin that will resolve this issue?

Thanks.

You are indeed correct!

I found several records with identical primary keys because of the conversion from hex to UTF8. The ID hex values are different in the database but the UTF8 converted values in the backup file are identical.

Hi,

I fixed the import!

I found record 270 was one after the error, and it is this:

Screenshot link

I have added it as an image link as every time I paste it in, the content changes.

I deleted this record, and tried the import again and it worked fine.

Any idea what is wrong with this record?

Thanks for your help with this.