MyFeeds — Affiliate Product Feed Importer & Shoppable Product Cards

Changelog

1.0.38

• Improved: the storefront picture on the E-commerce page shows the shop as it looks now.
• Improved: the changelog on WordPress.org was being cut off part way through. The recent releases are listed there in full again, and the complete history now ships with the plugin in changelog.txt.

1.0.37

• Fixed: a digit no longer starts a word in search. Looking for «tee» could match a sunglasses model number like 214050TEESPIBOR, and «slim» three eyeglass part numbers — the same kind of false match the whole-word rule exists to prevent. It also made search contradict itself: a long word was matched one way and a short one another.
• Improved: the size a merchant’s image CDN is asked for is now checked against that merchant instead of assumed. One widely documented parameter turned out to be ignored by a large retailer’s image server, and a wrong assumption could never correct itself before.

1.0.36

• Improved: product images are asked for at the size they are shown. Some merchants ship the print master — one feed averaged 2 MB per product image, with individual files past 25 MB — which makes a post crawl and can leave an image stuck on its alt text while the browser waits. MyFeeds now asks the merchant’s image CDN for a copy that fits the card. On a shop page with 72 product images that was 61.4 MB before and 5.8 MB after.
• Improved: for an image host MyFeeds has not seen before, it works out how to ask, once, in the background, and remembers the answer. Nothing is re-imported, no image is copied to your server, and a host that cannot make a smaller copy is left exactly as it was.
• Improved: one product, one card. Sizes of the same product are now grouped in the block picker and in the picker’s detail view, whichever way the feed writes the size — «Size 11.0 W», «Size: Large», «- S» or a separate size field. The card says how many sizes a product comes in, and the detail view lists each size and colour with its own link.
• Fixed: the detail view asked for a product’s sizes with an empty id and came back with nothing. The list of sizes stayed empty however the feed was written.
• Fixed: re-importing your feed now marks the products your merchant has withdrawn, instead of leaving them on sale with a link that goes nowhere. They are never deleted — a product already placed in a post turns into the «no longer available» card, so nothing disappears from your posts without warning. If more than half the feed would be marked at once, the import treats that as a truncated download and leaves everything alone.
• Fixed: «Showing whole-word matches only» no longer costs a row of empty space right above the products in the search window. It sits next to the result count.
• Improved: two redundant indexes have left the products table, making imports a little faster and the table a little smaller. Existing installations are cleaned up once, automatically.

1.0.35

• Improved: a search word of three letters or fewer now has to start a word, the way longer words always did. Searching «men» used to return every women’s product because the word sits inside «women»; on a real catalogue that was 58,176 matches where 27,358 were meant.
• Added: a line under the search toolbar says whether you are seeing whole-word matches, and offers the partial ones with one click. Nothing is dropped, so a Sweatshirt is still one click away from «shirt».
• Fixed: when a search found nothing and the plugin fell back to a looser match, it did not say so. It does now.
• Fixed: a number in a search was silently ignored on MySQL 8 in that fallback, because it used a word-boundary syntax that only the older MySQL understands.
• Fixed: a search word of three letters or fewer also demanded every one of its synonyms. Searching «men» quietly meant «men and man» and found a fraction of what it should. A synonym is an alternative now, the way it always was for longer words.

1.0.34

• Fixed: product titles lost every dash, curly quote and ellipsis, and some accented letters, showing question marks instead. A pattern that strips trademark marks was matching single bytes rather than characters, so it deleted the first byte of those characters and left something that was no longer readable text. Titles now keep them, and a mis-declared encoding is repaired instead of being filled with question marks.
• Fixed: products from feeds that write a size as «Shirt – XL» with a long dash appeared once per size in the block picker. The rule that recognises a size suffix could not match that dash, so the sizes never collapsed into one product.
• Fixed: the mapping editor could sit on «Loading…» forever for a large feed. It pulled the whole file into memory to read a single row; it now streams from disk like the importer does, and unpacks gzip and zip on the way.

1.0.33

• Fixed: adding or re-importing one feed could turn into an update of every feed. The import of a single feed has no background worker to wait for, so ten seconds in it looked stuck, and the recovery step started a full update in its place. It now leaves single-feed imports alone.

1.0.32

• Fixed: on password-protected sites the import restarted itself from the status poll and marked real products unavailable. The fix applies to any site whose own server cannot reach it without a password, and to every feed on it.

1.0.31

• Filtering, sorting and paging inside a search are near-instant. The first search still asks the index once; from then on a filter chip reads from what that search found, instead of searching the whole catalogue again with the filter attached. A brand filter on a 90,000-row catalogue took 7.6 seconds and now takes a few hundredths.
• Every sort order gives one answer: two products that tie on price, discount or date come back in the same order every time.
• «Back to search» and «Add to selection» return you to where you were in the results, not to the top.
• The mapping editor reads XML and JSON feeds. It used to show an empty form for any feed that is not CSV, and no error.
• Feeds are listed alphabetically in the mapping editor.
• Card images are no longer routed through Jetpack’s image CDN. Shopify and other merchant CDNs need the exact address the feed delivered, and the CDN dropped part of it, so some cards showed no image while the editor showed the product.
• A feed without a currency column is priced in the currency of the market it names (a delivery-time column per country, or the country in the shop link). Partnerize feeds priced in pounds showed euros. A default currency set in the mapping editor still wins.

