This topic is: not resolved
- This topic has 11 replies, 3 voices, and was last updated 10 years, 8 months ago by .
- You must be logged in to reply to this topic.
The Support Forum is closed. Not to worry! Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.
Premium Support
Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?
Please open a Support Ticket in your user account.
Free Support
Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.
Please open a new support topic in the WordPress support forums for Connections.
Tagged: 8.5.4
Ah well, no luck.
I updated all the zip codes using CSV import, using the entry_id field and the work address zip code. The import worked fine (gave no errors, data looks correct in DB), but the site still shows the old zip codes even though the new ones are correct in the database, and correct when you edit them one at a time in Connections.
They do still update correctly when you edit/save an individual in Connections.
The CSV has rows of data like this:
6 32611
I’m mapping the first one to entry_id, the second to work address zipcode.
Is there something I’m doing wrong? Is there perhaps another field besides zip code that must be edited to cause the caches to be refreshed (perhaps something like name in the _connections data table instead of only updating something in the connections_address table)?
BTW, we do have W3 Total Cache, but I emptied all the cache, and even turned that plugin off, with the same results.
I’m so sorry to keep bugging you with this! I thought we had it licked.
:(
Steve K.
re: Steve
The first/last name or org name are still required when doing imports, even updates. So, that said, any rows missing those fields will be skipped. I hope the have the updating feature a bit more fleshed out in the next major update to the CSV Import extension. Kinda why I do not advertise it as a feature because it is more of a tack on that incorporated.
