Easy Property Listings WordPress Real Estate Plugin › Forums › Real Estate Formats: MLS, RETS, REAXML, JUPIX, Real, custom feeds › Duplicate listings as drafts upon import using WP All Imports plugin
Tagged: WP All Import
- This topic has 10 replies, 3 voices, and was last updated 8 years, 9 months ago by Merv Barrett.
These forums are closed to new replies / tickets. Please open a support ticket from our new Support page.
-
AuthorPosts
-
October 9, 2014 at 6:40 am #2347Trimson PartnersParticipant
Good morning Merv,
We’re witnessing some strange behaviour when re-running the imports. We’re finding that a whole lot of our listings, rather than being updated, are being duplicated, with the old listing being made into a draft.
Our automatic record matching is always set to:
{uniqueID[1]}{./@modTime}We have got the import set to ‘set to draft’ rather than deletion, but surely that shouldn’t be happening to listings that already exist – they should just be updated?
Have you heard of this happening to others?
Cheers,
GraceOctober 9, 2014 at 10:01 am #2349Merv BarrettKeymasterYour answer lies here {uniqueID[1]}{./@modTime}
Every single entry is unique with the above two fields being used and you will end up with duplicates becasue the {./@modTime} is unique for every single entry.
If you want to perform updates then you need to remove the {./@modTime} from the record matching and then you can update the entries without producting duplicates.
October 9, 2014 at 10:55 am #2353Trimson PartnersParticipantHoly moly! No wonder it was stuffing up.
For some reason I thought you told me to have that set as the record matching?
Or does it have to be different when adding or updating? That would be a bit annoying…?
October 9, 2014 at 10:57 am #2354Trimson PartnersParticipantHmm, it doesn’t let me edit it though. Do I have to set it to ‘manual’?
October 9, 2014 at 11:15 am #2356Merv BarrettKeymasterYou will have to delete and re-start. The real question is why are you doing it this way instead of the recommended way?
October 9, 2014 at 11:19 am #2357Merv BarrettKeymasterThe recommended was is setup to minimise server load and be able to import current listings more frequently.
This way you never set it to update the listings, just delete and replace with new data becasue we never know what has been updated. Could be text, image order, price or combination of all.
The images are the performance killer. You can update everything but you will have to start again without the modtime in the record matching field. Again the question is why?
October 9, 2014 at 11:23 am #2358Merv BarrettKeymasterAnd if you attempt to use the update features with the sold list, your server will not survive 🙁
October 9, 2014 at 11:43 am #2359Trimson PartnersParticipantSo you’re saying it’s less taxing on the server to completely delete and re-upload all data, images etc, of all the listings, rather than to just check what needs updating and update that instead?
Why do I want to update, rather than replace? Well, for one thing, wouldn’t a replacement reset the post published date? My client wants to be able to order them manually. At the moment I have the import script set to ignore the post date (i.e. don’t update it), so that the ordering of the listings remains the same, even after an update.
But the main reason at the moment I want to just update, is because every time I do a re-run of the import it wipes my manually set property_authority and property_auction. And these are too important to lose. Ditto with the ‘featured’ custom field. I’ve set the update to not update any of these fields.
I’m not doing anything with the sold properties at the moment. They’re just being set to draft, then I delete.
Perhaps in future I will have it so that it works the way you suggest, but not until the the auction elements work correctly.
Cheers,
GraceOctober 9, 2014 at 12:09 pm #2360Merv BarrettKeymasterSo you’re saying it’s less taxing on the server to completely delete and re-upload all data, images etc, of all the listings, rather than to just check what needs updating and update that instead?
— Night and day difference, images are the killer.Well, for one thing, wouldn’t a replacement reset the post published date?
— Yes it does.
— This setup is more important for sold/leased as they don’t change after they become sold. (they can but from the sites we’ve setup this data doesn’t change)— Nothing stopping you from configuring the current listings to update, its just that you cant change the current import script, you need to delete and re-configure your import to behave differently. You’ll have to try different options to see what works best. The normal solution is optomised for server load and to set and forget.
My client wants to be able to order them manually.
— If they want fine control over the website, then they can manually enter listings in the site and skip importing. or work with your own script configuration.But the main reason at the moment I want to just update, is because every time I do a re-run of the import it wipes my manually set property_authority and property_auction. And these are too important to lose.
— Your setup is incorrect for this. All you should be doing is adding the auction date to property_auction. Then use get_custom_meta in your custom template and display the date.
— Your update sulution will cause you 10x more issues. Correct the way you are handling the auction field and then you will not have to update.— For the order use another custom post type and get the client to enter in the uniqueid of they listings and the order they want it in. Then use a custom loop to output the listings based on the new order.
Ditto with the ‘featured’ custom field. I’ve set the update to not update any of these fields.
— property_featured is not included in the REAXML format (it is, but it meants your client is adding a $3000 featured listing to RealEstate.com.au) so that cannot be relied on to set a featured listing.They’re just being set to draft, then I delete.
— Why?July 23, 2015 at 1:16 pm #14392Quader SyedSpectatorI’m confused about {uniqueID[1]}{./@modTime}
In one place it’s recommended to change to just {uniqueID[1]} and in other places to use the original.
http://easypropertylistings.com.au/support/search/%7BuniqueID%5B1%5D%7D/
Also is there a way to tell Allimport that the modtime hasn’t changed since last time so no need to look for changes in that part of the file? We’re testing and still laking 5 mins plus to run incremental updates even when there’s no change in modTime
July 24, 2015 at 7:03 pm #14553Merv BarrettKeymasterUnfortunately there is no way to compare mod-time and why we recommend using both fields {uniqueID[1]}{./@modTime} as a unique identifier. Then it only imports updated records and you can set WP All Import to not update and delete missing records.
Until we complete Listing Sync this is the best was to configure WP All Import Pro
-
AuthorPosts
These forums are closed to new replies / tickets. Please open a support ticket from our new Support page.
- The forum ‘Real Estate Formats: MLS, RETS, REAXML, JUPIX, Real, custom feeds’ is closed to new topics and replies.