1.0.30

• A search that reports 245 results now shows all 245. Where a feed ships a row per size, a search matches many more rows than it has products – sixteen rows per product in one measured case – and the plugin only ever looked at the first few hundred rows. So a search could report hundreds of results and hand you twenty, with «Load more» unable to reach past them. It now looks far enough to fill the pages it promises, and it is about twice as fast at the same time.
• Product links saved in a post could lose the ampersands out of them, leaving an address that looks fine and leads nowhere: the affiliate id and the merchant id were swallowed into one long parameter. Existing cards repair themselves as they are read, so your links point where they should again.

1.0.29

• In the product detail view, clicking one of the smaller images now shows it in the large frame. They were there to look at and did nothing.
• Choosing a size now selects that size. Picking a colour already switched the product for real – link, price and all – but a size only changed what was highlighted, so adding the product to a post linked to whichever size the search had opened. Pick 42 and the card links to 42.

1.0.28

• A card no longer sends readers to a size that has sold out. Feeds ship one row per size, and the address stored with a product carries the size along with it – so a reader following a card whose size had gone landed on exactly the size that was gone. MyFeeds now recognises the sizes of one product and links to one that can be bought. Colours stay apart: the grouping is confirmed against the product photograph, so a card showing the sand-coloured pair never links to the black one.

1.0.27

• There is one way to delete a feed again. A second one existed that dropped the feed from your settings and left every one of its products in the database – rows with an image, a price and a link into a partnership that had ended, which the product picker would still offer you. It could not actually be reached from the plugin’s screens, so nothing was broken by it; it is gone now rather than waiting to be found.
• The daily housekeeping also clears out products whose feed no longer exists, whatever removed it – a restored backup, an edit made straight in the database. Products a published post is showing are kept, as before, so your live pages never go blank.

1.0.26

• A product that is no longer available is left out of your pages instead of being shown as a grey «no longer available» card. That card told a reader nothing they could act on, and it made a good post look broken. Where a block has nothing left to show it now renders nothing at all, rather than an empty gap.
• Products your published posts are showing are no longer removed when you delete their feed. A product block stores only the id, so once the row was gone the post could not name what it lost and the editor could not show you what used to be there. Those rows are kept now, out of your pages but still there to work with.

1.0.25

• The plugin now lists MyFeeds as its author instead of a personal name, and links to myfeeds.site. Only the entry on your Plugins screen changes; nothing about how the plugin works is affected.

1.0.24

• Update All could not finish on some hosts. The importer runs the work in a background request to your own site; where that request is blocked – by hosting configuration, by a password-protected staging site – it falls back to running the import inline. That fallback referred to something that did not exist and stopped with an error the log recorded and nobody saw, so the progress bar sat at 1% until you gave up. On those hosts importing was simply impossible. Fixed.
• An import that could not read a feed now says so. A feed URL behind a login, a typo, an expired key: all of them used to end on «Update completed successfully» with a green tick and no products. The panel now names each feed it could not read and stays open until you dismiss it.
• Feeds that arrive as a .zip are unpacked for you. Several networks ship their catalogue that way, and until now the archive was handed to the CSV parser, which produced nothing and reported nothing. Files that are not feeds at all – an archive MyFeeds cannot open, a PDF, or the HTML login page a network returns when a link needs authentication – are now named in the error instead of being parsed as a spreadsheet.
• You can upload a feed file. Four networks hand publishers a file and no link, and the answer used to be «find your own hosting for it first». The dialog now offers a URL or an upload, recommends the URL, and says plainly that an uploaded file does not refresh by itself – the feeds list shows it as such. Accepted: .csv, .tsv, .psv, .ssv, .txt, .tab, .xml, .json, .jsonl, .ndjson, .gz and .zip.
• Deleting a feed now removes its products. They used to stay in the database, keep appearing in the Product Picker and keep inflating the product count on the Feeds page. Products that a published post still shows are the exception: those are kept so your pages do not go blank, with the values they last had, and they are no longer offered when you add new ones.
• The progress bar moves while an import runs. It updated once per batch of a thousand rows, so a small feed showed nothing at all between starting and finishing.
• MyFeeds now tidies up after itself. Once a day it removes options left behind by versions you no longer run, expired cached data, and its own finished background jobs once they are more than a week old. Other plugins‘ jobs are never touched.
• The feed address is checked before it is fetched. A feed URL that points at the server itself or into a private network is refused, so a mistyped or malicious address cannot be used to make your site fetch things that were never meant to face the internet.
• Advanced options: pipe-separated is now offered as a format, which is what several networks publish. Choosing a file pre-selects the matching format from its name. The gzip entry is gone because compression is unpacked before the file is read. The network list drops Amazon, which has its own connection flow, and adds FlexOffers, Sovrn and Other.

Older entries (1.0.23 and earlier) are in changelog.txt, which ships with the plugin.