Title: Missing DB field
Last modified: January 9, 2024

---

# Missing DB field

 *  [raaasmus](https://wordpress.org/support/users/raaasmus/)
 * (@raaasmus)
 * [2 years, 4 months ago](https://wordpress.org/support/topic/missing-db-field/)
 * Just trying to let you know that the latest version is missing a DB migration
   or you left some dev code in there.
 * There is no “status” field for terminals and couldn’t see in the migration but
   there are conditions for if “status” == 1 so the terminals are not printed out.
   The select dropdown is then empty.
 * [@dpdbaltics](https://wordpress.org/support/users/dpdbaltics/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  [dkvadratu](https://wordpress.org/support/users/dkvadratu/)
 * (@dkvadratu)
 * [2 years, 4 months ago](https://wordpress.org/support/topic/missing-db-field/#post-17335315)
 * Solution found. Deactivate and Activate plugin.
 *  Plugin Author [dpdbaltics](https://wordpress.org/support/users/dpdbaltics/)
 * (@dpdbaltics)
 * [2 years, 4 months ago](https://wordpress.org/support/topic/missing-db-field/#post-17343681)
 * Hey, [@raaasmus](https://wordpress.org/support/users/raaasmus/) , as [@dkvadratu](https://wordpress.org/support/users/dkvadratu/)
   is saying try deactivating and reactivating the plugin. 
   If the issue is not 
   solved after these steps, please let us know.
 *  [Eugenijus](https://wordpress.org/support/users/ugenijus/)
 * (@ugenijus)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/missing-db-field/#post-17496618)
 * This issue is not solved in version 1.2.75. Terminals dropdown is empty. It seems
   the last stable version is version 1.2.68.
 *  Plugin Author [dpdbaltics](https://wordpress.org/support/users/dpdbaltics/)
 * (@dpdbaltics)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/missing-db-field/#post-17520752)
 * Hey, [@ugenijus](https://wordpress.org/support/users/ugenijus/),
 * if terminal dropdown is still empty after 1.2.76 update please do these 2 steps.
 * **2 things to pay attention to after 1.2.76 version update:**
    1. After plugin is upgraded if there are still issues with pick-up points please
       manualy enter this URL → [https://<<your-domain>>/wp-admin/tools.php?force-dpd-tables-update=1](https://<<your-domain>>/wp-admin/tools.php?force-dpd-tables-update=1).
       After that you should see a success message and could go back to work.
 *  2. Just to ensure that DB table dpd_terminals work correctly, please RUN NOW this
       CRON EVENT after triggering the above URL → [https://prnt.sc/R_oXKRcv-DRN](https://prnt.sc/R_oXKRcv-DRN).
 *  [wmcvasily](https://wordpress.org/support/users/wmcvasily/)
 * (@wmcvasily)
 * [2 years, 1 month ago](https://wordpress.org/support/topic/missing-db-field/#post-17551457)
 * [@dpdbaltics](https://wordpress.org/support/users/dpdbaltics/)
   The plugin still
   doesn’t work. The Pickup Point is empty. I’ve tried different versions, tried
   to update forcefully. The wp_dpd_terminals table is empty. The cron job is running
   and is listed.
    -  This reply was modified 2 years, 1 month ago by [wmcvasily](https://wordpress.org/support/users/wmcvasily/).

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Missing DB field’ is closed to new replies.

 * ![](https://ps.w.org/woo-shipping-dpd-baltic/assets/icon-256x256.png?rev=2081212)
 * [DPD Baltic Shipping](https://wordpress.org/plugins/woo-shipping-dpd-baltic/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/woo-shipping-dpd-baltic/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/woo-shipping-dpd-baltic/)
 * [Active Topics](https://wordpress.org/support/plugin/woo-shipping-dpd-baltic/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/woo-shipping-dpd-baltic/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/woo-shipping-dpd-baltic/reviews/)

 * 6 replies
 * 5 participants
 * Last reply from: [wmcvasily](https://wordpress.org/support/users/wmcvasily/)
 * Last activity: [2 years, 1 month ago](https://wordpress.org/support/topic/missing-db-field/#post-17551457)
 * Status: not resolved