Jamil Jonna

I tried using and it inputted a tab but the output just had the html entity. This is really still a problem because the extension is CSV. If you the point is to output a CSV it should be correctly delimited.

Is it possible to use a tab character?

Never mind. Sorry, I stupidly missed that I could change the text qualifier.

Yes, this should be fixed right away because it breaks functionality in Woocommerce 3. See: 3.0 error option ajax is not allowed for select2

• This reply was modified 7 years, 7 months ago by Jamil Jonna.

Same issue here. This is very problematic. I have over 3k posts that use this plugin and this appears to be impacting all of them. I looked into one such post and noticed that the term_order in the wp_term_relationships table has the correct order for the authors. So it appears that co-authors is not respecting the term order.

I just realized you can simply move the entire backup folder. However, does that backup folder contain file types that are not recognized by ShortPixel? I.e., audio files, PDFs, etc.?

Is there a way to restore backups easily? It would be ridiculous to have to click “restore backup” for each individual image.

Refreshing permalinks DID NOT work for me. I had do downgrade then refresh permalinks. I am not exactly sure what is going. I also use Custom Post Type Permalinks and I thought that was the issue but apparently not. I think it is reasonable to wait until the next update.

I am getting this same error as well as a number of others. Please let me know if you find any solution.

some problem here. It would be nice to know when this is fixed

If anyone needs help fixing their terms, the method I used was to find all of the duplicate term entries created by CAP, delete them, and then change the slug to “cap-%” (%=wildcard). You can do this pretty easily by exporting your terms table and creating a MATCH column in Excel. The you have to create a bunch of MySQL commands to delete the extra terms, and the update the other terms.

So, I went through the tedious process of fixing all of these problems and now I have noticed that coauthors seems to disregard the sorting behavior of coauthors. I don’t remember this being the case before. Is there anyway to fix this? It is a major problem for sites that have books, as ours does. Feel free to move this to a new topic.

Edit: Actually, I know this is not how it used to work. Because this post is sorting correctly: https://monthlyreview.org/2012/09/01/medicine-and-empire. However, this is version 3.0—I have not updated yet. So, either the “magic” fix I just made screwed something up, or the behavior is different. I would love to know the answer here.

Moving the part of the discussion about sorting here: https://www.ads-software.com/support/topic/coauthor-sort-order-lost-in-31-or-32

I’m not sure you have any idea what an amazing clusterfuck this has created. In my DB, there are now hundreds of duplicate “cap-%” (%=wildcard) terms and because of their existence, I cannot change all of the incorrect “%-2” terms to “cap-%” since they MySQL correctly identifies them as duplicates. Did you really not write a script to transform these terms when you made this change? This seems like pretty bad programming.

In any case, what would you suggest I do? Delete all the current “cap-%” terms and so that I can change the current “%-2” terms? What a mess.

Further, this now appears to have created a disconnection with the authors database, such that the author posts don’t register correctly. This is really quite unfortunate.

Thank you: that did work.

But I feel like I should remind you that everything worked just fine before the update. Perhaps you should write a script to help folks that are having problems like this as I’m sure there are more? Or maybe you can help me “magically” change the 400 or so terms that need to be changed?

Is it ok to downgrade to the 2x branch? It does not seem like you’ll be getting this fixed any time soon.

Thanks.