#7269 closed defect (bug) (worksforme)
Scheduled posts are losing their geocoding
Reported by: | AndreasMoser | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.0 |
Component: | General | Keywords: | posts scheduled |
Focuses: | Cc: |
Description
If I schedule a post I lose the geotagging informations.
I did the following checks
- Create post, with geotagging information, publish date in future
--- a new entry gets generated in the table wp_postmeta with the meta_key _geo_location
- Reopen post - geotagging infos are still there (also in the table)
- Date of publish reached
- Post is published without the geotagging infos
--- the entry in the table wp_postmeta is gone
Change History (7)
#2
@
17 years ago
Can you test by mearly adding a Custom Field and testing, rather than using a plugin (Or whatever is supplying the geocoding)
I've just tried a scheduled post with a Meta key, and its published & meta key remembered fine (For both meta keys "abc" and hidden meta keys "_abc")
#3
@
16 years ago
- Milestone 2.7 deleted
- Resolution set to worksforme
- Status changed from new to closed
Works for me too. We'll need more information. Closing pending more feedback.
#4
@
15 years ago
- Resolution worksforme deleted
- Status changed from closed to reopened
- Version changed from 2.6 to 3.0
I am experiencing this issue when I schedule a post on a 3.0 installation. After the post is published the meta key remains but the meta value is blank.
#6
@
14 years ago
- Resolution set to worksforme
- Status changed from reopened to closed
In my instance (and probably other people's as well) it was a result of a poorly written or over-applied action added on the save_post handle. Resolving it back to worksforme since that's where it was before I reopened it.
Meanwhile I updated to V2.6 but the problem is still there.